Add SSSOM sets for mappings with the Alliance’s ontologies and vocabularies #263
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
Add a SSSOM section to the ODK configuration file and re-generate the Makefile.
Add initial mappings to some of the ontologies and "vocabularies" used at the Alliance. For now, this covers only the terms needed for migrating the scRNAseq data. The mappings to the "vocabularies" are kept in a separate set for convenience, since they are "literal" mappings (vocabulary terms at the Alliance are not proper semantic entities and do not have any kind of public identifier).
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.
This PR adds to FBcv two SSSOM mapping sets:
The second set only contains “literal mappings“, since “Vocabularies” at the Alliance are mere flat lists of terms, and “Vocabulary Terms” do not have any kind of identifier we can actually map to.
Upon release, those two sets are merged into a single
fbcv.sssom.tsvset, which will be published along with other release artefacts.Importantly, for now those mapping sets only cover the subset of FBcv terms that are needed for the annotation of scRNAseq data, since this kind of data requires the use of Alliance-specific terms rather than FBcv terms (despite the fact that FBcv itself is available at the Alliance). They may of course be extended later on as we will migrate more datatypes over to the Alliance.