SUSHISUSHI
SUSHI: SUSHI: Standardized Usage Statistics Standardized Usage Statistics
Harvesting InitiativeHarvesting Initiative
Oliver PeschOliver PeschTim JewellTim Jewell
NISO SUSHI Working GroupNISO SUSHI Working Group
ICOLC 2006
Philadelphia, PA
SUSHISUSHI
Overview
• Background– E-Resource Management Initiative– COUNTER (Release 2)
• With standards there are still problems
• SUSHI– Objective– The working group– The technology
SUSHISUSHI
DLF Electronic Resource Management Initiative
• ERMI ((original project completed 2004))– Detailed ERM functional requirements, data
dictionary, etc.– Some (but small) attention to usage data– Looked toward COUNTER development
• ERMI 2 (2006-2007) will focus on– License expression standards and training– Data Dictionary revision– Usage data intake and reporting requirements
SUSHISUSHI
COUNTER
• Member supported with members including: libraries; publishers; aggregators
• Formed in 2003
• Goal:– Allow credible and consistent usage
measurement between vendors
SUSHISUSHI
COUNTER Code of Practice
• Code of Practice first released Jan 2003
• Release 2 published Apr 2005
• Code of Practice Addresses:– Terminology– Layout and format of reports– Processing of usage data– Categories– Delivery of reports
SUSHISUSHI
COUNTER Usage Reports
• Journal Report 1: – Full Text Article Requests by Month and Journal
• Journal Report 2: – Turnaways by Month and Journal
• Database Report 1: – Total Searches and Sessions by Month and Database
• Database Report 2: – Turnaways by Month and Database
• Database Report 3: – Searches and Sessions by Month and Service
SUSHISUSHI
Clarify Consortium Requirements
• Only two reports apply:– Journal Report 1: Number of Successful Full-
Text Article Requests by Month and Journal– Database Report 1: Total Searches and
Sessions by Month and Database
• Vendor to provide (in separate files):– Aggregated reports for entire consortium– Individual reports for each member institute
• Aggregated reports includes totals for the whole consortium
SUSHISUSHI
COUNTER: Audit
• An audit must be passed for a vendor’s service to be compliant
• Deadline for initial audit is June 2007
• Conducted by auditor certified accountant or by organization accredited by COUNTER
• At vendor expense
SUSHISUSHI
COUNTER: Audit
• Audit will check each product and report for:– Layout
• Right rows and columns• Header rows• Column headings
– Formats• CSV or Excel
– Delivery of report • Email notification of availability• Access from password controlled web site
– Accuracy of data• Conduct series of tests for each report• Current tolerance is -8% to +2%
SUSHISUSHI
Usage Data Problems
• Expanding scope of E-resources
• Data proliferation (many content providers)
• COUNTER extremely helpful, but…
• Lack of standardized “containers”
• Time consuming to gather, assemble, report
• Hence, SUSHI (Standardized Usage Statistics Harvesting Initiative)
SUSHISUSHI
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
SUSHISUSHI
NISO SUSHI Working Group
• Adam Chandler (co-chair), Cornell• Oliver Pesch (co-chair), EBSCO• Ivy Anderson, California Digital Library• Patricia Brennan, Thomson Scientific• Ted Fons, Innovative Interfaces, Inc.• Bill Hoffman, Swets Information Services• Tim Jewell, University of Washington• Ted Koppel, Ex Libris
http://www.niso.org/committees/SUSHI/SUSHI_comm.html
SUSHISUSHI
SUSHI Contributing Partners
Founding Members:
• EBSCO• Ex Libris• Innovative Interfaces, Inc.• Swets Information
Services• Thomson Scientific
Newer members:
• Endeavor Information Systems
• Florida Center for Library Automation
• College Center for Library Automation (CCLA) from the State of Florida Community Colleges
• Otto Harrassowitz• OCLC• Project Euclid• Serials Solutions• SirsiDynix
SUSHISUSHI
Usage Consolidation
A new genre of application is being offered to assist with dealing with use
statistics. Usage Consolidation software is being offered by many ILS vendors and other service providers to
the library market.
A new genre of application is being offered to assist with dealing with use
statistics. Usage Consolidation software is being offered by many ILS vendors and other service providers to
the library market.
SUSHISUSHI
Usage ConsolidationERM
knowledgebase
Associated with these applications will be a knowledgebase that describes the e-resources (e.g. the databases and packages the library subscribes to and the titles contained within). Frequently this is the same knowledgebase
that controls a library’s ERM system.
Associated with these applications will be a knowledgebase that describes the e-resources (e.g. the databases and packages the library subscribes to and the titles contained within). Frequently this is the same knowledgebase
that controls a library’s ERM system.
SUSHISUSHI
Usage Consolidation
Import ERM knowledge
base
ConsolidatedUsage Data
Usage Usage Usage UsageUsage Usage
Content providers
An “import” function is used to collect usage from the library’s
content providers and accumulated in a central data storage
An “import” function is used to collect usage from the library’s
content providers and accumulated in a central data storage
SUSHISUSHI
Usage Consolidation
Import
Reports Interface
ERM knowledge
base
ConsolidatedUsage Data
Usage Usage Usage UsageUsage Usage
Content providers
ConsolidatedUsage reports
User
The customer uses a “Reports Interface”
which connects to the knowledgebase (to
select scope of report) and extracts the usage
to create the consolidated reports.
The customer uses a “Reports Interface”
which connects to the knowledgebase (to
select scope of report) and extracts the usage
to create the consolidated reports.
SUSHISUSHI
Usage Consolidation
Import
Reports Interface
ERM knowledge
base
ConsolidatedUsage Data
Usage Usage Usage UsageUsage Usage
Content providers
ConsolidatedUsage reports
User
However, the act of importing is not as
simple as “importing” the usage statistics
from content providers
However, the act of importing is not as
simple as “importing” the usage statistics
from content providers
SUSHISUSHI
ERM knowledge
base
Usage Consolidation
Import(manual)
Reports Interface ConsolidatedUsage Data
Usage Usage
Webinterface
ConsolidatedUsage reports
Usage UsageUsage
Webinterface
Usage
Webinterface
User
Content providers
The reality is that each content provider’s site must be accessed, reports requested and generated
then downloaded to the library and finally imported into the
application. Repeating this for each content provider is a great deal of
time and energy.
The reality is that each content provider’s site must be accessed, reports requested and generated
then downloaded to the library and finally imported into the
application. Repeating this for each content provider is a great deal of
time and energy.
SUSHISUSHI
ERM knowledge
base
Usage Consolidation
Import(manual)
SUSHI(automatic)
Reports Interface ConsolidatedUsage Data
Usage Usage
Webinterface SUSHI
ConsolidatedUsage reports
Usage
SUSHI
Usage
SUSHI
Usage
Webinterface
Usage
Webinterface
User
Content providers
The role of SUSHI is to allow the consolidation
application to leverage the knowledgebase, which
knows where usage can be obtained, to
automatically harvest the statistics without human
intervention.
The role of SUSHI is to allow the consolidation
application to leverage the knowledgebase, which
knows where usage can be obtained, to
automatically harvest the statistics without human
intervention.
SUSHISUSHI
Client
Server
Usage
SUSHI is machine-to-machine web service.
The usage consolidation application acts as the “client” and initiates a request. The content
provider hosts the “server” web service which fulfills the request and returns
the results.
SUSHI is machine-to-machine web service.
The usage consolidation application acts as the “client” and initiates a request. The content
provider hosts the “server” web service which fulfills the request and returns
the results.
SUSHISUSHI
Client
Server
Usage
reportRequest
•requestor
•customerReference
•reportDefinition
reportRequest
•requestor
•customerReference
•reportDefinition
The REQUEST is a simple XML structure and includes the following
basic elements:-The requester identifies the consolidation application (e.g. Innovative ERM).- The customerReference identifies the customer for which the usage is to be pulled. -The reportDefinitiion describes the report to pull and any parameters, such as the date range.
The REQUEST is a simple XML structure and includes the following
basic elements:-The requester identifies the consolidation application (e.g. Innovative ERM).- The customerReference identifies the customer for which the usage is to be pulled. -The reportDefinitiion describes the report to pull and any parameters, such as the date range.
SUSHISUSHI
Client
Server
Usage
reportRequest
•requestor
•customerReference
•reportDefinition
reportRequest
•requestor
•customerReference
•reportDefinition
The Content Provider’s server will verify that the customer referenced
has authorized the requestor to harvest reports on their behalf. Note that a standard security approach for
Web Services will be used to authenticate the requestor.The Content Provider then
processes the request and formats the XML response.
The Content Provider’s server will verify that the customer referenced
has authorized the requestor to harvest reports on their behalf. Note that a standard security approach for
Web Services will be used to authenticate the requestor.The Content Provider then
processes the request and formats the XML response.
SUSHISUSHI
Client
Server
Usage
reportRequest
•requestor
•customerReference
•reportDefinition
reportRequest
•requestor
•customerReference
•reportDefinition
reportResponse
•requestor
•customer
•reportDefinition
•reports
reportResponse
•requestor
•customer
•reportDefinition
•reports
The RESPONSE is an XML structure basically repeats the request (to allow the client to confirm that the response matches the request) and includes the “reports” element which encapsulates
the COUNTER report.
The report itself if formatted using the official COUNTER schema for reports.
This protocol is designed to be easily extended to harvest other reports.
The RESPONSE is an XML structure basically repeats the request (to allow the client to confirm that the response matches the request) and includes the “reports” element which encapsulates
the COUNTER report.
The report itself if formatted using the official COUNTER schema for reports.
This protocol is designed to be easily extended to harvest other reports.
SUSHISUSHI
Security Concerns
• SUSHI will use security layer for Web Services to secure the “connection”
• SUSHI clients must have credentials to access server
• SUSHI Client must declare who they are and also specify the library to retrieve usage for
• Server can implement system where library must grant permission for certain SUSHI client applications to access their usage
SUSHISUSHI
SUSHI Project Status
• Web site available
http://www.niso.org/committees/SUSHI/SUSHI_comm.html Overview, list of participants, toolkit, sample code, developer Overview, list of participants, toolkit, sample code, developer
listservlistserv
• Journal Report 1 Prototype doneJournal Report 1 Prototype done• Security “wrapper” doneSecurity “wrapper” done• First deployment completeFirst deployment complete• Memorandum of Understanding between NISO Memorandum of Understanding between NISO
and COUNTERand COUNTER
SUSHISUSHI
SUSHI Time-line
• July 2005 – Working group formed– Requirements drafted– Initial WSDL created
• Sep 2005– Conference call to kick-off development work
• Oct 2005– Initiative enters NISO standards track – Initiative is named SUSHI– Development underway at EBSCO, Swets, Innovative
and Ex Libris
SUSHISUSHI
SUSHI Time-line
• Nov 2005– Innovative and Ex Libris successful test pilot releases
of EBSCO and Swets
• Jan 2006– Security layer added
• Feb 2006– Innovative releases version of ERM which includes
SUSHI– NISO and COUNTER draft Memorandum of
Understanding
SUSHISUSHI
NISO/COUNTER ‘MOU’
• Memorandum of Understanding (draft)– NISO/SUSHI will act as maintenance agency
for COUNTER XML Schema– COUNTER remains in control of COUNTER
Guidelines– Vendor’s SUSHI compliance will be reflected
on COUNTER website
• Draft MOU will be presented to COUNTER Executive Committee in April 2006
SUSHISUSHI
SUSHI Next Steps
• Publicize, push for adoption by data providers • Write NISO “Draft Standard for Trial Use”• Conduct a series of Web-based seminars to
promote and educate• Organize NISO-sponsored stakeholder meeting
(late 2006) to gather input from trial use• Revise draft into “real standard”• Expand scope beyond Journal Report 1
(Database Reports likely next)• Seek endorsement by library community to expect
SUSHI compliance from content providers
SUSHISUSHI
Summary of Resources
• Project COUNTER– http://www.projectcounter.org
• COUNTER Auditing Requirements and Tests– http://www.projectcounter.org/r2/R2_Appendix_E_Auditing_Requirements_and_Tests.pdf
• SUSHI Web Site– http://www.niso.org/committees/SUSHI/SUSHI_comm.html
• JURO: Journal Usage Report Online– http://hkiug.ln.edu.hk/meetings/am2005/presentations/9-juro.ppt#1
Top Related