mobile-menu mobile-menu-arrow Menu
 
 

13.0 Transitioning from Previous Releases or to New Reporting Services

A requirement of the COUNTER Code of Practice is that content providers offer libraries access to the current year plus the prior 24 months of usage or from the date they first became compliant, whichever is later. This requirement must continue to be met even when a provider may be transitioning to a new release of the COUNTER Code of Practice or if they are moving to a new reporting service.

13.1 Transitioning to a New Reporting Service

When a content provider implements a new reporting service, underlying logging system, or approach, they:

  • MUST continue to meet the requirement to offer valid COUNTER reports for the current year plus the prior 24 months (or from the date they first became compliant, whichever is later) via a web interface and via a SUSHI server.
  • MUST support COUNTER reports that may include a range of months that span the transition period. If the new reporting service was deployed in August of 2017, a customer could request a report for January–December 2017 and receive a single report.
  • When it is not practical to support a single report with date ranges that span the transition period, the content provider MUST perform the transition on the first day of a month. If the new reporting service was deployed in August 2017, a customer wanting January–December 2017 usage would request January–July 2017 from the previous reporting service and August–December 2017 from the new reporting service. For clarity, a provider MUST NOT perform the transition mid-month such that the customer is required to run reports on both the old and new reporting services for the same month and merge and sum the results to obtain actual monthly usage.

13.2 Transitioning to a New Code of Practice

New releases of the COUNTER Code of Practice will typically be assigned an effective date after which a content provider must be compliant. In such cases, a content provider may choose to implement the new release before the effective date. New releases of the COUNTER Code of Practice may come with specific transition instructions, but, in general, content providers:

  • May implement the new release prior to the effective date of the new release.
  • Are not required to release reports for usage transacted prior to the implementation date; however, they may choose to do so at their discretion.
  • MUST continue to meet the requirement to offer valid COUNTER reports for the current year plus the prior 24 months (or from the date they first became compliant, whichever is later) via a web interface and via a SUSHI server.
  • MUST provide a means for customers to receive prior-release reports for usage transacted from the content provider’s transition date through to 3 full months after the effective date of the new release. For clarity, if a new release becomes effective 1 February 2019 and a content provider implements the new release 1 October 2018, a customer must be able to obtain the prior-release usage reports for usage prior to the transition period as well as for usage that occurred in October 2018 to April 2019. A content provider can meet this requirement in one of the following ways:
    • Maintain two reporting systems such that usage is logged to the old and new reporting services and customers can access current-release reports on the new reporting service and prior-release reports on the old reporting service.
    • Support the prior-release reports on the new reporting service. This may involve using the metrics from the new release to produce reports formatted to the prior release; or it may involve logging additional data to the new reporting service such that the prior release reports can continue to be supported.
    • If the new release offers metrics compatible with the prior release, offer only new release reports provided customers have access to freely available tools that will automatically generate the required prior release report from an equivalent new release report and meet the requirement that these reports are available in tabular form and via the COUNTER_SUSHI API.
  • May choose to support COUNTER reports that include a range of months that span the transition period. E.g. if the new reporting service compliant with a new COUNTER release was deployed in October of 2018, a customer could request a report for January–December 2018 and receive a single report in either the new release or the previous release (see previous point on the transition period).
  • When it is not practical to support a single report with date ranges that span the transition period, the content provider MUST perform the transition on the first day of a month. E.g. if the new reporting service was deployed in October 2018, a customer wanting January–December 2018 usage would request January–September 2018 from the previous reporting service and October–December 2018 from the new reporting service. For clarity, a provider MUST NOT perform the transition mid-month such that the customer is required to run reports on both the old and new reporting services for the same month and merge and sum the results to obtain actual monthly usage.

13.3 Transitioning from COUNTER R4 to R5

The transition from R4 to R5 meets the general requirements outlined in 13.2.

  • Content providers MUST be compliant by February 2019 for delivery of R5 reports starting with January 2019 usage.
  • Content providers may choose to release their R5 compliant reporting service before February 2019.
  • A content provider’s customers MUST be able to obtain R4-compliant reports for that content provider from the time the content provider’s R5 reporting service was released through to April 2019 (providing access to March 2019 usage). A content provider may provide access to R4 reports beyond April 2019 at their discretion.
  • Content providers may choose to meet the requirement to provide R4 report based on R5 metrics. The following R4 reports must be supported (when applicable to the platform): BR1, BR2, BR3, DB1, DB2, JR1, JR2, JR5, and PR1. The following table presents the equivalent R4 metric types and R5 Metric_Types and filters by report.
R4 Report R4 metric R5 equivalent
BR1 Full-text requests (at the book level) Unique_Title_Requests AND Data_Type=Book AND Section_Type=Book
BR2 Full-text requests (at the chapter/section level) Total_Item_Requests AND Data_Type=Book AND Section_Type=Chapter|Section
BR3 Access denied – concurrent/simultaneous user limit exceeded Limit_Exceeded AND Data_Type=Book
Access denied – content item not licensed No_License AND Data_Type=Book
DB1 Regular searches Searches_Regular
Searches – federated and automated SUM (Searches_Automated, Searches_Federated)
Result clicks Total_Item_Investigations attributed to the database
Record views Total_Item_Investigations attributed to the database. (Note that resulting result click and record view counts will be the same. Librarians should use one or the other and not add them up.)
DB2 Access denied – concurrent/simultaneous user limit exceeded Limit_Exceeded AND Data_Type=Database
Access denied – content item not license No_License AND Data_Type=Database
JR1 Full-text requests Total_Item_Requests AND Data_Type=Journal
HTML requests Leave blank unless format of HTML and PDF are also logged in which case: Total_Item_Requests AND Data_Type=Journal AND Format=HTML
PDF requests Leave blank unless format of HTML and PDF are also logged in which case: Total_Item_Requests AND Data_Type=Journal AND Format=PDF
JR2 Access denied – concurrent/simultaneous user limit exceeded Limit_Exceeded AND Data_Type=Journal
Access denied—content item not licensed No_License AND Data_Type=Journal
JR5 Full-text requests (by year of publications) Total_Item_Requests AND Data_Type=Journal, pivot on YOP
PR1 Regular searches Searches_Platform
Searches – federated and automated Leave blank (Searches performed on the platform via federated and automated searching are included in Searches_Platform).
Result clicks SUM (Total_Item_Investigations attributed to the databases)
Record views SUM (Total_Item_Investigations attributed to the databases). (Note that resulting result click and record view counts will be the same. Librarians should use one or the other and not add them up.)
 
Release 5 Queries COP Register Members Guides Members

Gold, Silver and Bronze Sponsors