What's in this article:

• Setting up SUSHI reporting
• What to do if you encounter an error

In January 2019, JSTOR became compliant with COUNTER 5 reporting standards. COUNTER 4 reports are only available on JSTOR as pre-generated reports from January 2017-April 2019 that are available on the JSTOR admin site.

Please see the COUNTER 5 SUSHI support page for more information on the change to COUNTER 5 compliant reporting on JSTOR and getting started with usage statistics.

Retrieving COUNTER 4 reports via SUSHI

To set up SUSHI you need two things. You can find this information in your individual administrative JSTOR account via the COUNTER 5 report homepage:

• Customer ID
• Requester ID

If you are an administrator for more than one institution, take these steps to see the SUSHI credentials for each one: 

1. Go to the COUNTER 5 report interface 
2. Click "Create Report"
3. Select the institution you want from the dropdown field
4. Your credentials will appear in the report creation interface

If you get an error when you run your SUSHI report:

COUNTER 4 reports for January 2018-April 2019 are pre-generated. Because of this, your SUSHI request must exactly match reports that are available for download on the JSTOR admin website. If you requested a report outside of the parameters of the pre-generated reports available for download within the administrator site, you will see an error message.

Things to look for:

• Is your Customer ID correct? These are case sensitive.
• Is your Requester ID correct? These are also case-sensitive.
• Are you requesting a report for a calendar year or month? We only have C4 reports available by year for institutions, and by month for consortia
• CR2 reports for consortia are no longer available in the C4 records
• Is your endpoint URL correct?
  • For most providers it should be: http://www.jstor.org/sushi/ 
  • Ex Libris UStat and Alma customers must request SUSHI reports via: http://www.jstor.org/sushi/ustat/
  • If http: is not working for either option, try running it with https:
• A timestamp after the date. Delete the timestamp and resend the request.

Examples of successful SUSHI request for COUNTER 4: 

JR1 Example:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<sc:ReportRequest xmlns:sc="http://www.niso.org/schemas/sushi/counter">
<Requestor xmlns="http://www.niso.org/schemas/sushi">
<ID>test-user</ID>
<Name/>
<Email>test-user@jstor.org</Email>
</Requestor>
<CustomerReference xmlns="http://www.niso.org/schemas/sushi">
<ID>demo.edu</ID>
<Name/>
</CustomerReference>
<ReportDefinition xmlns="http://www.niso.org/schemas/sushi" Name="JR1" Release="4">
<Filters>
<UsageDateRange>
<Begin>2018-01-01</Begin>
<End>2018-12-31</End>
</UsageDateRange>
</Filters>
</ReportDefinition>
</sc:ReportRequest>
</soap:Body>
</soap:Envelope>

DB1 Example:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<sc:ReportRequest xmlns:sc="http://www.niso.org/schemas/sushi/counter">
<Requestor xmlns="http://www.niso.org/schemas/sushi">
<ID>test-user</ID>
<Name/>
<Email>test-user@jstor.org</Email>
</Requestor>
<CustomerReference xmlns="http://www.niso.org/schemas/sushi">
<ID>demo.edu</ID>
<Name/>
</CustomerReference>
<ReportDefinition xmlns="http://www.niso.org/schemas/sushi" Name="DB1" Release="4">
<Filters>
<UsageDateRange>
<Begin>2017-01-01</Begin>
<End>2017-12-31</End>
</UsageDateRange>
</Filters>
</ReportDefinition>
</sc:ReportRequest>
</soap:Body>
</soap:Envelope>

If everything looks good and you still have problems, contact us. Please include the following in the message:

• A screenshot of your set-up screen
• What kind of SUSHI client you use
• The XML files of the Request and Response from the SUSHI request.