PTH005: Toolkit Modifications for API Endpoints Integration

[tenzin3]

Description

We are developing endpoints to automate the conversion of our data into the OpenPecha Foundation (OPF) format and subsequently upload it to the pecha.org website. Therefore, modifications to the Toolkit are necessary to meet the requirements of these endpoints.

Expected Input from the API for parsing

• input text in .docx format.
• metadata as Dict.
• type of text i.e Root/Translation

Expected Output

For this sprint, the endpoints will handle both the root text and the translation text, along with their metadata. The Toolkit should be capable of covert those to OPF and able to upload to pecha.org.

Implementation Steps

Fixes:

• Avoid updating the Root OPF when publishing a translation OPF
• take metadata input as a dictionary, not XLSX.
• Return Pecha only from TranslationParser.
• Make the serializer and parser static

To-Do:

• Take translation's root info from catalog with metadata
• Update the published pecha metadata to catalog.

Reviewer

• @gdetari

[tenzin3]

Modifications needed for Translation Parser

• Take metadata as input
• Return Pecha instance only
• Rather than taking source_path as class constructor input, extract this info from the catalog.

[tenzin3]

Fixes:
Modify Parser/ get root layer file name from Catalog
Modify Serializer/Get Root pecha id from Catalog and get content for translation Pecha