update users' ORCID record on dataset publication

[pameyer]

For users with ORCID, update their ORCID record with datasets when they're published through Dataverse (with their permission).

More details to follow.

[michbarsinai]

see requirement document here:
https://docs.google.com/document/d/12z7LsIGUfnof57bOYctwx8pOTSbWvzDluY1gvF5xusM/edit?usp=sharing

[pdurbin]

I guess this could be implemented outside of Dataverse with a PostPublishDataset workflow: https://guides.dataverse.org/en/5.12/developers/workflows.html

Also related:

• ORCID integration in Dataverse #4236

[qqmyers]

DataCite and CrossRef appear to update your ORCID record directly if you configure it.

[pdurbin]

DataCite and CrossRef appear to update your ORCID record directly if you configure it.

This "search and link" feature on the ORCID side is very cool. I haven't played with it myself but I think this is the feature that @j-n-c identified as problematic in his post at https://groups.google.com/g/dataverse-community/c/hFZRMXJ_-CE/m/J_TnqhkuAAAJ

Here's what he said, "One of our investigators has brought to our attention that having DOIs both on datasets and files will generate separate entries on its ORCID dashboard and that because of this the dashboard gets cluttered with (possibly) superfluous entries. From the research we've made, most Dataverse installations are getting DOIs for both dataverses and files."

We talked about it on a recent community call: https://docs.google.com/document/d/1H8XTmrQd6TIILCZ--YMrZGEicmcgJGpwc5c0vC9JTJw/edit?usp=sharing

And then he created this doc that explains the cluttered records on the ORCID side: https://docs.google.com/document/d/1P1txmW0MUWm35AQPTDoh5Kl1X0m7HOZvXwXjX5wZAps/edit?usp=sharing

And he left this comment on a related issue: #5086 (comment)

All this is to say let's try to avoid the clutter. 😄