Issues / Roadmap

Issues / Roadmap

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

  • Open

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

Umbrellaleaf

Improve handling of COUNTER API Exceptions

Steps

1. Add new icons

CoP Error codes

Jira / Features

2. Remove harvester function for COUNTER 4

So far, only service types have been added to eUsage; none have been removed. For this reason, a fallback solution and a migration process must be integrated into eUsage for existing UDP records in case a service type is deleted.

3. Add new service types to the aggregator and delete old ones

4. Implement new features

4.1. Preparing for the new features: Harvester (Backend)

UXPROD-5578: eUsage harvester backend: Modification to enable individual handling to exceptionsIn Refinement

4.2. Add new features

Others


Vetch


Not scheduled

Release date not yet determined.


eUsage Reports (Plugin Agreements)

Hebis

UXPROD-5535: Hebis: Statistics in ERM (FOLIO module eUsage/eUsage reports)In Progress

Others

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

Open / Draft