-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Develop enums for Study, Biospecimen, Data File, Assay and add ontology terms #108
Comments
Application ontology will also be very useful for the new Study/Datatset fields. Please see the yellow highlighted cells in this sheet. |
Related to #159 |
Matt and I have discussed two options for including enums from ontology terms, (1) an explicit enumeration of terms in enum definitions or (2) referencing subsets of terms defined in an external Application Ontology. Currently the decision is for (1) to define a fixed set of terms in the schema in advance because the LinkML docs says "this works well if the vocabulary is known in advance and it is a relatively small number of terms" [1]. A small example for sample type is in this branch The notes from our discussion are in the INCLUDE gDrive here. Two open questions are:
|
Closing since we now have separate tickets for this, plus the slots might be changing |
Add/review/finalize enums/ontology terms for the following Study/Dataset fields (see notes here):
Pierrette's comments:
For Biospecimen/Assay/DataFile, we have discussed EDAM, OBI, etc. Sample Type, File Type, etc.
Currently, we have a controlled vocabulary, but using a pre-existing ontology might allow us to have more relationships/hierarchies, e.g., between Data Categories & Types. Maybe we could annotate Experimental Platform and then have a search widget for users to search parent categories?
The text was updated successfully, but these errors were encountered: