We notice you are using a browser that our site does not support. Some features on this site may not work correctly. We recommend that you upgrade to a supported browser

Case studies: Publishers using ORCID

ORCID promotes a community of practice and encourages that publishers and associations share how they use ORCID and engage with authors and reviewers. We highlight recent case studies below.


ORCID in journal articles


eLife: Authenticating co-authors’ iDs during proofing

eLife enables contributing authors to associate their authenticated ORCID iD with their work during the production process. When corresponding authors share the proof link with their co-authors, they are required to sign in via ExeterPremedia’s Kriya platform using their ORCID iDs, which are collected and displayed with the article and delivered downstream to platforms such as PubMed and Crossref.


Open letter signatories: Implementing ORCID best practices

As of May 2018, nearly 50 publishers have signed the open letter committing their organizations to require iDs for, at a minimum, corresponding authors of accepted articles, and to implement the best practices for ORCID in publication workflows. Of those signatories, to date 21 have confirmed that they are actively putting that commitment into effect, collecting authenticated ORCID iDs and displaying them in works and work metadata with Crossref.


ORCID in peer review


F1000: Authenticating iDs during submission and adding works and reviews to records

F1000 worked with ORCID to launch our peer review functionality, partnering to develop a practical method to cite peer review activities, based on a standard terms and persistent identifiers, and to test peer reviews while they were still in beta. Their F1000 Open Research integration allows authors to connect their iD on submission and add publications and peer review activities to their records. F1000 has also enabled auto-update of ORCID records.


Publons: Connecting verified reviews to ORCID records

Publons authenticates researchers’ ORCID iDs and displays them on their Publons profile. Researchers can then grant Publons permission to update their ORCID records with verified reviews provided by publishers, and to automatically update their ORCID records when new reviews are available. ORCID-enabled systems including ScholarOne Manuscripts and Editorial Manager are also able to export review activity to Publons to enable review recognition.


ORCID in books


Report: ORCID in book workflows

In 2017, ORCID convened a community working group on ORCID in book workflows comprised of representatives from service providers and publishers small and large. We engaged a consultant to survey around 100 organizations and interview representatives from the books community and create a summary report. The report recommended that implementing ORCID in books should target the points in the book workflow where there is the most direct author and editor contact and the most perceived benefit: acquisitions, proofing, marketing.
https://orcid.org/content/case-studies-publishers-using-orcid
orcid.org
crawl=CC-MAIN-2020-24
32182
application/http; msgtype=response
sha1:W2SJOXEO5PQVBQAISDJSS6XOTRNB3Z2E
<urn:uuid:0dbe8fca-7440-465b-a8bc-8a6397aa95c8>
2020-05-26T13:50:27Z
104.20.228.70
text/html
sha1:OFZNSPNDV3LTJ5VYCJEYQ6CLL3RUZHYW
<urn:uuid:a30435a4-69ab-44a2-a4e4-49a054cdcb71>
https://orcid.org/content/case-studies-publishers-using-orcid
response
<urn:uuid:51e4301b-ca95-4c53-a8fb-22e517b3827d>
isPartOf: CC-MAIN-2020-24
publisher: Common Crawl
description: Wide crawl of the web for May/June 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-124.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/