NISO Standardized Usage Statistics Harvesting Initiative (SUSHI): Z39.93 Adam Chandler Cornell University Library Charleston Conference Charleston, SC November 6, 2008

SUSHI: What it is and Isnt What it is: –A web-services model for requesting data Replaces the users need to download files from vendors website What it isnt: –A model for counting usage statistics (that's what the COUNTER Code of Practice does) –A usage consolidation application

Content ProviderLibrary Internet The Librarys consolidation client and Content Providers systems are both connected to the Internet. Slide courtesy of Oliver Pesch, EBSCO Information Services

Content ProviderLibrary SUSHI Client Internet The SUSHI client is software that runs on the librarys server, usually associated with an ERM system. Usage Consolidation Client / ERM Slide courtesy of Oliver Pesch, EBSCO Information Services

Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Internet Usage Consolidation Client The SUSHI server is software that runs on the Content Providers server, and has access to the usage data. Slide courtesy of Oliver Pesch, EBSCO Information Services Usage Consolidation Client Usage Consolidation Client Usage Consolidation Client / ERM

Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Request Internet ERM 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 Usage Consolidation Client Usage Consolidation Client / ERM

Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Request Internet Usage Consolidation Client / ERM 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 SUSHI Server (web service) Usage Data SUSHI Client Internet ERM The SUSHI server reads the request then processes the usage data. Request Slide courtesy of Oliver Pesch, EBSCO Information Services

Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Internet ERM The SUSHI server creates the requested COUNTER report in XML format. COUNTER

Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Internet ERM A response message is prepared according to the SUSHI XML schema. COUNTER Response Slide courtesy of Oliver Pesch, EBSCO Information Services

Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Internet ERM 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 SUSHI Server (web service) Usage Data SUSHI Client Internet ERM 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 SUSHI Server (web service) Usage Data SUSHI Client Internet ERM The SUSHI client processes the response and extracts the COUNTER report. Response COUNTER Slide courtesy of Oliver Pesch, EBSCO Information Services

Content ProviderLibrary SUSHI Server (web service) Usage Data SUSHI Client Internet ERM The extracted COUNTER report is passed to the ERM system for further processing. COUNTER Slide courtesy of Oliver Pesch, EBSCO Information Services

COUNTER / SUSHI relationship DateStandardEvent January 2003COUNTERCode of Practice Release 1: Journals and Databases

COUNTER / SUSHI relationship DateStandardEvent April 2005COUNTERCode of Practice Release 2: Journals and Databases

COUNTER / SUSHI relationship DateStandardEvent February 2006NISO SUSHIVersion 0.1 of the SUSHI schema [proof of concept]

COUNTER / SUSHI relationship DateStandardEvent September 2006 NISO SUSHIVersion 1.0 of the SUSHI schema: Draft Standard for Trial Use, NISO Z X

COUNTER / SUSHI relationship DateStandardEvent October 2007NISO SUSHIVersion 1.5 of the SUSHI schema: ANSI/NISO Z

COUNTER / SUSHI relationship DateStandardEvent July 2008COUNTERCode of Practice Release 3: Journals and Databases

COUNTER / SUSHI relationship DateStandardEvent October 2008NISO SUSHIa) Version 3.0 of the COUNTER Code of Practice XML Schema; b) Version 1.6 of the SUSHI schema

May 2008 Survey Results survey monkey –10 questions –short answer, yes or no, multiple choice –list of contacts from Peter Shepherd, Director of COUNTER 48 sent successfully in May 2008, 24 responses 6 consolidators. (Thomson counts as content provider and consolidator) 18 content providers

consolidators ERM In production with 0.1 and 1.0 today. Support for 1.5 planned Q Innovative Interfaces, Inc. Journal Use Reports Planned 2009 Thomson Reuters COUNTER 360 Planned Q3 – 2008 Serials Solutions ScholarlyStats In production with 0.1 and 1.0 today. Support for 1.5 planned Q MPS Technologies Ltd ERM Planned Q Ex Libris productSUSHI 1.5 (Z39.93)? name

content providers (part 1 of 3) Q EBSCO / EBSCOHost Planned Q Annual Reviews Planned 2009Informa plc (Taylor & Francis Group, Informa Healthcare) Planned Q HighWire Press, Stanford University Planned Q Gale - Cengage Learning Already implementedEBSCO / EJS Planned 2009American Chemical Society Publications Division SUSHI 1.5 (Z39.93)? name

content providers (part 2 of 3) No plans to implementJapan Science and Technology Agency Planned Q ProQuest Planned Q MetaPress Planned 2009John Wiley & Sons Planned Q IOP Publishing SUSHI 1.5 (Z39.93)? name

content providers (part 3 of 3) In production with 0.1. Support for 1.5 planned for 2009 Swets No plans to implementWorld Engineering Xchange, Ltd. Planned 2009William S Hein & Co., Inc. Planned 2009Thomson Reuters 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. The Royal Society of Chemistry: Planned Q S. Karger AG SUSHI 1.5 (Z39.93)? name

Next steps Continue to refine documentation and support Track content provider implementations through COUNTER Code of Practice Release 3 compliance auditing process. Deadline is August 31, 2009

Committee membership Adam Chandler (co-chair), Cornell University Library Ted Fons, OCLC Tae Kim, Serials Solutions, Inc. Nettie Lagace, Ex Libris, Inc. Hana Levay, University of Washington Libraries Chan Li, California Digital Library Oliver Pesch (co-chair), EBSCO Information Services and lots of help from NISO staff

More information Web site: – Schemas: – Discussion List: –