/
2025-07-21 eUsage subgroup

2025-07-21 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/x/BQBS (ERM SIG Home - Members).

Wiki pages

New name for SUSHI API?

https://cop5.countermetrics.org/en/5.1.0.1/08-api/index.html

  • Is the new name for SUSHI-API now COUNTER API? This is described in the documentation from version 5.1.0.1 but not for 5.1.

  • Should this be changed in the UI?

New requirement(s)

skipped

 

  • S3 Objekt Cloud Storage

    • https://folio-org.atlassian.net/wiki/x/SABS

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

Harvester - Improving the processing of CoP error codes

  • @Bernd Oberknapp created an overview of the CoP exception codes. In the next meetings we would like to discuss how eUsage should react to the individual exception codes.

  • In Jira, there is an EPIC https://folio-org.atlassian.net/browse/UIEUS-429 under which the CoP error codes are listed. There is a ticket for each CoP error code that is linked to the EPIC. The EPIC is therefore used for grouping. This is better for development because it allows us to plan better.

Feel free to add points to the list

 

Next meeting

  • August 18th