Usage Report Issues

If you have experienced problems with SUSHI or COUNTER reports, you can report it to us here. We check every issue that you report to us and take action when we need to. The information which you give us can help us to identify and to resolve problems.

Reports

SUSHI TR_J2 and others - GeoScienceWorld - 4th Mar 2020 - +

Issue Report: Tr_j2 and some others are not sending report_items but no exception in header. Sample URL: https://sitemaster.geoscienceworld.org/sushi/reports/tr_j2?customer_id=2320&requestor_id=15359&api_key=2d3422e9-04c5-448b-bb62-811f4ad3a1ee&begin_date=2019-01&end_date=2019-12

Usus Response:

JSTOR SUSHI R5 all reports pre-2019 - 3rd Mar 2020 - +

Issue Report: JSTOR uses the wrong exception when requesting reports before their R5 start date. The header for all supported reports is returning: "Exceptions" : [ { "Code" : 3030, "Severity" : "Error", "Message" : "No Usage Available for Requested Dates", "Help_URL" : "https://support.jstor.org", "Data" : "" } ] Example URL: https://www.jstor.org/sushi/reports/dr/?customer_id=upei.ca&requestor_id=collections%40upei.ca&begin_date=2018-01&end_date=2018-12

Usus Response:

AM Digital returning empty json - 3rd Mar 2020 - +

Issue Report: https://www.counter.amdigital.co.uk/CounterSushi5Api/reports?customer_id=collections%40upei.ca&api_key=492368c9-2338-49e8-a01b-8cb88504dc49

Usus Response:

SquidSolutions/APS wrong info in Created_by - 3rd Mar 2020 - +

Issue Report: https://inqwell.squidsolutions.com/release/aps/sushi/reports/pr?customer_id=PR447048&requestor_id=5c9290982b734cbb9893a765&begin_date=2017-01&end_date=2017-12 They're putting UPEI in the Created_by header field instead of who is generating the data

Usus Response:

proquest ebook central tabular not offering tsv - 3rd Mar 2020 - +

Issue Report: Proquest Ebook Central only offers HTML and XLSX format for tabular R5 reports

Usus Response:

Proquest Ebook central returns html 503 instead of json - 3rd Mar 2020 - +

Issue Report: 503 Service Unavailable Service Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Apache/2.4.7 (Ubuntu) Server at pqbi.prod.proquest.com Port 443 My understanding is the 503 https should be returning a json exception but this is returning html. https://pqbi.prod.proquest.com/release/sushi/ebooks/r5/reports/tr_b1?customer_id=upei&requestor_id=5e31c5140c18c070632e35e4&begin_date=2019-01-01&end_date=2019-12-31

Usus Response:

Brill giving various wrong errors - 3rd Mar 2020 - +

Issue Report: Depending on which report and which of my two SUSHI clients, I'm getting 403 errors, 404 errors, and spurious "invalid api key" errors from Brill. https://ams.brill.com/rest/COUNTER/v5/reports/ir?customer_id=5923&api_key=FWjEKsp1+ocRWaQuwvySMw==&begin_date=2019-01-01&end_date=2019-12-31

Usus Response:

Usage Report Issues

Submit a new report

Reports

Gold and Silver Sponsors