/
2025-12-15 eUsage subgroup

2025-12-15 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).

Release notes - Trillium

https://folio-org.atlassian.net/wiki/x/Z4T-Nw

The development of new features has been completed. Only platform requirements are still being implemented. Everything else will be developed from Umbrellaleaf onwards.

Monthpicker

There are differences in how pickers for dates behave in FOLIO. We are working to clarify how this can be standardized. In eUsage, the month picker will then be adjusted accordingly. Other points will also be clarified in this context.

Using the UI with the keyboard:

  • Open/ Close: Calendar can be opened using the keyboard with Space or Enter. That depends on the app at the moment.

    • eUsage: The calendar icon should be selectable and openable via the keyboard. The key on the keyboard used to open it should follow the rules of the date picker. We will have to wait and see what the discussion on this topic yields.

  • Paging: Check whether it is possible to navigate within the calendar using the arrows at the top or whether the drop-down menus should be used.

Prioritization of requirements for 2026

  • Discussions were held on which implementers topics should be discussed next year.

  • Next year, the group plans to hear reports on the development of the plugin (still to be discussed).

Redesign of the harvester (not discussed)

The backend of the harvester needs to be redesigned. The current design cannot meet the new requirements.

New requirements:

  • Error handling of the several CoP codes with different requirements

  • Multiple harvester accounts per provider

  • Extend information from Counter exceptions

  • …

The DevTeam Leipzig has already completed a draft, which is still being discussed internally. Once the draft is finalized, it will be presented to the eUsage subgroup.

First draft:

draft_harvester.png

Please note: This blocks CoP error handling. We can still prepare the issues in the SIG. However, the new error handling can only be implemented after the harvester has been redesigned.

Open points that are discussed depending on the time available

 

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

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 - 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.

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

 

 

 

Feel free to add points to the list