Closed Bento007 closed 6 months ago
I'm not sure that I fully understand the motivation.
There's never been a schema reference to the CLI which processed the "pinned" versions of ontology releases.
From my perspective, the schema defines requirements for COG similar to the requirements on the CLI. For example - chanzuckerberg/cellxgene-ontology-guide#80
Perhaps there should be a COG reference in the README.md in the single-cell-curation repo?
I'm not sure that I fully understand the motivation.
There's never been a schema reference to the CLI which processed the "pinned" versions of ontology releases.
From my perspective, the schema defines requirements for COG similar to the requirements on the CLI. For example - chanzuckerberg/cellxgene-ontology-guide#80
Perhaps there should be a COG reference in the README.md in the single-cell-curation repo?
I see, you want the schema to be updated first and everything else follow. We can close this.
As part of the migration process it should be documented that COG needs to be updated.
As part of the migration process it should be documented that COG needs to be updated.
Nit - but migration occurs after the CLI is updated. COG will be updated when the schema/CLI are updated - prior to migration.
Motivation
The schema.md should be the source of truth for what is in the schema. Now that cellxgene-ontology-guide is used to track the ontology version used, it should be mentioned where it can be found and that it is used.
Definition of Done
Within the Required Ontologies section mention the locked version are in cellxgene-ontology-guide