Close search
 
Home | Tech Support | Retiring Release 5

Retiring Release 5

22 June 2026

One of the questions that comes to me reasonably frequently is about when Release 5 will be retired. The answer, of course, is “it depends on what you mean by retired”.

If we’re talking about when publishers can stop delivering R5 reports, there are two factors in play. First, we required three months during which both R5 and R5.1 reports were available to libraries (dual running). After that dual running period, the usual rule about having year-to-date plus two back years of reports (YTD+2) still applies, but we don’t specify a particular format.

I’m posting this on 22 June, so YTD+2 means publishers who completed their migration to R5.1 on time will have:

  • R5 reports for January to December 2024.
  • R5 and R5.1 reports for January to March 2025.
  • R5.1 reports for April 2025 to April 2026.

YTD+2 means libraries need to be able to harvest January 2024 to December 2026, so the R5 reports for 2024 needs to remain accessible at least until the December 2026 reports are available. When the January 2027 reports become available (due date: 28 Feb 2027), publishers no longer need to maintain their 2024 data and they can retire their old R5 services.

Reprocessed data

Some publishers chose to re-process their older usage data into R5.1 format. As long as the reprocessed data covers YTD+2, those publishers can retire their R5 systems early.

What about the Registry?

We kept Release 4 information in the Registry until March 2023, four years after the compliance date with R5, for the subset of publishers who’d left their R4 services up and running. Our plan is to keep information about R5 reports and COUNTER API (sushi) services available in the Registry for the same amount of time, meaning it’ll show up until March 2029, unless publishers tell us they’ve closed the R5 service. Those reports come with a health warning, though, as no R5 reports have been audited since 2024.

And the Code?

The Code is built and maintained in GitHub, and rendered through Read the Docs. We’ll keep the R5 Code live there. There’s also an archive of all previous releases of the Code in PDF format on this website.

This website uses cookies
This site uses cookies to enhance your browsing experience. We use necessary cookies to make sure that our website works. We’d also like to set analytics cookies that help us make improvements by measuring how you use the site. By clicking “Allow All”, you agree to the storing of cookies on your device to enhance site navigation, analyse site usage, and assist in our marketing efforts.
These cookies are required for basic functionalities such as accessing secure areas of the website, remembering previous actions and facilitating the proper display of the website. Necessary cookies are often exempt from requiring user consent as they do not collect personal data and are crucial for the website to perform its core functions.
A “preferences” cookie is used to remember user preferences and settings on a website. These cookies enhance the user experience by allowing the website to remember choices such as language preferences, font size, layout customization, and other similar settings. Preference cookies are not strictly necessary for the basic functioning of the website but contribute to a more personalised and convenient browsing experience for users.
A “statistics” cookie typically refers to cookies that are used to collect anonymous data about how visitors interact with a website. These cookies help website owners understand how users navigate their site, which pages are most frequently visited, how long users spend on each page, and similar metrics. The data collected by statistics cookies is aggregated and anonymized, meaning it does not contain personally identifiable information (PII).
Marketing cookies are used to track user behaviour across websites, allowing advertisers to deliver targeted advertisements based on the user’s interests and preferences. These cookies collect data such as browsing history and interactions with ads to create user profiles. While essential for effective online advertising, obtaining user consent is crucial to comply with privacy regulations.