ORCID is now widely integrated in manuscript submission systems for journals including Aries Editorial Manager, eJournalPress, Open Journal System, and ScholarOne. We are now starting to work on embedding ORCID in book publication processes. We have learned from EDItEUR that the book metadata standard ONIX has been updated to include fields for storing ORCID iDs. And we were further delighted when Springer Nature announced last year that they were starting to collect ORCID iDs for book authors. Since then, we’ve had a number of conversations with other book publishers about using ORCID. With the recent launch of our Collect & Connect program, intended in part to help clarify best practices for integrating ORCID iDs, the time seemed right to engage with the the community on the use of ORCID in book workflows.
Current members of the books community working group
Tony Alves (Aries Systems)
Margo Bargheer (Goettingen University Press )
Tim Devenport (EDItEUR)
Justin Gonder (California Digital Library) orcid.org/0000-0001-7456-3912
Christina Hoppermann (Springer Nature) orcid.org/0000-0001-8858-7536
Andrew Joseph (Wits University Press) orcid.org/0000-0002-1486-1018
Emily Marchant (Cambridge University Press)
Martijn Roelandse (Springer Nature) orcid.org/0000-0001-5596-8084
Terence Smyre (UMN Press)
Parallel with our community working group on displaying iDs in journal articles, we are pleased to announce a working group that will focus on book workflows. Over the coming months, the group will collect suggestions, current practices, and queries from stakeholders, and consider questions including:
- What are the common elements of book workflows across publishers?
- At what point in the process should validated ORCID iDs be introduced?
- Whose iDs should be collected (authors, reviewers, or both)?
- Is a fully automated publishing system required or recommended?
- Should publishers push works information to ORCID records?
- What are the challenges for large publishers vs small ones?
Community input on where and when validated ORCID iDs should brought into book workflows is greatly needed from all disciplines, regions, and sectors – and from organizations large and small. Please send your use cases, suggestions, and questions and issues related to the use and display of ORCID iDs in books workflows to firstname.lastname@example.org by August 15, 2016. We also warmly welcome interested parties to join the group; please contact us by the same date.
The group will distill these into draft recommendations, which will be circulated for community review before formal release. Once released, ORCID will work to disseminate best practices through our Collect & Connect program.
All in the ORCID community are welcome to join in these discussions.