-
Notifications
You must be signed in to change notification settings - Fork 493
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
Support flexible option for DOI and Handle registration, in same installation #3623
Comments
@amberleahey thanks for opening this issue. It's a nice follow up to what you had written at https://groups.google.com/d/msg/dataverse-community/E_nxXqH68NE/BwkHbR_IGQAJ |
At https://projects.iq.harvard.edu/dcm2017 someone mentioned they really want this but I can't remember who. Probably @amberleahey 😄 |
"This PR takes significant steps toward making PID Providers plugable and allowing multiple DOI accounts to manage different authority/shoulder combinations." |
2023/08/29
|
2023/09/25: Follow up with @qqmyers to determine whether he has already addressed this issue. |
Another use case from Andrzej Zemla: "we are very interested in pluggable PID's since we are hosting repositories for 6 Universities, and were forced by DataCite policy to use 6 different doi's - so we have to run 6 instances, and then harvest them." I assume he's referring to the installations in Poland that were recently added to the map: |
2023/10/23: Sized at approx. 80 (as per slack conversation: 5 October 2023) |
At Scholars Portal (and possibly other library hosted installations) we'd like to have the choice to assign a handle to a dataset that we don't have "authority" over, or, when there are multiple copies of that data across various access repositories (e.g. licensed data for example). This would be in accordance with DOI best practice for data copies.
Support for both handle and doi as a PID in the same installation would be great. Possibly the user can choose which PID to assign upon deposit.
Related, but different than #2943
The text was updated successfully, but these errors were encountered: