6
edits
Changes
m
no edit summary
* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu
How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound mattersdifficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.
NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems.
This presentation discusses some of the nutty things how we did to help to us learn learned enough about NCIP and OpenSRF from scratch to take on a project to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium which uses that relies on over 20 different ILSes.
==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==