Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project-specific KBT's - cross-referencing another project's project-specific KBT list is not correctly supported #661

Open
mmartin9684-sil opened this issue Feb 14, 2025 · 0 comments
Assignees
Labels
bug Something isn't working pipeline 2: extract Issue related to extracting parallel corpora

Comments

@mmartin9684-sil
Copy link
Collaborator

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.

@mmartin9684-sil mmartin9684-sil added bug Something isn't working pipeline 2: extract Issue related to extracting parallel corpora labels Feb 14, 2025
@ddaspit ddaspit moved this from 🆕 New to 🔖 Ready in SIL-NLP Research Feb 17, 2025
@ddaspit ddaspit assigned TaperChipmunk32 and unassigned ddaspit Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working pipeline 2: extract Issue related to extracting parallel corpora
Projects
Status: 🔖 Ready
Development

No branches or pull requests

3 participants