This presentation was provided by Karen Wetzel of NISO, during the NISO update of the ALA Midwinter Conference, held from June 23rd to June 26th, 2009.

1. CORECORE
Cost of Resource ExchangeCost of Resource Exchange
www.niso.org/workrooms/corewww.niso.org/workrooms/core
January 2009 UpdateJanuary 2009 Update
Karen A. WetzelKaren A. Wetzel
Standards Program Manager, NISOStandards Program Manager, NISO

2. What I’ll talk aboutWhat I’ll talk about
 Review of goalsReview of goals
 HistoryHistory
 ParticipationParticipation
 Status ReportStatus Report
 Next StepsNext Steps

3. What?What?
 An effort to build on the White PaperAn effort to build on the White Paper
published by Medeirospublished by Medeiros et alet al regardingregarding
acquisitions-related data elements foracquisitions-related data elements for
exchange between ILS, ERM, and otherexchange between ILS, ERM, and other
systemssystems

4. Why?Why?
 ERM customers say that they want to beERM customers say that they want to be
able to look up Acq information whileable to look up Acq information while
working in their ERMworking in their ERM
 Leverages data investment in individualLeverages data investment in individual
modules, shares rather than duplicatesmodules, shares rather than duplicates
 Realization that single ILS hegemony isRealization that single ILS hegemony is
giving way to a multi-vendor environmentgiving way to a multi-vendor environment

5. HistoryHistory
 Publication of the Medeiros White PaperPublication of the Medeiros White Paper
(2007) and its revision (2008)(2007) and its revision (2008)
 Ed Riding (Ed Riding (SirsiDynixSirsiDynix), Jeff Aipperspach (), Jeff Aipperspach (SerialsSerials
SolutionsSolutions), and Ted Koppel (), and Ted Koppel (then Ex Libris, nowthen Ex Libris, now
Auto-GraphicsAuto-Graphics) needed to serve mutual) needed to serve mutual
customer(s)customer(s)
 Decided that rather than building one-offDecided that rather than building one-off
idiosyncratic sharing mechanisms, anidiosyncratic sharing mechanisms, an
acquisitions exchange standard made senseacquisitions exchange standard made sense

6. Early 2008Early 2008
 Ed, Jeff, and Ted surveyed various ERM and ILSEd, 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 standardsApproached NISO (Spring 2008) as standards
development frameworkdevelopment framework

7. Summer 2008Summer 2008
 NISO Business Information TopicNISO Business Information Topic
Committee approved CORE WorkingCommittee approved CORE Working
GroupGroup
 Solicitation of members beganSolicitation of members began
 First meeting: August 6, 2008First meeting: August 6, 2008

8. 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 (ColoradoRose 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 (SerialsJeff 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)

9. Determined goalsDetermined goals
 Not just ERM <-> ILS exchange butNot just ERM <-> ILS exchange but
broader applications exist (vendors,broader applications exist (vendors,
consortia, etc.)consortia, etc.)
 Didn’t want to duplicate work of existingDidn’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 !!!

10. 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 commonOctober: analyzed use cases for common
needs, vocabulary, and data elementsneeds, vocabulary, and data elements
 October-November: Refined use cases toOctober-November: Refined use cases to
identified core CORE elementsidentified core CORE elements
 November-December: XML messageNovember-December: XML message
structure, transport mechanismstructure, transport mechanism
 December-January: Drafting documentDecember-January: Drafting document

11. 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 moreSend all transaction info on one or more
productsproducts
 Send all transaction info on all productsSend all transaction info on all products
 Can filter by datesCan filter by dates

12. XML StructureXML Structure
 (see the draft)(see the draft)
 Simple and compactSimple and compact
 Is the ‘payload’ for any web serviceIs the ‘payload’ for any web service
messagesmessages
 CORE schema outlines repeatable fields,CORE schema outlines repeatable fields,
Booleans, etc.Booleans, etc.

13. Transport MechanismTransport Mechanism
 Delivers the CORE payloadDelivers the CORE payload
 Determined that SUSHI protocol webDetermined that SUSHI protocol web
service mechanism is a good generalservice mechanism is a good general
purpose ‘envelope’purpose ‘envelope’
 SUSHI can be used by CORE virtuallySUSHI can be used by CORE virtually
without changeswithout changes
 Leverages vendor efforts in SUSHILeverages vendor efforts in SUSHI

14. January 2009January 2009
 NISO has completed first draft of the writtenNISO 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 inFinal’ DSFTU publication expected in
FebruaryFebruary
 Draft Standard period will be 12 monthsDraft Standard period will be 12 months

15. During the DSFTU period ..During the DSFTU period ..
 Vendors will write their applications to useVendors will write their applications to use
CORE and SUSHICORE and SUSHI
 Vendor report problems to WG; WGVendor report problems to WG; WG
considers solutionsconsiders solutions
 Possible additional drafts/updatesPossible additional drafts/updates
 Early 2010: Final StandardEarly 2010: Final Standard

16. 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 ontenacity, and willingness to work hard on
CORECORE
 Mark Wilson for his work on XMLMark Wilson for his work on XML

17. Please contactPlease contact
 Ted Koppel (Ted Koppel (tpk@auto-graphicstpk@auto-graphics.com.com))
 Ed Riding (Ed Riding (ed.ed.riding@sirsidynixriding@sirsidynix.com.com))
 COREinfo List:COREinfo List: www.www.nisoniso..org/lists/coreinfoorg/lists/coreinfo