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 License Agreements To encourage widespread implementation of the COUNTER Code of Practice, customers are urged to include the following clause in their license 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 API. The specification for the RESTful COUNTER_SUSHI API is maintained by COUNTER on SwaggerHub: https://app.swaggerhub.com/apis/COUNTER The Swagger files are a comprehensive reference version that contains a detailed description of the entire COUNTER_SUSHI API. It is expected that reporting services will use only 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 of all 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 the COUNTER_SUSHI API. Delivery requirements are: Reports MUST be provided in the following formats: Microsoft Excel file (see Section […]
4.1 Platform Reports Platform Reports provide a summary of activity on a given platform to support the evaluation of platforms and to provide high-level statistical data to support surveys and reporting to funders. Table 4 (below): Platform Master Report and Standard Views Report_ID Report_Name Details Host_Types PR Platform Master Report A customizable report summarizing activity […]
3.1 COUNTER Reports for Libraries Reports for R5 consist of four Master Reports that allow the librarian to filter and configure to create customized views of their usage data. R5 also specifies Standard Views (pre-set filters/configuration). To achieve compliance, a content provider MUST offer the Master Reports and Standard Views that are applicable to their […]
This section provides an overview of the scope of the COUNTER Code of Practice. Section 3 Technical Implementation of COUNTER Reports introduces the REQUIRED reports, describes the common format shared by all COUNTER reports, and defines the COUNTER report attributes and their values. Section 4 COUNTER Reports provides detailed specifications for each COUNTER report. Use […]
Menu
