-
Notifications
You must be signed in to change notification settings - Fork 0
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
GREI 2: HDV Task: Support Multiple DataCite Providers #132
Labels
Dataverse Project
Issues related to Dataverse Project software
GREI 2
Consistent Metadata
Harvard Dataverse
Issues related to Harvard Dataverse Repository
Project: NIH GREI
Tasks related to the NIH GREI project
Comments
cmbz
added
Harvard Dataverse
Issues related to Harvard Dataverse Repository
Dataverse Project
Issues related to Dataverse Project software
Project: NIH GREI
Tasks related to the NIH GREI project
labels
Dec 22, 2023
This was referenced Jan 3, 2024
2 tasks
Could be closed by IQSS/dataverse#10234 |
#10370 fixes one problem with backward compatibility after the main #10234 PR was merged. This Issue should close after 10370 is merged. |
Status: March 2024This task is complete, with the completion and merging of the following issues and PRs:
The functionality now enters a maintenance phase involving minor fixes, as demonstrated by: IQSS/dataverse#10391 |
24 tasks
2024/03/20
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Dataverse Project
Issues related to Dataverse Project software
GREI 2
Consistent Metadata
Harvard Dataverse
Issues related to Harvard Dataverse Repository
Project: NIH GREI
Tasks related to the NIH GREI project
Overview
Dataverse currently allows DataCite Repository credentials to be specified at the instance/installation level. This means that all datasets will be part of the same DataCite Repository and have the same prefix. Currently, it is not possible to specify different credentials for different Dataverse collections. Because only one set of DataCite Repository credentials can be specified, all DOIs must be managed by the administrator of the instance.
A growing use case for Dataverse collections is to serve as institutional repositories within a single Dataverse installation. With this setup, institutions should be able to manage their own DataCite DOIs. This proposal outlines the work required to allow multiple sets of DataCite repository credentials to be active within a single Dataverse instance.
Source: Proposal: Collection-level specification of DataCite repository credentials
Background
Four Dataverse installations serve as use cases for this task: (see Multiple DataCite credentials in Dataverse)
Tasks
Issues
Related
Resources
The text was updated successfully, but these errors were encountered: