Hydra on Fedora ORCID Capabilities: Further information
The examples on this page have been grouped using the ORCID ‘Collect and Connect’ terminology of:
- Collect ORCID IDs
- Display ORCID IDs on your website
- Connect ORCID records with affiliation information
- Synchronise ORCID record data with your systems
More details on the Collect and Connect actions for Research Institutions are given on the ORCID website.
Hydra ORCID Plug-in
Version 0.9.1 of the Hydra ORCID Plug-in was released in December 2014 and is the output of a project led by the University of Notre Dame and other partners. It integrates Hydra/Fedora with ORCID and its features include creating new ORCIDs for repository users, looking up existing ORCIDs, and linking ORCIDs to user profiles in the repository.
In addition, it has limited capabilities to query and update the works associated with an ORCID, although this functionality currently caries the caveat: *”The functionality exists, but it will be a bit bumpy to implement. Plans are to improve the integration with Version 1.0.0 of the Orcid gem.”*
The plugin is currently implemented in the University of Notre Dame’s Institutional Repository, [CurateND].
- Hydra ORCID Plug-in project page
- Hydra ORCID Plug-in source code
- CurateND: University of Notre Dame’s Institutional Repository
Whilst not strictly a Hydra project; this Ruby project converts the output of the ORCID Public API into a number of different computer and human-readable citation formats, including RSS, JSON, BibTeX and 8000+ pre-defined styles defined in the Citation Style Language, such as APA, Harvard and Vancouver. It could be used to as part of a cross-checking process.
There may be a use case in addition to those discussed below for users to authenticate directly with ORCID. The OmniAuth framework and the OmniAuth ORCID strategy maintained by DataCite support this behaviour, allowing users to authenticate with ORCID via OAuth2.
Sufia is a popular Hydra head, providing a web-based interface to an underlying Fedora Commons repository. Sufia adds basic support for ORCID, storing the ORCID identifier with the user’s profile. However, the validation of the ORCID checks only the format of the identifier using a Regular Expression, rather than the correctness of the identifier (e.g. is it actually registered).
Sufia allows users to link their profile to an existing ORCID.
CurateND at the University of Notre Dame has implemented the Hydra ORCID Plug-in to allow users to register for new ORCIDs, and to look-up and link to existing ORCIDs. Once an ORCID is assigned to a user, it is displayed on their profile page. Implementing the plug-in requires some technical expertise and familiarity with Hydra, Ruby on Rails and gem libraries.
Currently no examples of the ‘Connect’ action within Hydra have been documented for inclusion here. If you have an example please let us know at firstname.lastname@example.org.
Currently no examples of the ‘Synchronise’ action within Hydra have been documented for inclusion here. If you have an example please let us know at email@example.com.
The Hydra ORCID Plug-in is intended to allow publications to be pushed from the Institutional Repository to ORCID. The implementation is currently described as “bumpy” but will be improved in later versions of the plug-in.
The ORCID Feed project could be used as a step in the workflow for crosschecking publications in an ORCID profile vs those in an Institutional Repository.