2026-09-07 eUsage subgroup

2026-09-07 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 ERM SIG (ERM SIG Home - Members).

WOLFcon 2026 (Review)

  • A short session on eUsage took place. The goal was to raise awareness of the eUsage working group.

  • CELUS: Provider of a Counter report harvesting service. See https://celus.net/

  • Session from Jason Moore: Combining acquisition data for eResources with Counter statistics in CELUS. (ROI)

→ Perhaps this group could refocus and discuss topics related to Counter reports in general. The items on the agenda could then cover various solutions related to the topic of Counter. It's important that it be related to FOLIO.

Validation of identifiers in Counter Reports

There is currently a discussion about whether to allow identifiers that may be incorrect, but to flag them. At the moment, reports are rejected due to invalid validation. This is an issue that keeps coming up. On the one hand, we need valid identifiers because the data is reused (e.g., eUsage reports). On the other hand, we can’t simply reject reports just because the identifier is incorrect. Providers will never be able to get this 100% right.

See: https://github.com/Project-Counter/cop5/blob/planned/api-specification/COUNTER_API.json (starting at line 16465)

Discussion:

  • We need to determine how eUsage Reports should import data from eUsage. Charlotte will be invited to the next meeting.

  • One idea might be to mark the IDs in such a way that it's clear they aren't valid according to the standard counter.

    • for eUsage reports we agree with this idea (UB Kassel)

  • Another idea: eUsage Reports could use the data and try to use it by normalizing it.

  • eUsage reports (UB Kassel)

    • identifiers used in eUsage reports for matching:

      • currently: ISSN, ISBN

      • planned:

        • GOKB UUID

        • URI → remove “http(s)” for matching

        • DOI

        • ISBN

        • p-ISSN

        • e-ISSN

        • Provider ID

        • Name (normalized, in lower case)

      • Possible combinations:

        • p-/e-ISSN + name

        • ISBN + name

      • Requirement: Use additional identifiers for matching and normalize them (remove special characters from the identifiers in the statistics and the local KB, e.g., remove hyphens from ISBNs and ISSNs and convert the “X” as a check digit to lowercase). Hypens in ISBNs are already ignored for matching.

      • eUsage report ideas for matching - current status 03.09.2026

Idea from WOLFcon

[…] ‘Maybe there should be an option to link form a usage data provider to an organization? If the usage data provider is linked to an agreement and the agreement to an organization, there already is an indirect link (actually there might be multiple indirect links), but a direct link might be helpful, especially for usage data providers that do not offer SUSHI. Additionally, once we have the integration with the COUNTER registry, it probably would be helpful to offer a link to the registry record.’ […]

Feel free to add points to the list