necessity is the mother of invention: using erm to manage electronic books a poster for iug 2014,...
TRANSCRIPT
RESEARCH POSTER PRESENTATION DESIGN © 2012
www.PosterPresentations.com
After a major outage of an e-book vendor in 2012 resulted in a lengthy cleanup project, UNR Libraries’ Discovery Services team began adding net check-in records to all e-book bibliographic records, linking e-book collections to corresponding ERM Resource records. This change facilitates easy identification of the scope of an e-book collection, provides a place to store contact and license information, and gives the Metadata & Cataloging Department a place to store MARC record loading notes and administrative information.
INTRODUCTION
Problems & frustrations before ERM
Implementation of ERM for e-books
44 new ERM resource records were created to represent e-book collections.
At the end of Phase 1, over 50,000 e-book bibliographic records were linked to ERM via attached check-in records.
License records are now being attached, as well as other vendor information.
Results
After ERM: Everything is connected!
RECOMMENDATIONS
Credits and Contacts
You will need the Electronic Resources Management module.
Get buy-in from all involved units.
You will need a cataloger with loader table training.
Use a consistent naming convention for different resource IDs so that it will be easy to match bibs to Resource Record.
Start small. Add one resource as a test, then expand the project
No place to track e-resource access problems for e-books.
No place for vendor tech support contact information.
No way to attach licensing information to e-books – which made it harder to diagnose access problems.
Didn’t pass the “bus” test. Information on e-book packages was saved in heads of individual staff, so if someone got hit by a bus no one would know how to proceed.
No place to attach general cataloging procedural notes – for example, which vendors offer individual bib records for their titles versus those that don’t.
Very difficult to know which titles to manage in Serials Solutions knowledgebase.
Performing updates to fix broken access and other collection maintenance took too much time. Never sure if all problems associated with an broken URL or other issue were caught in the process.
Mathewson-IGT Knowledge CenterUniversity of Nevada, Reno
Necessity is the Mother of Invention: Using ERM to Manage Electronic Books
Item record
Bibliographic record
E-book 1973 held pkg.
code
Item record
Bibliographic record
E-book 2973 held pkg.
code
Item record
Bibliographic record
E-book 3973 held pkg.
code
Invoice Recordsuppressed stub bib;
includes contact info for sales accounts,
not tech support
Order record
Before ERM: free-floating e-book records
Bibliographic Record
E-book 1
Net Check-in Record
Net Check-in Record
Net Check-in Record
License Record ERM Resource Record for
entire package of e-books
Vendor Contact Record
Order Record
Invoice Recordsuppressed stub bib
Item record
Bibliographic Record
E-book 3
Item record
Bibliographic Record
E-book 2Item
record
1. Determine how to find records for a particular subscription, whether a set of individual titles, or a package. What criteria?
2. Create a new ERM record to which new e-book type check-in records will be attached.
3. Find all e-book records for a particular resource using Create Lists function.
4. Export bib record number, e-book title (MARC field 245). Use txt file to create coverage load file.
5. Using ERM coverage loader, load against review file created in step 3.
6. Done!
1. When new e-book bibliographic records are received, the cataloger finds corresponding ERM record for the package.
2. The cataloger copies Resource ID information into 949 fields in e-book MARC records.
3. During load process, loader table produces new check-in records.
4. Done!
Phase 1: Existing E-book Records Phase 2: New E-book Records – General workflow
URLs for retrieving records, as well as login/password information and notes for MARC record retrieval are now stored in ERM.
All records can be found in the “Summary view” of the ERM record. No longer is there the need to run any review files to find them.
Maintenance of all phases of a package lifecycle can easily be shared by multiple departments in Technical Services.
Ticklers can be set in ERM to remind catalogers to check for new records.
LOGOLOGO
University of Nevada, LibrariesMathewson IGT Knowledge Center
Discovery Services Department Trish Tlapak [email protected] Wiley [email protected]