Any software platform that uses person-based data (names, works or affiliations attributed to a person) can benefit from connecting with ORCID via the ORCID API. Many systems either already support ORCID or can be configured locally to connect with ORCID. Some systems do not yet support ORCID. The list below provides ORCID-related information on some commonly used systems in the US (this list is not comprehensive). Questions about this list should be sent to email@example.com.
arXiv - users can authenticate and connect their ORCID iD with their arXiv works, ORCID iD displayed on author page, see documentation.
Converis - allows for ORCID authentication and exporting publications from Converis to ORCID; see documentation.
Digital Measures - allows users to authenticate and connect their ORCID iD with their Digital Measures profile, and allows for importing publications data from ORCID into Digital Measures, see documentation. Users should contact Watermark directly to request additional functionality, such as importing additional ORCID data and writing to ORCID.
DSpace - ORCID is currently not built in out of the box (although there are plans for this in future versions), but DSpace can be configured to work with the ORCID API, and ease of ORCID integration depends on what version of DSpace is being used. For example, see ORCID documentation for DSpace 6.x. Duke University has integrated ORCID into their DSpace instance, DukeSpace, see example and documentation.
Editorial Manager - provides support for ORCID; see ORCID’s website for details.
ePrints - two ORCID plugins are available: ORCID Support (includes manual entry ORCID iD field, and displays iDs on user profile and publication pages) and ORCID Support Advanced (recommended: associates authenticated iDs with user profiles, displays iDs on user profile and publication pages, pulls works data in from ORCID, pushes works and affiliations data to ORCID). See documentation and more information.
Faculty180 - allows for ORCID authentication and importing publications, employment, education, funding, and biography data from ORCID to Faculty180, see details. Access to the ORCID functionality, if it is turned on for your institution, is available in the “Vitas and Biosketches” menu of Faculty180; further details can be found by searching the Faculty180 help system for “ORCID”.
Fedora - can be configured to work with ORCID, typically as part of a Samvera or Islandora repository. See Samvera and Islandora respectively for details.
Figshare - Figshare can associate authenticated iDs with user profiles, display iDs on user profile pages, generate Datacite DOIs with iDs included in metadata, and push works to ORCID via Datacite. See Figshare blog and documentation for details.
Islandora - can be configured locally to work with the ORCID API. ORCID is on the radar for inclusion in Islandora CLAW, and the Islandora LASIR (Liberal Arts Sprint for Institutional Repositories) project also includes ORCID integration; see LASIR executive summary and GitHub.
Open Journal System - an ORCID plugin for OJS version 3 allows authors to authenticate their ORCID iD in their OJS profile and automatically pull in data from their ORCID profile, like their name and iD. An enhanced plugin for OJS 3.1.2 is now available, to allow for publication data to be written from OJS to the author’s ORCID record, see demo.
Open Monograph Press - the ORCID OJS plugin should also work for OMP. See Open Journal Systems above for details.
PeopleSoft - can be configured to integrate with the ORCID API. Boston College has integrated ORCID with PeopleSoft, including ability to authenticate ORCID iDs and write employment data to ORCID from PeopleSoft, see demo (1:55-8:35).
Pivot - Pivot allows users to authenticate and link their ORCID iD and read information from ORCID, see documentation.
Pure - Pure allows for exporting/writing publication data from Pure to ORCID, and displays ORCID iDs on user profiles. See demo video. Version 5.13 adds ability to read works from ORCID records and assert/write institutional affiliations and works to ORCID records.
Samvera - can be configured to work with the ORCID API via the Samvera Labs ORCID Gem or a customized approach. University of Virginia has integrated ORCID as a microservice with two of their institutional repositories, see documentation.
Symplectic Elements - Elements allows researchers to authenticate & connect their ORCID iD, granting permission to import data from ORCID into Elements. Elements can then search ORCID for any Publication-IDs associated with ORCID works and use them to harvest publications to auto-claim for the researcher. See demo video. Elements is looking to add functionality in 2019 for writing to ORCID records.
Vireo ETD submission - Vireo 3 has a field for ORCID that validates the ORCID iD number and name of a user, see demo. Administrator's view has settings to turn ORCID validation/authentication on or off. ORCID iDs can be exported in repository XML files. Vireo 4 is currently in development. Questions should be sent to the Vireo listserv.
VIVO - VIVO currently allows users to authenticate and connect their ORCID iD with their VIVO profile. OpenVIVO allows users to authenticate and connect their ORCID iD, as well as log in to VIVO using ORCID credentials, and import data from ORCID to VIVO.