1 / 54

Achieving Interoperability

Achieving Interoperability. LITA National Forum Salt Lake City, Utah Oct. 2, 2009. On behalf of the NCIP-IG. Susan Campbell, Library Reports Coordinator; CCLA Ted Koppel, Product Manager for Integrated Library Systems; Auto-Graphics

maeve
Download Presentation

Achieving Interoperability

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. Achieving Interoperability LITA National Forum Salt Lake City, Utah Oct. 2, 2009

  2. On behalf of the NCIP-IG • Susan Campbell, Library Reports Coordinator; CCLA • Ted Koppel, Product Manager for Integrated Library Systems; Auto-Graphics • Lynne Branche Brown, Product Manager, Resource Sharing; Innovative Interfaces • Gail Wanner, Resource Sharing Specialist; SirsiDynix & NCIP-IG Chair

  3. NCIP – a librarian’s perspective ~~ Susan Campbell College Center for Library Automation

  4. Library A Library B

  5. Library C Library B

  6. Library A Library B

  7. ?

  8. committee (1999)- http://www.flickr.com/photos/niassembly/3384173073/ docs stack (2002) - http://www.flickr.com/photos/sonrisaelectrica/3695743740/ presentation (2005)- http://www.flickr.com/photos/peterjlambert/97671748/ finish (2007 review) - http://www.flickr.com/photos/wallyg/280932690/ university - http://www.flickr.com/photos/uniinnsbruck/3719819021/ coleman - http://www.flickr.com/photos/crownjewel82/2893939220/ strozier - http://www.flickr.com/photos/underatree/1554946230/ doorshrub - http://www.flickr.com/photos/ceoln/69242273/ carnegie1 - http://www.flickr.com/photos/dublincitypubliclibraries/373898623/ carnegie2 - http://www.flickr.com/photos/75905404@N00/3591431643/ 9 to 1 - http://www.flickr.com/photos/dcdead/2839396999/ testbed - http://www.flickr.com/photos/13010608@N02/3079790297 confused - http://www.flickr.com/photos/photojonny/2268845904/ tools - http://www.flickr.com/photos/wonderlane/2315545267 tangled - http://www.flickr.com/photos/randomurl/440190706/ running http://commons.wikimedia.org/wiki/File:08913-Perspective_Run.jpg hat: http://www.scripting.com/stories/2009/09/16/whatsWrongWithThisPicture.html

  9. NCIP: The Vendor’s ViewTed KoppelAuto-Graphics, Inc.

  10. Brief History • SIP and SIP2 preceded NCIP • 3M defacto standard • Useful but designed for Self Service (only) • NCIP Goals: expand on SIP2, structure data, ‘remote circ’ capability • Tried to do a large number of functions

  11. Realities All of us ILS vendors – even Open Source – are in business to make a profit None of us controls the entire library market, and we never will. Economic and political conditions have accelerated moves towards grouping (consortia) and sharing resources.

  12. Realities (2) Libraries take their mission of delivering information to their users very seriously Many (most) libraries don’t have the resources to build their own systems for library management and interoperability. ILS vendors are expected to fill that role.

  13. Result MARC (Z39.2) SRW/SRU/CQL OpenURL I2 ISO 10160 Z39.71 (Holdings) SUSHI ONIX for Serials CORE NCIP Z39.50 / Bath / USNP etc. ILS vendors must work together on common standards and protocols in order to serve customer needs.

  14. NCIP = Swiss army knife 40 some messages and responses Each message has multiple query elements and even more in the response Powerful, capable, but complex, even after simplification in version 2.

  15. NCIP – if done right • Streamlines staff workflows • Allows libraries to provide many enhanced services to users • Financial transaction exchange • Integration with proxies • Authentication management • Services we haven’t even thought of yet • Should be invisible to users.

  16. It’s a challenge Vendors update their product lines 2-3 times/year or more Development timelines are scheduled months in advance Vendor A’s priorities may not be Vendor B’s priorities

  17. Another set of realities Each NCIP vendor builds to the NCIP standard a little differently Testing, re-testing is required Takes time and resources ILS vendors usually manage priorities based on their customers’ needs more than from other vendors’ testing requirements

  18. We want to serve you well and we need your help to do so Tell us who you need to interoperate with and what you’re trying to do. Work with us in field testing Encourage your vendor to comply with, implement, and deliver to the standard.

  19. Conclusion • Vendors have made progress in designing NCIP ver. 2 • Core messages • Moving towards testbed • Better, simpler messages • NCIP ver.2 development just beginning, should see new apps in 2010

  20. NCIP: Version 2 Lynne Branche Brown Innovative Interfaces Inc.

  21. Why a V2? Minimal implementation of V1: seeking a protocol that more vendors will adopt Multiple issues with original standard for self-service Desire to streamline Backwards compatibility issues – naming new version clarifies compatibility

  22. What’s new in V2? • Lots of minor changes and corrections • Added MessagingError as an element • Made optional: InitiationHeader and ResponseHeader • Added element NameInformation to Routing Information • Consolidated UniqueUserId / VisibleUserID and UniqueItemID / VisibleItemId …among others

  23. What’s new in V2? • And some BIG changes • DTD Schema • Eliminated AuthenticateUser/Authenticate User Response • Added ANY element to all elements & messages • Added DeleteItem and DeleteUser messages • Added LookUpRequest & LookUpRequest Response (formalized)

  24. More importantly… The NCIP Implementers Group defined a core message set that supports the most fundamental functions and commonly used messages. Vendors are encouraged to implement – either as initiator or responder (or both!) all 9 messages in the core message set.

  25. Core NCIP Messages Lookup User Lookup Item Request Item Cancel Request Item Accept Item Check Out Item Check In Item Recall Item Renew Item

  26. Goals of the core message set Define a core set of tasks supported by NCIP messaging Narrow the scope of needed development Facilitate adoption of NCIP messaging between ILS systems and resource sharing systems

  27. NCIP: Success Stories Gail Wanner SirsiDynix

  28. Measuring Success Implementers who initiate NCIP messages 3M Auto-Graphics CybraryN Innovative OCLC Overdrive Polaris Relais SirsiDynix eXtensible Catalog Possibly others

  29. Measuring Success Implementers who respond to NCIP messages Ex Libris Polaris SirsiDynix TLC eXtensible Catalog Coming soon Innovative CARL

  30. Comparison of Application Areas

  31. Working Together? Not all initiators use the same messages or data elements Not all responders support the same messages or data elements Core Message Set will help set the bar for real interoperability Today there are many examples of libraries using NCIP successfully NOT!

  32. Countdown to Launch • Behind the scenes • Planning • Designing • Coding • Testing • Internally • With other systems • Begin actual implementation • Install • Test actual interoperability • Go live

  33. Launched* • Resource Sharing • Reciprocal Borrowing • Self Service • Bindery • Other * Incomplete list; see NCIP website for additional information or ask your vendor for current implementations and their status

  34. On the launch pad

More Related