GREI 2: HDV Task - Support multiple DataCite providers

[cmbz]

Overview

Support multiple DataCite providers was originally Aim 2.2.3

"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)

1. Universidad del Rosario (El Repositorio de datos de investigación)
2. Consortio Madrono
3. Texas Data Repository @ Texas Digital Library
4. Borealis (formerly Scholars Portal Dataverse)

Tasks

• Define and prioritize work
• Implement Multiple DataCite credentials in Dataverse

Related

• Support Registering Multiple Prefixes for DataCite DOIs In an Installation dataverse#2943
• Support flexible option for DOI and Handle registration, in same installation dataverse#3623
• DANS/Local PermaLink PID Provider dataverse#8674

Resources

• Project: NIH GREI - Generalist Repository Ecosystem Initiative #124
• Epic: GREI 2 - Consistent Metadata #116
• APPROVED - NIH GREI Coopetition Plan Year 3
• DRAFT: Year 3 Realignment Proposal Plan (Document)
• NIH GREI Aim 2 Yearly Progress (Year 2) (Document, Deprecated)

[cmbz]

Closed as a duplicate of #132