2025-06-23 eUsage subgroup

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

Updates from the development

• Manual Upload of Counter Reports

  • With the Trillium release, Counter reports can be uploaded manually in JSON, CSV, TSV and XLSX format. There is a new converter in the backend. This converter converts the various file formats of Counter 5.1 into JSON. This also improves exports.

  • Improved view for manual upload of counter reports UIEUS-421: Update upload form for manual upload of COUNTER reportsClosed

  • In progress: UIEUS-403: Improvement of the notification of exceptions when manually uploading COUNTER filesBlocked . This should improve the display of error messages and control processing. See also: MODEUS-208: Return structured ReportUploadError JSON object on failed report uploadsOpen

• A new date picker is being developed where you can only select the month and year. It is being checked whether this can become part of Stripes.

  • See UIEUS-420: Create Monthpicker component based on stripesIn Code Review

    • UIEUS-416: Month picker within the harvest configuration of a UDPBlocked

    • UIEUS-423: Month picker within the section to exporting statisticsBlocked

• MODEUSHARV-121: Improve Credential Management for Periodic Harvesting by Implementing Secret Manager IntegrationOpen

• MODEUSHARV-140: Problem with several vendors in eUsage app in FolioClosed

• EUREKA: Various feedback on the configuration from the community is being reviewed.

• Planned: UXPROD-5386: Integrate provider listsDraft Integration of a provider list for transferring data from the counter registry into the forms when you creating a provider.

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

Slight delay in development until mid-September

Our backend developer for eUsage will be away from work from July to mid-September. There may therefore be delays.

• We can formulate the new requirements within this time.

• The most important goals for Trillium can be implemented. Newer requirements would probably have to be moved to later versions.

Harvester - Improving the processing of CoP error codes

• @Bernd Oberknapp will create 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.

• An EPIC will be created in Jira under which the CoP error codes are listed. There will be one ticket for each CoP error code linked to the EPIC. The EPIC is therefore used for grouping.