connecting e resource management systems and usage statistics l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Connecting E-Resource Management Systems and Usage Statistics PowerPoint Presentation
Download Presentation
Connecting E-Resource Management Systems and Usage Statistics

Loading in 2 Seconds...

play fullscreen
1 / 79

Connecting E-Resource Management Systems and Usage Statistics - PowerPoint PPT Presentation


  • 228 Views
  • Uploaded on

Connecting E-Resource Management Systems and Usage Statistics. IFLA ERMS Satellite Meeting Cape Town, South Africa August 16, 2007 Oliver Pesch EBSCO Information Services opesch@ebsco.com. Overview. Brief history of usage statistics for e-resources

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Connecting E-Resource Management Systems and Usage Statistics' - jana


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
connecting e resource management systems and usage statistics

Connecting E-Resource Management Systems and Usage Statistics

IFLA ERMS Satellite Meeting

Cape Town, South AfricaAugust 16, 2007Oliver PeschEBSCO Information Services

opesch@ebsco.com

overview
Overview
  • Brief history of usage statistics for e-resources
  • ERM systems are well suited for usage statistics
  • Reporting potential of the ERM
  • Challenges faced for successful reporting
  • COUNTER
  • SUSHI (Standardized Usage Statistics Harvesting Initiative)
  • Looking ahead
overview3
Overview
  • Brief history of usage statistics for e-resources
  • ERM systems are well suited for usage statistics
  • Reporting potential of the ERM
  • Challenges faced for successful reporting
  • COUNTER
  • SUSHI
  • Looking ahead
timeline5
Timeline

….

….

  • E-resource usage grows
  • online resources become significant
  • libraries need to measure use
  • not all vendors provide usage reports
  • reporting inconsistent
timeline6
Timeline

  • ICOLC Guidelines for usage released
  • consortia buying more e-resources
  • troubled by lack of consistent reporting
  • developed guidelines for usage reporting
  • normalized terminology
  • set expectations for vendor reporting
timeline7
Timeline

  • ICOLC Guidelines release 2
  • Refined guidelines
timeline8
Timeline

  • Project COUNTER formed
  • ICOLC guidelines helped, but…
  • Inconsistencies in counting and formatting
  • Libraries, publishers and aggregators formed COUNTER
  • Developed code of practice for…
  • Consistent, comparable and credible usage
timeline9
Timeline

  • COUNTER code of practice – release 1
  • Clarified terminology (consistent with other standards)
  • Addressed web log and double-click issues
  • Identified specific reports (journals and databases)
  • Specified formatting and delivery
timeline10
Timeline

  • ERMI Committee formed
  • Managing e-resources problematic
  • Many libraries developing their own solution
  • Committee formed to collaborate on the on the problem
  • Work sponsored by DLF
  • Final report published in 2004
timeline11
Timeline

  • First commercial ERM released
  • Innovative Interfaces, Inc.
  • Based on ERMI functional specifications
  • Served as a pilot to the ERMI work
timeline12
Timeline

  • SUSHI Committee formed
  • Consolidated usage reporting being added to ERM systems.
  • Based on COUNTER Journal Report 1
  • Effort to retrieve reports was great
  • Consistency issues continued
  • Standardized Usage Statistics Harvesting Initiative formed to automate and simplify
timeline13
Timeline

  • COUNTER code of practice release 2
  • Clarified formatting expectations
  • Added key data elements to reports
  • Introduced the need for an audit
timeline14
Timeline

  • SUSHI released as draft standard
  • Efforts sponsored by NISO
  • Successful pilots completed late 2005
  • Standard finalized in September 2006
  • Introduced as draft standard for trial use
timeline15
Timeline

  • SUSHI standard under ballot
  • Trial of standard was a success
  • Minor adjustments made to clarify and address concerns
  • Presented to ballot as Z39.93 in July
overview16
Overview
  • Brief history of usage statistics for e-resources
  • ERM systems are well suited for usage statistics
  • Reporting potential of the ERM
  • Challenges faced for successful reporting
  • COUNTER
  • SUSHI
  • Looking ahead
erms are suited for usage consolidation
ERMs are suited for usage consolidation
  • Intended to manage all e-resources
  • Intended as a single place to record all information about those resources
  • Tie-in to global knowledge bases
  • Data relationships
data relationships
Data relationships

Products

Hosts

Platform

E-journals

Hosts

includes

Packages/

Databases

includes

E-books

data relationships19
Data relationships

Publisher

Published by

E-journal

Platform

Hosted on

Included in

Hosted on

Package

data relationships20
Data relationships

Blackwell

Published by

Abacus

Synergy

Hosted on

Included in

BlackwellSynergyCollection

Included in

EBSCOhost

Hosted on

AcademicSearchPremier

data elements partial list
Data elements (partial list)
  • Descriptive information
    • Package names, resource names, etc.
  • Identifiers
    • ISSNs, ISBNs, package identifiers, etc.
  • Subject headings
  • URLs (link to resource)
  • Rights and restrictions for content use
  • Coverage information
  • Cost information
  • Usage information
  • And much more... (ERMI identified more than 300 data elements)
