Close search
 
Home | News | Pathways to Compliance: consultation outcomes and next steps

Pathways to Compliance: consultation outcomes and next steps

11 March 2026

We’re excited to share a progress update following our open consultation on the draft Pathways to Compliance best practice guidelines. The consultation ran from early December 2025 to early February 2026 and we had a good selection of responses. Huge thanks to everyone who provided feedback! The responses offer a clear direction in many areas, with only two points needing extra discussion.

Consensus points

The consultation revealed overwhelming agreement (85%+) on several key points:

  • All respondents agreed to adopt the eligibility criteria for ‘small publishers’ that we proposed in the draft recommendations.
  • Everyone also agreed that Pathway publishers will only need to provide the COUNTER reports. That means the PR, DR, TR, and IR, as relevant, with all attributes by default. That means no standard views.
  • Another unanimous point was that Pathway publishers should be exempt from formal audits. As we said in the consultation, we’ll be making updates to the Registry to make Audit and Pathway statuses clearly visible.
  • Denial metrics weren’t quite unanimous, but a solid majority (86%) of respondents were comfortable with denial metrics being optional.

Areas for discussion

Two areas saw a significant split in responses: report formats, and search metrics. They’ll be the focus of the working group’s next steps.

Respondents were really divided on the JSON format, delivered through the COUNTER API (sushi). Many librarian and consortia respondents strongly advocated for JSON reports delivered through the COUNTER API. Further questions suggest that it’s the delivery mechanism that is the stumbling block. Manual harvesting and converting tabular to JSON is seen to be too time consuming. By contrast our small publisher respondents said that requiring JSON and the COUNTER API immediately would make the Pathway non-viable for them. The working group agrees that tabular reports are better than no reports, but we’ll need to flesh out requirements about how they should be shared with librarians.

Search metrics also split our respondents. 59% agreed that search metrics should be optional, and 41% stated that they’re absolutely necessary for database providers. At the moment, the working group is suggesting that we should make search metrics recommended but not mandatory in the Database Report for relevant Host Types, but allow other publishers on the Pathway to exclude search metrics if they need to.

Next steps

The working group is finding the best way forward on our areas for discussion, and will prepare a best practice guide for the Executive Committee to review. Stay tuned for more updates as we finalize the guidelines!

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.