Overview of III’s Electronic Resources Management system

Tony Harvell

tharvell@ucsd.edu

March 11, 2004

ERM record structures

• Resource record – describes resource– Contacts information– Holdings information at title level are linked to

these

• License record – uses some of the DLF definitions in fixed or variable fields

• Order record – payment information• Holdings record – holdings statement in MARC

or non MARC format

Records are linked by relationship

• The holdings record for a particular title is linked to a resource record that represents the provider

• Holdings records remain attached to full bibliographic records

• A separate holdings record is often created for each provider (resource)

• Order (payment information) can be linked to a resource record

Example of Resource Record

Example of license record

License and resource records

• Uses many of the DLF elements

• Has a number of locally defined fields

• Data is stored in both fixed and variable fields

• Labels are being redefined to more closely match DLF language

E holdings load

• Allows libraries to load data (text or XML) from vendors or exported data from an ILS

• ERM can create new holdings and/or bibliographic records, if no matching record is found during the electronic holdings load

• In batchloading from XML, ERM uses metatags to associate with field tags from Millennium

Coverage database

• Allows e-holdings information to reside in a discreet portion of the system as opposed to within a bib record 856 or separate holdings record

• Can be created locally by outputting text files or xml files and using e-holdings load

• Allows easy update of holdings information by matching on ISSN, then on another match point (resource ID)

Displaying information in OPAC

• Can choose which fields from resource and license record to display to the public

• Ability to insert a “resource advisory” to alert users of inability of a resource at the title level

• WWWoptions and stylesheets allow customization of display for local needs