E-Resource usage data: Report management (UXPROD-576)

[UXPROD-2104] Manage harvesting errors: filter providers by error type Created: 07/Oct/19  Updated: 16/Sep/20  Resolved: 02/Mar/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2020
Parent: E-Resource usage data: Report management

Type: New Feature Priority: P3
Reporter: Annika Schröer Assignee: Annika Schröer
Resolution: Done Votes: 0
Labels: eUsage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UIEUS-117 Manage harvesting errors: filter prov... Closed
relates to UXPROD-2042 Manage harvesting errors: filter prov... Closed
Epic Link: E-Resource usage data: Report management
Analysis Estimate: Small < 3 days
Front End Estimate: Large < 10 days
Back End Estimate: Medium < 5 days
Development Team: Leipzig
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R2
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (ERM Aut 2019): R2
Rank: TAMU (MVP Jan 2021): R2

 Description   

FEATURE SPLIT FROM UXPROD-2042 Closed

Background:
Harvesting statistics from a provider often does not work and leads to errors. Those errors are indicated in the statistics section of a usage data provider detail view. Sometimes those errors occur only once and the next harvesting is successful (server was down, timeout, harvesting limit exceeded, ...). But in other cases, the error needs manual correction (typo in account credentials, account needs activation by provider, ...).
To make it easy for a librarian to find those usage data providers in the system, there needs to be a filtering option by error.

SUSHI is defining error codes for common problems, e.g. data not yet processed, no data available, wrong credentials etc:
https://www.projectcounter.org/appendix-f-handling-errors-exceptions/

In order to be able to work through the known issues with providers, it is helpful for the user to filter according to these error codes (resp. their verbal representations).
This should best be done in a dropdown filter as can be seen in the agreements app for filtering by organisation.


Generated at Fri Feb 09 00:21:10 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.