questions an erm can answer
Questions an ERM can answer
  • Which packages and databases are available from a given vendor?
  • Which resources are included with a database or package?
  • In which databases and packages will a given resource be found?
  • On what platforms (interfaces) can a database or package be accessed?
  • What databases or packages can be accessed on a given platform?
  • What resources can be accessed on a given platform?
  • What resources were included in a given deal?
    • From what vendor(s)?
    • On what platform?
overview23
Overview
  • Brief history of usage statistics for e-resources
  • ERM systems are well suited for usage statistics
  • Reporting potential of the ERM
  • Challenges faced for successful reporting
  • COUNTER
  • SUSHI
  • Looking ahead
erm systems and usage
ERM systems and usage

E-journal

Platform

Hosted on

data relationships25
Data relationships

Platform

Packages/

Databases

E-journals

Synergy

AcademicSearchPremier

Abacus

EBSCOhost

BlackwellSynergyCollection

full text usage reports
Full text usage reports
  • Which journals are most/least used in the collection
  • Report by platform, or
  • Aggregate usage across all platforms
  • Summarize by platform to determine the platforms generating the most full text views
data relationships27
Data relationships

Cost

Cost

Platform

Packages/

Databases

E-journals

Synergy

AcademicSearchPremier

Abacus

EBSCOhost

BlackwellSynergyCollection

cost analysis
Cost analysis
  • Combine usage with cost data
  • Cost per use is an indicator of value
    • The higher the use, the lower the cost per use
  • Assist with collection management
link out reports
Link out reports
  • Uses link resolver and A-to-Z activity
  • A quick view of how the collection is being used
  • Identify most productive sources of links
  • Identify most used targets
  • Does not require loading vendor usage (but neither is it comprehensive)
database reports
Database reports
  • Track searches and sessions
  • Discover which databases are being used
  • Use for marketing (perhaps patrons are not finding the databases)
  • Budget management
overlap analysis
Overlap analysis
  • Determine overlap between packages and databases
  • Includes coverage overlap as well as title overlap
  • Identify redundant packages or databases
  • Combined with usage data to determine which overlapping databases are most used
benchmark reports
Benchmark reports
  • Possible with hosted services
  • Compare a library with peer libraries
  • Collection analysis
  • Usage analysis
overview35
Overview
  • Brief history of usage statistics for e-resources
  • ERM systems are well suited for usage statistics
  • Reporting potential of the ERM
  • Challenges faced for successful reporting
  • COUNTER
  • SUSHI
  • Looking ahead
challenges
Challenges
  • COUNTER reports are key
    • Inconsistencies in formatting remain
    • Excel not the best format for loading into automated systems
  • Gathering and processing the reports is time-consuming
    • Many vendors
    • Many sites log in to
    • Many reports to pull
    • Many different procedures
challenges38
Challenges
  • COUNTER reports are key
    • Inconsistencies in formatting remain
    • Excel not the best format for loading into automated systems
  • Gathering and processing the reports is time-consuming
    • Many vendors
    • Many sites log in to
    • Many reports to pull
    • Many different procedures
  • Identifiers
overview39
Overview
  • Brief history of usage statistics for e-resources
  • ERM systems are well suited for usage statistics
  • Reporting potential of the ERM
  • Challenges faced for successful reporting
  • COUNTER
  • SUSHI
  • Looking ahead
slide40
Non-profit organization includes librarians, publishers and aggregators
  • Lead in the standardization of usage
    • How use is counted
    • How use is reported
  • “Consistent, credible, comparable”

http://www.projectcounter.org/

counter code of practice
COUNTER Code of Practice
  • Code of Practice first released Jan 2003
  • Release 2 released Jan 2006
  • Code of Practice Addresses:
    • Terminology
    • Layout and format of reports
    • Processing of usage data
    • Delivery of reports

http://www.projectcounter.org/code_practice.html

counter usage reports
COUNTER Usage Reports

Journal Reports:

  • JR1: Full Text Article Requests by Month and Journal
  • JR2: Turnaways by Month and Journal

Database Reports:

  • DB1: Total Searches and Sessions by Month and Database
  • DB2: Turnaways by Month and Database
  • DB3: Searches and Sessions by Month and Service

Books and Reference Works:

  • Title Requests, Section Requests, Searches and Turnaways
credible counter audit
“Credible” – COUNTER Audit
  • Effective now, an audit must be passed for a vendor’s service to be compliant
  • Conducted by auditor certified accountant or by organization accredited by COUNTER (ABCE)
  • At vendor expense
overview46
Overview
  • Brief history of usage statistics for e-resources
  • ERM systems are well suited for usage statistics
  • Reporting potential of the ERM
  • Challenges faced for successful reporting
  • COUNTER
  • SUSHI
  • Looking ahead
sushi objectives
SUSHI: Objectives
  • Solve the problem of harvesting and managing usage data from a growing number of providers.
  • Promote consistency in usage formatting (XML)
  • Automate the process
sushi what is it
SUSHI: What is it?
  • An XML Message
  • Methods to transfer the message between two systems
  • Implemented as a Web service
  • Using SOAP (Simple Object Access Protocol)
