-
Notifications
You must be signed in to change notification settings - Fork 2
Reconcile the assay ontology vocabulary with existing vocabularies. #511
Copy link
Copy link
Labels
app: backendTask implementation touches the backendTask implementation touches the backendsprint: carried overTask was carried over from a previous sprintTask was carried over from a previous sprinttype: enhancementEnhancement to an existing featureEnhancement to an existing featureworkstream: clinicalTask relates to clinical featuresTask relates to clinical featuresworkstream: pillarTask relates to pillar projectTask relates to pillar project
Metadata
Metadata
Assignees
Labels
app: backendTask implementation touches the backendTask implementation touches the backendsprint: carried overTask was carried over from a previous sprintTask was carried over from a previous sprinttype: enhancementEnhancement to an existing featureEnhancement to an existing featureworkstream: clinicalTask relates to clinical featuresTask relates to clinical featuresworkstream: pillarTask relates to pillar projectTask relates to pillar project
Type
Fields
Give feedbackNo fields configured for Task.
Version 2 of the AVE-DCD minimum information standard for MAVEs should be used as a guide to vocabulary selection. In addition, the IGVF Coding Variants pillar project data curation team's workbook already uses standard vocabularies for some terms.
In particular, Gene Ontology values or similar should be used for the "phenotypic assay mechanism" attribute. A validator that requires GO codes for this attribute should then be un-commented (in lib/validation/keywords.py), together with its unit tests (in tests/validation/test_keywords.py and tests/routers/test_experiments.py).