1 / 12

COUNTER Code of Practice

COUNTER Code of Practice. Consortial Reports Kathy Perry, VIVA Director kperry@gmu.edu ICOLC, Montreal April 25, 2007. Consortium Reports. Current reports are inadequate Committee formed to seek input and propose alternatives Peter Shepherd, Project COUNTER Kathy Perry, VIVA

paloma
Télécharger la présentation

COUNTER Code of Practice

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 Code of Practice Consortial Reports Kathy Perry, VIVA Director kperry@gmu.edu ICOLC, Montreal April 25, 2007

  2. Consortium Reports • Current reports are inadequate • Committee formed to seek input and propose alternatives • Peter Shepherd, Project COUNTER • Kathy Perry, VIVA • Oliver Pesch, EBSCO Information Services • New COUNTER Consortial Reports • Full text download requests • Database searches

  3. Consortia Reports • Not just a single number total of all searches by the consortium each month • Accumulates the reports for all members • Only in XML • Requires “processing” by consortium • Proposed COUNTER schema update will support Consortium Reports as well as all other reports • No need to tally totals in XML report

  4. Section 4.3 Report Delivery Report delivery must conform to the following standards: • XML is the only approved format for consortial reports. An XML schema for such reports is available at http://www.niso.org/schemas/sushi/index.html. • Reports should be made available on a password-controlled website (accompanied by an e-mail alert when data is updated). Access to consortia level reports must be through the same user id and password for all consortium members. (This user id and password must be different from those used for administrative purposes for each institution.) • Reports must be readily available • Reports must be posted and available monthly • Data must be updated within four weeks of the end of the reporting period • All of last calendar year’s data and this calendar year’s to date must be supplied

  5. 4.2 Usage Reports for Consortia COUNTER has drafted two new reports for library consortia • Consortium Report 1: Number of successful full-text requests by month(XML only). This report will be a single XML file, broken down by consortium member, which contains the full-text usage data for every online journal and book taken by individual consortium members. • Consortium Report 2: Total searches by month and database (XML only). This report will be a single XML file, broken down by consortium member, which contains the search counts for every each database taken by individual consortium members.

  6. Timeline

  7. Timeline for Revised Consortia Reports • Winter 2006: Redraft Section 4.3 • April – May 15, 2007: ICOLC Review and Comments • Summer 2007: Vendor Review and Comments • Early Fall 2007: Optional Consortial Reports • Late 2007: COP Release 3 out for review and comments • By Summer 2008: Release 3 Approved

  8. Role of ICOLC Members • JoinCOUNTER • Monitor the relevant listserv on usage statistics issues lib-stats@newcastle.ac.uk • Talk with your colleagues

  9. Librarians in COUNTER • Board of Directors • David Goodman, Long Island University, USA • Ann Okerson, Yale U and NERL, USA • Christine Fyfe, U of Leister, UK • Executive Board • Christine Fyfe, U of Leister, UK • David Goodman, Long Island U, USA • Tony Kidd, U of Glasgow, UK • Kathy Perry, VIVA, USA • Hazel Woodward, Cranfield U, UK • Joe Zucca, U of Penn, USA

  10. Librarians in COUNTER (cont’d) • International Advisory Board • Lars Bjornshauge, Lund U, Sweden • Andrew Braid, British Library, UK • David Brown, British Library, UK • Diane Costello, CAUL, Australia • Denise Davis, ALA, USA • Lorraine Estelle, JISC, UK • Bernd-Christoph Kaemper, U of Stuttgart, Germany • Shinya Kato, U of Tokyo, Japan • Ross MacIntyre, U of Manchester, UK • Alison McNab, U of Nottingham, UK • James Mouw, U of Chicago, USA • Sherrie Schmidt, ARL, USA • Jill Taylor-Roe, U of Newcastle, UK

  11. Role of ICOLC Members (cont’d) • Actively encourage Counter Compliance (Nag!) • Require in licenses and RFPs • Check list of COUNTER Compliant Vendors • http://www.projectcounter.org/articles.html • Urge all vendors to be COUNTER compliant at all appropriate levels at most recent level of Code of Practice • Urge them to have XML reports • Verify their status is accurate and complete • Report anomalies to Peter Shepherd

  12. For more information………. http://www.projectcounter.org Peter Shepherd, COUNTER pshepherd@projectcounter.org Kathy Perry, VIVA kperry@gmu.edu

More Related