DOI: Add support for direct DataCite doi registration about dataverse HOT 11 CLOSED

Original Redmine Comment
Author Name: Kevin Condon (@kcondon)
Original Date: 2013-12-05T17:28:35Z

Merce sent a follow up email on 12/5:

Kevin - in case we don't have a ticket for this, could you enter in redmine to support the DataCite API.

Gustavo, Steve, if this is only a small change from the EZID API, we should include it for 4.0.

Merce

https://mds.datacite.org/static/apidoc

from dataverse.

Original Redmine Comment
Author Name: Eleni Castro (@posixeleni)
Original Date: 2014-04-10T13:06:42Z

Merce sent an email which is useful and important for when we reimplement DOI's for 4.0:

-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]] Im
Auftrag von Robert R Tupelo-Schneck
Gesendet: Montag, 7. April 2014 19:26
An: [email protected]
Betreff: [DOI-RATech] The Which RA Service

We have deployed a service on dx.doi.org to quickly provide the registration
agency responsible for a DOI.

Append the DOI name to "http://dx.doi.org/doiRA/". A resolution (HTTP GET)
of that URL will return a bit of JSON specifying the RA.

Example: http://dx.doi.org/doiRA/10.5240/B1FA-0EEC-C316-3316-3A73-L

You can use commas to find multiple results in one request:
http://dx.doi.org/doiRA/10.1594/PANGAEA.57055,10.1037/0003-066X.59.1.29,10.5
555/test,10.1002/doidoesnotexist

This is based on the service already offered by CrossRef at
doi.crossref.org, and described here:
http://www.crossref.org/crweblog/2013/05/find_the_registration_agency_f.html

Best,
Robert

DOI-RATech mailing list
[email protected]
http://www.doi.org/mailman/listinfo/doi-ratech

from dataverse.

For 4.0 we are using EZID for DOI registration. can we defer direct support until after 4.0?

from dataverse.

@sekmiller Support for more general DataCite API or Handle support will need to be in place when we help non-EZID DataCite members with Dataverses migrate to 4.x.

from dataverse.

Pasing to @scolapasta because I am not sure why this was given to me and am not sure of what needs to happen.

from dataverse.

Handle support will need to be in place

"Here in UBC, we would strongly support continue issuing handles for datasets (and not just DOIs) in Dataverse 4. We will be relying on handles to assign/resolve DOIs in our new discovery level for UBC Library - open collections. Our thinking is to use handles to resolve DOIs to. So handles will continue to be essential for us to use. As we have to work with DataCite API in Canada for now, we cannot use EZID, hence handles are a must for us to have. " -- @eugene-barsky at https://groups.google.com/d/msg/dataverse-community/xVb9a6dY8FQ/qS995aZyHQAJ

from dataverse.

Thanks, Philip!

E

from dataverse.

I don't know if that helps, but Dspace has been in a similar situation, supporting DataCite DOI registration initially only via EZID, and later adding support for registration with the DataCite MDS directly: https://wiki.duraspace.org/display/~pbecker/DOI+support+using+DataCite.

DataCite has three members in the US: CDL (EZID), Purdue and OSTI, so the issue here is not strictly US vs. non US.

from dataverse.

Assigning to QA - Pull request has been made

from dataverse.

Tested, works with some issues opened in separate ticket.

Test checklist:
Documentation
-Are the steps to enable clear?
Configuration
-Do the configuration steps work?
Create Dataset
-Does an appropriate DOI/persistent Url get created and appear in the Draft Citation?
-Since DataCite does not reserve DOIs, does the identifier appear in the DOIDataCiteRegisterCache table?
Publish Dataset
-Is the DOI created at DataCite?
-Is the persistent URL resolvable?
-Is the dataset metadata included?
-Is there an updated DOI version with updated metadata for each published version of a dataset?
Deaccession Dataset
-When there is at least one published version available, persistent URL will resolve to that.
-When all versions are deaccessioned, persistent URL will resolve to deaccessioned tombstone page and isActive flag at DataCite set to false.
-What happens when all versions are deaccessioned except one draft version?
Delete Dataset
-No special handling, other than removing draft dataset. DOI identifier remains in DOIDataCiteRegisterCache table. If a published version exists, persistent URL will resolve to that, if no published version, just remove it. Will review with Gustavo.
Destroy Dataset
-No special handling, other than removing all versions of dataset. We do not update record at DataCite nor remove identifier form DOIDataCiteRegisterCache table. Will review with Gustavo.
Supported Metadata
-identifier
identifierType (DOI)
-creators
creator
creatorName
nameIdentifier
affiliation
-titles
title
-publisher (automatic: dataverse name)
-publicationYear (automatic: current year/ year published)
-resourceType (Dataset)
-descriptions (only first description listed)
description
descriptionType (Abstract)
-contributors
contributor
contributorType (ContactPerson)
contributorType (Producer)
contributorName
affiliation
Validation
-Bad credentials
-Unique identifier
-Failure to register
-DOI format (shoulder)
Error handling
-Messages (indicate possible DataCite or temporary issue, try again later)
-Behavior (if duplicate detected, will keep trying with different id)
Logging
-Verify there are no debugging statements left in place.
Out of Scope
-Multiple DOI providers
Questions
-Interactions between namespaces/shoulders
-Interactions between DOI providers

from dataverse.

This has been delivered with separate tickets opened for individual issues. Closing.

from dataverse.