A standardized browser-based spreadsheet editor and validator that can be run offline and locally, and which includes templates for SARS-CoV-2 and Monkeypox sampling data. This project, created by the Centre for Infectious Disease Genomics and One Health (CIDGOH), at Simon Fraser University, is now an open-source collaboration with contributions from the National Microbiome Data Collaborative (NMDC), the LinkML development team, and others.
MIT License
91
stars
25
forks
source link
Remove "draft CanCOGeN" label from ntologized terms in EBI OLS #257
Right now all of the ontologized fields pertaining to COVID in GenEpiO show up in EBI OLS with the label "draft CanCOGeN:XXX".
That is confusing for users as the ontologized fields are meant to be universal and only implemented in the PHA4GE spec right now. So users who look up the fields in OLS will see the CanCOGeN label. Can we make the generic fields NOT spec-specific, keeping the current IDs? (So the current IDs become generic ontology terms that can be used across specs without a particular label)?
Spec-specific IDs could be developed in the next iteration.
Currently, the CanCOGeN label makes the fields hard to find and confusing for international users who have been sending us issues that we need to address.
This will be updated in next OLS refresh. Note that Ontobee is having some problems loading some ontologies; it needs a complete reload of GenEpiO at moment. This has been reported to Ontobee.
ddooley
commented
2 years ago
Right now all of the ontologized fields pertaining to COVID in GenEpiO show up in EBI OLS with the label "draft CanCOGeN:XXX".
That is confusing for users as the ontologized fields are meant to be universal and only implemented in the PHA4GE spec right now. So users who look up the fields in OLS will see the CanCOGeN label. Can we make the generic fields NOT spec-specific, keeping the current IDs? (So the current IDs become generic ontology terms that can be used across specs without a particular label)?
Spec-specific IDs could be developed in the next iteration.
Currently, the CanCOGeN label makes the fields hard to find and confusing for international users who have been sending us issues that we need to address.