Integra(on between ins(tu(onal repository, researcher directory and library catalog
using ORCID and Next-‐L Enju �July 9th, 2015. Open Repositories 2015�
Library catalog (Next-‐L Enju)
Integra(on module (Enju IR)
Cataloging module
1. Introduc(on This poster describes a case study in integra(ng an ins(tu(onal repository, a researcher directory and a library catalog using ORCID and Next-‐L Enju and Enju IR, an open-‐source library system and its add-‐on module. The mo(va(on is to centralize metadata management in the library catalog.
2. What is Enju IR? Enju IR extends the default cataloging module in Next-‐L Enju. Enju IR links the authority files in Next-‐L Enju to researcher directories using ORCID. In addi(on to that, Next-‐L Enju can syncronize bibliographic data including ORCID and items’ DOI between ins(tu(onal repositories and the library catalog. Next-‐L Enju is built on Ruby on Rails, and Enju IR is implemented as a module (Rails Engine).
Kosuke Tanabe <[email protected]> �
Ins(tu(onal Repository (PubMan, etc)
3. Integrate ORCID into library catalog Librarians can add an ORCID number to new and exis(ng bibliographic records using Enju IR. Librarians can link ORCID to not only born-‐digital items, but also old materials (such as paper-‐based books) in the library catalog.
4. Discussion This implementa(on works while items in ins(tu(onal repositories are mainly documents (theses or scanned books). But it is a challenge to manage research data in the repositories from the cataloging module in Next-‐L Enju, because each dataset has its own metadata schema. Further study will be needed to determine the specifica(on to define and manage mul(ple schemas and share them between researchers and librarians.
Researcher directory
(researchmap, SAMURAI, etc)
Reference: Next-‐L Enju hbps://github.com/next-‐l/enju_leaf
DOI RAs ORCID Web service
Bibliographic record
Authority record
