Open pbuttigieg opened 7 years ago
Great comment and request.
About the first one: yes. Ontology access for edits is tied to the login. We uploaded ENVO last year with this old version to populate the repo in the beginning (and hardly any metadata). But this is really a community task so users create their own login and use it for changes. Here is what I propose: I'll go and delete the current ENVO so there won't be a conflict. After that you can create a new version with the appropriate metadata.
Obviously, your second suggestion is much better. We'll see how this could incorporated into the new NCBO VA.
Thanks @linepouchard ! I've added the latest version of ENVO using the import via link option. This said that it will check every day for updates, which may actually keep things current. However, this would mean that my version tag will be obsolete the next time we make a release.
Tracking URL: http://ec2-52-23-64-194.compute-1.amazonaws.com/ontologies/ENVO
Is there a way I can update the info for ENVO?
It would be best if authoritative data is auto-harvested from this page: http://www.obofoundry.org/ontology/envo.html
OBO releases all such data for all its ontologies in YAML, JSON-LD, and RDF/Turtle. Here are the exports for all ontologies in JSON-LD
Thanks!