Close search
 
Home | Education | Reports | Why not to rely on standard views

Why not to rely on standard views

Anyone who’s attended one of Tasha’s presentations in the last three years knows that she always recommends using the COUNTER Reports rather than the standard views. We built Release 5 from the ground up to be a powerful, flexible and comprehensive usage reporting framework. It replaced the more content-specific reports required in Release 4. To help report consumers (libraries) make the transition to Release 5, we designed a selection of standard views – pre-configured filters of the COUNTER Reports – that mimicked the old Release 4 reports. In this guide, we’ve provided comparison tables to help you spot the limitations of standard views.

Please note: the comparisons on this page are presented as images, as that is the best way to compare the contents of the Reports and the standard views. There is alt-text for each image, but the PDF version of this guide may be more accessible for screen readers.

Platform Report versus PR_P1

The PR_P1 standard view eliminates two Access_Types, one Access_Method, and three metrics. It includes all of the Data_Types that are available in the PR, so for ease of reading we’ve not included that element in this table.

A table comparing the Platform Report with the PR_P1 standard view. The rows show which Access_Type, Access_Method, and Metrics appear in the various reports.
A table comparing the PR and PR_P1

Database Report versus DR_D1 and DR_D2

The DR and its derivative standard views exclude information about Access_Type, so that element is not shown in the table. Both DR_D1 and DR_D2 aggregate metrics by database, meaning it is not possible to see usage or denial information by Data_Type in the standard views. They also both eliminate TDM usage, and only show a limited subset of metrics.

A table comparing the Database Report with the DR_D1 and DR_D2 standard views. The rows show which Data_Type, Access_Method, and Metrics appear in the various reports.
A table comparing the DR with DR_D1 and DR_D2

Title Report versus TR_B series standard views

The TR_B series of standard views eliminate all Data_Types other than Book and Reference_Work. They are all restricted to a single Access_Method, with a limited subset of metrics, and in most cases exclude all but Controlled usage.

A table comparing the Title Report with the book standard views. The rows show which Data_Type, Access_Type, Access_Method, and Metrics appear in the various reports.
A table comparing TR with TR_B1, TR_B2 and TR_B3

Title Report versus TR_J series standard views

The TR_J series of standard views eliminate all Data_Types other than Journal. They are all restricted to a single Access_Method, with a limited subset of metrics, and in most cases exclude all but Controlled usage.

A table comparing the Title Report with the journal standard views. The rows show which Data_Type, Access_Type, Access_Method, and Metrics appear in the various reports.
A table comparing TR with TR_J1, TR_J2, TR_J3 and TR_J4

Item Report versus IR_A1 and IR_M1

The standard views of IR show all three Access_Types, so that element is excluded from the table for ease of reading. Like other standard view, IR_A1 and IR_M1 eliminates one Access_Method and several metrics.

A table comparing the Item Report with the IR_A1 and IR_M1 standard views. The rows show which Data_Type, Access_Method, and Metrics appear in the various reports.
A table comparing IR with IR_A1 and IR_M1
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.