1 / 31

COUNTER in context Where have we got to? Where are we going? Peter Shepherd UKSG, March 2009

COUNTER in context Where have we got to? Where are we going? Peter Shepherd UKSG, March 2009. COUNTER: current Codes of Practice. 1) Journals and databases Release 1 Code of Practice launched January 2003 Release 2 published April 2005 replacing Release 1 in January 2006

bairn
Télécharger la présentation

COUNTER in context Where have we got to? Where are we going? Peter Shepherd UKSG, March 2009

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. COUNTER in contextWhere have we got to?Where are we going?Peter ShepherdUKSG, March 2009

  2. COUNTER: current Codes of Practice 1) Journals and databases • Release 1 Code of Practice launched January 2003 • Release 2 published April 2005 replacing Release 1 in January 2006 • Now a widely adopted standard by publishers and librarians • 100+ vendors now compliant • 15000+ journals now covered • Librarians use it in collection development decisions • Publishers use it in marketing to prove ‘value’ • Release 3 published August 2008, implemented by 31 August 2009 • 2 vendors already compliant: HighWire Press, MPS Technologies 2) Books and reference works • Release 1 Code of Practice launched March 2006 • 12 vendors now compliant • Relevant usage metrics less clear than for journals • Different issues than for journals • Direct comparisons between books less relevant • Understanding how different categories of book are used is more relevant

  3. Code of Practice for Journals and Databases:Release 3 – main features • SUSHI protocol incorporated into R3 • Usage Reports must be provided in XML as well as in Excel • Vendors providing journal archives as a separate acquisition must report usage of these in a separate report • Search and Session activity generated by federated search engines and automated search agents must be reported separately • New library consortium usage reports, in XML only • Activity generated by internet robots, crawlers, etc. must be excluded form the COUNTER reports • A new optional additional report that enables usage of journals and books available on the same platform to be included in the same COUNTER report Release 3 is available at http://www.projectcounter.org/code_practice.html

  4. Journal and Database Code of Practice: Release 3 Usage Reports • Consortium Report 1 (XML only) • Successful full-text journal article or book chapter requests by month • Consortium Report 2 (XML only) • Total searches by month and database • Journal Report 1 • Full text article requests by month and journal • Journal Report 1a • Full text article requests from an archive by month and journal • Journal Report 5 • Full-text article requests by year-of-publication and journal • Journal Report 2 • Turnaways by month and journal • Database Report 1 • Total searches and sessions by month and database • Database Report 2 • Turnaways by month and database • Database Report 3 • Searches and sessions by month and service

  5. Code of Practice for books and reference works: Release 1 • Book Report 1 • Number of successful requests by month and title • Book Report 2 • Number of successful section requests by month and title • Book Report 3 • Turnaways by month and title • Book Report 4 • Turnaways by month and service • Book Report 5 • Total searches and sessions by month and title • Book Report 6 • Total searches and sessions by month and service

  6. COUNTER Audit • Independent audit required within a specified period from compliance, and annually thereafter • Audit is online, using scripts provided in the Code of Practice • Auditor can be: • Any Chartered Accountant • Another COUNTER-approved auditor • ABCe is the first COUNTER-approved auditor • Industry-owned • Not-for-profit • Independent and impartial • Part of ABC (Audit Bureau of Circulations) • Providing website traffic audits for over 150 companies and certifying over 1400 domains • Have successfully completed audits on Release 2 compliant vendors

  7. Future challenges • Improving/extending the Codes of Practice • Reliability ( audit, federated searches,) • Usability (number of compliant vendors, XML format, additional usage reports) • Database usage reports • Additional data (year of publication, individual article usage data) • Usage statistics for Institutional Repositories • Categories of content/activity • Online publications are more than collections of articles • How to reflect the value provided by other features • Deriving metrics from the Codes of Practice • Journals (cost per use, Usage Factor) • Databases? • Books?

  8. The Database Report Question……… • Searches and sessions inadequate metrics • Legacy of pre-internet database environment • Overtaken by developments in technology • Federated searches, automated searches • No longer useful measures of value • Possible new metrics… • e.g.…….. ‘Effectiveness ratio’ = no. of searches/no. of results discuss……..

  9. PIRUS Publisher and Institutional Repository Usage Statistics • A COUNTER Project • Sponsored by JISC through the PALS Metadata and Interoperability programme (phase 3) • Not just about measuring article usage in IRs

  10. Increasing interest in article level usage • More journal articles hosted by Institutional and other Repositories • Authors and funding agencies are increasingly interested in a reliable, global overview of usage of individual articles • Online usage becoming an alternative, accepted measure of article and journal value • Knowledge Exchange report recommends developing standards for usage reporting at the individual article level • Usage-based metrics being considered as a tool for use in the UK Research Excellence Framework and elsewhere.

  11. Article usage metrics now more practical • Implementation by COUNTER of XML-based usage reports makes more granular reporting of usage a practical proposition • Implementation by COUNTER of the SUSHI protocol facilitates the automated consolidation of usage data from different sources.

  12. The challenge • An article may be available from:- • The main journal web site • Ovid • ProQuest • PubMed Central • Authors’ local Institutional Repositories • If we want to assess article impact by counting usage, how can we maximise the actual usage that we capture?

  13. PIRUS Project Mission • To develop a global standard to enable the recording, reporting and consolidation of online usage statistics for individual journal articles hosted by Institutional Repositories, Publishers and other entities

  14. PIRUS Project Aims • Develop COUNTER-compliant usage reports at the individual article level • Create guidelines which, if implemented, would enable any entity that hosts online journal articles to produce these reports • Propose ways in which these reports might be consolidated at a global level in a standard way.

  15. Stakeholder survey • Survey of publishers, aggregators, and hosts by Peter Shepherd:- • American Chemical Society • American Institute of Physics • Atypon • BioMed Central • EBSCO • Elsevier • Informa • Ingenta • Institute of Physics Publishing • Nature • OUP • Ovid • Sage • Springer • Wiley-Blackwell

  16. Stakeholder survey • Survey of IRs by Paul Needham, covering these systems:- • DSpace • Eprints • Fedora • Digital Commons

  17. Publisher response • Majority enthusiasm for concept • All surveyed publishers use DOIs to identify all versions of a single published work • Minority concern that article level reporting to institutional customers is our goal • It isn’t • Concern about size of any reports providing usage data at article level. • Not the intention of the project to recommend publishers produce reports relating to more than one article at a time

  18. IR response GOOD NEWS • The overwhelming majority of respondents add DOIs to their records - where they are available. BUT……. • No standard process for allocating DOIs in IRs • Great variation in the metadata element used to store them:- • dc.description • dc.identifier • dc.identifier type DOI • dc.identifier.citation • dc.relation.isreferencedby • dc.rights • DOI • relation

  19. PIRUS Outputs • A proof-of-concept COUNTER-compliant XML prototype for an individual article usage report • Can be used by both repositories and publishers

  20. PIRUS outputs 2. A tracker code, to be implemented by repositories that sends a message to either: • an external party that is responsible for creating and consolidating usage statistics and for forwarding them to the relevant publisher for consolidation • The local repository server

  21. Step 1: a fulltext article is downloaded Step 2: tracker code invoked, generating an OpenURL log entry Scenario A Scenario B Scenario C Step A1: OpenURL log entries sent to external party responsible for creating and consolidating the usage statistics Step B1: OpenURL log entry sent to local server Step C1: OpenURL log entry sent to local server Step B2: OpenURL log entries harvested by external party responsible for creating and consolidating usage statistics Step C2: logs filtered by COUNTER rules Step A2: logs filtered by COUNTER rules Step C3: COUNTER-compliant usage statistics collected and collated per article (DOI) in XML format Step B3: logs filtered by COUNTER rules Step A3: COUNTER-compliant usage statistics collected and collated per article (DOI) in XML format Step B4: COUNTER-compliant usage statistics collected and collated per article (DOI) in XML format Step C4: COUNTER compliant usage statistics available from IR to authorized parties Step A4: COUNTER compliant usage statistics available from central organization to authorized parties Step B5: COUNTER compliant usage statistics available from central organization to authorized parties PIRUS outputs 3.

  22. PIRUS outputs 4.Specification for the criteria for a a central facility that will create the usage statistics where required or collect and consolidate the usage statistics

  23. PIRUS recommendations • To JISC: PIRUS has demonstrated that it is technically feasible to create, record and consolidate usage statistics for individual articles using data from repositories and publishers. To translate this into a new, implementable COUNTER standard and protocol further research will be required into technical, organizational, economic and political aspects.

  24. PIRUS recommendations • To COUNTER: expand the mission of COUNTER to include usage statistics from repositories; consider implementing the new Article Report 1 as an optional additional report; modify the existing independent COUNTER audit to cover new reports and processes.

  25. PIRUS recommendations • To Repositories: subject repositories to participate in the next stage of this project. All repositories should use standard data descriptions for article versions etc.

  26. PIRUS recommendations • To publishers/vendors: accept, in principle, the desirability of providing credible usage statistics at the individual article level.

  27. PIRUS recommendations • To publishers/vendors: accept, in principle, the desirability of providing credible usage statistics at the individual article level.

  28. PIRUS Project Team • Richard Gedye Oxford University Press • Ed Pentz CrossRef • Ross MacIntyre MIMAS • Tim Brody University of Southampton • Sally Rumsey University of Oxford • Paul Needham Cranfield University • Peter Shepherd COUNTER (Project Manager)

  29. COUNTER Membership • Member Categories and Annual Fees (2009) • Publishers/intermediaries: $850 • Library Consortia: $560 • Libraries: $425 • Industry organization: $425 • Library affiliate: $170 (non-voting member) • Benefits of full membership • Owner of COUNTER with voting rights at annual general meeting, etc. • Regular bulletins on progress • Opportunity to receive advice on implementation • Vendors: no compliance fee; reduced price audit fees

  30. http://www.projectcounter.org Apply for COUNTER membership

  31. For more information………. http://www.projectcounter.org Thank you! Peter Shepherd, COUNTER pshepherd@projectcounter.org

More Related