sushi the exchange
SUSHI : The Exchange
  • Report Request

<Requester>

<Customer Reference>

<Report Definition>

  • Report Response
    • <Requester>
    • <Customer Reference>
    • <Report Definition>
    • <Report as payload>
sushi architecture
SUSHI Architecture
  • The next series of slides graphically show a SUSHI transaction
    • Library system requests a usage report
    • SUSHI client makes the request
    • SUSHI server processes request
    • SUSHI server prepares COUNTER report
    • SUSHI server “packages” and returns response
    • SUSHI client processes COUNTER report
slide61

The Library and Content Provider’s systems are both

connected to the internet.

Library

Content Provider

Internet

slide62

The SUSHI client is software that runs on the library’s server, usually associated with an ERM system.

Library

Content Provider

ERM

Internet

SUSHI

Client

slide63

The SUSHI server is software that runs on the Content Provider’s server, and has access to the usage data.

Library

Content Provider

ERM

Internet

SUSHI

Client

SUSHI

Server

(web service)

Usage

Data

slide64

When the ERM system wants a COUNTER report, it sends a request to the SUSHI client, which prepares the request.

Library

Content Provider

?

ERM

Internet

Request

SUSHI

Client

SUSHI

Server

(web service)

Usage

Data

slide65

The SUSHI request is sent to the Content Provider. The request specifies the report and the library the report is for.

Library

Content Provider

?

ERM

Internet

Request

Request

SUSHI

Client

SUSHI

Server

(web service)

Usage

Data

slide66

The SUSHI server reads the request then processes the usage data.

Library

Content Provider

?

ERM

Internet

Request

SUSHI

Client

SUSHI

Server

(web service)

Usage

Data

slide67

The SUSHI server creates the requested COUNTER report in XML format.

Library

Content Provider

?

ERM

Internet

SUSHI

Client

SUSHI

Server

(web service)

COUNTER

Usage

Data

slide68

A response message is prepared according to the SUSHI XML schema.

Library

Content Provider

?

ERM

Response

Internet

SUSHI

Client

SUSHI

Server

(web service)

COUNTER

Usage

Data

slide69

The COUNTER report (XML) is added to the Response as its payload. The response is sent to the client.

Library

Content Provider

?

ERM

Response

Internet

SUSHI

Client

SUSHI

Server

(web service)

COUNTER

Usage

Data

slide70

The COUNTER report (XML) is added to the Response as its payload. The response is sent to the client.

Library

Content Provider

?

ERM

Response

Internet

SUSHI

Client

SUSHI

Server

(web service)

COUNTER

Usage

Data

slide71

The SUSHI client processes the response and extracts the COUNTER report.

Library

Content Provider

?

ERM

Response

Internet

SUSHI

Client

SUSHI

Server

(web service)

COUNTER

Usage

Data

slide72

The extracted COUNTER report is passed to the ERM system for further processing.

Library

Content Provider

ERM

COUNTER

Internet

SUSHI

Client

SUSHI

Server

(web service)

Usage

Data

sushi status of z39 93 200x
SUSHI: Status of Z39.93 200x
  • Trial period ended in May 2007
  • Successful implementations
  • A few minor technical adjustments made
  • Revisions to the standard have been finalized
  • Currently at ballot
overview74
Overview
  • Brief history of usage statistics for e-resources
  • ERM systems are well suited for usage statistics
  • Reporting potential of the ERM
  • Challenges faced for successful reporting
  • COUNTER
  • SUSHI
  • Looking ahead
timeline looking ahead
Timeline – looking ahead

  • SUSHI to be released as NISO Z39.93
  • Ballot closes early September
  • With approval, SUSHI should be a standard by the end of 2007
timeline looking ahead76
Timeline – looking ahead

  • COUNTER code of practice release 3under consideration…
  • Introducing specific consortium reports
    • XML based
    • One report with details for each member of the consortium
  • SUSHI support may become a requirement for COUNTER compliance.
looking ahead
Looking ahead
  • COUNTER
    • Consortium reports
    • Updated schema
    • New metrics and reports
  • SUSHI can be expanded to harvest other data
    • Holdings (ONIX SOH)
    • License terms (ONIX PL)
    • Financial terms
  • Tools and services to assist with data normalization
    • E.g. XISBN, XISSN projects from OCLC
sushi resources
SUSHI: Resources
  • 1999 ICOLC guidelines for usage statistics: http://www.clir.org/pubs/reports/pub94/appendixb.html
  • 2001 ICOLC Guidelines for Usage Statistics: http://www.library.yale.edu/consortia/2001webstats.htm
  • COUNTER Code of Practice web site: http://www.projectcounter.org/code_practice.html
  • SUSHI web site: http://www.niso.org/committees/sushi_com.html
  • ERMI DLF Report: http://www.diglib.org/standards/dlf-erm02.htm
  • NISO Newsline, Jan 2006: http://www.niso.org/news/newsline/NISONewsline-Jan2006.htm#Story3
  • XISBN home page: http://www.worldcat.org/affiliate/webservices/xisbn/app.jsp
sushi
SUSHI

Thank you!

Oliver Pesch

opesch@ebsco.com