This workflow explains how ORCID members can collect permissions from the researchers in one application and use the authenticated iD and permissions in other internal applications where ORCID is required.
Having your researchers only needing to provide permission to your organization once, saves time for the researcher and can increase the use and availability of ORCID iDs within your organization across the multiple systems.
This workflow is suitable for organizations that have multiple systems where ORCID is included plus having technical resources available to build a custom integration using the ORCID API.
An example of this workflow could be collecting iDs within your identity management system
- User is asked by a centralized system (e.g. identity management system) to provide your organization permission to interact with their ORCID iD
- User chooses to sign in to their ORCID record or register for an ORCID record
- User provides permission for your organization to interact with their ORCID record (part of the oauth process)
- The centralized system stores the users ORCID iD and the permissions that the user has granted your organisation
- The ORCID iD and the access tokens can then be moved to any other system that your organisation needs to capture ORCID iDs such as your CRIS system, HR or an institutional repository.
- Using the ORCID iD and token, individual systems can read/write to and from ORCID records. CRIS systems can push affiliations/works, repositories can push works etc
- Display the authenticated iD within your systems
We would recommend that you make it clear in your communication and your own documentation the expected workflow. This will ensure that your researchers are aware of your organization’s integration with ORCID and what is expected.
More detailed tutorials can be found here.