In the past year, the major groundwork has been laid for repository systems to support ORCID identifiers. DSpace, Hydra, and EPrints all have support for storing and managing ORCIDs. However, we are still in the early stages of ORCID adoption. Only a small fraction of repository content is annotated with ORCIDs, and most end-users have not yet realized any benefit from the features based on ORCID. This panel will bring together representatives of major repository systems to relate the current status of ORCID implementations, discuss plans for future work, and identify shared goals and challenges. The panelists will discuss how ORCID support provides practical benefits both to repository staff and end-users, with a focus on features that exist now or will exist in the next year. Rick Johnson (1), Hardy Pottinger (2), Ryan Scherle (3), Peter West (4), Bram Luyten (5) (1) University of Notre Dame; (2) University of Missouri System; (3) Dryad Digital Repository; (4) Digital Repository Services Ltd; (5) @mire

1. So we all have ORCID integrations,
now what?

2. Update on latest trends

3. ORCID Support Status

4. Available today
• Lookup and import of an author’s works from ORCID.
• A framework for working with the Tier 2 API
• Extraction of ORCID iDs for authors from University CRIS data.
• RIOXX2 plugin: Author lookup via the ORCID API.
6 month roadmap
• Get notified of modifications to works using WEB HOOKS API
• Workflows to add ORCID iDs to existing items in the repository.

5. Available today
• Author lookup in item submission and administrator edit
• Author lookup in CSV batch ingests
• Local cache of used ORCID data, separate from item metadata
6 month roadmap
• Improve how ORCID information is shown to end users

6. Available today
• Link Repository user account to ORCID iD
• Publish repository user works or bio information to ORCID
• Import researcher metadata records from ORCID
• External collaborator authentication via ORCID iD
• Can be used by anyone using Ruby on Rails at ORCID API
Request layer
6 month roadmap
• Maintain support inline with ORCID API changes and improvements

7. Available today
• Author lookup in item submission and administrator edit
• Local cache of used ORCID data
• Tool to claim repository content on user's ORCID profile
Available real soon now
• Links from item pages to ORCID profiles
• Login via ORCID authentication
• ORCID identifiers in DataCite DOI metadata
• Tool to import ORCID identifiers into repository metadata
6 month roadmap
• Leverage ORCID identifiers to allow editing permissions for co-
authors

8. What should we achieve by next OR?

9. Make it easier for someone to log in

10. Automate submission of new content

11. Maximize metadata reuse - Minimize work

12. Put contributors in the spotlight

13. Ensure our repositories are relevant to them

14. Integrate more metrics and metadata

15. Increase reach by feeding back to ORCID

16. Ok, let's do this
• Priorities: what should we be doing first?
• How can development in one platform benefit
another? Can we share more than ideas?
• Can we align UX across platforms?
• What do we jointly need from ORCID?

17. Hydra Rick Johnson University of Notre Dame rick.johnson@nd.edu
DSpace Hardy Pottinger University of Missouri System PottingerHJ@missouri.edu
DSpace Bram Luyten @mire bram@atmire.com
Dryad Ryan Scherle Dryad ryan@datadryad.org
EPrints Peter West Digital Repository Services Ltd pjw@repositoryservices.co.uk
Keep in touch with us

18. José Luís Agapito https://www.flickr.com/photos/blvesboy/
Seemann http://www.morguefile.com/creative/Seemann
Raul Pacheco-Vega https://www.flickr.com/photos/rolexpv/
Noah Sussman https://www.flickr.com/photos/thefangmonster/
Boston public library https://www.flickr.com/photos/boston_public_library/
Berkeley Lab https://www.flickr.com/photos/berkeleylab/
Image Credits