Incorrect Author Name Order from ORCID Integration
FREDRIK SAHLSTRÖM
At DataverseNO, we have recently enabled integration with ORCID in the metadata field “Author.” In some cases, names do not appear in the correct SURNAME, FIRST NAME order because they have been entered incorrectly in the ORCID profile.
If the issue is corrected in the ORCID profile, the name is displayed properly in the “Author” metadata field. However, it still appears in the incorrect order in the dataset citation generated by the repository.
An example of a dataset with this issue is: https://doi.org/10.18710/MRTNPI
Does anyone know if and how this can be resolved?
Thank you very much in advance.
Kind regards,
Fredrik Sahlström
DataverseNO admin team
James Myers
Fredrik,
There are two places external vocabulary scripts can store old values like this.
When configured as on the author field, where there is a separate name field, the old value is still in the hidden author name field. You can update that by changing the author to someone else (then save) and then editing it back to the correct author via their ORCID (and save again, and use Update-Current-Version as a superuser to republish and update the metadata exports and DataCite metadata without creating a new version).
The value originally retrieved from ORCID (or other external vocabulary source service) is also stored in the ExternalVocabularyValue table. This value is more important when a script is used on a single field like depositor where there is no separate name field. Removing the relevant value can be done via a database query: DELETE FROM externalvocabularyvalue where uri=’<the ORCID in URL form, e.g. https://orcid.org/0000-0002-8349-7288>’; . This will cause Dataverse to retrieve the value again the next time it is needed. (Nominally one could edit the retrieved value in the table instead of deleting). Dataverse doesn’t immediately rerun exports or update metadata at DataCite so you either need to republish (Update-Current-Version as a superuser) or run the reExportDataset and modifyRegistrationMetadata API calls for the dataset as when resetting the authorName field above.
This is definitely something where an API call to do an update could simplify things – feel free add an issue in the Dataverse repository if you (or anyone) want to prioritize this. (FWIW – to me this is the kind of thing that makes new features start out as “experimental” – things work, but we don’t have all the functionality in place to make it easy to manage.)
Hope that helps. If you get stuck, let me know.
-- Jim
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
dataverse-commu...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/dataverse-community/f3cf9935-3c04-4620-82d3-e90075b7c7f8n%40googlegroups.com.