Release Description of Change Substantive? Date approved Date for compliance 5.0 New Code of Practice to replace Release 4. Yes 2017-07-01 2019-02-28 (with support for January 2019 usage)
A requirement of the COUNTER Code of Practice is that content provider’s offer libraries access to the current year plus the prior 24 months of usage 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 […]
With R5, the COUNTER Code of Practice will operate under a continuous maintenance procedure to allow incremental changes to be made to the Code of Practice without creating a completely new release. This section describes those procedures. 12.1 Instructions for Submittal of Proposed Change Changes and updates to the COUNTER Code of Practice can be […]
COUNTER recognises that some content providers may want to provide customized versions of COUNTER reports to address reporting needs specific to their platform and content. This section describes a method of extending the Code of Practice that avoids creating conflicting custom implementations between content providers. 11.1 Platform as a Namespace Content providers and other organizations […]
Content providers seeking COUNTER compliance are expected to comply with the following. 10.1 Including COUNTER in Licence Agreements To encourage widespread implementation of the COUNTER Code of Practice, customers are urged to include the following clause in their licence agreements with content providers: ‘The licensor confirms to the licensee that usage statistics covering the online […]
An important feature of the COUNTER Code of Practice is that compliant content providers (including third-party services providing stats on behalf of content providers) MUST be independently audited on an annual basis in order to maintain their COUNTER-compliant status. To facilitate this, a set of auditing standards and procedures has been published in Appendix E […]
Content providers MUST support automatic harvesting of COUNTER reports via the COUNTER_SUSHI. Specifications for the RESTful COUNTER_SUSHI API are found here: https://app.swaggerhub.com/apis/COUNTER/counter-sushi_5_0_api/1.0.0 8.1 COUNTER_SUSHI API Paths to Support The following paths (methods) MUST be supported: Path Description GET /status Returns the current status of the COUNTER_SUSHI API service. This path returns a message that includes the […]
Usage data collected by content providers for the usage reports to be sent to customers should meet the basic requirement that only intended usage is recorded and that all requests that are not intended by the user are removed. Because the way usage records are generated can differ across platforms, it is impractical to describe […]
Usage data can be generated in a number of ways, and COUNTER does not prescribe which approach should be taken. The two most common approaches are: Log file analysis, which reads the log files containing the web server records all of its transactions Page tagging, which uses JavaScript on each page to notify a third-party […]
Content providers MUST make tabular versions of COUNTER reports available from an administrative/reporting site accessible by members of the institution requesting the report. All COUNTER reports provided by the content provider MUST also be available via SUSHI protocols. Delivery requirements are: Reports MUST be provided in the following formats: Microsoft Excel file (see Section 4.1 […]
Menu
