Tech Support
Audit extensions as we transition to Release 5.1
COUNTER has always had rules for granting audit extensions. As report providers transition between Release 5 and Release 5.1, we recognise there needs to be some flexibility. In this tech…
Managing ‘Reporting Period Total’ in JSON format
The Code of Practice allows for different facets of granularity in reporting usage metrics. One of those facets is whether usage is reported month-by-month, or as the sum of all…
Counting usage for Tables of Contents
Release 5.1 brought usage tracking for books and reference works into line with that for other data types like journals and multimedia, but there are still some complexities. This post…
Syndicated usage reporting and GetFTR
Earlier this year, we released best practice guidance about reporting usage of content that is syndicated and available on multiple platforms. Syndicated usage reports allow publishers to understand which syndication…
Choosing the right COUNTER metric
One of the most common questions people ask us is which metric libraries should be using to assess return on investment. As it says in our FAQs, that depends on…
Common validation errors: learning from others’ mistakes
It’s been about a month since our new Validation Tool for R5.1 became publicly available (time flies!). Thus far, nine report providers – representing over a third of publishing platforms…
Free to read?
We’ve had a couple of messages asking about one particular change in Release 5.1. This change is the inclusion of the new Free_To_Read Access Type alongside Controlled and Open. We…
Release 5.1 Validation Tool
We are extremely pleased to announce that we have updated the COUNTER Validation Tool to support Release 5.1 of the Code of Practice. We are very grateful to the wonderful…
Guest post: COUNTER API (sushi) validation
In this guest post, Beda Kosata from our partner Big Dig Data, the developers of the COUNTER harvesting tool Celus, explains how to validate a response from a COUNTER API…