dataverse-external-vocab-support

Scripts and material related to using external vocabulary services with Dataverse

View the Project on GitHub

Person or Org support for Dataverse

This directory contains configurations that allow support lookup of people (via ORCID), or organizations (via ROR), or both (with user selecting “Person” or “Organization” when adding an entry). The configurations support multiple fields. The choice of ORCID, ROR, or both is made by setting the protocol (orcid, ror, orcid-or-ror) in the configuration JSON. Any of these choices should work for any of the fields for which a configuration is supplied.

Dataverse Compatibility note:

Use of the person-or-org.js script and the configurations in this directory require Dataverse >= 6.11.

Scripts Compatibility note:

The person-or-org.js script is designed as a replacement for the person.js and ror.js scripts. Using either of them in other fields will be less efficient (multiple scripts loading and running) and could cause errors or unexpected behavior.

Configuration JSON files:

How to install:

Minimal:

Testing vs. Production

Testing:

Production:

Dataverse Author Field

This config manages the author field (the name, idType, Identifier, and affiliation child fields), providing ORCID and or ROR lookup in the author name field and ROR for the affiliation.

This config requires the changes that were added to Dataverse in [PR #12331[(https://github.com/IQSS/dataverse/pull/12331) as part of v6.11.

Grant Number Agency Field

This config supports ORCID or ROR lookup in the grant number agency field (“Funding Agency” in the Dataverse UI).

Depositor Field

This config supports ORCID lookup in the depositor field. If you wish to use ROR instead, or both ORCID and ROR, change the “protocol” in the JSON config file.

Interesting Features