We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Low
related to https://git.yale.edu/LUX/unit-data/issues/221 and https://git.yale.edu/LUX/unit-data/issues/220
Units may start referencing AAT IDs as Periods, specifically in the Production > occurs_during block.
Pipeline will probably treat them as Concepts, as everything from AAT right now == Concept.
Research how we can programmatically determine if they are a Period instead, so we can trigger the creation of the correct Class of record.
Investigate methods AAT mapper can determine if a referenced ID is a Period as opposed to a Concept.
tbd once research is complete
The text was updated successfully, but these errors were encountered:
kkdavis14
No branches or pull requests
Priority Level
Low
Background
related to https://git.yale.edu/LUX/unit-data/issues/221 and https://git.yale.edu/LUX/unit-data/issues/220
Units may start referencing AAT IDs as Periods, specifically in the Production > occurs_during block.
Pipeline will probably treat them as Concepts, as everything from AAT right now == Concept.
Research how we can programmatically determine if they are a Period instead, so we can trigger the creation of the correct Class of record.
Description
Investigate methods AAT mapper can determine if a referenced ID is a Period as opposed to a Concept.
Changes Required
tbd once research is complete
Tasks
The text was updated successfully, but these errors were encountered: