icolc use data webinar episode 3

ICOLC Use Data WebinarEpisode 3

TANSY MATTHEWSJULY 2010

SUSHI

From the NISO website:

The Standardized Usage Statistics Harvesting Initiative (SUSHI) Protocol standard (ANSI/NISO Z39.93-2007) defines an automated request and response model for the harvesting of electronic resource usage data utilizing a Web services framework. It is intended to replace the time-consuming user-mediated collection of usage data reports.

The protocol was designed to be both generalized and extensible, meaning it could be used to retrieve a variety of usage reports. An extension designed specifically to work with COUNTER reports is provided with the standard, as these are expected to be the most frequently retrieved usage reports.

The standard is built on SOAP (Simple Object Access Protocol) for transferring request and response messages. The GetReport method is used for transferring ReportRequest as the input message and returning ReportResponseas the output message.

The standard includes a versioned Web Services Description Language (WSDL), to describe the Web service namespace and operations, and a generalized XML schema with the syntax of the SUSHI protocol. Rules for report naming are outlined and complemented by an external reports registry, which provides for the definition of both COUNTER and non-COUNTER reports.

SUSHI Translated (sort of)

SUSHI establishes a standardized format for the DELIVERY of use data, which means that harvesting the use data can be automated.

How SUSHI works

ERMLocal SUSHI client

Developments

PRO: Serials Solutions developed an open-source SUSHI client called MISO

CON: Still needed someone who could make it work.

CON: Not practical for consortia harvesting use data for many institutions.

Things coming together

CR1 began causing problems – simply too large

Possible solution – develop a means to use MISO to batch download individual JR1s for all consortia members.

Unnamed Batch Download Tool

Developed by Oliver Pesch at EBSCO.

Feeds a list of a consortia’s members, with login credentials, to a vendor’s SUSHI server. COUNTER reports are batch-downloaded to a specified directory.

Since they’re XML files, they can then be loaded directly into Excel.

Command Line Version

Library CodeProvider NameRelease URL Requestor IDRequestor NameRequestor E-MailCustomer IDCustomer Name JR1 DB1 DB2(Not yet Supported)AU Bioone 3 http://www.bioone.org/api/soap/analytics/SushiServiceviva@gmu.edu? ? 1234 Averett University y n nBRCC Bioone 3 http://www.bioone.org/api/soap/analytics/SushiServiceviva@gmu.edu? ? 2345 Blue Ridge Community College y n nCNU Bioone 3 http://www.bioone.org/api/soap/analytics/SushiServiceviva@gmu.edu? ? 3456 Christopher Newport University y n nCVCC Bioone 3 http://www.bioone.org/api/soap/analytics/SushiServiceviva@gmu.edu? ? 4567 Central Virginia Community Collegey n nCWM Bioone 3 http://www.bioone.org/api/soap/analytics/SushiServiceviva@gmu.edu? ? 5678 College of William and Mary y n nDCC Bioone 3 http://www.bioone.org/api/soap/analytics/SushiServiceviva@gmu.edu? ? 6789 Danville Community College y n nDSLCC Bioone 3 http://www.bioone.org/api/soap/analytics/SushiServiceviva@gmu.edu? ? 7890 Dabney S. Lancaster Community Collegey n n

Config file

Command LineHARVEST command downloads the specified COUNTER report from the specified vendor for all institutions listed in the config file.

The downloads for VIVA take a matter of minutes.

Command LineFiles are saved in a specified directory.

Because they are XML files, they can be loaded directly into an Excel spreadsheet or Access database, whichever you prefer.

XML Reminder

SUSHI delivers all reports in XML, so they can be loaded directly into Excel or Access.

Status check

GUI interface is in first stages of testing.

Command line interface seems to be working well.

Questions?tmatthe6@gmu.edu