Typically a book publication workflow will follow these steps, although we are aware that this can vary between integrators depending on specific use cases.
- The author submits a proposal/submission process to the Publisher
- The publisher collects the authenticated author’s ORCID iD and requests permission to interact with their record, and stores that permission.
- The publisher collects data from the author’s record using the ORCID API and uses it to help populate the proposal/submission form. This helps to save the author time manually completing information that is already available within their ORCID record.
- When a proposal is accepted and the book or book chapter is published, the publisher adds the publication to the author’s ORCID record, connecting the person with the publication.
- The publisher displays the iD within the book and the books metadata and displays the iD on the authors information page
We are aware that things are never this simple. The ORCID iDs and permissions potentially would need to be moved from the submission system to a production system, and there may not even be a system in place that authors interact with.
We still think it’s worth doing. ORCID can help streamline the publishing process, improve the management of author and reviewer databases, and enhance the accuracy of name-based repository searches.
Publishers use ORCID to clearly link authors and reviewers—and all their name variants—with their research work, by embedding ORCID iDs into their publication metadata and displaying them on finished publications. By including validated iDs in your metadata you can free researchers from having to manually update their ORCID records, help speed the communication of research works, and reduce the risk of errors. You can also use data from the ORCID record such as researchers’ names, education history, and current affiliations to populate profiles in your own system to save your users time and reduce errors.
A more detailed tutorial can be found here.