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

Support Registering Multiple Prefixes for DataCite DOIs In an Installation #2943

Closed
posixeleni opened this issue Feb 10, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@posixeleni
Copy link
Contributor

commented Feb 10, 2016

Alan Darnell from Scholars Portal informed us on our User Community that there is an additional use case we need to consider for fully supporting DataCite DOI registration for their installation.

In particular, I am interested in whether it will be possible to associate different DataCite accounts (and prefixes) with different Dataverses. We have a number of libraries using a shared Dataverse instance -- each library has its own account with DataCite and so its own prefix. Ideally, we would like to associate accounts and prefixes with IP Groups so that datasets created under a specific IP group can be registered with an institution specific prefix.

We are already working on Phase 1 of implementing DatCite DOI support (#24 ) which will only allow for the registration of a single prefix at the system level to begin with. But we will be looking at supporting the Scholars Portal use case as well in the future (more from Alan):

We could start out with a single installation prefix, but there should be an option to suppress automatic generation of a DOI to allow an institution that uses DataCite to mint its own DOIs with its own institution prefix to add these manually. Otherwise, we would end up with 2 DOIs pointing to the same resource, which would not be terrible, but could be confusing.

Ultimately, it would be good to have a prefix "override" at the Dataverse level -- a place to enter institutional DataCite credentials -- that would override the default server level credentials and prefix. The reasons for this include stats tracking. If you look at this Datacite site, you can see how stats on registrations and resolutions are captured: https://stats.test.datacite.org

@pdurbin

This comment has been minimized.

Copy link
Member

commented Feb 3, 2017

Related: #3623.

@pdurbin

This comment has been minimized.

Copy link
Member

commented Jul 4, 2017

Closing in favor of #3623.

@pdurbin pdurbin closed this Jul 4, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.