erm implementation at unc wilmington’s randall library

ERM Implementation at UNC Wilmington’s

Randall Library

Dan Pfohl, Associate University Librarian for Computing Services

Arlene Hanerfeld, Associate University Librarian for Technical & Collection Services

Rebecca Kemp, Serials Supervisor

August 28, 2007Regional Center Pembroke, NC

What is ERM / what does ERM do?Central database to hold information about e-

resources Contact record

Company name, address, contact name, address, phone, e-mail

Resource record Resource name, URL, administrative info, resource

format, resource advisory, usage statistics License record

Authentication method, number of concurrent users, perpetual access, permitted & restricted usage

Coverage information and usage information

Why use ERM? Gather information into one central location Present journal coverage in catalog Link from journal title to provider title Show in the catalog which resources may / may not

be ILL-ed Track negotiations about resources (e.g., trials) Manage incidents for resources (e.g., outages) Manage SSL, domain name subscriptions Interface with WebBridge?

What does it look like in the catalog?

Here’s a preview of what we’ll be talking about for the next few hours...American Imago in UNCW’s catalog

Consortial ERM Implementation

How ERM implementation differs for a single site vs. a consortium

Consortial meetings to discuss decisions that affect all concerned parties.

Getting started: Making Decisions (UNCP & FSU)

UNCP implementation plans FSU implementation plans

Getting started: Making Decisions

Assigning values to customizable fixed length and variable length fields

Deciding what will be displayed in OPAC Deciding whether to continue to use bib records

for e-resources, or just resource records, or some combination

Getting started: Making Decisions (cont’d)

Should resource name should be indexed? Where to attach order records – bib record or

resource record? Coverage Load: Brief Bib vs. Full MARC Record

Making Decisions: Resource fixed-field codes

Making Decisions: Resource variable-field codes

Getting Started: ERM Resources Millennium Manual

Link from Millennium or http://csdirect.iii.com/documentation/references/

CSDirect http://csdirect.iii.com/ Presentations (by Innovative staff) FAQ’s - ERM Tutorials - CASE

Innovative Users Group website http://www.innopacusers.org/ Includes IUG Clearinghouse and presentations

Getting Started: ERM Resources, cont’d. ERM listserves

[email protected] Listserv archives: http://listserv.iii.com

/read/?forum=erm

WebEx training with Innovative staff Entitled to 1 session

Getting Started: Organizing information Documentation for the choices we have

made Keeping together information sources

(recommend keeping a binder) Manual other people’s presentations meeting minutes relevant listserv posts

ERM Record Relationships

Arlene, can you find the image that you had in mind for the different record relationships?

UNCW’s Contact Record

UNCW’s Resource Record

ERM Quick Start Resource Record Supplied by Innovative

Science Direct Resource Record

Tickler Logs

Email Tickler

UNCW’s License Record

ERM Records, Multi Line Field Labels

Useful for prompted input, ease of reading, formatted output.

Innovative must define field as multi line,ORCoordinator can define, if ASAA trained.

Set up in -MilAdmin | ASAA | Multi line field labels

ERM Records, Multi Line Field Labels:

ERM Records, Multi Line Field Labels:

Notes:

Creation of and changes to multi line profile are not retroactive!

Must start new MilERM session to see changes.

Always enter VENDOR NAME for the LABEL 1 element of the vendor record ADDRESS1 field.

ERM Records, Multi-Value Variable-Length Fields:Useful for profiling specific text

– aids consistent OPAC display – Aids in data input and retrieval

Innovative must define field as multi-value.Local user must have authorization for function 686 to edit values.

Edit values in – MilERM or MilAdmin Admin | Parameters | ERM

ERM Records, Multi-Value Variable-Length Fields:

ERM Records, Multi-Value Variable-Length Fields:

Notes:

Must start new MilERM session to see changes.

Use semi-colon (;) to add multiple entries to single field.

Break For Lunch.

We’ll continue after we return with live demonstrations.

OPAC display:

OPAC display, continued:

OPAC display, continued:#ERM Record on bib displaye|t|||Resource Name||e|e|x|||Alternate Resource Name||e|e|e|||Description||e|e|u|||Trial Information||e|e|g|||User Support||e|e|f|||Public Note||e|#e|s|||Pricing & Payment||e|e|w|||||e|e|v|||Resource Type||e|e|b|||Resource Format||e|e|h|||Coverage||e|#

Webpub.def determines which fields can display and the order in which they display.

Entry syntax explained at #106853

Resource_display.html controls the display (layout) of resource records.

<div id="infoTable"><div style="text-align:right;font-size:85%;padding-right:5px;"></div><div style="padding:2px 0px 2px 25px;width:95%;">

OPAC display, continued:Tokens:

Examples on handouts

Bib_display.html tokens listed at #106854

Resource_display.html tokens listed at #107106

{holdings} in bib_display.html

{recordinfo} in resource_display.html

{recordlink} resource_display.html


CSS Files:

Styles.css and ie_styles.css

Selected styles on handout

Use Firefox plug-in (Firebug) to discover CSS classes and values

