Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Research on 0 use reportingDistinguish 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

Use by month:

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:

  1. Requests by date of use
  2. Request by publication year

Grouping by reporting period:

Several different possibilities

    • let user group by year
    • list every year of reporting period
    • have one row for the whole reporting period

Kristen: Is it a good idea to let the user do configurable grouping? With that tool each of the possibilities above could be produced.
Group: Yes, good idea in general.

Annika: In addition, a way to group for Publication year? In order to have a difference between backfile and frontfile?
Group: Good idea, in theory, but it’s complicated to get the data. 


Best way might be to have the most detailed report and have the user filter.
Grouping will be made available depending on capacity of the dev team.
Annika: If we rely on Counter R5 we will only have reporting periods from 2020 onwards. So the functionality could not be used at first, anyway.

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!

  • No labels