/
2025-09-29 eUsage subgroup

2025-09-29 eUsage subgroup

Calendar file:

You can request a calendar invitation from @Stefan Dombek by e-mail

Zoom link: https://openlibraryfoundation.zoom.us/j/87822401037?pwd=aajKWPM0kaAGlXG6nq0OZg03plmPjt.1

Time: 10 a.m. ET

Recording of the meeting: https://recordings.openlibraryfoundation.org/folio

Item

Notes

Item

Notes

New members?

Introduce yourself!

Please add “eUsage” to “Focus of Work” in the table https://folio-org.atlassian.net/wiki/spaces/ERMSIG (ERM SIG Home - Members).

Workshopping

If anyone has errors in the system or problems, these can be presented at the meeting. We can look at these together.

Roadmap update

If you did not have the opportunity, please read the minutes from the last meeting. https://folio-org.atlassian.net/wiki/x/KgDGQg

Implementers topic - S3 Objekt Cloud Storage

  • Not only via AWS, but general connection to S3 object cloud storage (data sovereignty).

  • Feedback from backend developer: It would work for the non-Counter reports. For the Counter reports, you would have to modify the backend a lot.

Implementers topic - Extend information from Counter exceptions

Additional properties in JSON object for Counter reports for the parts of COUNTER API exception messages

Implementers topic - Multiple harvester accounts per provider

Due to the different releases, there should be a solution. It should be possible to create multiple SUSHI accounts per provider. This is also done in Alma by Ex Libris.

See draft: Multiple harvester accounts per provider

Harvester - Improving the processing of CoP error codes

In the next meetings we would like to discuss how eUsage should react to the individual exception codes.

  1. https://folio-org.atlassian.net/wiki/x/AYDhPw

  2. EPIC https://folio-org.atlassian.net/browse/UIEUS-429

Refinement / Discussion

  • CoP 303X (discussed)

    • Notification when selecting a period for which no report data exists. Can it stay that way, or should it be displayed differently?

  • CoP 1020 (Refinement)

    • The handling of the exception will be changed. The harvester should stop and make no further attempts. Instead, an error message is displayed in the Detail View. This can also be filtered to search for it.

    • Also a solution for 1000 and 1010?

Feel free to add points to the list