Electronic Resources Management
The home-grown perspective
Andrew K. Pace
Head, Systems
NCSU Libraries
andrew_pace@ncsu.edu
Classic Integrated System
MARC
Records
Patron
Records
WEBPAC
circ
transactions
serial
holdings
Serials
Control
Records
item
holdings
Acquisitions
Records
reserve
records
Patron
selfservice
• websites (856)
• e-books
• e-journals
• databases
• datasets
Dis-integrated Library System
• Licensing Files
alpha list of
databases
• ILL Files
• Collection Management Files
• Helpdesk Files
• Statistical Files
subject list of
databases web
subject
e-journal
guides
finder
Serials
Solutions
institutional
repository
alert
services
TDNet
SFX
Openly
Authentication
& Authorization
MyLibrary
• websites (856)
• e-books
• e-journals
• databases
NCSU Libraries E-Matrix
• July 1999 – NCSU “E-Shepherding”
specification written (and shelved)
• 2000-2002 – the square peg and round
hole era  “ERM” begins to emerge;
DLIF-ERMI takes shape
• Fall 2002 – electronic resources in the
catalog; E-Journal Finder; SFX; Licensing
database; Collection Management OASIS
database E-Matrix begins to emerge
Electronic Resource Management
• THE WEB HUB:
http://www.library.cornell.edu/cts/elicensestudy/
NCSU Libraries E-Matrix
An ad hoc committee charge
• The ad hoc E-Matrix Committee will
implement a prototype electronic
resources management system to
support acquisition and licensing,
collection management, and resource
discovery for the Libraries' electronic
resources [and all the print journals, too,
please]
E-MATRIX
statistics
technical
support
remote
access
evaluative
data
vendor
data
M
E
T
A
D
A
T
A
L
S
Website
Data
Repositories
Catalog
E
M
A
T
R
I
X
Evaluative
Tools
DATA
HOOKS
Other Databases:
E-journal finder
ETDs
Instn’l Repository
Etc.
LAYER
subscription info
I
PRESENTATION
licensing
A
D
M
I
N
I
S
T
R
A
T
I
V
E
E-resources
Alert Services
Local DBs &
Collections
Digital
Archives
E-matrix Challenges
• Public interface is
secondary concern
• Leveraging existing
data—all of it!
• Embrace the serial
work
• Workflow, Workflow,
Workflow
• Avoid solutions
looking for problem
Solve Only Known Problems
• Can the library ILL this pdf article?
• How do we manage subscription agent
changes?
• How does Acquisitions schedule renewals for
50 different providers?
• How do we represent an embargo period?
• How do I inform all the stake-holders in the
library any time there is a change?
• etc….
Some expected (and unexpected)
discoveries
• Non-standard data ain’t so bad (SFX KB,
acquisitions, serials, etc.)
• Standard data ain’t as good as you think it is
• There’s a reason no one has provided a
definitive solution for expressing the “serial
work”
• ERM strongly suggests radical changes to
technical services workflow
• There’s as much data about data as there is
data (at least it seems that way)
“It’s the seriality, stupid”
E-matrix / ERM Future
•
•
•
•
Taking the “E” out of E-matrix
Is the ILS superfluous?
Is MARC dead?
Will libraries or their vendors corner the
ERM market?
• Are we going to share the code?
• Would we do it again?
Yes, we would do it again
• The Serial Work
• Migration of / Interoperability with
existing data
• Putting our development dollars where
our collections dollars are
Thank you.
Andrew K. Pace
Head, Systems
North Carolina State University Libraries
andrew_pace@ncsu.edu
http://www.lib.ncsu.edu/staff/pace