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

[UXPROD-957] Integration of non-COUNTER usage statistics Created: 18/Jun/18  Updated: 16/Sep/20  Resolved: 27/Aug/20

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

Issue links:
Relates
relates to UIEUS-175 Integration of non-COUNTER usage stat... Closed
Potential Workaround: Annika:
Originally non-COUNTER statsitics can be prepared as a CSV file according to COUNTER formatting standard and then uploaded. This is already possible for several reports.
Warning: The workaround will NOT solve the flagging/marking requirement, so the user should be fully aware of maybe inserting data into the system that does not comply to counting mechanisms defined by COUNTER.
Epic Link: E-Resource usage data: Report management
Analysis Estimate: Large < 10 days
Front End Estimate: Large < 10 days
Front-End Confidence factor: Medium
Back End Estimate: Large < 10 days
Development Team: Leipzig
PO Rank: 25
PO Ranking Note: This is ranked lower, because it is very expensive while there is a sensible workaround.
Rank: Cornell (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: 5Colleges (ERM Jun 2020): R4
Rank: Leipzig (Full TBD): R1
Rank: Leipzig (ERM Aut 2019): R2

 Description   

Info: All rankings deleted, because of new concept.

Background:
Although COUNTER standard is well adapted across vendors, there are still a lot of not standard compliant statistics offered to libraries. As the standard doesn't only regulate the format to store and exchange usage statistics, but primarily how the statistics are generated, what metrics are to be counted and which rules should be applied, non-COUNTER statistics will most often not be directly comparable to COUNTER ones. Therefore, there will be no possibility to upload them into the eUsage app's report storage, which will be the data source for comporative statistics and visualizations. If a user ist absolutely sure taht the data of a non-COUNTER vendor is comparable and should be added, the data can be formatted manually as a COUNTER-compliant CSV and uploaded.

Concept:
A user can upload any statistics file to a usage data provider, where it will be saved, stored and downloadable.

Section "Statistics Upload"
The user can choose between "COUNTER" and "other format".
a) COUNTER: The already implemented file upload area without further form fields is displayed
b) other format:
Two fields:

  • Reporting year: [YYYY]
  • Note: [free text field]
    and a file upload area.

In the note, the user can e.g. specify the kind of data contained by the report as well as the exact reporting period, if it differs from a full calendar year

Section "Statistics"
Renamed from the current term "COUNTER statistics".
The section is divided into two sub-sections "COUNTER" and "other format"
a) COUNTER: The already implemented statistics tables, grouped by reporting year
b) other format:

  • grouped by reporting year
  • File icons, with note displayed next to them
  • Click on icon will open Detail info box

Detail info box
Styled like the already implemented box for COUNTER-Reports
Shows:

  • info entered by the user on upload (reporting year and note)
  • uploading user and upload date/time, file size
  • Buttons for downloading and for deleting the file


 Comments   
Comment by Cate Boerema (Inactive) [ 13/Sep/18 ]

Assigning to Owen as PO.

Comment by Cate Boerema (Inactive) [ 13/Sep/18 ]

Per Owen Stephens, I am assigning all the features for the usage data epic to Annika.

Comment by Khalilah Gambrell [ 11/Sep/19 ]

Annika Schröer was this implemented?

Comment by Annika Schröer [ 12/Sep/19 ]

Khalilah Gambrell No, it wasn't. There are several problems that need more discussion (e.g. flagging data as not neccessarily comparable etc.), which might lead to a decision against implementation. The workaround described above might in this case become a long term solution. It is also up to further discussion whether a simple file upload would be helpful to at least store records in the same place.
Info on workaround: CSV upload needed re-implementation, will be avaiable in Q4 2019 (see UXPROD-2040 Closed )

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