-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update users' ORCID record on dataset publication #3490
Comments
see requirement document here: |
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: |
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. 😄 |
2024/09/09: Keep open, there are other related issues. |
For users with ORCID, update their ORCID record with datasets when they're published through Dataverse (with their permission).
More details to follow.
The text was updated successfully, but these errors were encountered: