ORCID Integration

This page collects the various features that Dryad may implement using ORCID. We expect that many of these features will be of value to the larger DSpace community. If you have feedback, please send it to [mailto:help@datadryad.org help@datadryad.org].

Basic authentication
See description on the DSpace wiki.

Adding ORCIDs to items at submission
See description on the DSpace wiki.

This use case is being addressed for DSpace 5.0: https://wiki.duraspace.org/display/DSDOC5x/ORCID+Integration

Update ORCIDs in Dryad from ORCID metadata
Requirements:
 * There should be an automated way to harvest previously claimed items (both articles and data packages) from ORCID and add the associated ORCIDs into Dryad metadata.
 * Note that anyone can claim any work in ORCID -- so self-claims cannot be used for managing co-author privileges. Self-claimed items should have a lower confidence score than ORCIDS attached by a submitter.

A prototype of this feature, called ODIN's HAMR, was created as part of the ODIN CodeSprint. It will be integrated into Dryad once the core DSpace supports storage of ORCIDs. We expect this to be completed as part of the Missouri/Atmire ORCID project.

Enhancements to adding ORCIDs with a submission
Requirements:
 * If the pre-population metadata (from CrossRef or a journal) includes an ORCID, we include it automatically, with a high confidence level.
 * If the submitter is unable to locate an ORCID for a coauthor, an email invitation is sent to the coauthor. The invitation should explain that (a) data has been submitted to Dryad (b) they need an orcid to claim their coauthor rights, and (c) here's a link to do it. Following the link opens a Dryad page that pops up the ORCID registration sub-window. When they're done registering, it returns to the dryad page and adds their newly minted ORCID to the item.

Allowing users to claim their items
See the prototype from ODIN.

Requirements:
 * For data packages that are archived in Dryad, we want to allow researchers to self-claim the package.
 * Self-claiming a data package means that:
 * the data package will be associated with the researcher's ORCID profile.
 * the data package in Dryad will contain the researcher's ORCID, which will support search/browse features.

Expected changes to DSpace:
 * Add buttons for the ODIN claiming tool into the My Submissions page. Each item should have either a button "claim this in ORCID", or a label "claimed in ORCID".
 * When an item has been claimed, store the associated ORCID in the appropriate author field. It will be stored as an authority control value, but with a low confidence.
 * The claiming user needs a way to specify which dc.author should be attached to the ORCID.

Other notes and questions:
 * Is there a general version of this use case that would be relevant for other DSpace users?
 * This is primarily accomplished via the ODIN app for "claiming" a data package
 * How best to move this information back into Dryad?
 * Add capability for users to claim the package's associated article as well?
 * Open question: What happens if someone wants to claim something, but there is not a matching dc.author?

Coauthor permissions
We want coauthors to have permission to edit items and version items that were originally created by another author.

Requirements:
 * When an item contains an ORCID with a high confidence score (see above use cases):
 * If the item is an in-process submission, the researcher associated with the ORCID should be able to take control of the submission (e.g., move it into their workspace)
 * If the item is archived, the researcher associated with that ORCID should be able to create a new version of the item.

Future Ideas
These are ideas we would like to implement in the long term, but we're not actively pursuing them now.

Importing metadata from ORCID

 * See the "sync" tool from Figshare
 * while an author is submitting to Dryad, we mine the ORCID metadata for useful additions (e.g., to suggest coauthors?)
 * This will not work well until the ORCID database contains more content.

Update ORCIDs in Dryad from CrossRef metadata

 * when Dryad is updating articles with CrossRef metadata, automatically collect associated ORCIDs

Tracking funder vouchers

 * Funder sends Dryad a list of ORCIDs that have been funded; only these people are eligible to use vouchers from that funder.
 * postponed -- funders don't have this info yet

Enabling third-party statistics lookup

 * This may be completely outside the scope of Dryad -- simply a benefit of providing good metadata.
 * external tool (e.g., impactstory) can use ORCID ID to get Dryad DOIs to get DataCite statistics

Tools
Tools and code that may be useful for developing further ORCID integration:
 * Tom Demeranville's ORCID library
 * ODIN linking tool