.resourceBibEntry { color: #000000; background: #FFF8EF; text-align: left; }

.resourceBibHeader { color: #FFFFFF; background: #00437f; font-weight: bold; text-align: left; }

.resourceInfoData { }

.resourceInfoLabel { background: #FFF8EF; font-style: italic; }

.resourceLicense { }

.resourceLicenseEntry { color: #000000; background: #FFF8EF; text-align: left; }

.resourceLicenseHeader { color: #FFFFFF; background: #00437f; font-weight: bold; text-align: left; }

OPAC display, continued:.resourceBibEntry { color: #000000; background: #FFF8EF; text-align: left; }

.resourceBibHeader { color: #FFFFFF; background: #00437f; font-weight: bold; text-align: left; }

.resourceInfoData { }

.resourceInfoLabel { background: #FFF8EF; font-style: italic; }

.resourceLicense { }

.resourceLicenseEntry { color: #000000; background: #FFF8EF; text-align: left; }

.resourceLicenseHeader { color: #FFFFFF; background: #00437f; font-weight: bold; text-align: left; }


Web Options for ERM:

•BIB_LICENSE_FIELDS

•BIB_LICENSE_FIELDS_BRIEF

•BIB_RESOURCE_CAPTION

•BIB_RESOURCE_FIELDS

•BIB_RESOURCE_FIELDS_BRIEF

•BIB_RESOURCE_NUM_BRIEF


•ICON_BIB_RESOURCE_DETAILS

•ICON_RESOURCE_RECORD

•ICON_VIEW_ADDITIONAL_ITEMS


•RESOURCE_ADVISORY

•RESOURCE_HOLDINGS_FIELDS

•RESOURCE_HOLDINGS_MAX

•RESOURCE_LICENSE_FIELDS


•TABLEPARAM_BIB_LICENSE

•TABLEPARAM_BIB_RESOURCE

•TABLEPARAM_BIB_RESOURCE_BRIEF

•TABLEPARAM_RESOURCE_BIB

•TABLEPARAM_RESOURCE_LICENSE

•TABLEPARAM_RESOURCE_RESOURCE

Live Demonstration

Building Contact, Resource, and License Records

Using Create Lists Usage Statistics

Scholarly Stats CASE coverage service description

Using Create Lists to Find UNCW Resource Records

Statistical Reports

ERM Usage Statistics (from Ted Fons’ presentation) – Can only get CPU if you automatically import statistics

Title Comparison Report26 titles appear in more than 1 resource

New Procedure: Coverage Load

How coverage load works, part I Configure spreadsheet conversion rules in ERM

Admin Set up resource record for the desired resource, set

the Provider ID (and affiliation, for consortial implementations)

Set up templates for creation of new checkins, brief bibs during coverage load process

Obtain coverage spreadsheet from journal database provider / use Serials Solutions coverage data

Format spreadsheet for coverage load

New Procedure: Coverage Load, cont’d. How coverage load works, part II

Batch input spreadsheet data into ERM coverage load module

Coverage load module creates and populates checkin records for titles in spreadsheet (Matching algorithm can be found in Manual page 106010)

Coverage information displays in the OPAC Coverage load data is stored for future use in the

Coverage Edit database Look at error report to see holdings that did not affix

properly, fix and re-run

Coverage Load, continued: Coverage Spreadsheet Conversion Rules

Coverage Load, continued: Checkin Record template

Coverage Load, continued: Spreadsheet of holdings

Coverage Load Spreadsheet Data Elements (part I)

See page 105561 of the manual

PROVIDER (e.g., Blackwell) ISSN (e.g., 1398-9995) TITLE (e.g., Allergy) URL (e.g.,

http://0-www.blackwell-synergy.com.uncclc.coast.uncwil.edu/openurl?genre=journal&stitle=ach

) ENUMCAPTION1 (e.g., v.) ENUMSTART1 (e.g., 5) ENUMCAPTION2 (e.g., no.)

Coverage Load Spreadsheet Data Elements (part II)

ENUMSTART2 (e.g., 1) START_DATE (e.g., 1990) ENUMEND1 (e.g., 10) ENUMEND2 (e.g., 4) END_DATE (e.g., 2000) EMBARGO (e.g., 3 years) ALTLOOKUP (e.g., b19313305)

Coverage Load, continued: Coverage Load

Coverage Load, continued: Error Report

Coverage Load, continued: Coverage Edit

Coverage Load, continued: A finished checkin record

Coverage Load, continued: Brief bibliographic record elements

UNCW’s Implementation: OPAC display

UNCW’s Implementation: OPAC display, continued

Concluding thoughts: Workflow changes Division of labor at UNCW straightforward

Dan Pfohl: maintains all the systems capabilities and is our Innovative contact person

Arlene Hanerfeld: inputs all resource and license records

Rebecca Kemp: maintains holdings information and runs coverage load process

Concluding thoughts: Unexpected challenges

Purchasing an additional module to allow for a consortium to use ERM software

Coverage load database issues Time needed CASE products WebBridge in a consortium

Questions? Discussion?

Thank you for attending!

Presenter Contact InformationDan Pfohl

[email protected]

Arlene Hanerfeld

[email protected]

Rebecca Kemp

[email protected]

erm implementation at unc wilmington’s randall library

Documents

resource records

resource format

resource advisory

decisions contdshould

bib records

order records bib record

field codesmaking decisions

erm webex training