sandy hurd director of strategic markets march 30 2007 l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Sandy Hurd Director of Strategic Markets March 30, 2007 PowerPoint Presentation
Download Presentation
Sandy Hurd Director of Strategic Markets March 30, 2007

Loading in 2 Seconds...

play fullscreen
1 / 35

Sandy Hurd Director of Strategic Markets March 30, 2007 - PowerPoint PPT Presentation


  • 298 Views
  • Uploaded on

Got Chopsticks? Get SUSHI! 16 th North Carolina Serials Conference, 2007. Sandy Hurd Director of Strategic Markets March 30, 2007. If I can’t eat it, what is it?. Standardized Usage Statistics Harvesting Initiative Protocol Z39.93. First some history…. Nothing happens in a vacuum….

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Sandy Hurd Director of Strategic Markets March 30, 2007' - Audrey


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
sandy hurd director of strategic markets march 30 2007

Got Chopsticks?

Get SUSHI!

16th North Carolina Serials Conference, 2007

Sandy Hurd

Director of Strategic Markets

March 30, 2007

slide7

Transactions:

Order

Order confirm

Invoice

Dispatch data

Claims

Claims Response

Library / ILS

Subscription Agent

Publisher

SISAC, ICEDIS, EDItEUR, SICI, DOI, NISO

The Old EDI Presentation

slide8

Transactions:

Order

Order confirm

Invoice

Dispatch data

Claims

Claims Response

Plus:

License data

Serials Online Holdings

Serials Release Notice

Usage statistics

Cost per use

Acquisitions data

Library / ILS / ERM /

Coverage Database

Publisher /

Information Provider

Subscription Agent /

E-journal Provider

DLF, XML, ONIX, COUNTER, SUSHI, NISO

The World Spins Beyond EDI….

icedis discussions
ICEDIS Discussions

Journal supply chain efficiency improvement

E-journal order format

E-journal activation message

ONIX SOH and SRN

International Standard Party Identifier (ISPI) – entities involved in the creation and production of content

More….

sushi
SUSHI

A formal, recognized NISO protocol designed for moving COUNTER reports from a content provider to a library

A web-services model for requesting and delivering data

  • “Report Request”
  • “Report Response”

A request for data where the response includes COUNTER data

SUSHI doesn’t count, it moves what has been counted

COUNTER compliant + SUSHI compliant

key definitions courtesy of niso
Key Definitions, Courtesy of NISO

COUNTER = Counting Online Usage of Networked Electronic Resources = An international initiative to facilitate the recording and exchange of online usage statistics

SOAP = Simple Object Access Protocol = A protocol that specifies a self-contained messaging system used to exchange data and access services across a network (commonly the Internet)

Web service = A server-based software system that provides information or functionality in response to XML-based messages sent through the Internet

slide18

Note:

  • JR1 = Journal Report 1: Number of Successful Full-Text Article
  • Requests by Month and Journal
  • JR2 = Journal Report 2: Turnaways by Month and Journal
  • DB1 = Database Report 1: Total Searches and Sessions by Month
  • and Database
  • DB2 = Database Report 2: Turnaways by Month and Database
  • DB3 = Database Report 3: Total Searches and Sessions by Month
  • and Service
  • JR3 = Number of Successful Item Requests and Turnaways by Month,
  • Journal and Page Type
  • JR4 = Total Searches Run by Month and Service
why sushi
Why SUSHI?

A formal, recognized NISO protocol designed for moving COUNTER reports from a content provider to a library

Eliminates the time consuming and expensive process of manual statistics downloads

Makes possible repositories of usage data

Demonstrates feasibility of using XML Web Services for cross vendor machine interoperability

why sushi20
Why SUSHI?

Because we need good data to make good decisions

slide24

Industry-wide support

  • More rapid development
  • Deployment underway
barriers to easy e resource management
Barriers to Easy E-resource Management

For libraries

  • Complex contracts and purchasing models
  • Overlapping consortia
  • Internal bureaucracy
  • Select a tool
  • Statistics
    • Time-consuming to do manually
    • Need a single place to store and manipulate statistics
    • What do the numbers mean
    • Retrieval has been the bottleneck

For information providers

  • Consortia requirements and desires
  • Compliance with standards as core to business
  • Statistics
    • COUNTER >>> SUSHI
what do librarians want
What do Librarians Want?

Ease of retrieval, preferably automated

Easy to understand

Flexible date ranges in management reports

Cost per use

Central repository

Simple interfaces

good for information providers
Good for Information Providers

Usage data critical in collection decisions for libraries and providers too

Usage data demonstrates value

Credible COUNTER results

Make it easy and everyone is happy

implementation challenges
Implementation Challenges
  • Library / ILS / ERM / Coverage Database
    • Get a tool
    • Continue development and roll-out
    • Interoperability
  • Publisher / Information Provider
    • Begin and/or continue development and roll-out
    • Make service delivery a priority
  • Subscription Agent / E-journal Provider
    • Begin and/or continue development and roll-out
    • Make service delivery a priority
what s in the works
What’s in the Works?

SUSHI 1.0 (formalizes the NISO 0.1 draft)

SERU (http://www.niso.org/committees/SERU/ ) Shared E-Resource Understanding

DLF ERMI Phase 2 Steering Group work on interoperability between ILS acquisitions and ERM

More work to come

  • NISO SUSHI
  • ONIX SOH and SRN
  • ICEDIS XML messages between publishers and agents
why does sushi make a difference
Why does SUSHI Make a Difference?

Automated retrieval

Saves time

Frees staff for more complex work

Lets machines do what machines do well

Supports collection analysis and management

remember
Remember…

Standards are voluntary

Development takes commitment, time, and testing

Development takes less time today, but it’s still development

Broad adoption still takes time

There is value in what vendor partners bring to libraries