This document outlines a session on the transition from COUNTER R4 to R5 usage reporting standards and the new reports available in JUSP. It discusses JUSP transitioning their reports to R5, challenges libraries are facing understanding and working with R5 data, new report features in JUSP to help with the transition like comparing R4 and R5 metrics, and where to find training and support resources.

1. COUNTER R4 to R5 transition
and comparison with JUSP
5 December 2019

2. Session outline
COUNTER R4 to R5 transition and comparison with JUSP
1.JUSP transition from R4 to R5
2.Institution/library transition from R4 to R5
3.New JUSP reports
4.Explanation of ‘unique’ metrics
5.Your questions

3. JUSP: transition from R4 to R5

4. JUSP R5 portal and reports
COUNTER R4 to R5 transition and comparison with JUSP
• JUSP launched new interface in April 2019 with Standard views and Custom views
• Functionality to filter Master reports was introduced in July
• Summary reports, SUSHI server and Data visualisations are in development

5. JUSP R5 collaboration and engagement activities
COUNTER R4 to R5 transition and comparison with JUSP
• Suppliers, publishers and stats providers
• encourage transition, understand timescales, test reports and add datasets
• Library community: Community Advisory Group and R5 co-design group
• understand key challenges, how to support, what reports to develop and what priorities
• provide training and support
• COUNTER
• common issues, communications and sharing info
• Joint letter calling for COUNTER Release 5 compliance
• https://www.sconul.ac.uk/publication/community-call-for-counter-release-5-compliance
• coordinated by Jisc, SCONUL, RLUK, COUNTER, and the CC PLUS Steering Committee, and
supported by international library consortia
• International initiatives

6. JUSP R5 update: R4 and R5 publishers
COUNTER R4 to R5 transition and comparison with JUSP
https://jusp.jisc.ac.uk/participants/
36
43
7
0
Title master report
Platform master report
Database master report
Item master report
Release 5 (R5) master reports added 2019
to date
R4 data collection update:
Still collecting – 27 suppliers (44 publishers)
Stopped collecting – 40 publishers, including 4
which no longer supply R4
3 publishers no longer supply R4, but we have
R5 data now – JSTOR, RSC, Wiley
Emerald stopped supplying R4 data in June
2019) but their R5 reports are not yet ready

7. Current challenges and concerns for the community
COUNTER R4 to R5 transition and comparison with JUSP
Based on JUSP user interviews, co-design group workshop, community advisory
group feedback, helpdesk enquiries, mailing list questions….
Understanding the new reports
• new metrics, terminology and format
• training and supporting staff
• answering queries
• theory vs practice
Continuity of reporting
• getting comparable metrics
• interpreting real data
• explaining changes
R5 data availability
• slow transition
• incomplete data
• keeping track of R4 and R5
• trusting R5 (and R4) data
Integrating into existing workflows
• unfamiliar formats and metrics
• Standard Views have multiple lines for each title
and no totals
• More manipulation of spreadsheets required
• ERMs not yet supporting R5

8. Opportunities
COUNTER R4 to R5 transition and comparison with JUSP
Librarians like…
• Greater flexibility and granularity
• enables more detailed analysis
• De-duplication with unique item and title metrics
• provides better comparisons between platforms and providers
• E-book usage includes copyright year
• easier package analysis
• Wide availability of accesses denied (turnaways) data
• supports consistent collections management processes
• Gold open access usage and TDM usage excluded by default but available on demand
• ideal for cost-per-use and also supports future reporting requirements
BUT need more time and a full year of data before exploring and exploiting the full benefits

9. Confidence rating poll
How confident are you in understanding and working with the R5 usage data?
Scale of 1 to 10
1 = not at all confident
10 = extremely confident

10. New JUSP report features
R4 transition reports and comparing R5 metrics

11. Overview of R5 title reports in JUSP
COUNTER R4 to R5 transition and comparison with JUSP
Title
Master
Report
Pre-set filters
Standard
Views
Custom
views
New
Transition
(R4/R5)
Select own
filters and
display
TR: Filter Title Master Report
New display option added

12. Making comparisons with R4 data
COUNTER R4 to R5 transition and comparison with JUSP
TR: Transition (R4 <--> R5)
• presents R5 data in the form and style of the R4 JR1 and BR2
• ‘counts’ are extracted from R5 title master report (TR) using filters specified in COUNTER guidance
• offers quick and easy view without needing to use TR: Filter Title Master Report
We selected as priorities for development as they support two immediate needs:
• To analyse trends in usage over a few years
• To report comparable data (internally and externally)
Remember: These are NOT R4 JR1 and BR2 reports. They are closest equivalents based on R5 data. There will
be some differences with the ‘real’ R4 reports for the same period.
• This temporary report is intended to aid the transition from COUNTER R4 to R5 during 2019/20.
• This report presents COUNTER R5 usage data in the style of an R4 report. The selection of data is consistent
with section 13 of the COUNTER R5 CoP.

13. Report selection
COUNTER R4 to R5 transition and comparison with JUSP

14. Screenshot showing report selection
COUNTER R4 to R5 transition and comparison with JUSP

15. Screenshot showing report view
COUNTER R4 to R5 transition and comparison with JUSP

16. Multiple Metric_Types per row
COUNTER R4 to R5 transition and comparison with JUSP
Alternative display for the custom views and filter report
Use cases
• compare multiple metrics for a title
• understand the differences
• demonstrate changes to others
• dual reporting during the transition
• easy to view report to share with others

17. Where to find the display options
COUNTER R4 to R5 transition and comparison with JUSP

18. Two display options
COUNTER R4 to R5 transition and comparison with JUSP

19. Journal example: Unique item requests
COUNTER R4 to R5 transition and comparison with JUSP
represents the number of unique
content items requested in a user
session
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

20. Book example: Unique title requests
COUNTER R4 to R5 transition and comparison with JUSP
represents the number of unique
titles requested in a user session
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

21. Platform comparison
COUNTER R4 to R5 transition and comparison with JUSP
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

22. Your questions

23. Further training and support
COUNTER R4 to R5 transition and comparison with JUSP
• JUSP resources
• Guides https://jusp.jisc.ac.uk/guides
• Webinar recordings https://jusp.jisc.ac.uk/events-training
• Workshops:
• Manchester 12 February https://www.jisc.ac.uk/events/making-the-switch-to-counter-release-5-with-jusp-12-feb-2020
• London 25 February https://www.jisc.ac.uk/events/making-the-switch-to-counter-release-5-with-jusp-25-feb-2020
• Edinburgh – to be confirmed
• COUNTER resources
• Foundation classes https://www.projectcounter.org/counter-foundation-classes
• Friendly guides https://www.projectcounter.org/friendly-guides-release-5
• FAQ https://www.projectcounter.org/frequently-asked-questions-faqs-counter-code-practice-release-5
• Webinars https://www.projectcounter.org/all-about-book-reports-and-metrics-webinar/
Contact us at help@jisc.ac.uk – mention JUSP in subject line