ROR v2 API support #46
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the main ror.js script and the configurations applying it to the author affiliation field and grantNumberAgency field to use the ROR v2 API (needed prior to ~12/31/25).
The PR doesn't update the affiliation.js script - an earlier example with different UI, but does switch it to explicitly use the ROR v1 API which is needed to make it work until 12/31/25.
The changes in the API were relatively minor for our purposes - the name and acronym fields are replaced with a single names array that has entries of type acronym and ror_display/label that can be used as replacements. The new API does allow labels in multiple languages - it's not clear how many entries have that populated, so I did not try to adapt the UI to use internationalized labels in this PR. The retrieval filtering will pick up all such values for use in the metadata exports though (as it gets the whole /names array).
I'm testing this at QDR, but if anyone else would like to try it now and review the PR, please do. Otherwise I'll merge this at some later date.
Note that this PR requires #11782 which is being QA'd for inclusion in Dataverse 6.8. To use this with earlier versions of Dataverse, the "retrieval-filtering" entry should be emptied/removed.
In Dataverse 6.8, using the "termName" with "params":["/names"] will result in the list of acronyms and names (possibly in different languages) for the organization to be added to exports such as the JSON and OAI_ORE exports. However, the organization name will not be sent to DataCite/appear in the DataCite XML export.
For Dataverse 6.9, additional options for retrieval-filtering are being added.
With either of these, the organization name will be sent to DataCite and appear in the DataCite XML export, and the JSON/OAI_ORE exports will include just this single name rather than the array of available names.
Closes: #41