|Updates to cost per request report mockup||Kristen Wilson|
Cost per request (continued)
Axel: There should be some kind of warning/flag, if the usage is not complete for the reporting period.
Kristen added a field “Order type” to indicate whether the order is ongoing or one-time
No other comments on “cost per request report”
|Continue reviewing additional rough mockups||Kristen Wilson|
Request per month
Have everything on title level, no packages. Titles from packages are pulled out.
Metric type as a columns to be able to filter for total vs unique item requests
Axel: How ill we indicate the difference between zero usage and no data for a given month
Nicole: What about titles that are not in the package anymore?
Nicole: We sum up the usage for each month - could there be a total row?
Searches by month
Are people interested in all metric types → come back with feedback next meeting
Requests by publication year
Annika: Idea to have a second tab (as in Counter 4), where the data is swapped and shows usage per publication year
Axel: In the “swapped version”, displaying usage per publication year: could we be able to group by publication years, and make the grouping interval configurable to show e.g. decades or to be able to differentiate back files/front files
In the swapped version: should we break down usage per month or aggregate it in one year?
→ Kristen will present mockups of different options next meeting, for the group to decide
Titles without use:
Nicole: Counter 5 doesn’t show rows without usage
Axel: maybe you could have a treshold to be able to also include low use titles?
Kristen: Maybe it would be better to include the zero use titles into the requests per month report combine the two. Then the requests per month report would show all titles from an agreement, regardless of whether there is usage or not.