Skip to content

Project versification needs to be read from the parent project for non-Standard Paratext projectsΒ #929

@mmartin9684-sil

Description

@mmartin9684-sil

For non-Standard Paratext projects, the project versification is not typically specified in the project's Settings.xml file. Instead, the versification needs to be read from the parent project's Settings.xml file. Since the versification is not found in the project's Settings.xml file for non-Standard projects, silnlp current defaults to assigning English (4) versification to the project. If the parent project uses a different versification (e.g., Original), the extract_corpora script may create an incorrect verse extract file; the behavior of other tools may also be negatively affected by this.

Paratext project types that do not typically have their own project versification include: Auxilliary; BackTranslation; ConsultantNotes; Daughter; Front Translation/FrontTranslation; StudyBible; Transliteration; TransliterationWithEncoder.

  • There may be other project types as well.
  • Some projects do not have a project type specified in their Settings.xml file.

Our current method of storing multiple datestamp'ed versions of a parent project in the Paratext > projects folder makes it more challenging to match the parent project name from the Settings.xml file to the parent project folder.

Another difficulty is that we do not typically download and onboard the parent project when working with these non-Standard projects. This workflow will need to be updated so that the parent project's versification setting is available.

A partial refresh of the projects and project extracts for the affected non-Standard projects may be needed.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingonboardingServal onboardingpipeline 2: extractIssue related to extracting parallel corpora

Type

Projects

Status

πŸ— In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions