Built-in support for ORCIDIO #1312
Description
I believe that by now, several OBO ontologies have adopted the idea of importing the OWL version of the ORCID database (aka ORCIDIO) to include some additional data about contributors in the form of OWL individuals.
The idea is popular enough that there is even a OBOOK tutorial about how to do it.
While it is not very complicated, it is still (1) something that requires a tutorial, and (2) something that may easily go wrong if the user does not completely understand how the ODK works. For example, the proposed tutorial would not work as expected if the ontology also happens to be using the “base merging” feature (as explained here).
Also, there are several ways of achieving the same goal of importing ORCID:
- as a ODK import module (as in the aforementioned tutorial);
- as a ODK component;
- as a completely custom-made file, entirely managed in
$(ONT).Makefile.
This may not be a critical thing, but I think this is the kind of small things that the ODK is supposed to standardize across the field, instead of letting each ontology come up with its own way of doing it.
So I hereby propose supporting the automatic import of ORCIDIO as a built-in feature of the ODK, that users could enable simply by toggling an option in their ODK configuration file, without having to worry about how it’s done under the hood.