In 2019, we announced the launch of the ORCID in Repositories Task Force, chaired by Michele Mennielli, International Membership and Partnership Manager at DuraSpace. The group was charged with drafting recommendations for repository platform developers. You can read more about it’s formation in this blog post.
The key components of the recommendations that came out of this work include:
- Support collecting authenticated ORCID iDs, which means that users sign into their ORCID accounts and authorize the repository to obtain their ORCID iD and (optionally) permission to update their ORCID records
- Support other ways of obtaining ORCID iDs, including in mediated deposits and bulk uploads by repository managers, as well as automated deposits from other systems
- Allow administrators to request authenticated ORCID iDs and ORCID record update permission from authors and co-authors, in cases where iDs are missing or have not been authenticated
- Support displaying ORCID iDs wherever user/contributor information is displayed. ORCID iDs that have not been authenticated by their owner should be displayed slightly differently from those that have been authenticated
- Support pulling and pushing information to and from ORCID
- Provide testing, logging and reporting features for administrators
- Support exposing ORCID iDs in metadata outputs, such as OAI-PMH XML, wherever possible
- Provide documentation about ORCID features, for both administrators and end users
You can read full recommendations in the document here.
For more about Repositories in ORCID you can visit our documentation here