E-Resource usage data: Report management
(UXPROD-576)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | R1 2021 | Parent: | E-Resource usage data: Report management |
| Type: | New Feature | Priority: | P4 |
| 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 | ||
| Attachments: |
|
||||||||
| Issue links: |
|
||||||||
| Epic Link: | E-Resource usage data: Report management | ||||||||
| Analysis Estimate: | Medium < 5 days | ||||||||
| Front End Estimate: | Very Small (VS) < 1day | ||||||||
| Estimation Notes and Assumptions: | Back end estimate depends strongly on the outcome of the analysis and the decisions made. Maybe no effort at all, maybe Medium to Large. | ||||||||
| Development Team: | Leipzig | ||||||||
| PO Rank: | 2 | ||||||||
| Rank: Chalmers (Impl Aut 2019): | R4 | ||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||
| Rank: Duke (Full Sum 2021): | R4 | ||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||
| Rank: hbz (TBD): | R4 | ||||||||
| Rank: Lehigh (MVP Summer 2020): | R4 | ||||||||
| Rank: Leipzig (Full TBD): | R4 | ||||||||
| Rank: Leipzig (ERM Aut 2019): | R4 | ||||||||
| Rank: TAMU (MVP Jan 2021): | R4 | ||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||
| Description |
|
As the harvester runs a request for each reporting month seperately, the configuration of a new provider with several report types or of a new report type for an existing provider can lead to many separate harvester requests to the provider. Some providers have limits on the daily number of reports to be generated, e.g. EBSCO host:
As a result, not all reports can be downloaded in one step after having configured the provider and harvesting for the first time (see screenshot: harvest JR1, BR2, DB1 for 2018-01 to 2019-05, Error message "Client has made too many requests"). We should come up with some strategy to deal with this problem:
|