CORAL: Implementing an open source ERM
Presenter: Derrik Hiatt, Wake Forest University This session will focus on the benefits and challenges of implementing CORAL (Centralized Online Resource Acquisitions and Licensing), an open source ERM developed at the University of Notre Dame. CORAL offers libraries the option to reorganize their electronic resource management workflow and to collect information about their electronic resources into one central place without having to commit funding for a new library software from the ever shrinking library budget. CORAL currently includes four modules: licensing, resources, organization, and usage statistics. In addition to the challenges that are faced in any ERM implementation such as data collection, data preparation, staff buy in, etc., this session will address issues specific to using an open source software in an academic library.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Más de NASIG
Más de NASIG (20)
Último
Último (20)
CORAL: Implementing an open source ERM
- 1. CORAL Implementing an open source ERM C. Derrik Hiatt Electronic Resources Librarian Z. Smith Reynolds Library
- 2. About Wake Forest University • Private university • 7,288 FTE • Open Source friendly • No ERMS before CORAL
- 6. Resource name Alternate name Organization name
- 12. CORAL’s future at WFU • Next priority – set up Workflows • Tracking database desiderata? • Usage statistics module? • Drive public A-Z list
- 13. Thank you! C. Derrik Hiatt hiattcd@wfu.edu
Notas del editor
- Public-facing A-Z database list, with alphabetical browse, expandable subject lists, and search box.
- Clicking on the (i) button in the database list links to more detailed database info.
- Public A-Z list is driven by a static XML file
- Worked with Web Librarian to map data from the existing XML file into the CORAL database. Mapped <Title> to Resource Name, <alternative> to Alternate Name, <Publisher> to Organization Name, etc.
- Data transfer not perfect, but successful overall (for example, provider of ABELL was in XML file as “Literature Online” instead of Chadwyck Healey). Transfer also did not capture parent/child relationships, such as Chadwyck Healey and ProQuest.
- Data cleanup example: Originally mapped XML file’s <Format> field into CORAL’s Resource Format field, but realized later that it made more sense to be in CORAL’s Resource Type field
- Using CORAL to track e-journals at the package/platform level but not individual e-journal titles. Only a few packages are in CORAL right now (because source XML file included only those packages that reference dept. had wanted in the public list), but gradually adding more as the need arises.
- Organizations module - Haven’t entered Contacts or Role(s) for most organizations. Have entered contact info for larger or frequently-contacted vendors, adding more as we go along (e.g. whenever I have to look one up elsewhere, I then add it to CORAL).
- Entering new licenses, but no systematic effort yet to add existing licenses (WFU library already has networked drive with dedicated space for licenses).
- Want to use CORAL to track purchase requests, but the functionality doesn’t appear to be there. Need to explore Statistics module more.Hope to eventually use CORAL to drive public A-Z database list. Main missing component: Subject headings.
- Thank you!