Project-specific KBT's - cross-referencing another project's project-specific KBT list is not correctly supported
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39
- Forks
- 7
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 5
Description
A project using a project-specific KBT list can be configured in Paratext to refer to another project's project-specific KBT list. For instance, the bPou project is configured to use the aArp project's project specific KBT list, as shown in this line from the bPou project's Settings.xml:
<BiblicalTermsListSetting>Project:aArp:ProjectBiblicalTerms.xml</BiblicalTermsListSetting>
When the bPou project is extracted, a metadata file (bPou-metadata.txt) and a renderings file (wra-bPou-Project-renderings.txt) are created, but a vref file (bPou-vrefs.txt) file is not created.
Subsequently, when the bPou project is used in a corpus_pair with the key term glosses enabled, no key terms are included in the training data.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing extraction for the BiblicalTermsListSetting value in Settings.xml, especially the Project:aArp:ProjectBiblicalTerms.xml cross-reference. Compare the generation of bPou-metadata.txt and wra-bPou-Project-renderings.txt with the missing bPou-vrefs.txt, then check the corpus_pair path with key term glosses enabled. Done means the referenced project's key terms are included in the training data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100