ORCID identifiers in repositories The ORCID identifier has been incorporated into numerous repository platforms. This session will offer a discussion of integration points, policy issues, data flow between systems, researcher participation, discovered opportunities, and demonstrations by universities, research organizations, and vendors. Moderator: Salvatore Mele, Head of Open Access at CERN Presenters: Robin Haw, Scientific Associate and Reactome Outreach Coordinator, Department of Informatics and Bio-computing, OICR Rick Johnson, Co-Program Director, Digital Library Initiatives and Scholarship E-Research and Digital Initiatives, Notre Dame University Ann Campion Riley, Associate Director for Access, Collections and Technical Services, University of Missouri Library Sarah Shreeves, Coordinator, Illinois Digital Environment for Access to Learning and Scholarship (IDEALS), University Library. University of Illinois at Urbana-Champaign Michael Witt, Head, Distributed Data Curation Center, Purdue University

1. www.atmire.com
ORCID Adoption and
Integration in DSpace
University of Missouri - @mire

2. OVERVIEW
1. Integration with ORCID API
2. Data consistency and Performance
3. Assignment of ORCID in CSV Batch Deposit
4. ORCID lookup during submission
5. ORCID lookup administrative Item Edit
6. Contribution to the DSpace community
7. Deployment at your institution
8. Possible next steps

3. 0. INTRODUCTION
• ORCID in DSpace
• Focus on ingestion
• Manual item submission
• Batch item submission
• Using Authority Control
• ORCID in dissemination
• Future development

4. 1. INTEGRATION WITH ORCID API
• In DSpace, a facade has been implemented
that presents ORCID’s public search and
retrieve APIs in a similar way as native
DSpace objects.
• Results in objects that hide the details about
searching and retrieving from ORCID
• Allow ORCID data to be used in the same way
local DSpace data is accessed.

5. 2. DATA CONSISTENCY AND PERFORMANCE
• Subset of ORCID biography metadata will
be replicated into a local store and
indexed for local lookup of the ORCID
metadata in DSpace.
• This store will be further referred to as
the DSpace Authority Cache.

6. 2. DATA CONSISTENCY AND PERFORMANCE

7. 2. DATA CONSISTENCY AND PERFORMANCE:
DSPACE AUTHORITY CACHE
<doc>
<arr name="all_labels">
<str>
BioExternalIdentifier{id_orcid='0000-0002-5982-8983',
id_common_name='Scopus Author ID',
id_reference='7006121728',
id_url='http://www.scopus.com/inward/authorDetails.url?
authorID=7006121728&amp;partnerID=MN8TOARS'}
</str>
</arr>
<str name="field">dc_contributor_author</str>
<str name="value">Wagstaff, Adam</str>
<str name="first_name">Adam</str>
<str name="last_name">Wagstaff</str>
<str name="id">e514b530-0f23-4f3e-8a8c-9c2e0ee09278</str>
<str name="orcid_id">0000-0003-4442-5070</str>
<date name="last-modified-date">2014-04-03T10:48:26.938Z</date>
<arr name="label_external_identifier">
<str>
BioExternalIdentifier{
id_orcid='0000-0002-5982-8983',
id_common_name='Scopus Author ID',
id_reference='7006121728',
id_url='http://www.scopus.com/inward/authorDetails.url?
authorID=7006121728&amp;partnerID=MN8TOARS'}
</str>
</arr>
</doc>

8. 2. DATA CONSISTENCY AND PERFORMANCE:
DSPACE AUTHORITY CACHE
Authority control cache is linked to the DSpace
item metadata in METS.
<mets:xmlData>
<dim:dim dspaceType="ITEM">
<dim:field
authority="e514b530-0f23-4f3e-8a8c-9c2e0ee09278"
element="contributor"
qualifier="author"
confidence="ACCEPTED"
mdschema="dc">Wagstaff, Adam
</dim:field>
<dim:field element="title"
language="en_US"
mdschema="dc">A publication</dim:field>
...
</dim:dim>
</mets:xmlData>

9. 3. ASSIGNMENT OF ORCID IN CSV BATCH DEPOSIT
• GOAL:
• Repository Administrators should be able to
add ORCID IDs as part of the DSpace CSV
Batch Deposit process.
• DSpace CSV Batch Deposit tool has been
extended to allow addition of ORCID
identifiers in a new column.

10. 3. ASSIGNMENT OF ORCID IN CSV BATCH DEPOSIT
Add ORCID identifier to spreadsheet
for batch deposit of metadata into DSpace:
“ORCID:dc.contributor.author”
Non-ORCID authors can still be imported:
“dc.contributor.author”
CSV spreadsheet

11. 3. ASSIGNMENT OF ORCID IN CSV BATCH DEPOSIT
ORCID authors are retrieved automatically,
and the author’s name is displayed in DSpace

12. 4. ORCID LOOKUP DURING SUBMISSION
• GOAL:
• To lower the threshold for ORCID adoption,
IDs should be easy to include in metadata by
non technical users during the submission of
a new item.
• To add an author, the submitter will be
able to click a “Lookup” button, to
perform a live search in ORCID.

13. 4. ORCID LOOKUP DURING SUBMISSION
• Should be easy to differentiate between:
• ORCID authors that have already been
associated with other items in the repository
• and ORCID authors that have not been
associated with an item in the repository.

20. Indicates that author is in
DSpace Authority control

21. Authors in red are in
DSpace Authority Control
Authors in black are NOT in
DSpace Authority Control

22. 5. ORCID LOOKUP ADMINISTRATIVE ITEM EDIT
• GOAL:
• To be able to edit and/or add ORCID
identifier after item is submitted to DSpace
• “Edit item” page shows DSpace Authority
Control ID
• ORCID lookup functionality has been
integrated in “Edit item” page

23. DSpace
Authority
Control ID

25. 6. CONTRIBUTION TO THE DSPACE COMMUNITY
• To be release in DSpace 5
• Scheduled for Fall 2014
• Patches for earlier DSpace 4.x and 3.x:
• will be made available for download on
atmire.com/website/?q=contributions

26. 7. DEPLOYMENT AT YOUR INSTITUTION
• Add your local staff identifiers
• Local storage is solr based, and the schema can
easily store any local staff identifiers as well.
• A single author object is created per person.
This object is uniquely identified.
• Each person can have an ORCID id, as well as
a local staff id.

27. 8. POSSIBLE NEXT STEPS
• Display ORCID identifier on item pages
• Link to author ORCID profile
• Add ORCID identifiers to Google Scholar
<meta> tags
• UI to manage DSpace Authority Control