1 / 24

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

Adam Chandler Cornell University Library Charleston Conference Charleston, SC November 6, 2008. NISO Standardized Usage Statistics Harvesting Initiative (SUSHI): Z39.93. What it isn’t: A model for counting usage statistics ( that's what the COUNTER Code of Practice does ) ‏

maddy
Download Presentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. What it isn’t: A model for counting usage statistics (that's what the COUNTER Code of Practice does)‏ A usage consolidation application 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

  3. The Library’s consolidation client and Content Provider’s systems are both connected to the Internet. Library Content Provider Internet Slide courtesy of Oliver Pesch, EBSCO Information Services

  4. The SUSHI client is software that runs on the library’s server, usually associated with an ERM system. Library Content Provider 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 Provider’s server, and has access to the usage data. Library Content Provider 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. Library Content Provider ? 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. Library Content Provider Usage Consolidation Client / ERM Internet Request Request SUSHI Client SUSHI Server (web service)‏ Usage Data Slide courtesy of Oliver Pesch, EBSCO Information Services

  8. The SUSHI server reads the request then processes the usage data. Library Content Provider ERM Internet Request SUSHI Client SUSHI Server (web service)‏ Usage Data Slide courtesy of Oliver Pesch, EBSCO Information Services

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

  10. A response message is prepared according to the SUSHI XML schema. Library Content Provider ERM Response Internet SUSHI Client SUSHI Server (web service)‏ 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. Library Content Provider ERM Response Internet SUSHI Client SUSHI Server (web service)‏ 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. Library Content Provider ERM Response Internet SUSHI Client SUSHI Server (web service)‏ COUNTER Usage Data Slide courtesy of Oliver Pesch, EBSCO Information Services

  13. The SUSHI client processes the response and extracts the COUNTER report. Library Content Provider ERM Response Internet SUSHI Client SUSHI Server (web service)‏ 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. Library Content Provider  ERM COUNTER Internet SUSHI Client SUSHI Server (web service)‏ 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. 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

  23. 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

  24. 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/

More Related