Bug 38804 - erm : make usage data harvestable via SUSHI if the data provider enqueue the production of the report
Summary: erm : make usage data harvestable via SUSHI if the data provider enqueue the ...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: ERM (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Jonathan Druart
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-30 18:42 UTC by Mathieu Saby
Modified: 2025-04-02 13:07 UTC (History)
6 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Saby 2024-12-30 18:42:55 UTC
Trying to harvest JSTOR usage data via SUSHI returns an error in Koha job : 
"SUSHI returned: Warning - Report Queued for Processing 1011"

This behavior is documented in Counter registry (https://registry.countermetrics.org/platform/335608df-e4d2-46ad-bd89-fb3683035441), for JSTOR "The same report cannot be requested more than 5 times per day. JSTOR uses reporting queuing so if data is not yet available, clients will need to re-request the report at a later date."
and in JSTOR site : 
https://support.jstor.org/hc/en-us/articles/360015483214-SUSHI-reports-COUNTER-5-overview
"Please wait at least one (1) hour between report requests to allow time for report files to be generated."

I suppose other data provider may have the same policy. For Koha to be able to harvest them, it should be necessary to add an option to relaunch the harvesting process after a parametrable delay
Comment 1 Andrew Auld 2025-04-02 13:07:38 UTC
There is a plugin that Jake Deery (Open Fifth) is working on to schedule cron jobs. This is potentially a tool that could be used to schedule SUSHI harvests. However it needs work.