Extending JBA PEs with UBERON terms #394
Open
Conversation
This file contains hidden or 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
UlrikeS91
added
the
SANDS
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.
I've added this (indirectly) in the SANDS article (one example presents this as available data in the instances) and would like to have the data behind it publicly available before submitting the paper.
Therefore, I extracted the existing list of PEs and assigned suitable UBERON terms. These terms were assigned purely on sematic relation (i.e., PE name == UBERO name or one of its exact synonyms). I took the liberty to add a few more terms to JBA PEs that were abbreviated (e.g., JBA_STN was assigned "UBERONParcellation/subthalamicNucleus").
@lzehl, feel free to assign somebody else to review this PR (e.g., somebody involved in developing the atlas)
Note: I made a PR for one missing UBERON term (#393), but I already linked its future at_id here.