Slides from JUSP workshop "Making the switch to COUNTER Release 5 with JUSP" held at University of Edinburgh on 11 March 2020

1. Making the switch to COUNTER
Release 5 with JUSP
March 2020
University of Edinburgh - 11 March 2020

2. What we are doing today
2
Time Topic
10:00 Introduction
Overview of COUNTER Release 5
Using JUSP Release 5 reports in practice
12:15 Lunch
13:00 Getting more out of COUNTER R5 data
JUSP developments
Managing the transition
14:45 End of workshop
SHEDL requirements meeting 14:50 to 16:00

3. Introductions
3
Discuss on your tables
•What you would like out of the day?
•Where you are with Release 5? Have you started using it?
•What other training have you done?
Share a brief summary of the discussion (e.g. key points,
common themes, differences) with the whole group.

4. Overview of COUNTER Release 5
Reports and terminology

5. What is COUNTER?
5
COUNTER - a not-for-profit organisation
COUNTER Code of Practice - a standard for e-resource usage statistics
…
Release 3
Release 4
Release 5
COUNTER Release 4
reports
COUNTER Release 5
reports
S
U
S
H
I

6. Report structure: R4 and R5
6
Release 4
• Series of standalone reports
• Some required, some optional
• Grouped by content type e.g. book, journal,
database, multimedia
Release 5
• 4 Master Reports reporting all types of
interaction
• Standard Views extract and summarise data to
meet common use cases
• All required where applicable
Release 5
Master Reports
Platform
Master
Report
Database
Master
Report
Title
Master
Report
Item
Master
Report
Standard views
PR_P1
DR_D1
DR_D2
TR_J1
TR_J2
TR_J3
TR_J4
TR_B1
TR_B2
TR_B3
IR_M1
Userdefinedcustomviews

7. Standard views based on the Title Master Report
Report name What does it show? What's it used for?
TR_J1 Journal Requests (Excluding
OA_Gold)
full-text usage for all journal articles that are
not Gold Open Access
Evaluating usage of journal
subscriptions
TR_J2 Journal Access Denied number of times users are denied access to
articles
Identifying demand for journal
content
TR_J3 Journal Usage by Access
Type
all usage (both requests and investigations)
broken by access type (controlled and OA)
Comparing usage of subscribed
and open access content
TR_J4 Journal Requests by YOP
(Excluding OA_Gold)
breakdown by publication year for full-text
usage for all journal articles that are not Gold
Open Access
Assessing usage of backfile or
subscribed content
TR_B1 Book Requests (excluding
OA_Gold)
full-text usage for all book content that is not
Gold Open Access
Evaluating usage of books
TR_B2 Book Access Denied number of times users are denied access to
book content
Identifying demand for book
content
TR_B3 Book Usage by Access Type all usage (both requests and investigations)
broken by access type (controlled and OA)
Comparing usage of subscribed
and open access content
7

8. Standard views based on Database Master Report
Report name What does it show? What's it used for?
DR_D1 Database Search and Item
Usage
searches, investigations and requests at a
database level
Evaluating database
subscriptions
DR_D2 Database Access Denied number of times users are denied access to a
database
Identifying demand for database
content
8

9. Standard views based on Platform Master Report
9
Report name What does it show? What's it used for?
PR_P1 Platform Usage searches, investigations and requests at a
database level
Reporting on high level summary
of usage for a platform

10. JUSP data collection update

11. What does JUSP do to get R5 data?
11
• Initial communication re: accounts and details of the R5 SUSHI service – endpoint, API_keys etc.
• Test COUNTER compliance and send back reports to vendors and COUNTER as applicable
• Once reports compliant, harvest data back to Jan 2019
• All reports are additionally run through our own checking software before adding to JUSP
• Regular, ongoing spot checks on data once we have reports from a supplier
• Restate data when notified of any changes
• Maintain records of progress, issues and restatements
JUSP harvests:
• PR: Platform master report
• TR: Title master report
• DR: Database master report
• IR: Item master report (planned for future)
Data presented as:
• Standard and custom views
• Master report filtering
• Aggregated / summary reports
• Data visualisations

