CORE CORE Cost of Resource Exchange Cost of Resource Exchange

www.niso.org/workrooms/corewww.niso.org/workrooms/core

January 2009 UpdateJanuary 2009 UpdateKaren A. WetzelKaren A. Wetzel

Standards Program Manager, NISOStandards Program Manager, NISO

What I’ll talk aboutWhat I’ll talk about

Review of goalsReview of goals HistoryHistory ParticipationParticipation Status ReportStatus Report Next StepsNext Steps

What?What?

An effort to build on the White Paper An effort to build on the White Paper published by Medeiros published by Medeiros et al et al regarding regarding acquisitions-related data elements for acquisitions-related data elements for exchange between ILS, ERM, and other exchange between ILS, ERM, and other systemssystems

Why?Why?

ERM customers say that they want to be ERM customers say that they want to be able to look up Acq information while able to look up Acq information while working in their ERMworking in their ERM

Leverages data investment in individual Leverages data investment in individual modules, shares rather than duplicatesmodules, shares rather than duplicates

Realization that single ILS hegemony is Realization that single ILS hegemony is giving way to a multi-vendor environmentgiving way to a multi-vendor environment

HistoryHistory

Publication of the Medeiros White Paper Publication of the Medeiros White Paper (2007) and its revision (2008)(2007) and its revision (2008)

Ed Riding (Ed Riding (SirsiDynixSirsiDynix), Jeff Aipperspach (), Jeff Aipperspach (Serials Serials

SolutionsSolutions), and Ted Koppel (), and Ted Koppel (then Ex Libris, now Auto-then Ex Libris, now Auto-

GraphicsGraphics) needed to serve mutual customer(s)) needed to serve mutual customer(s) Decided that rather than building one-off Decided that rather than building one-off

idiosyncratic sharing mechanisms, an idiosyncratic sharing mechanisms, an acquisitions exchange standard made senseacquisitions exchange standard made sense

Early 2008Early 2008

Ed, Jeff, and Ted surveyed various ERM and ILS Ed, Jeff, and Ted surveyed various ERM and ILS vendors to determine feasibilityvendors to determine feasibility

Picked CORE as acronymPicked CORE as acronym

Discussed goals at ER&L 2008, at ALA Summer, Discussed goals at ER&L 2008, at ALA Summer, and various other venues to determine interest, and various other venues to determine interest, need, potential participantsneed, potential participants

Approached NISO (Spring 2008) as standards Approached NISO (Spring 2008) as standards development frameworkdevelopment framework

Summer 2008Summer 2008

NISO Business Information Topic NISO Business Information Topic Committee approved CORE Working Committee approved CORE Working GroupGroup

Solicitation of members beganSolicitation of members began

First meeting: August 6, 2008First meeting: August 6, 2008

MembersMembers

Ted Koppel (Auto-Graphics)Ted Koppel (Auto-Graphics) Ed Riding (Sirsi-Dynix)Ed Riding (Sirsi-Dynix) Kathy Klemperer, (EDItEUR)Kathy Klemperer, (EDItEUR) Nettie Lagace (Ex Libris)Nettie Lagace (Ex Libris) Brian Rosmaita (VTLS)Brian Rosmaita (VTLS) Rose Nelson (Colorado Rose Nelson (Colorado

Alliance)Alliance) Joyce McDonough (Columbia)Joyce McDonough (Columbia) Debbie Logan (EBSCO)Debbie Logan (EBSCO) Bob McQuillan, (Innovative)Bob McQuillan, (Innovative) Kelvin Watson (TLC/CARL)Kelvin Watson (TLC/CARL)

