Pretranslations formatted into Paratext project

johnml1135 commented 1 year ago

Especially for more stand-alone use of the tool, it would be helpful for Serval to make a Paratext project combined from the input data and the pretranslations. A potential solution could be:

A new endpoint called /translation/engines/{id}/corpora/{corpusId}/paratext-pretranslations
Added to POST /translation/engines/{id}/builds, the textId field acts as a full Scripture filter that follows all the conventions, including filtering by chapter (filter by chapter can be broken off into a new issue if needed if it is not already implemented)
Documentation in swagger to match

johnml1135 commented 1 year ago

@ddaspit what do you think?

johnml1135 commented 1 year ago

As for filtering language, should we implement such instructions as:

NT,-MAT
NT,-MAT11-20
OT,MAT,MRK1-10
OT,NT
[All books in English OT/NT]
[All books per versification?]

Enkidu93 commented 11 months ago

Is this a priority, @johnml1135? @ddaspit, what did you think? I just noticed that this issue seemed a bit stale.

ddaspit commented 11 months ago

We don't have a specific requirement for this right now, so we can leave it on the backlog.

johnml1135 commented 9 months ago

Duplicate of https://github.com/sillsdev/serval/issues/242

sillsdev / serval

Pretranslations formatted into Paratext project #147