12. Data collection and JUSP
12
We continue to collect a mix of R4 and R5 data
• R4 data collection continues where no (or limited) R5 data available
• Once all R5 data available, we stop R4 data collection – mix of end dates
• R5 data collected back to Jan 2019 where possible
At Feb 12th:
• ~ 40 R4 suppliers, 48 R5 suppliers (with mix of PR, TR, DR reports)
• Where to find this information - DEMO!

13. Metric types
What they are and how they relate to COUNTER R4 reports

14. Metrics types: counting user actions
14
Investigations
 Total_Item_Investigations
 Unique_Item_Investigations
 Unique_Title_Investigations
Requests
 Total_Item_Requests
 Unique_Item_Requests
 Unique_Title_Requests
Access denied
 No_License
 Limit_Exceeded
Searches
 Searches_Regular
 Searches_Automated
 Searches_Platform
 Searches_Federated

15. Which metric types are found in the TR?
15
Title Master Report TR_J1 TR_J2 TR_J3 TR_J4 TR_B1 TR_B2 TR_B3
Total_Item_Investigations
Unique_Item_Investigations
Unique_Title_Investigations
Total_Item_Requests
Unique_Item_Requests
Unique_Title_Requests
No_License
Limit_Exceeded

16. Total and unique
• Key metric types for usage
• Journals: Total_Item_Requests and Unique_Item_Requests
• Books: Total_Item_Requests and Unique_Title_Requests
• Total_Item_Requests count all full-text requests for “items” such as an article or
book chapter
• Unique_Item_Requests de-duplicate use when a user requests the same item
(e.g. an article in different formats) in a user session
• Can apply to books, but mainly relevant to journals
• Unique_Title_Requests de-duplicate use when a user requests the same title
(e.g. multiple chapters in the same book) in a user session
• Only applies to book, not reported against journal titles
Insert footer16

17. Journal example
3 users access articles from same journal
HTML
HTML
PDF
PDF
PDF
This is counted in the TR as:
Total
item
requests
=
5
Unique
items
requests
=
4
17

18. Comparing journal usage metrics with R4
R4
report
R4 metric R5
Master
Report
R5
Standard
View
R5 Metric Type R5 Access
Type
R5 Data
Type /
Section
Type
JR1
successful full-text
article requests
TR TR_J3 Total_item_requests
Controlled
+ OA_Gold
Journal /
Article
JR1
GOA
successful full-text
article requests
TR TR_J3 Total_item_requests OA_Gold
Journal /
Article
JR1
Archive
successful full-text
article requests
TR TR_J4 Total_item_requests
Controlled
+ OA_Gold
Journal /
Article
JR1
minus
JR1
GOA
successful full-text
article requests
TR TR_J1 Total_item_requests Controlled
Journal /
Article
Insert footer18

19. Book example
3 users access different chapters in the same title (e.g. book)
This is counted in the TR as:
Total
item
requests
=
11 Unique
title
requests
=
4
19

20. Platform comparison
Scenario: a user goes to three different book platforms, views the first page and then downloads the whole book
Platform 1 Platform 2 Platform 3
Arrangement Book is available as
single PDF
Book is divided into 10
chapters
Book consists of 100
pages and user can
select pages to
download
R4 BR1 as 2 whole book
request
BR2 as 11 section
requests
BR2 as 101 section
requests
R5 total item requests 2 11 101
R5 unique title
requests
1 1 1
20

21. Search metrics
Metric type How was the search
conducted?
What was searched? Master
report
Searches_Regular • conducted against a database
• results are returned to the user on the
host UI
• a single database
• multiple databases and the user had
the option of selecting the databases
to be searched
DR
Searches_Automated • conducted against a database on the
host site or discovery service
• results are returned in the host UI
• multiple databases and the user does
NOT have the option of selecting the
databases to be searched
DR
Searches_Platform • conducted by users and captured at
the platform level
• searches against multiple databases
on the platform will only be counted
once
PR
Searches_Federated • conducted remotely through a
federated search service
• end user not responsible for selecting
the database being searched
DR
21

