Status of the Standardized Usage Statistics Harvesting Initiative (SUSHI), Z39.93 Adam Chandler Cornell University Library NISO Update American Library Association Annual Conference June 29, 2008
Dec 30, 2015
Status of the Standardized Usage Statistics Harvesting Initiative
(SUSHI), Z39.93
Adam ChandlerCornell University Library
NISO UpdateAmerican Library Association Annual Conference
June 29, 2008
presentation outline
• Oliver’s “what is SUSHI/COUNTER” slides
• Results of May 2008 survey of COUNTER vendors
• Next steps
• Discussion
Timeline for usage related standards efforts
Slide courtesy of Oliver Pesch, EBSCO Information Services
Timeline for usage related standards efforts
Growing need for statistics which few vendors provided
Growing need for statistics which few vendors providedICOLC GuidelinesICOLC Guidelines
Credibility and consistency
problems
Credibility and consistency
problemsCOUNTER codes of practice
COUNTER codes of practice
Consolidation and reporting neededConsolidation and reporting neededUsage Consolidation
ModulesUsage Consolidation
ModulesGathering and
processing filesGathering and processing files
SUSHISUSHISUSHISUSHIsolutionsolution
Legendproble
mproble
m
Slide courtesy of Oliver Pesch, EBSCO Information Services
Why do librarians collect usage statistics?
• Because they must– Government and funding bodies may require them– Management asks for them– Industry associations expect them
• To inform renewal decisions– Overall use– Cost-per-use
• Support cancellation decisions• Generally manage e-resources and the tools and
programs that support them
Slide courtesy of Oliver Pesch, EBSCO Information Services
SUSHI: What it is and Isn’t
• What it is:– A web-services model
for requesting data• Replaces the user’s
need to download files from vendor’s website
– A request for data where the response includes COUNTER data• Using COUNTER’s
schema
• What it isn’t:– A model for counting
usage statistics– A usage consolidation
application
Slide courtesy of Oliver Pesch, EBSCO Information Services
COUNTER Codes of Practice
• Definitions of terms used
• Specifications for Usage Reports
– What they should include
– What they should look like
– How and when they should be delivered
• Data processing guidelines
• Auditing
• Compliance
Slide courtesy of Oliver Pesch, EBSCO Information Services
SUSHI : The Exchange
Report Request
<Requester>
<Customer Reference>
<Report Definition>
Report Response
<Requester>
<Customer Reference>
<Report Definition>
<Report as payload>
Slide courtesy of Oliver Pesch, EBSCO Information Services
Content ProviderLibrary
Internet
The Library’s consolidation client and Content Provider’s systems are both connected to the internet.
The Library’s consolidation client and Content Provider’s systems are both connected to the internet.
Slide courtesy of Oliver Pesch, EBSCO Information Services
Content ProviderLibrary
SUSHIClient
Internet
The SUSHI client is software that runs on the library’s server, usually associated with an ERM system.
The SUSHI client is software that runs on the library’s server, usually associated with an ERM system.
Consolidation client
Slide courtesy of Oliver Pesch, EBSCO Information Services
Content ProviderLibrary
SUSHIServer
(web service)
UsageData
SUSHIClient
Internet
ERM
The SUSHI server is software that runs on the Content Provider’s server, and has access to the usage data.
The SUSHI server is software that runs on the Content Provider’s server, and has access to the usage data.
Slide courtesy of Oliver Pesch, EBSCO Information Services
Content ProviderLibrary
SUSHIServer
(web service)
UsageData
SUSHIClient
Request
Internet
ERM
When the ERM system wants a COUNTER report, it sends a request to the SUSHI client, which prepares the request.
When the ERM system wants a COUNTER report, it sends a request to the SUSHI client, which prepares the request.
?
Slide courtesy of Oliver Pesch, EBSCO Information Services
Content ProviderLibrary
SUSHIServer
(web service)
UsageData
SUSHIClient
Request
Internet
ERM
The SUSHI request is sent to the Content Provider. The request specifies the report and the library the report is for.
The SUSHI request is sent to the Content Provider. The request specifies the report and the library the report is for.
?Request
Slide courtesy of Oliver Pesch, EBSCO Information Services
Content ProviderLibrary
SUSHIServer
(web service)
UsageData
SUSHIClient
Internet
ERM
The SUSHI server reads the request then processes the usage data.
The SUSHI server reads the request then processes the usage data.
?Request
Slide courtesy of Oliver Pesch, EBSCO Information Services
Content ProviderLibrary
SUSHIServer
(web service)
UsageData
SUSHIClient
Internet
ERM
The SUSHI server creates the requested COUNTER report in XML format.
The SUSHI server creates the requested COUNTER report in XML format.
?
COUNTER
Content ProviderLibrary
SUSHIServer
(web service)
UsageData
SUSHIClient
Internet
ERM
A response message is prepared according to the SUSHI XML schema.
A response message is prepared according to the SUSHI XML schema.
?
COUNTER
Response
Slide courtesy of Oliver Pesch, EBSCO Information Services
Content ProviderLibrary
SUSHIServer
(web service)
UsageData
SUSHIClient
Internet
ERM
The COUNTER report (XML) is added to the Response as its payload. The response is sent to the client.
The COUNTER report (XML) is added to the Response as its payload. The response is sent to the client.
?Response
COUNTER
Slide courtesy of Oliver Pesch, EBSCO Information Services
Content ProviderLibrary
SUSHIServer
(web service)
UsageData
SUSHIClient
Internet
ERM
The COUNTER report (XML) is added to the Response as its payload. The response is sent to the client.
The COUNTER report (XML) is added to the Response as its payload. The response is sent to the client.
?Response
COUNTER
Slide courtesy of Oliver Pesch, EBSCO Information Services
Content ProviderLibrary
SUSHIServer
(web service)
UsageData
SUSHIClient
Internet
ERM
The SUSHI client processes the response and extracts the COUNTER report.
The SUSHI client processes the response and extracts the COUNTER report.
?Response
COUNTER
Slide courtesy of Oliver Pesch, EBSCO Information Services
Content ProviderLibrary
SUSHIServer
(web service)
UsageData
SUSHIClient
Internet
ERM
The extracted COUNTER report is passed to the ERM system for further processing.
The extracted COUNTER report is passed to the ERM system for further processing.
COUNTER
Slide courtesy of Oliver Pesch, EBSCO Information Services
survey results
• 48 sent successfully in May 2008, 24 responses• 6 consolidators. (Thomson counts as content
provider and consolidator)• 18 content providers• survey monkey
– 10 questions– short answer, yes or no, multiple choice– list of contacts from Peter Shepherd, Director of
COUNTER
consolidators
name SUSHI 1.5 (Z39.93)?
product
Ex Libris Planned Q4 - 2008 ERM
Innovative Interfaces, Inc. In production with 0.1 and 1.0 today. Support for 1.5 planned Q3 2008
ERM
MPS Technologies Ltd In production with 0.1 and 1.0 today. Support for 1.5 planned Q4 2008
ScholarlyStats
Serials Solutions Planned Q3 – 2008 COUNTER 360
Scholarly iQ Planned Q4 - 2008 Optimal IQ product
Thomson Reuters Planned 2009 Journal Use Reports
content providers (part 1 of 3)
name SUSHI 1.5 (Z39.93)?
American Chemical Society Publications Division
Planned 2009
Annual Reviews Planned Q4 - 2008
EBSCO / EJS Already implemented
EBSCO / EBSCOHost ?
Gale - Cengage Learning Planned Q2 - 2008
HighWire Press, Stanford University Planned Q4 - 2008
Informa plc (Taylor & Francis Group, Informa Healthcare)
Planned 2009
content providers (part 2 of 3)
name SUSHI 1.5 (Z39.93)?
IOP Publishing Planned Q4 - 2008
Japan Science and Technology Agency No plans to implement
John Wiley & Sons Planned 2009
MetaPress Planned Q4 - 2008
ProQuest Planned Q3 - 2008
content providers (part 3 of 3) name SUSHI 1.5
(Z39.93)?S. Karger AG Planned Q4 - 2008
Swets In production with 0.1. Support for 1.5 planned for 2009
The Royal Society of Chemistry: Our statistics are produced by an external organisation - Coremetrics/SurfAid. We have been pushing then for implementation details and they have been holding off until the standard was agreed.
Thomson Reuters Planned 2009
William S Hein & Co., Inc. Planned 2009
World Engineering Xchange, Ltd. No plans to implement
recruit for committee
• Adam Chandler, Cornell (co-chair)• Oliver Pesch, EBSCO (co-chair)• Ted Fons, OCLC• Nettie Legace, Ex Libris• Bill Hoffman, Swets• ?• ?• ?
Sushi-Shokunin" ( 寿司職人 )
• We have identified a role that needs to be filled. • We are recruiting a few developers willing to monitor the
SUSHI developers list and help answer questions. In addition to the committee, our "Sushi-Shokunin" ( 寿司職人 ) will serve as part of the support team to help organizations to get online with SUSHI.
• Shokunin means artisan or craftsman; an expert sushi chef, a shokunin, can roll and cut six to eight sushi rolls in a ....
• So far:– Tommy Barker, Penn Library– John Batte, EBSCO
Coming soon…Release 3 of the Journals and Databases
Code of Practice
Key features…
• Consortium reports
• Sets expectations for handling of:
– Federated searching
– Internet robots and archives like LOCKSS
• Reports must be available in XML format
• Revised COUNTER XML Schema
• SUSHI support becomes a requirement for compliance
Slide courtesy of Oliver Pesch, EBSCO Information Services
Work!
• Hunker down and work hard for the next 12 months so we can get everybody synced across the supply chain!