Closed cmbz closed 5 months ago
Could be closed by https://github.com/IQSS/dataverse/pull/10234
#10370 fixes one problem with backward compatibility after the main #10234 PR was merged. This Issue should close after 10370 is merged.
This 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: https://github.com/IQSS/dataverse/pull/10391
2024/03/20
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