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

[UXPROD-2042] Manage harvesting errors: filter providers by error occurance Created: 09/Sep/19  Updated: 16/Sep/20  Resolved: 07/Oct/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q4 2019
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, split
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UIEUS-103 Manage harvesting errors: filter prov... Closed
relates to UXPROD-2104 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: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: Leipzig (ERM Aut 2019): R2

 Description   

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.

Idea 1 (basic):
Harvesting error(s)

  • () yes
  • () no

----------------------------------------

FEATURE SPLIT:
More advanced filter options (= by error type) are adressed in UXPROD-2104 Closed .

Idea 2:
Harvesting error(s)

  • [ ] none
  • [ ] yes, still retried
  • [ ] yes, action required

Idea 3, additional filter (will be implemented in later feature, if necessary):
Error code

  • dropdown menu
  • > Error codes from providers are very different, list might become too long and heterogeneous to be of much use. Needs real data experience to determine.

Different ideas listed above are being discussed.


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