Required Research Organization Registry Changes

[James Myers]

FYI: If you are using Dataverse's "External Vocabulary Mechanism" to allow author affiliations to be looked up in the ROR registry, a change at ROR broke things as of July 31. You'll need to update your script and :CVocConf setting to make it work. The change is minor - the addition of a /v1 to a URL in the script at the setting.

The change in the script is shown at https://github.com/gdcc/dataverse-external-vocab-support/blob/34d44a24ad080c0b991931c92319658c871ee719/scripts/ror.js#L4 and is live from github.io.

The change in the setting is show in the example: https://github.com/gdcc/dataverse-external-vocab-support/blob/6ca2c6dd174168968b7ee370a80f7222ef022e78/examples/config/authorsOrcidAndRor.json#L7

I apologize for not getting the word out sooner - I've been unexpectedly away.

-- Jim

[James Myers]

FYI – It looks like several installations did not make this required change (see original email below) and are now seeing failures when trying to publish datasets (due to a combination of bad values captured from the ROR v2 API and a bug (#11782) in the recent DataCite metadata/export generation code (Dataverse >v6.3) that fails when trying to read it. More details are in #11941.

 

The fix is to make the changes to the ROR configuration and script listed below and to remove the bad values from the externalvocabularyvalue table. Doing a truncate  externalvocabularyvalue; in postgres will work or you can remove just ROR values or only the problematic ones (the table is a cache that is regenerated as needed).

 

Please note that ROR will be dropping support for the v1 API at the end of the year and an additional update will be needed at that time to code that uses v2. (More details in a future email.)

 

-- Jim