Code of Practice Release 5.1.1

We have published the latest fix and feature release of the COUNTER Code of Practice, R5.1.1.

New features and links to best practice

• COUNTER’s Bots list is now under our control: we’ve migrated the list to a new repository and updated Section 7.8 for clarity
• There’s an extension to the COUNTER API /reports endpoint about the date of last data change and another about extension for platform information
• The new Pathway to Compliance is in Section 10.5
• We’ve added information about reporting syndicated usage and the removal of distributed usage logging (DUL)
• We’ve incorporated the Code of Practice for Research Data into the main Code, as Section 10.4.

Bug fixes

• Fix list of reports for Data_Type in Section 3.2.2 (Table 3.l)
• Fix invalid ISIL pattern in COUNTER API Specification
• Fix Status.Registry_Record in the COUNTER_API Specification
• Fix missing DR_D1 for Unique_Item_Investigations and Unique_Item_Requests in Section 3.3.3 (Table 3.s)
• Fix Section 4 to require Institution_ID in report headers
• Fix regular expression for proprietary identifiers in the COUNTER API Specification
• Having JSON Report_Filters sorted differently for Standard Views leads to a validation error
• Fix the COUNTER API Specification to only allow Release 5.1 in the /r51/reports response
• Fix definitions of the include_parent_details and include_component_details parameters in the COUNTER API Specification
• Fix description of Standard Views of the Title Report in Section 3.1.2.3
• Fix broken link and add missing entry for R5.1.0.1 CHANGELOG

Clarifications and minor text edits

• Add missing Article_Version in IR samples for COUNTER R5.1
• Add a proprietary Institution_ID to the sample reports
• Add missing rules for counting redirect HTTP status codes to Section 7.1
• Add missing keywords from RFC 2119 to Section Conventions
• Clarify audit tests for the COUNTER API (formerly sushi)
• Clarify audit timelines in Section 9.3
• Clarify appropriate security for the COUNTER API
• Clarify handling of reports without usage and use of Exceptions 303X
• Clarify which Report Filters and Attributes are optional for the report providers to implement
• Update custom report example in Section 11.1
• Update COUNTER URL domain
• Update Glossary for R5.1.1
• Rename COUNTER Validation Tool to COUNTER Validator
• Merge the Code for Research Data into the COUNTER Code of Practice