You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem with that is that we never know which version of NCBI we are actually aligning with. @jamesaoverton told me that only some, not all of the "latest" versions are being properly archived and versioned.
I would like to suggest to obtain the latest archived version of NCBITaxon rather than the latest snapshot, thereby having a clear provenance trail to which NCBI taxon version was used. As a second benefit, people that do not use the owl or OBO versions can still be in sync with the latest release of the ontology when they obtain the corresponding archived ncbitaxon from the source!
The text was updated successfully, but these errors were encountered:
Right now, NCBI taxon depends on the latest working release in
https://ftp.ncbi.nih.gov/pub/taxonomy/.
The problem with that is that we never know which version of NCBI we are actually aligning with. @jamesaoverton told me that only some, not all of the "latest" versions are being properly archived and versioned.
I would like to suggest to obtain the latest archived version of NCBITaxon rather than the latest snapshot, thereby having a clear provenance trail to which NCBI taxon version was used. As a second benefit, people that do not use the owl or OBO versions can still be in sync with the latest release of the ontology when they obtain the corresponding archived ncbitaxon from the source!
The text was updated successfully, but these errors were encountered: