Standards in E-Resource Management
JISC Seminar on Standards and the Information Chain, 7th December
Robert BleySales Account Manager
Ex Libris
E-Resource Management
An E-Resources Management System: the vision
“ A system that supports management of the information and workflows necessary to efficiently select, evaluate, acquire, maintain, renew/cancel and provide informed access to e-resources in accordance with their business and license terms”
- Ivy Anderson, Robin Wendler (Harvard University Library) and Ellen Duranceau (MIT Libraries)
E-Resource Management
ERM: A staff tool that deals with…Relationships
Interfaces, Packages, and their constituent partsKnowing which resources share the same interface, license terms, business terms …
InformationLicense permissions and constraintsUser IDs, passwords, administrative infoContacts for support and troubleshootingCancellation restrictions, price caps, etc.
WorkflowsTrialsRenewals/cancellationsImplementing accessNotifying relevant staff
…according to the DLF ERMI “standard”
E-Resource Management
Basic ERM Data ElementsElement Includes data points
such as….
Descriptive Title fields, holdings, publisher, ISSN, interface, package…
Licensing Authorized users, ILL rights, archiving rights…
Financial Price, price cap, relationship to print…
Administrative and Support
Administrative password, vendor contact information…
Access Authorization method
E-Resource Management
The bottom line:
ERM is about more than statistics and licenses
ERMs are (or will become) the library’s corporate memory for all factors related to electronic resources at all levels
In filling that role, ERMs become central to all process and all services within the library
Interoperability with ERMs is vital for all players in the information chain – including publishers
E-Resource Management
Why ERM? (Management View)
Manage lifecycle events for e-productsFinancial management and audit-abilityTool to centrally store and maintain contracts, licenses, other raw documentsRationalize ER processing and related proceduresSearch, retrieve, report across management attributesHarvest, calculate, apply user and financial statisticsSupport consistent workflows to support data qualityEnsure compliance with license terms!
E-Resource Management
The bigger picture
Legacy systemsSerialsAcqHomegrown ERMLicensingILLOPAC Spreadsheets & paper records
ERM’s roleProcess managementLink Server interactionILL / resource sharingBusiness transactionFinancial system interoperabilityPermission authorityCentral and integrated
E-Resource Management
ERMs today touch many different areas
Authentication
Acquisitions
OPACs
Link resolvers
Campus Finance Systems
ILL Management
Serials
Library Web Applications
Metasearch
Content providers (& agents?):
•Statistics
•Holdings
•Licenses
•Orders, Renewals
•Help Desk
VLEs
E-Resource Management
And the current ILS model is …
E-Resource Management
Dis-integrating, or perhaps
E-Resource Management
Re-forming around a new model
E-Resource Management
What we can expect?
Discovery and delivery tools will become more distinct from ILS/LMS in presentation and function
ERMs will feed just-in-time data to any public service applications (including discovery, link resolvers, metasearch, library web apps, VLEs and institutional portals)
ERMs will eventually subsume (and then, expand on) large portions of Acq and Serials functionality and responsibility
EDI is not enough…
E-Resource Management
What we can expect (2)
As the notion of an ILS morphs, interoperability among the ERM and other vendors’ systems becomes essential – not just for management, but also because …
Library efficiency measures and statistics will assume a streamlined management process (whether true or not), and interoperability with other institutional and external systems
E-Resource Management
What we can expect (3)
Increased demand on content providers from ERMs and libraries for rapid implementation of SUSHI, License Expression transmission, etc.
Increased transparency from content providers on pricing (esp. titles within packages) for meaningful cost-per-use numbers
E-Resource Management
Top 7 Standards Wish List
7. Standard for communicating IP address changes to content providers
6. Standard for vendors to communicate real-time availability (that is, advise when you’re down and when you’re back up)
5. A sub-library level unique library identifier – something like the SAN but international in scope. ISO 15511 (ISIL) doesn’t do it …
4. A unique collection identifier for aggregations and databases: like an ISBN per e-package
E-Resource Management
Wish List…
3. ACQUISITIONS – a set of standard structures that would encapsulate elements relevant to an acquisitions transaction:
Order recordInvoice recordVendor information (selected)
X.12 and current EDI doesn’t do the job
E-Resource Management
Wish List
2. SUSHIhttp://www.niso.org/committees/SUSHI/SUSHI_comm.html
- Will enable evidence-based librarianship
E-Resource Management
Wish List
1. License exchange formathttp://www.editeur.org/onix_licensing.html
-Will make it easier to tell users what they can(‘t) do
-Will ensure compliance – linked to link resolvers, proxy servers and so on…
-Will make for easier comparisons-Will reduce ambiguity-… and paperwork! - There may be a role for intermediaries here?
E-Resource Management
Other vendor <--> library transmissions?Publisher to Library
Suspected license breach communications to libraryInteraction with library financial systems on pay-per-use titlesNon-e-journal and non-e-book identification and electronic delivery (for instance, patents, technical reports, digital objects)
Library to PublisherCustomer incident reporting to publisher when resource misbehavesLicense expression delivery/receipt with library-based changes (versioning)
E-Resource Management
In conclusionE-products have changed the priorities for standards in data interchange
Previous models for automated library management are changing, largely because of e-products
The ERM will is the nexus/crossroad/bridge between libraries and the e-product world
The ERM will ultimately supplant the ILS for many (perhaps even most) back-room functions (my opinion :-) )
Content providers will need to exchange data with such systems
The top priorities are (1) the electronic expression of license terms and (2) the automation of COUNTER stats collection