Mapping of VIVO work information into the ORCID API work record

[chenejac]

Is your feature request related to a problem? Please describe.
This is preparation and precondition for implementation of pushing works data from VIVO into ORCID

Describe the solution you'd like
It might be a spreadsheet document describing crosswalk between the VIVO ontology and ORCID API work record

[chenejac]

@tawahle prepared draft mapping.

Some open questions for a discussion:

• How do the IDs need to be provided to ORCID for inclusion? As simple strings, or is it more complex? Are there guidelines on how to provide a DOI for example, or is there a sanitizing process on their end?
• We found the blog post https://info.orcid.org/ufaqs/does-orcid-support-schema-org-linked-open-data-and-json-ld/. We would be really interested in using and reusing the metioned. We are able to curl data in different forms, but we could not find any data schema or a list of properties that is being used in the RDF or n-triples serialization. It would be good to know for a potential reuse.
• Regarding the list of IDs that ORCID allows we would like to learn the domain of the IDs. That means, if a certain ID is for projects, for organizations, for publications, for persons etc.

[hauschke]

The current draft of the mapping was discussed in a meeting yesterday. Meeting notes: https://wiki.lyrasis.org/display/VIVO/2025-09-11+Meeting+Notes

[tawahle]

Added JSON notation to the mapping.