As information resources move into an ever-more digital environment, it is critical for libraries and publishers alike to prove how the data is accessed and by whom.
Librarians want to understand better how the information resources—usually purchased from a variety of sources—are being used; publishers want to know how the information products they disseminate are being accessed. An essential requirement to meet these objectives is an international set of standards and protocols governing the recording and exchange of online usage data as established by the COUNTER Codes of Practice.
COUNTER is supported by a global community of members, including libraries, library consortia, publishers, vendors, and professional associations. Please support COUNTER and keep up-to-date with our news and developments by becoming a member.
Drawing upon a single set of standards on a worldwide scale, BPA-iCompli’s COUNTER audits meet those strict quality guidelines for CREDIBILITY, CONSISTENCY, and COMPATIBILITY.
Am iCompli COUNTER Audit allows publishers to provide:
Credibility: By performing actual resource requests on the publisher’s system, recording all of these requests and then comparing the recorded requests with the resultant COUNTER reports, iCompli verifies that the data represented in the report accurately match the activity that was performed. This process ensures that libraries can trust the reliability of the media owner’s activity claims.
Consistency: COUNTER Code of Practice standards include specific rules regarding formatting and content of all reports. iCompli’s COUNTER Audit independently verifies that the media owner’s reports follow these rules. This assures libraries, which may receive activity reports from many different sources, that all data can be analyzed consistently and on a comparable basis.
Compatibility: iCompli’s COUNTER Audit provides assurance that the publisher adheres to the COUNTER Code of Practice requiring data be made available in either CSV or Excel format for maximum compatibility with all library database platforms. In addition, release 3 requirements add that data must be available in XML format for automated retrieval purposes.