Status: Closed (View Workflow)
For reports with YOP, in some cases data gets only downloaded for one instead of all YOPs, leading to massive data loss in the downloaded files.
In addition, the YOP and data do not match: the YOP in the downloaded file is the first of all YOPs for a given title, while the counts belong to the last YOP with usage.
The behaviour was first noticed on the Thor test environment, where eUsage is installed in the Juniper release versions:
- The error only occurs when using the multiple months download (below the statistics table)
- Downloading a single report (from the report info modal) results in correct data.
- The eUsage reports plugin, using the API/JSON version, gets correct data as well.
Reproducing on the current Snapshot system leads to
- the error for multiple months download
- and the same error also for single months download
- eUsage reports plugin couldn't be tested, as the matching doesn't work on snapshot
Steps to Reproduce:
- Log into (a) Thor or (b) Spanshot system
- Upload the attached Annual reviews 01/2021 CSV report to a UDP (or harvest data)
- Download the report via the report info modal, save the report.
- Download the report via the multiple months download, start 2021-01, end 2021-01, save the report.
See attached files/screenshots,.
This is most likely the same problem reported in
- relates to
MODEUSCNT-20 Reading data from CSV reports results in invalid JSON report data
MODEUR-83 Discrepancies in eUsage reports when YOP is present