search

EBISPOT / DUO

Ontology for consent codes and data use requirements
Other
64 stars 15 forks source link

Would it be possible to include version numbers as part of the DUO accession/code? #89

Open ega-agent opened 4 years ago

ega-agent commented 4 years ago

Greetings DUO team,

Because DUOs are a living standard versioning of the codes is a necessity. The current versioning used for DUO codes uses a date which can be difficult for data submitters to fathom and has the added disadvantage of being challenging to roll into submission platforms. I was wondering if it was worth exploring the merits of a different versioning strategy, such as that employed by GenBank where the version is included as part of the accession (i.e. https://www.ncbi.nlm.nih.gov/nuccore/AJ277892.1 and https://www.ncbi.nlm.nih.gov/nuccore/AJ277892.2 which allow for the retrieval and comparison of versions 1 & 2 of part of the human Titin gene sequence respectively).

Many thanks for your time in considering this feature request

mcourtot commented 4 years ago

Hello Matthieu @ega-agent

We have opened an issue to better formalise he deprecation policy under the OBO Foundry, which principles we follow. In short, we don't version terms because we don't change the meaning of the terms - or if we do they should be deprecated. That being said it may be useful to think about ways to retrieve specific terms versions in addition to the whole file and I have added this to the OBO ticket.