NISO Standardized Usage Statistics Harvesting Initiative SUSHI: Z39.93

1
NISO Standardized Usage Statistics Harvesting
Initiative (SUSHI) Z39.93

• Adam ChandlerCornell University Library
• Charleston Conference
• Charleston, SC
• November 6, 2008

2
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

3
The Librarys consolidation client and Content
Providers systems are both connected to the
Internet.
Content Provider
Library
Internet
Slide courtesy of Oliver Pesch, EBSCO Information
Services
4
The SUSHI client is software that runs on the
librarys server, usually associated with an ERM
system.
Content Provider
Library
Usage Consolidation Client / ERM
Internet
SUSHI Client
Slide courtesy of Oliver Pesch, EBSCO Information
Services
5
The SUSHI server is software that runs on the
Content Providers server, and has access to the
usage data.
Content Provider
Library
Usage Consolidation Client
Usage Consolidation Client
Usage Consolidation Client
Usage Consolidation Client / ERM
Internet
SUSHI Server (web service)?
SUSHI Client
Usage Data
Slide courtesy of Oliver Pesch, EBSCO Information
Services
6
When the ERM system wants a COUNTER report, it
sends a request to the SUSHI client, which
prepares the request.
Content Provider
Library
?
ERM
Usage Consolidation Client
Usage Consolidation Client / ERM
Internet
Request
SUSHI Server (web service)?
SUSHI Client
Usage Data
Slide courtesy of Oliver Pesch, EBSCO Information
Services
7
The SUSHI request is sent to the Content
Provider. The request specifies the report and
the library the report is for.
Content Provider
Library
Usage Consolidation Client / ERM
Internet
Request
Request
SUSHI Server (web service)?
SUSHI Client
Usage Data
Slide courtesy of Oliver Pesch, EBSCO Information
Services
8
The SUSHI server reads the request then processes
the usage data.
Content Provider
Library
ERM
Internet
Request
SUSHI Server (web service)?
SUSHI Client
Usage Data
Slide courtesy of Oliver Pesch, EBSCO Information
Services
9
The SUSHI server creates the requested COUNTER
report in XML format.
Content Provider
Library
ERM

Internet
SUSHI Server (web service)?
SUSHI Client
COUNTER
Usage Data
10
A response message is prepared according to the
SUSHI XML schema.
Content Provider
Library
ERM
Response
Internet
SUSHI Server (web service)?
SUSHI Client
COUNTER
Usage Data
Slide courtesy of Oliver Pesch, EBSCO Information
Services
11
The COUNTER report (XML) is added to the Response
as its payload. The response is sent to the
client.
Content Provider
Library
ERM
Response
Internet
SUSHI Server (web service)?
SUSHI Client
COUNTER
Usage Data
Slide courtesy of Oliver Pesch, EBSCO Information
Services
12
The COUNTER report (XML) is added to the Response
as its payload. The response is sent to the
client.
Content Provider
Library
ERM
Response
Internet
SUSHI Server (web service)?
SUSHI Client
COUNTER
Usage Data
Slide courtesy of Oliver Pesch, EBSCO Information
Services
13
The SUSHI client processes the response and
extracts the COUNTER report.
Content Provider
Library
ERM
Response
Internet
SUSHI Server (web service)?
SUSHI Client
COUNTER
Usage Data
Slide courtesy of Oliver Pesch, EBSCO Information
Services
14
The extracted COUNTER report is passed to the ERM
system for further processing.
Content Provider
Library
?
ERM
COUNTER
Internet
SUSHI Server (web service)?
SUSHI Client
Usage Data
Slide courtesy of Oliver Pesch, EBSCO Information
Services
15
COUNTER / SUSHI relationship
16
COUNTER / SUSHI relationship
17
COUNTER / SUSHI relationship
18
COUNTER / SUSHI relationship
19
COUNTER / SUSHI relationship
20
COUNTER / SUSHI relationship
21
COUNTER / SUSHI relationship
22
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

23
consolidators
24
content providers (part 1 of 3)?
25
content providers (part 2 of 3)?
26
content providers (part 3 of 3)
27
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

28
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

29
More information

• Web site
• http//www.niso.org/workrooms/sushi/
• Schemas
• http//www.niso.org/schemas/sushi
• Discussion List
• http//www.niso.org/lists/sushidevelopers/