15
Electronic Resources Management The home-grown perspective Andrew K. Pace Head, Systems NCSU Libraries [email protected]

Electronic Resources Management

  • Upload
    shino

  • View
    38

  • Download
    0

Embed Size (px)

DESCRIPTION

Electronic Resources Management. The home-grown perspective. Andrew K. Pace Head, Systems NCSU Libraries [email protected]. Classic Integrated System. MARC Records. Patron Records. Patron self-service. WEBPAC. circ transactions. websites (856) e-books e-journals databases - PowerPoint PPT Presentation

Citation preview

Page 1: Electronic Resources Management

Electronic Resources Management

The home-grown perspective

Andrew K. Pace

Head, Systems

NCSU Libraries

[email protected]

Page 2: Electronic Resources Management

Classic Integrated System

MARC Records

item holdings

serial holdings

Patron Records

circtransactions

reserve records

Acquisitions Records

• websites (856)

• e-books

• e-journals

• databases

• datasets

WEBPACPatron self-

service

Serials Control Records SERIA

LS!!!

!

Page 3: Electronic Resources Management

Dis-integrated Library System

• websites (856)

• e-books

• e-journals

• databases

alpha list of databases

subject list of databases

e-journal finder

Serials Solutions

TDNet

web subject guides

• Licensing Files

• ILL Files

• Collection Management Files

• Helpdesk Files

• Statistical Files

institutional repository

Authentication & Authorization

MyLibrary

alert services

SFX Openly

Page 4: Electronic Resources Management

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

Page 5: Electronic Resources Management

Electronic Resource Management

• THE WEB HUB:http://www.library.cornell.edu/cts/elicensestudy/

Page 6: Electronic Resources Management

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]

Page 7: Electronic Resources Management

licensing

statistics

subscript-ion info

technical support

remote access

evaluative data

PR

ES

EN

TA

TIO

N

LA

YE

R

ADMINISTRATIVE

METADATA

E-MATRIX

I

L

S

Other Databases:E-journal finderETDsInstn’l RepositoryEtc.

DATA HOOKS

Website

Catalog

E-resources

Alert Services

Local DBs & Collections

Digital Archives

DataRepos-itories

vendor data

Evaluative Tools

E-MATRIX

Page 8: Electronic Resources Management

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

Page 9: Electronic Resources Management

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….

Page 10: Electronic Resources Management

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)

Page 11: Electronic Resources Management

“It’s the seriality, stupid”

Page 12: Electronic Resources Management
Page 13: Electronic Resources Management

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?

Page 14: Electronic Resources Management

Yes, we would do it again

• The Serial Work

• Migration of / Interoperability with existing data

• Putting our development dollars where our collections dollars are

Page 15: Electronic Resources Management

Thank you.

Andrew K. Pace

Head, Systems

North Carolina State University Libraries

[email protected]

http://www.lib.ncsu.edu/staff/pace