ERM Implementation Team
Helgoth, Jobe, Wakimoto
for the update session: 2:00 pm,
Oct. 26, Location Engineering Conference Room (N410 in use that date for
cataloging workshop. E303 in use
for PWR). Plan shorter session for
an upcoming bibliographers meeting.
committee further discussed plans for the ERM update session. Issues that may be covered include:
does ERM stand for?
Resource Management—an Innovative module that interacts with other components
of the system.
explanation of the process
faced with new problems. No
first on the market with a product.
Partnered with U. Washington, UC San Diego, and others to
working to standardize systems www.diglib.org/pubs/dlfermi0408
ERM (the context)
the workflow diagram from report cited above. http://www.diglib.org/pubs/dlfermi0408/dlfermi0408appb.pdf
work of the committee to date
documents—minutes and definitions
record structure chart (relationships between resource, license, and
record for ArtStor. Show a couple of the fixed
fields to show how the contents of the fixed fields relate to documents
the committee is working on.
(Rights Type, Resource Status, and Full Text) Show contact record.
resource status DURING the demonstration
the choices made by different libraries.
Try to find examples for an A & I database, an aggregator, a
publisher’s package, and a full text database in other catalogs. (Yem has
personnel that can work on this.
We need to script. Look for
databases held by most libraries. Yem to send a
list of ERM libraries with URLs so that we can add to the ERM page on
To do list:
a blurb about the program
URLs for ERM Libraries. Script
sample scearches. (Yem?)
the local subject headings list with subjects from the Find Articles and
More page. (John?)
a contact record for the CU System (Yem)
Next meeting scheduled for October 19, 12:30, N410.