Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

ORCID identifiers for DSpace


Published on

The University of Missouri System and @mire are currently developing an integration between DSpace and ORCID, an infrastructure for persistent digital identifiers for researchers. The project pursues two distinct goals:

Lowering the threshold to adopt ORCID for the members of the DSpace community

ORCID offers an API, allowing developers to build points of integration between ORCID and third party applications. Today this still requires individual members of the DSpace community to implement front-end and back-end modifications to the DSpace source code in order to leverage these APIs.

Because DSpace is meant as a turnkey Institutional Repository platform, not every institution using DSpace has software development resources available to implement this kind of functionality.

By contributing a solution directly to the core DSpace codebase, this threshold to adopt ORCID functionality in DSpace repositories is effectively lowered. The ultimate goal is to allow easy adoption of ORCID without customization of the DSpace software, by allowing repository administrators to enable or disable functionality by means of user friendly configuration.

Address generic use cases with appealing end user functionality

This proposal aims to provide user friendly features for both repository administrators as well as non- technical end users of the system. The addition of ORCID functionality to DSpace should not come at the cost of making the system more difficult for administrators and end users to use.

Published in: Technology, Education

ORCID identifiers for DSpace

  1. 1. ORCID for DSpace University of Missouri - @mire Bram Luyten
  2. 2. OVERVIEW The problem Implemented functionality DSpace 5 contribution Future opportunities
  3. 3. The Problem
  4. 4. These were just a few uncommon exceptions, right? NO.
  5. 5. WHY IS THIS A PROBLEM? Trust Re-use of repository metadata
  6. 6. OBJECTIVE Making it easy for repository managers to enhance and cleanup author metadata knowing that Names are not reliable Not everyone will have an ORCID
  7. 7. IMPLEMENTED FUNCTIONALITY ORCID and DSpace Authority Control Integration Author lookup for new submissions (UI) Author lookup for edits on items (UI) Author identifiers in Batch CSV editing
  9. 9. INTEGRATION String representation of the name in standard Dublin Core metadata enhanced with DSpace compliant authority control id “authority cache” stores extended contributor metadata, including ORCID ID and alternative names
  10. 10. NEW SUBMISSIONS Adding an author with an identifier should ideally be as easy as providing a simple name.
  11. 11. Indicates that author is in DSpace Authority control
  12. 12. Authors in red are in DSpace Authority Control Authors in black are NOT in DSpace Authority Control
  13. 13. ITEM EDITS Editing existing items should offer the same easy of use for administrators.
  14. 14. DSpace Authority Control ID
  15. 15. Staff enhances contributor string names with ORCID Administrator finalizes by re-uploading edited file Administrator exports existing work metadata Author identifiers in Batch CSV editing
  16. 16. SPREADSHEET EXAMPLE Add ORCID identifier to spreadsheet for batch deposit of metadata into DSpace: “” Non-ORCID authors can still be imported: “”
  17. 17. SPREADSHEET EXAMPLE ORCID authors are retrieved automatically, and the author’s name is displayed in DSpace
  18. 18. DSPACE 5 CONTRIBUTION To be released as part of DSpace 5 Scheduled for Fall 2014 Patches for earlier DSpace 4.x and 3.x: will be made available for download through
  19. 19. FUTURE OPPORTUNITIES 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
  20. 20. Questions? Thank You