DOI: Add support for direct DataCite doi registration

[eaquigley]

---

Author Name: Kevin Condon (@kcondon)
Original Redmine Issue: 3397, https://redmine.hmdc.harvard.edu/issues/3397
Original Date: 2013-12-03
Original Assignee: Gustavo Durand

---

See RT #171127

We already have a DataCite account and use DOIs for our articles,
published
via the OJS system (http://pkp.sfu.ca/ojs/).
Is there any possibility to register DOIs within DataVerse directly with
DataCite? Or would we really have to pay for
an extra mediator service (EZID)?

[eaquigley]

---

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

[eaquigley]

---

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: doi-ratech-admin@www.doi.org [mailto:doi-ratech-admin@www.doi.org] Im
Auftrag von Robert R Tupelo-Schneck
Gesendet: Montag, 7. April 2014 19:26
An: doi-ratech@doi.org
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
DOI-RATech@www.doi.org
http://www.doi.org/mailman/listinfo/doi-ratech

[sekmiller]

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

[posixeleni]

@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.

[eaquigley]

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

[sekmiller]

Assigning to QA - Pull request has been made

[kcondon]

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

[kcondon]

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