Skip to content
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

Open
pameyer opened this issue Nov 23, 2016 · 5 comments
Open

update users' ORCID record on dataset publication #3490

pameyer opened this issue Nov 23, 2016 · 5 comments

Comments

@pameyer
Copy link
Contributor

pameyer commented Nov 23, 2016

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

More details to follow.

@pameyer pameyer added the SBGrid label Nov 23, 2016
@pdurbin pdurbin changed the title update users's ORCID record on dataset publication update users' ORCID record on dataset publication Nov 23, 2016
@michbarsinai
Copy link
Member

@pdurbin
Copy link
Member

pdurbin commented Oct 8, 2022

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:

@qqmyers
Copy link
Member

qqmyers commented Oct 8, 2022

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

@pdurbin
Copy link
Member

pdurbin commented Oct 11, 2022

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. 😄

@pdurbin pdurbin added the Type: Feature a feature request label Nov 12, 2023
@cmbz
Copy link

cmbz commented Sep 9, 2024

2024/09/09: Keep open, there are other related issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ⚠️ Needed/Important
Development

No branches or pull requests

6 participants