Dani Roach (Univ. of St Thomas)Dani Roach (Univ. of St Thomas) Mary Walker (Wichita State)Mary Walker (Wichita State) Clara Ruttenberg (Georgetown)Clara Ruttenberg (Georgetown) Bill Hoffman (Swets)Bill Hoffman (Swets) Jeff Aipperspach (Serials Jeff Aipperspach (Serials

Solutions)Solutions) Rafal Kasprowski (Rice)Rafal Kasprowski (Rice) Gracemary Smulewitz (Rutgers)Gracemary Smulewitz (Rutgers) Candy Zemon (Polaris)Candy Zemon (Polaris) Karen Wetzel (NISO)Karen Wetzel (NISO) Mark Wilson (retired; XML advice)Mark Wilson (retired; XML advice)

Determined goalsDetermined goals

Not just ERM <-> ILS exchange but Not just ERM <-> ILS exchange but broader applications exist (vendors, broader applications exist (vendors, consortia, etc.)consortia, etc.)

Didn’t want to duplicate work of existing Didn’t want to duplicate work of existing standards (SOH, etc.)standards (SOH, etc.)

Keep it simple and genericKeep it simple and generic

Define the data – not the application !!!Define the data – not the application !!!

Working Group’s activitiesWorking Group’s activities

August-September: wrote, designed, August-September: wrote, designed, discussed Use Cases.discussed Use Cases.

October: analyzed use cases for common October: analyzed use cases for common needs, vocabulary, and data elementsneeds, vocabulary, and data elements

October-November: Refined use cases to October-November: Refined use cases to identified core CORE elementsidentified core CORE elements

November-December: XML message November-December: XML message structure, transport mechanismstructure, transport mechanism

December-January: Drafting documentDecember-January: Drafting document

DecisionsDecisions

Two levels of query/responseTwo levels of query/response Cost information OnlyCost information Only Cost information + Product InformationCost information + Product Information

Three type of queriesThree type of queries Send info on one particular transactionSend info on one particular transaction Send all transaction info on one or more productsSend all transaction info on one or more products Send all transaction info on all productsSend all transaction info on all products Can filter by datesCan filter by dates

XML StructureXML Structure

(see the draft)(see the draft) Simple and compactSimple and compact Is the ‘payload’ for any web service Is the ‘payload’ for any web service

messagesmessages CORE schema outlines repeatable fields, CORE schema outlines repeatable fields,

Booleans, etc.Booleans, etc.

Transport MechanismTransport Mechanism

Delivers the CORE payloadDelivers the CORE payload Determined that SUSHI protocol web Determined that SUSHI protocol web

service mechanism is a good general service mechanism is a good general purpose ‘envelope’purpose ‘envelope’

SUSHI can be used by CORE virtually SUSHI can be used by CORE virtually without changeswithout changes

Leverages vendor efforts in SUSHILeverages vendor efforts in SUSHI

January 2009January 2009

NISO has completed first draft of the written NISO has completed first draft of the written Draft Standard for Trial Use (DSFTU)Draft Standard for Trial Use (DSFTU)

Working Group is reading, clarifying, editing, Working Group is reading, clarifying, editing, illustrating, and adding examplesillustrating, and adding examples

‘‘Final’ DSFTU publication expected in Final’ DSFTU publication expected in FebruaryFebruary

Draft Standard period will be 12 monthsDraft Standard period will be 12 months

During the DSFTU period ..During the DSFTU period ..

Vendors will write their applications to use Vendors will write their applications to use CORE and SUSHICORE and SUSHI

Vendor report problems to WG; WG considers Vendor report problems to WG; WG considers solutionssolutions

Possible additional drafts/updatesPossible additional drafts/updates

Early 2010: Final StandardEarly 2010: Final Standard

We want to thankWe want to thank

The Working Group for their participation, The Working Group for their participation, tenacity, and willingness to work hard on tenacity, and willingness to work hard on CORECORE

Mark Wilson for his work on XMLMark Wilson for his work on XML

Please contactPlease contact

Ted Koppel (Ted Koppel (tpk@auto-graphics.com))

Ed Riding (Ed Riding (ed.riding@sirsidynix.com))

COREinfo List: COREinfo List: www.niso.org/lists/coreinfo