Replace CARO anatomical entity with Uberon #302
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@dustine32 If you want to coordinate this with @vanaukenk and roll this out (i.e. dev first then prod), that's good by me. Otherwise, this would wait until when I get back. |
|
@vanaukenk I think we should go ahead and merge this. Any reason not to? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are replacing CARO with Uberon terms globally (see obophenotype/uberon#2349 and oborel/obo-relations#695 and geneontology/go-ontology#25485).
I have a PR in Minerva to return Uberon 'anatomical entity' as a root type (geneontology/minerva#515). Once that is deployed, Noctua should switch over to using the Uberon term rather than the CARO term (geneontology/noctua#838). We should merge this around the same time.