These "Usage Data Collection Best Practices" were developed by the consortium's Acquisitions and Eresources Team. They offer a guide on effective methods for collecting and analyzing usage data. This resource is designed to support library staff in making informed decisions about resource management and assessment.
Later users of your data need to know the criteria used. Note the report type (COUNTER 5 or other), the date range, and any other relevant details. If possible, embed this info into the report output itself. If that is not possible, add a separate document to your folder as a read-me or with another descriptive filename like "About Report X.” If you combine or otherwise modify data in Excel, when possible use formulas that can later be viewed by others, rather than keying in calculated data. If a report requires data to be combined from multiple sources, document each of the sources so it can be compiled consistently in the future.
Cost-per-use (CPU) = cost divided by the number of uses. This metric assigns a financial value to each recorded use of a resource and is helpful in systematically identifying resources that may have a low return on investment. One rule of thumb is to review all resources with a CPU higher than the cost of interlibrary loan, since those represent cases where it would have been more cost effective to request the item through interlibrary loan for each recorded use than to pay for a subscription. Your institution can determine a CPU threshold that makes sense for your community’s patterns of use and resource needs.
CPU is just one aspect to consider in collection assessment. Since our primary goal is to serve an academic need and CPU is just one way to measure the effectiveness of our service, it is not the only metric that should be considered when making collection development decisions. If CPU is low, that shows the resource is cost effective, but if CPU is higher than the target threshold, this does not indisputably indicate that a subscription is not of value. Some resources are required for accreditation in certain departments or could be absolutely essential to the teaching and research of a group too small to contribute to a CPU equal to or greater than the desired threshold. Therefore, these calculations should be used to flag titles for further investigation and discussion with stakeholders rather than signal a straightforward need for cancellation.