PIRUSLast updated: October 2013
Introduction to Release 1 of the PIRUS Code of Practice for recording and reporting usage at the individual article level
The PIRUS Code of Practice has been established to provide a COUNTER-compliant standard for the recording, consolidation and reporting of usage at the individual article level of Journal Articles hosted by Publishers, Aggregators, Institutional Repositories and Subject Repositories.
PIRUS builds on the COUNTER Code of Practice and COUNTER will be responsible for its development, ongoing management and implementation. To have their usage statistics and reports designated PIRUS-compliant vendors and services will have to provide usage statistics that conform to this Code of Practice. Vendors that are already COUNTER-compliant will find it relatively straightforward to conform to the PIRUS standard. In addition to what is already provided for COUNTER, the key additional metadata requirements for PIRUS- compliance will be:
The PIRUS Code of Practice provides a standard that enables any organization hosting journal articles to report in a credible, consistent and compatible way the usage of these articles to authors, their institutions and their funding organizations. It also enables vendors to consolidate usage of articles on different platforms into a global usage total.
Scope of PIRUS
The PIRUS Code of Practice provides a framework for the recording, exchange and interpretation of online usage statistics for individual full-text journal articles. In doing so, it covers the following areas:
While this Release focuses on journal articles, its principles may be applied to other categories of individual content items that are well defined, and have sufficiently robust metadata associated with them
Features of PIRUS
The PIRUS Code of Practice provides the specifications and tools that will allow COUNTER-compliant publishers, repositories and other organizations to record and report usage statistics at the individual article level that are credible, compatible and consistent. COUNTER-compliant publishers may build on the existing COUNTER tools to do so, while an alternative approach is provided for non-COUNTER compliant repositories, which is tailored to their systems and capabilities. This Code of Practice contains the following features:
Reporting usage at the individual article level
Unlike the standard COUNTER usage reports, which vendors must update monthly for all products covered, the PIRUS usage reports do not have to be provided monthly for every article they cover (but should be broken down by month when reported). Rather, the vendor must have the capability to produce the PIRUS reports for all the journal articles they host on an annual basis, as a minimum requirement.
The PIRUS Code of Practice provides two reports for this purpose: