1 / 17

CORE Cost of Resource Exchange niso/workrooms/core

CORE Cost of Resource Exchange www.niso.org/workrooms/core January 2009 Update Karen A. Wetzel Standards Program Manager, NISO What I’ll talk about Review of goals History Participation Status Report Next Steps What?

paul
Download Presentation

CORE Cost of Resource Exchange niso/workrooms/core

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CORE Cost of Resource Exchangewww.niso.org/workrooms/core January 2009 Update Karen A. Wetzel Standards Program Manager, NISO

  2. What I’ll talk about Review of goals History Participation Status Report 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

  4. Why? • 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 • 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) 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

  6. Early 2008 Ed, Jeff, and Ted surveyed various ERM and ILS vendors to determine feasibility Picked CORE as acronym 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

  7. Summer 2008 NISO Business Information Topic Committee approved CORE Working Group Solicitation of members began First meeting: August 6, 2008

  8. Members • Ted Koppel (Auto-Graphics) • Ed Riding (Sirsi-Dynix) • Kathy Klemperer, (EDItEUR) • Nettie Lagace (Ex Libris) • Brian Rosmaita (VTLS) • Rose Nelson (Colorado Alliance) • Joyce McDonough (Columbia) • Debbie Logan (EBSCO) • Bob McQuillan, (Innovative) • Kelvin Watson (TLC/CARL) • Dani Roach (Univ. of St Thomas) • Mary Walker (Wichita State) • Clara Ruttenberg (Georgetown) • Bill Hoffman (Swets) • Jeff Aipperspach (Serials Solutions) • RafalKasprowski (Rice) • Gracemary Smulewitz (Rutgers) • Candy Zemon (Polaris) • Karen Wetzel (NISO) • Mark Wilson (retired; XML advice)

  9. Determined goals Not just ERM <-> ILS exchange but broader applications exist (vendors, consortia, etc.) Didn’t want to duplicate work of existing standards (SOH, etc.) Keep it simple and generic Define the data – not the application !!!

  10. Working Group’s activities August-September: wrote, designed, discussed Use Cases. October: analyzed use cases for common needs, vocabulary, and data elements October-November: Refined use cases to identified core CORE elements November-December: XML message structure, transport mechanism December-January: Drafting document

  11. Decisions • Two levels of query/response • Cost information Only • Cost information + Product Information • Three type of queries • Send info on one particular transaction • Send all transaction info on one or more products • Send all transaction info on all products • Can filter by dates

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

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

  14. January 2009 NISO has completed first draft of the written Draft Standard for Trial Use (DSFTU) Working Group is reading, clarifying, editing, illustrating, and adding examples ‘Final’ DSFTU publication expected in February Draft Standard period will be 12 months

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

  16. We want to thank The Working Group for their participation, tenacity, and willingness to work hard on CORE Mark Wilson for his work on XML

  17. Please contact Ted Koppel (tpk@auto-graphics.com) Ed Riding (ed.riding@sirsidynix.com) COREinfo List: www.niso.org/lists/coreinfo

More Related