Download presentation
Presentation is loading. Please wait.
Published byColin Brooks Modified over 11 years ago
1
CORE Cost of Resource Exchange www.niso.org/workrooms/core January 2009 Update Karen A. Wetzel Standards Program Manager, NISO
2
What Ill talk about Review of goals Review of goals History History Participation Participation Status Report Status Report Next Steps Next Steps
3
What? An effort to build on the White Paper published by Medeiros et al regarding acquisitions-related data elements for exchange between ILS, ERM, and other systems An effort to build on the White Paper published by Medeiros et al regarding acquisitions-related data elements for exchange between ILS, ERM, and other systems
4
Why? ERM customers say that they want to be able to look up Acq information while working in their ERM ERM customers say that they want to be able to look up Acq information while working in their ERM Leverages data investment in individual modules, shares rather than duplicates Leverages data investment in individual modules, shares rather than duplicates Realization that single ILS hegemony is giving way to a multi-vendor environment Realization that single ILS hegemony is giving way to a multi-vendor environment
5
History Publication of the Medeiros White Paper (2007) and its revision (2008) Publication of the Medeiros White Paper (2007) and its revision (2008) Ed Riding ( SirsiDynix ), Jeff Aipperspach ( Serials Solutions ), and Ted Koppel ( then Ex Libris, now Auto-Graphics ) needed to serve mutual customer(s) Ed Riding ( SirsiDynix ), Jeff Aipperspach ( Serials Solutions ), and Ted Koppel ( then Ex Libris, now Auto-Graphics ) needed to serve mutual customer(s) Decided that rather than building one-off idiosyncratic sharing mechanisms, an acquisitions exchange standard made sense Decided that rather than building one-off idiosyncratic sharing mechanisms, an acquisitions exchange standard made sense
6
Early 2008 Ed, Jeff, and Ted surveyed various ERM and ILS vendors to determine feasibility Ed, Jeff, and Ted surveyed various ERM and ILS vendors to determine feasibility Picked CORE as acronym Picked CORE as acronym Discussed goals at ER&L 2008, at ALA Summer, and various other venues to determine interest, need, potential participants Discussed goals at ER&L 2008, at ALA Summer, and various other venues to determine interest, need, potential participants Approached NISO (Spring 2008) as standards development framework Approached NISO (Spring 2008) as standards development framework
7
Summer 2008 NISO Business Information Topic Committee approved CORE Working Group NISO Business Information Topic Committee approved CORE Working Group Solicitation of members began Solicitation of members began First meeting: August 6, 2008 First meeting: August 6, 2008
8
Members 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 Alliance) Rose Nelson (Colorado 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 Solutions) Jeff Aipperspach (Serials 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 goals Not just ERM ILS exchange but broader applications exist (vendors, consortia, etc.) Not just ERM ILS exchange but broader applications exist (vendors, consortia, etc.) Didnt want to duplicate work of existing standards (SOH, etc.) Didnt want to duplicate work of existing standards (SOH, etc.) Keep it simple and generic Keep it simple and generic Define the data – not the application !!! Define the data – not the application !!!
10
Working Groups activities August-September: wrote, designed, discussed Use Cases. August-September: wrote, designed, discussed Use Cases. October: analyzed use cases for common needs, vocabulary, and data elements October: analyzed use cases for common needs, vocabulary, and data elements October-November: Refined use cases to identified core CORE elements October-November: Refined use cases to identified core CORE elements November-December: XML message structure, transport mechanism November-December: XML message structure, transport mechanism December-January: Drafting document December-January: Drafting document
11
Decisions Two levels of query/response Two levels of query/response Cost information Only Cost information Only Cost information + Product Information Cost information + Product Information Three type of queries Three type of queries Send info on one particular transaction Send info on one particular transaction Send all transaction info on one or more products Send all transaction info on one or more products Send all transaction info on all products Send all transaction info on all products Can filter by dates Can filter by dates
12
XML Structure (see the draft) (see the draft) Simple and compact Simple and compact Is the payload for any web service messages Is the payload for any web service messages CORE schema outlines repeatable fields, Booleans, etc. CORE schema outlines repeatable fields, Booleans, etc.
13
Transport Mechanism Delivers the CORE payload Delivers the CORE payload Determined that SUSHI protocol web service mechanism is a good general purpose envelope Determined that SUSHI protocol web service mechanism is a good general purpose envelope SUSHI can be used by CORE virtually without changes SUSHI can be used by CORE virtually without changes Leverages vendor efforts in SUSHI Leverages vendor efforts in SUSHI
14
January 2009 NISO has completed first draft of the written Draft Standard for Trial Use (DSFTU) NISO has completed first draft of the written Draft Standard for Trial Use (DSFTU) Working Group is reading, clarifying, editing, illustrating, and adding examples Working Group is reading, clarifying, editing, illustrating, and adding examples Final DSFTU publication expected in February Final DSFTU publication expected in February Draft Standard period will be 12 months Draft Standard period will be 12 months
15
During the DSFTU period.. Vendors will write their applications to use CORE and SUSHI Vendors will write their applications to use CORE and SUSHI Vendor report problems to WG; WG considers solutions Vendor report problems to WG; WG considers solutions Possible additional drafts/updates Possible additional drafts/updates Early 2010: Final Standard Early 2010: Final Standard
16
We want to thank The Working Group for their participation, tenacity, and willingness to work hard on CORE The Working Group for their participation, tenacity, and willingness to work hard on CORE Mark Wilson for his work on XML Mark Wilson for his work on XML
17
Please contact Ted Koppel (tpk@auto-graphics.com) Ted Koppel (tpk@auto-graphics.com)tpk@auto-graphics.com Ed Riding (ed.riding@sirsidynix.com) Ed Riding (ed.riding@sirsidynix.com)ed.riding@sirsidynix.com COREinfo List: www.niso.org/lists/coreinfo COREinfo List: www.niso.org/lists/coreinfowww.niso.org/lists/coreinfo
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.