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.

Sign up for GitHub

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

Jump to bottom

Ensure correct import of NCBITaxon import after changes to top node #1071

Open
allenbaron opened this issue Aug 22, 2022 · 0 comments
Open

Ensure correct import of NCBITaxon import after changes to top node #1071

allenbaron opened this issue Aug 22, 2022 · 0 comments
Assignees
@allenbaron
Labels
data engineering Indicates code development to improve data/build imports Applies to ontologies imported into the Human Disease Ontology. Revisit - Q1 2025 For all issues that are not actionable and need to be revisited; timeframe updated on rolling basis

Comments

@allenbaron
Copy link
Collaborator

allenbaron commented Aug 22, 2022 •
edited
Loading

NCBITaxon's top node is being replaced.

When this import is to be updated next, we need to evaluate changes needed to ensure the import is correct and to determine how this may affect the top node for NCBITaxon in DO, which is currently NCBITaxon:1 (label: 'ncbitaxon').
@allenbaron allenbaron added the imports Applies to ontologies imported into the Human Disease Ontology. label Aug 22, 2022
@allenbaron allenbaron self-assigned this Aug 22, 2022
@lschriml lschriml added the data engineering Indicates code development to improve data/build label Aug 25, 2022
@allenbaron allenbaron added the Revisit - Q1 2025 For all issues that are not actionable and need to be revisited; timeframe updated on rolling basis label May 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@allenbaron allenbaron

Labels
data engineering Indicates code development to improve data/build imports Applies to ontologies imported into the Human Disease Ontology. Revisit - Q1 2025 For all issues that are not actionable and need to be revisited; timeframe updated on rolling basis
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lschriml @allenbaron