Usage Statistics and Publishers Implementation and New Insights

Usage Statistics and Publishers: Implementation and New Insights Usage Statistics in Context: related standards and tools Oliver Pesch Chief Strategist, E-Resources EBSCO Information Services September 20, 2010

Overview • • The librarian’s view of the landscape Tools and standards Importance of getting it right Looking ahead

Much of the library collection no longer resides in the library Library Collection Publisher Site 1 Publisher Site 2 Aggregator Site 1 Library

Users are often not in the library. Usage data is captured by the content provider (not the library) Library Collection Publisher Site 1 Publisher Site 2 Aggregator Site 1 Library

User are often not in the A librarian wanting to library. collect usage data has to Usage data is captured by download reports from the content provider (not content providers. the library) Library Collection Publisher Site 1 Publisher Site 2 Aggregator Site 1 Usage ? Library

These reports are then loaded into some kind of tool to consolidate the usage, so a single report can be prepared. Library Collection Publisher Site 1 Publisher Site 2 Usage consolidation tool Aggregator Site 1 Usage ? Library

Initially there were a number of challenges with this approach. COUNTER was created to address these. Library Collection Publisher Site 1 Different formats Different terminology Different counting rules Usage consolidation tool Publisher Site 2 Aggregator Site 1 Usage ? Library

Retrieving reports is a lot of work. The role of SUSHI is to automate this process. Library Collection Publisher Site 1 Retrieving stats can be time consuming Publisher Site 2 Usage consolidation tool Aggregator Site 1 Usage ? Library

SUSHI uses a client/server approach in which software at the library talks to software at the publisher site to retrieve the reports Library Collection Publisher Site 1 Publisher Site 2 Usage consolidation tool Aggregator Site 1 Usage ? Library

Acquire Librarians a client/server SUSHI uses also measure value by computing software approach in which cost-peruse. the library talks to at Cost data must be obtained and loaded into the software at the publisher system. site to retrieve the reports Agent Library Collection Publisher Site 1 Acquisitions System Publisher Site 2 Consortium Usage consolidation tool Other Cost/Use ? Library Aggregator Site 1

Acquire Cost information is combined with usage numbers to create the measures. Library Collection Publisher Site 1 Agent Acquisitions System Publisher Site 2 Consortium Usage consolidation tool Other Cost/Use ? Library Aggregator Site 1

Acquire If the library is using an ERM system, it will have a knowledge base. Publisher Site 1 Agent Acquisitions System Library Collection Knowledge base Publisher Site 2 Consortium Usage consolidation tool ERM Other Cost/Use Library Aggregator Site 1

Acquire The title lists for the knowledge base usually come from content providers Publisher Site 1 Agent Acquisitions System Library Collection Knowledge base Publisher Site 2 Consortium Usage consolidation tool ERM Other Cost/Use Library Aggregator Site 1

Acquire Inconsistent reports, inaccurate lists, lack of information cause problems Publisher Site 1 Agent Acquisitions System Library Collection Knowledge base Publisher Site 2 Consortium Usage consolidation tool ERM Other Cost/Use Library Aggregator Site 1

Acquire KBART is a recommended practice to improve the knowledge base quality Publisher Site 1 Agent Acquisitions System Library Collection Knowledge base Publisher Site 2 Consortium Usage consolidation tool ERM Other Cost/Use Library Aggregator Site 1

More on standards, tools and available assistance…

The technology behind SUSHI is a simple standard that: • Allows software on one computer to request a COUNTER report from another. • Describes a web service based on the SOAP standard, which is: – a client/server protocol; – using a “request”/”response” approach. • The client sends a “request” identifying the account, the desired report and the date range • The server prepares the report then sends back a “response” containing the COUNTER report.

SUSHI is an enabling technology (not a product) Publisher Site 2 Knowledge base Usage Consolidation tool Library SUSHI Client SUSHI Server Usage Reporting System

SUSHI Clients The library needs “client” software. Options are: • Use a free client (or create their own) to harvest reports and store them on the local system. • SUSHI client that comes with commercial (or other) usage consolidation system – often part of an EResource Management system. • Part of an outsourcing service for collection of statistics.

SUSHI Servers The content provider creates the “server” software. : • Integrates with administration/usage reporting module. • Provided by content hosting service. • Feature of an outsourcing service for handling usage.

Getting help with SUSHI NISO’s SUSHI Site… http: //www. niso. org/workrooms/sushi

FAQs for librarians, content providers and about COUNTER Getting started guides for client and server development. Links to free client software, a developer kit for a. NET server, a tool to help consortia harvest usage, and more…

Schemas both as text and graphical representations. A discussion list for developers. Get answers to questions, collaborate with others to test your services.

Getting help with SUSHI The SUSHI Server Registry http: //sites. google. com/site/sushiserverregistry/

Little things make a big difference…

Common problems… “The Journal of XYZ” Acquire Agent Journal of XYZ Cost doesn’t get applied correctly Library Collection The Journal of XYZ Publisher Site 1 Journal of XYZ, The Acquisitions System Knowledge Usage may be base rejected as “not in collection” Publisher Site 2 Consortium Under counting Other Usage consolidation tool ERM because usage not combined Cost/Use ? Library XYZ Journal Aggregator Site 1

Guidelines for titles and ISSNs • Ensure titles are consistent between various systems. • Make sure the right ISSN is being used for the right title. • Include both the print and online ISSN where possible. • If the title has changed names, keep the history.

Things to watch out for with COUNTER reports • Use the proper form of the title and the correct ISSN • If using comma-separated output format, be careful of titles with embedded commas and quotes • Avoid duplicate rows, where possible. Hint: When things don’t match usage may not be counted.

Things to watch out for with SUSHI • XML that is not valid. • Identifier types, categories and metric types that are not valid or the wrong case. • A service that needs custom client development to work. Hint: Test your service with the MISO client to ensure it is valid.

In the works…

SUSHI • SUSHI Registry could become machine readable – Allow auto-configuration of SUSHI clients – Content providers can “advertise”, URL to SUSHI server, authentication methods used, reports supported, day-of-the-month usage is available, etc.

COUNTER • Search Clicks – a new optional report – Measure value of databases by tracking the activity from the result list… • View full text • Click for more detail • Link to link resolver • View images or tables • Etc.

COUNTER – related to SUSHI • Guidance will be added to the Co. P about SUSHI authentication • SUSHI compliance will become part of the audit

The “usage reporting” landscape Acquire Library Collection Agent Publisher Site 1 Acquisitions System Knowledge base Publisher Site 2 Consortium Usage consolidation tool ERM Other Cost/Use Library Aggregator Site 1

Thank You Oliver Pesch opesch@ebsco. com