|Research on 0 use reporting||Distinguish between known “zero use” and “no data”. Will need to find a consistent way to handle the difference for all reports|
|Question from last week:|
Which metric types are important for working with database reports?
Separate columns for all different search metric types seems good. Better have more columns than to miss information
Difference between investigation and request for non-full text databases → Jessica will look up for next meeting.
|Review revised mock ups|
Report parameters to enter before downloading: Start date, end date, metric type: will prefilter metric type before download (for journals and books, not mandatory for databases)
Totals for unique and total requests in different rows
Filter for metric type (unique vs. total requests) would still be nice, but is not required for download (a user could filter in the downloaded spreadsheet afterwards). For visualizations it will become more interesting.
Use by publication year:
Kristen shows mockups to the group:
Two views in separate tabs:
Grouping by reporting period:
Several different possibilities
Kristen: Is it a good idea to let the user do configurable grouping? With that tool each of the possibilities above could be produced.
Annika: In addition, a way to group for Publication year? In order to have a difference between backfile and frontfile?
Best way might be to have the most detailed report and have the user filter.
Kirstin will wrap up reports for next week and we will start talking about visualizations next week.
Kristen will work on a mock-up for integration OA usage
|Report view download in eUsage|
Annika: We are currently working on integrating CSV download for Counter R5 report views. We most likely won’t be able to offer every report view as direct CSV download (but they can be created from the master reports). Which report views are the most commonly used views that we should support?
→ Please think about this and write into Slack or the notes until next week. Thanks!