22. Transitioning to COUNTER R5
• What report and metric should I use for ….
• What metrics I should present to others and how?
• How do I clearly and concisely communicate the differences?
• What data is available? Can I trust it?
Insert footer22
Current questions and challenges

23. Using Release 5 reports in practice
Focus on pre-set views and reports

24. What are COUNTER reports used for?
Insert footer24
• Internal reporting e.g. to justify costs or cancellations
• Renewals, decision making and evaluation
• cost per use
• value for money
• subscriptions vs Inter-library loan
• breath of usage e.g. % of titles used in a collection
• Trends of usage
• Spot issues e.g. ‘0’ usage, spikes or unusual activity
• SCONUL reporting
• Monitoring student engagement and promoting resources

25. Current reports and features in JUSP
25
Report or view type Description Purpose
Standard view • Filters and format specified by
COUNTER
To provide a quick and consistent
set of reports across suppliers
Custom view • Same data (filters) as standard views
but different format
• Added information (totals, core titles,
DOAJ)
• Two display options
To provide a streamlined view for
ease of viewing
Transition • Closest equivalent R5 metrics to R4
• Presented in JR1 and BR2 format
To support the need to compare
with historical R4 data
Filtering master reports • Advanced reporting tool with flexibility
to tailor the master reports
To enable you to customise the
detail in the reports to meet your
specific requirements
Summary report • Aggregates usage
• Pre-sets filters and display
• Also has customisable options
To support high-level internal and
external reporting requirements

26. Getting more out of COUNTER data

27. What tools do you use for handling,
managing and analysing usage data?

28. Sharing tips for working with usage data in Excel
28
What features and functions do you find useful for usage analysis?
• Filters
• Pivot tables and charts
• VLOOKUP
• SUM
• SUMIF
• SUBTOTAL
• Charts
• Conditional formatting (with small data sets)
• …
Working with COUNTER R5 Reports in Microsoft Excel
COUNTER Foundation Class 10
Watch: https://youtu.be/AU_DBLi4hSo
UKSG webinar 27th February
Register: https://www.uksg.org/event/free-uksg-webinar-
working-counter-5-reports-microsoft-excel

29. Master report filtering
When might you want to filter a master report?
29

30. TR filters applied to TR_J1
30
Filter TR can include
TR_J1 filters
applied
TR_J1 shows
Data_Type
Book, Database, Journal, Newspaper or
Newsletter, Other, Report, Thesis or
Dissertation
Journal No
Section_Type Article, Book, Chapter, Other, Section All No
Access_Type Controlled, OA_Gold Controlled No
Access_Method Regular, TDM Regular No
YOP 0001-9999 All No

31. Developments in progress
31
•Individual title search and view
•Summary report comparing years
•Visualisations: service summary and monthly trends
•SUSHI server

32. Future plans
32
Reports
• Title level aggregation across services: all titles, core titles, top titles
• Trends over time
• Usage/denials by publication year
• Databases summaries
Visualisations
• Additional e.g. annual trends, comparison, top titles
• Enhancements e.g. viewing underlaying data
Features
• Saving and sharing set reports (personalisation)

33. Managing the transition from R4 to R5
33
What else is needed to support the transition?
• What are the opportunities and options for…
• Community support and sharing ideas?
• New reports?
• Additional training?

34. Further support and resources
Guides and tutorials
• JUSP guides https://jusp.jisc.ac.uk/guides/
• JUSP webinars https://jusp.jisc.ac.uk/events-training/
• COUNTER Foundation Classes https://www.projectcounter.org/counter-foundation-classes/
Community support and mailing lists
• COUNTER-R5-LIB mailing list
• LIB-STATS mailing list
• JUSPLIBRARIES mailing list
Support contacts
• COUNTER at countertechnicalsupport@counterusage.org
• JUSP at help@jisc.ac.uk (mention JUSP in the subject line)
34

35. Any final questions or comments?

36. Thank you for attending