Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: fix title

ORCID Use-Cases


The release of the ORCID AuthN API opens opportunities for R&E federations to better integrate the ORCID ID into the FIM flow.

In the context of GN3plus, there is the possibility to work on using ORCID as a third party attribute provider and to do some kind of account linking. Use-cases that would benefit from the ORCID ID are welcome!


Use-casescaseSubmitted by:
The Data Observation Network for Earth ( project uses federated authentication ( / for data access. Linking ORCID identities with federated identities (via the ORCID OAuth API) would enable DataONE to associate the data owner's ORCID identity with the data. Since data objects will persist in DataONE for many years, using a persistent ORCID identity is valuable when data owners change institutions (resulting in changed federated identities).Jim Basney <jbasney@illinois<>edu>
The UCLA Faculty Information System (Opus) project will be using UCLA Shibboleth SSO (an InCommon IDP) for authentication. Opus will provide services to UCLA faculty as well as external scholars who are not part of UCLA IDP. Associating ORCID ID with institutional identity would allow Opus to track user identity and apply authorization rules based on ORCID ID returned from Shibboleth authentication for both federated authentication and local SSO case. It would also help in identity consolidation when scholars move from one institution to another.Ying Ma <yingma@ucla<>edu>
Enter TextEnter Text



DataONE use cases include ownership by individuals, ownership by organizations, and transfer of ownership (see: At many universities in the United States, academic works are owned by the creator, not the institution. Solving all the IPR challenges of long-term data curation is not a pre-condition for using ORCID IDs in metadata. 18:20, 30 May 2014 (UTC)