Lori Ayre's Blog

In case you've wondering what's up with FulfILLment, I thought I'd share this short Q&A piece.  It was prepared for a California consortium (thus the reference to a couple of products in use there) but the info is generally useful to everyone.  It includes some info I've grabbed from the FulfILLment and Equinox blogs (e.g. underlying architecture).  The other info comes from conversations with people who should know these things with a spattering of my own opinion.  Oh, and I see Equinox has updated the blog so be sure to go there and read about the Next Generation Discovery Interface component after you get the basics from below....

What is it?

Fulfillment is an open source, resource-sharing (aka ILL) product that will compete with Link+ (Innovative’s INN-Reach product), SuperSearch (SirsiDynix’s URSA product), as well as AutoGraphics Agent Resource-Sharing and RelaisD2D. Who’s developing it? It is being developed by Equinox Software, Inc. under contract with OHIONET.

SIP3 has just been released and it provides many new messages which means communication between ILS/LMS and your self-check, sorters, security system, PC management system....will be easier to implement and you'll have more options.  That is IF your ILS vendor supports it!  

So, make sure you start adding a requirement for SIP3 support to your procurement documents.

Here's what's new:

• allow creation / registration of patrons from self-service devices
• allow patrons to update their PINs / Passwords from a self-service device in the library
• allow patrons to update their home addresses and phone numbers
• support for handling electronic resources
• support for staff overrides on self-service circulation
• support for sortation systems
• support for PC Management systems
• added some other new messages simplify implementation and clarify usage
• added Undo Checkout and Undo Check-in messages to simplify implementation. It has been confusing for many developers to send a Check-in w/cancel flag to cancel a Checkout and send a Checkout w/cancel flag to cancel a Check-in. This was confounded by the fact that many ILS vendors did not support cancelling a transaction and would then proceed as a standard check-in (if cancelling a checkout) causing the patron to be removed from the hold list.
• added Off-line Checkout and Off-line Check-in messages to support off-line processing
• added Unsupported Message Response to indicate that the message request is not supported by the library system
• added Grouped data.  Data can now be grouped to provide all information required for a specific event. For example, a fee consists of the following fields: fee identifier, currency code, fee amount, and fee type. These fields can now be grouped together to simplify the passing of multiple fees on a single request or response message. Each set of group data starts with a group identifier and ends with a group end field.
  

I got a call the other day from one of my clients in the throes of an RFID implementation.  She was distressed because members of her consortium were not coming to agreement on which RFID vendor they would use so she wondered if it was possible to use one vendor's products in one location and another vendor's products at the other locations.

The answer is Yes You Can.  This is the beauty of standards.  

Below is a session description I contributed to the Library 2.011 Conference which will be held online November 2-4, 2011.  My session wasn't accepted, but plenty were, including one by Grace Dunbar of Equinox Software entitled Human Target: Staff is More Important than Software.

ILL is Dead: Network Effects and Resource-Sharing

The key is for libraries to start adding data repositories beyond their catalog into their discovery environment.  For example, why shouldn't Ted Talks be searchable within your catalog?  They are well-produced, authoritative videos on a broad array of topics. Every library should include them in their holdings.  But they don't.  OpenLibrary.org has 1.7 million books available online.  Are these in every library's discovery interface.  No. But this needs to change.  And it is.