Status Meanings

Each status has a certain significance in the development workflow. You can read this under https://folio-org.atlassian.net/wiki/x/8L0o (Product Owners / JIRA status). The Leipzig development team is guided by these specifications.

We use the following Jira status.

• Draft

• In Refinement

• In Progress

• In Review

• Closed

eUsage

UXPROD-576: E-Resource usage data: Report managementOpen

Please note: The releases mentioned for issues are plans. There is no guarantee that the issues will be ready on the release dates.

Ramsons (R2 2024 > Feb 2025)

Release notes

https://folio-org.atlassian.net/wiki/x/OgNNBg (see section eUsage)

Documentation

https://ramsons.docs.folio.org/docs/erm/eusage/

Sunflower (R1 2025)

Note: Update to Java 21 and other additional technical requirements

Release notes

https://folio-org.atlassian.net/wiki/x/aYHJFw?atlOrigin=eyJpIjoiNzdjZGM1MjE0OGRlNDMwYThjNjcwYWNkMjlhNTQxY2MiLCJwIjoiYyJ9 (see section eUsage)

Documentation

TBD

Trillium (R2 2025)

Note: From this version onwards, the first exception handlings will be improved.

Umbrellaleaf (R1 2026)

Vetch (R2 2026)

Draft / In Refinement

eUsage Reports (Plugin Agreements)

UXPROD-1253: E-Resource usage data: Calculate and visualize statisticsOpen

Open / Draft