ERMs and the E-Resource Life-Cycle
Gestione delle risorse elettroniche: l'offerta
del mercato e la situazione italiana.
Un'analisi sugli ERMS
Rome, March 27,2009
Oliver Pesch
EBSCO Information Services
[email protected]
Background of ERMs
• 2001 publication of Selection and Presentation of
Commercially Available Electronic Resources: Issues
and Practices by Timothy Jewell highlights the
problems with managing e-resources
• 2002 E-Resource Management Initiative (ERMI)
formed to allow librarians to collaborate with vendors
for commercial solutions
• 2004 ERMI report published with functional
specification for ERM systems
• 2004 first commercial ERM introduced
E-resource life cycle
License
terms
Libraries
Trial use
Order
Price
Assess
need/budget
Pay
Evaluate
Acquire
Evaluate
Monitor
Provide Support
Provide Access
Administer
E-resource life cycle
Libraries
IP addresses
Register
Proxy servers
Acquire
Catalogue
Evaluate
Monitor
Provide Access
A-to-Z lists
Link resolvers
Holdings lists
Provide Support
Administer
E-resource life cycle
Libraries
Acquire
Evaluate
Monitor
Provide Access
Holdings lists
Provide Support
Administer
User IDs
Admin module
information
Preferences
(store)
URL
Maintenance
Access
restrictions
Claiming
View rights for
use
E-resource life cycle
Libraries
Acquire
Evaluate
Monitor
Problem log
Hardware
needs
Software
needs
Contact info
Troubleshoot/
triage
Provide Support
Provide Access
Administer
E-resource life cycle
Libraries
User
feedback
Acquire
Usage stats
Downtime
analysis
Review
problems
Problem log
Evaluate
Monitor
Provide Support
Provide Access
Administer
E-resource life cycle
License
terms
Libraries
Trial use
Order
Price
Assess
need/budget
Pay
Evaluate
IP addresses
Register
User
feedback
Proxy servers
Acquire
Catalogue
Usage stats
Downtime
analysis
Review
problems
Evaluate
Monitor
Problem log
Hardware
needs
Software
needs
Contact info
Troubleshoot/
triage
Provide Access
A-to-Z lists
Link resolver
Holdings lists
Provide Support
Administer
User IDs
Admin module
information
Preferences
(store)
URL
Maintenance
Access
restrictions
Claiming
View rights for
use
E-resource life cycle
License
terms
New processes
Trial use
Order
Price
Assess
need/budget
Pay
Evaluate
Register
User
feedback
Proxy servers
Acquire
Catalogue
Usage stats
Downtime
analysis
Review
problems
Evaluate
Monitor
Problem log
Hardware
needs
Software
needs
Contact info
Troubleshoot/
triage
New
Existing
IP addresses
Provide Access
A-to-Z lists
Link
Link resolvers
resolver
Holdings lists
Provide Support
Administer
User IDs
Admin module
information
Preferences
(store)
URL
Maintenance
Access
restrictions
Claiming
View rights for
use
Deliverables/Outcomes from
ERMI
Deliverables
• Report
• Functional specifications
• Entity Diagram
• Data Dictionary
Outcomes
• Creation of a blueprint for
an ERM system
• The foundation of virtually
all commercial ERMs
• Innovative Interfaces Inc.
(ERM)
• Ex Libris (Verde)
• Serials Solutions (360 EResource Manager)
• EBSCO (ERM Essentials)
Common attributes of ERM
• Influenced by the ERMI specifications
• Act as a container for information needed to manage eresources
• Come with a “global” knowledge base to simplify
management of collections
• Facilitate end user access through an A-to-Z list and link
resolver
• Provide tools to help manage workflows
• Allow vendor usage reports to be tracked and consolidated
• Provide reporting and analysis tools
ERM Systems
License
terms
Features
Trial use
Price
Assess
need/budget
User
feedback
Usage stats
Evaluate
Acquire
•One place to store information
Evaluate
Monitor
Problem log
Hardware
needs
Software
needs
Contact info
Troubleshoot/
triage
Tracking
Pay
IP addresses
Register
Downtime
analysis
Review
problems
Manage
Order
Provide Access
Proxy servers
Catalogue
A-to-Z lists
Link resolvers
Holdings lists
Provide Support
Administer
User IDs
Admin module
information
Preferences
(store)
URL
Maintenance
Access
restrictions
Claiming
View rights for
use
ERM Systems
License
terms
Features
Trial use
Price
Assess
need/budget
User
feedback
Usage stats
Order
Pay
Evaluate
Register
Acquire
•One place to store information
Evaluate
•A single
knowledge base
for
Provide Access
Monitor
access tools
Downtime
analysis
Review
problems
Problem log
Hardware
needs
Software
needs
Contact info
Troubleshoot/
triage
Manage
Tracking
IP addresses
Proxy servers
Catalogue
A-to-Z lists
Link resolvers
Holdings lists
Provide Support
Administer
User IDs
Admin module
information
Preferences
(store)
URL
Maintenance
Access
restrictions
Claiming
View rights for
use
ERM Systems
License
terms
Features
Trial use
Order
Price
Assess
need/budget
Pay
Evaluate
IP addresses
Register
User
feedback
Acquire
•One place to store information
Evaluate
•A
single
knowledge base
for
Downtime
Provide Access
Monitor
analysis
access tools
Review
problems•Workflows for trials, renewals, etc.
Usage stats
Problem log
Hardware
needs
Software
needs
Contact info
Tracking
Manage
Troubleshoot/
triage
Provide Support
Proxy servers
Catalogue
A-to-Z lists
Link resolvers
Holdings lists
Administer
User IDs
Admin module
information
Preferences
(store)
URL
Maintenance
Access
restrictions
Claiming
View rights for
use
ERM Systems
License
terms
Features
Trial use
Order
Price
Assess
need/budget
Pay
Evaluate
IP addresses
Register
User
feedback
Acquire
•One place to store information
Evaluate
•A
single
knowledge base
for
Downtime
Provide Access
Monitor
analysis
access tools
Review
problems•Workflows for trials, renewals, etc.
•Problem logging
Problem log
Usage stats
Provide Support
Hardware
needs
Software
needs
Contact info
Tracking
Manage
Troubleshoot/
triage
Proxy servers
Catalogue
A-to-Z lists
Link resolvers
Holdings lists
Administer
User IDs
Admin module
information
Preferences
(store)
URL
Maintenance
Access
restrictions
Claiming
View rights for
use
ERM Systems
License
terms
Features
Trial use
Order
Price
Assess
need/budget
Pay
Evaluate
IP addresses
Register
User
feedback
Acquire
Proxy servers
•One place to store information
Catalogue
Evaluate
A-to-Z lists
•A
single
knowledge
base
for
Downtime
Provide
Access
Monitor
analysis
access tools
Link resolvers
Review
problems•Workflows for trials, renewals, etc.
Holdings lists
•Problem logging
Problem log
Support
Administer
•UsageProvide
consolidation
& reporting User IDs
Usage stats
Hardware
needs
Software
needs
Contact info
Tracking
Manage
Troubleshoot/
triage
Admin module
information
Preferences
(store)
URL
Maintenance
Access
restrictions
Claiming
View rights for
use
Challenges Remain
• Data required to manage e-resources is complex
• Locating the data is difficult
• The amount of information is immense making input a
challenge (ERMI defined over 300 fields)
• Keeping that information up-to-date is also a challenge
Standards and other initiatives to
solve remaining problems
•
•
•
•
•
E-Resource Management Initiative – 2 (ERMI-2)
Cost Of Resource Exchange (CORE)
ONIX for Publication License (ONIX-PL)
Better integration with the supply chain
Simplification of processes
References
• CORE http://www.niso.org/workrooms/core
• Electronic Resource Management Initiative (ERMI-2),
http://www.diglib.org/standards/dlf-erm02.htm
• ONIX-PL Working Group
(http://www.niso.org/workrooms/onixpl)
• Selection and Presentation of Commercially Available
Electronic Resources: Issues and Practices, Timothy
Jewell, CLIR Report, 2001,
http://www.clir.org/pubs/reports/pub99/pub99.pdf)
Thank you