1 / 13

SUSHI and ERM at Deakin

SUSHI and ERM at Deakin. Overview What is SUSHI? Why use SUSHI? Configuring Millennium’s ERM for SUSHI Troubleshooting What next?. What is SUSHI? SUSHI stands for Standardized Usage Statistics Harvesting Initiative.

mary
Download Presentation

SUSHI and ERM at Deakin

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. SUSHI and ERM at Deakin

  2. Overview • What is SUSHI? • Why use SUSHI? • Configuring Millennium’s ERM for SUSHI • Troubleshooting • What next?

  3. What is SUSHI? • SUSHI stands for Standardized Usage Statistics Harvesting Initiative. • It is a web service model for automatically requesting and retrieving the XML version of COUNTER usage reports.

  4. How does it work? SUSHI request for COUNTER report SUSHI client Millenium’s ERM SUSHI server Publisher/provider SUSHI response with xml format COUNTER report

  5. Why use SUSHI? • Usage statistics retrieval has been a manual, repetitive, time consuming process. • SUSHI automates this process.

  6. Configuring Millennium’s ERM for SUSHI • The Millenium User Manual and CSDirect have useful outlines for configuring ERM’s autostat File to automatically harvest usage statistics. • For each provider that offers a SUSHI feed you add an entry to the autostat configuration file.

  7. AutoStat Configuration

  8. Customer ID- ID number issued by resource provider Consortium Affiliation- affiliation code, only used if your library uses ERM as part of a consortium Day of the month- day of the month on which to automatically obtain the statistics from the resource provider From- number of months back from which you are collecting statistics To- number that represents where to end the import WSDL URL- URL through which the provider makes statistics available Requestor ID- your library’s requesting agent ID SUSHI Release- the release number used by the provider’s SUSHI server

  9. Troubleshooting Check the SUSHI harvest log in via the text-based interface to check whether statistics have been harvested, and if not, use the error message to identify the problem. M Management Information > M Miscellaneous Acquisitions and Serials > View SUSHI harvest log 11382 > INFO: <AutoStat> for ojot [Affl:]from 2009-06-01 to 2009-08-31 11383 > [2009-10-23  02:28:35 AM EST] <AutoStat> start... 11384 > Oct 23, 2009 2:28:35 AM com.iii.erm.ERMLogging logMessage 11385 > INFO: <AutoStat> start... 11386 > java.net.ConnectException: Connection timed out 11387 > [2009-10-23  02:31:44 AM EST] <ERMAutoStat-startProcess()> Attempt 1 : 11388 > java.net.ConnectException: Connection timed out 11389 > Oct 23, 2009 2:31:44 AM com.iii.erm.ERMLogging logMessage Provider’s WSDL URL had changed

  10. Errors ISSN in provider’s usage report did not match ISSN in coverage database 0884 > INFO: <ERMAutoStat-processEntry()> No resource found for :Bmj | 0959-8138 4718 > INFO: <ERMAutoStat-processEntry()> retrieved journal array is null Scholarly Stats had been unable to collect our Informaworld usage reports so there was no data to harvest 053 > INFO: <ERMAutoStat-startProcess()> Attempt 1 : 054 > java.lang.NullPointerException 055 > retrial 1 056 > Cannot get envvars 057 > [2009-10-26  01:34:38 PM EST] <ERMAutoStat-getCoverageDBName()> envvars       proto returns error 058 > Oct 26, 2009 1:34:38 PM com.iii.erm.ERMLogging logMessage 059 > INFO: <ERMAutoStat-getCoverageDBName()> envvars proto returns error 060 > [2009-10-26  01:34:38 PM EST] <ERMAutoStat-processEntry()> Cannot get the       coverage DB name ???

  11. What next? • CPU cost calculation • Configure other providers

  12. Any questions?

More Related