Useful Nuggets

August 31, 2010   SirsiDynix and the FUD Factor

Two online tidbits led me to check in with the folks at SirsiDynix about what they are telling their customers about the viability of moving to an open source ILS.  Officially, SirsiDynix states that “we believe that competition is good. It challenges all vendors who are invested in the success of libraries to continuously improve our products and services, and fuels innovation that make libraries better for users around the world. Open source solutions, either independently or commercially developed and maintained, can be the right solution for a library for a number of reasons.”

But privately, they are telling people that some unspecified number of SirsiDynix customers “who have left SirsiDynix solutions for an open source solution [ ] have since returned to SirsiDynix.”

So the burning question is this…what is that unspecified number?  According to Arcadia Library, their SirsiDynix Field Sales Consultant stated this number was 30% as in “30% of the libraries that left SirsiDynix for open source software ended up with SirsiDynix again.” (Source: http://koha4arcadialibrary.blogspot.com/)

In other parts of the world (Washington), Kitsap Sun reporter Chris Henry interviewed SirsiDynix Global Marketing and Communications Manager, Julianne Hancock, who stated that “most of their customers who migrated to open-source software have since returned because they found managing the systems a drain on scarce resources.” (Source: http://www.kitsapsun.com/news/2010/aug/30/kitsap-regional-library-catalog-system-ailing/)

I decided to pursue the matter further.  A PDF of my communications with Julianne is here.

Besides, the one library that Julianne mentions in our email exchange (McMaster University)….do you know of a SirsiDynix customer that tried Koha or Evergreen and then decided to go back to SirsiDynix????  If most, or even just 30% switched back, there should be a whole bunch of you out there!  I mean they have 4,000 clients!  (Source: http://www.sirsidynix.com/company).

August 18, 2010   FulfILLment spins off Evergreen as Independent OS Project

A new state-of-the-art resource sharing software has been in the works at Equinox (with sponsorship from ohioNET) for some time now.  And while it isn’t ready for download, it did cross a new threshold recently.  As of August 2, 2010, FulfILLment was established as its own open source project (as opposed to a piece of Evergreen).

This is especially FANTASTIC news for everyone who isn’t on Evergreen where the resource-sharing software options are….well, they stink frankly.  Current offerings have three problems:

  1. work well on one ILS but not another
  2. too expensive
  3. too labor-intensive for staff.

Most often, it’s a three strikes situation.

Mike Rylander explained the design concepts underlying FulfILLment in an Equinox blog post:

FulfILLment brings the benefits of a circulation and hold system based on the core algorithms in Evergreen to the ILL problem space. By encouraging and facilitating the participating institutions to collect and enter all relevant information about ILL policy and system definition, FulfILLment can provide not only truly automated mediation of ILL request (holds) but also full ILL transaction (circulation) management and automated transit management.

If the infrastructure and algorithms of Evergreen are the heart of FulfILLment, the FulfILLment Next Generation Discovery Interface (NGID) is its public face. The FulfILLment NGDI is a hybrid physical/virtual union catalog which automatically loads and deduplicates bibliographic records from all participating institutions for central search. Records can be pulled in using standard protocols such as OAI-PMH, Z39.50 or SRU, or can be automatically pushed into the NGDI from the local systems by whatever means are available.

FulfILLment leverages the hold targeting and capture algorithms from Evergreen — arguably the most advanced in the world in terms of policy and process modeling — and uses them to find the best item to fulfill the request of the patron based on all available information.

FulfILLment’s hands and eyes consist of the Local Automation Integrator, or LAI. This system uses the best and most appropriate protocol for each participating institution’s ILS, be it NCIP, SIP2 or a custom connector, to query each local ILS that advertises items on the requested record in real-time in order to provide status information to the hold processing mechanism. Data concerning the requesting patron is also pulled in real-time, and can be automatically obfuscated or expunged if required as soon as all open ILL requests and transactions for that patron are completed.

Once an ILL request has been accepted by the lending library and the item captured for remote circulation, FulfILLment tracks the complete life-cycle of this transaction. Both ends of the ILL, the lending and borrowing libraries, know the current status of items on loan and can generate reports based on this information using the Evergreen Reporter, one of the most advanced and flexible reporting engines available for an ILS.

[Source:  http://blog.esilibrary.com/2008/03/13/the-path-to-fulfillment/]

If you are a developer or someone comfortable pulling code off trunk…you can find the code here:  http://fulfillment-ill.org/websvn/listing.php?repname=FulfILLment.

Official FulFILLment website here: http://fulfillment-ill.org/

This is all very good news for LibraryLand!

May 30, 2010   UHF and HF RFID Tags

I’ve been focused recently on developments in UHF technology and how it might help libraries improve on the RFID products we currently use (which are  based on HF tags).  My interest, of course, is having something that fits our library applications best and if UHF is a better fit, I’d rather know now than later after we have an even greater investment in the HF technology.

So, several of us have been discussing this very thing and I feel we finally got a pretty definitive response from Alan Butters who has been one of the people talking quite a bit about UHF  and it’s promise (he certainly peaked my interest).  The response, co-authored with Paul Chartier (they are co-authors of ISO 28560-2) is provided here (with their permission):

As co-Project Editors of ISO 28560-2, we thought it useful to provide some input to the list.

Let’s start with the installed base of RFID systems.  At a conference a few months ago, one of the major vendors of chips (they produce HF and UHF) estimated that there were 2500 libraries that had implemented RFID systems using high frequency technology.  The count for UHF was less than 1% of this number.  Our guess is that the 2500 might be a slightly low estimate.

When the work started on ISO 28560, we had to consider the installed base and the infrastructure and associated investment that had already been made.  Simply disenfranchising all the libraries that had adopted national models or proprietary solutions would have been unthinkable – the aim was to increase interoperability between existing systems.

As those on this list probably know. ISO 28560 is a three-part standard as follows:

* Part 1 defines the data element – almost certainly more than necessary for a single library, but trying to cover all aspects of circulation, collection management and the acquisition of library material.

* Part 2 defines a flexible encoding system based on ISO/IEC 15962, which is increasingly being used in a number of applications and is independent of frequency and air interface protocol.

* Part 3 is a fixed structure data model, effectively standardising the Danish national model.

These three standards together will allow libraries to move away from proprietary data models or systems providing an increased degree of interoperability. Furthermore, it may be possible to intermix old and new tag formats in the same library system.

Both Part 2 and Part 3 specify the use of ISO/IEC 18000-3 Mode 1 tags (also known as ISO/IEC 15693 when used as a smart card).  This is a mature technology that is tried and tested, but is probably no longer the best RFID technology (other than its extensive installed base) with a wide choice of vendors for chips, tags and reading devices. However, it does still have some strong features that are not necessarily supported by other tags and one particular feature is the capability of selective memory locking.

Now, let’s consider the position of UHF which has failed to make extensive market penetration in any library sector as was expected by some at the time that we started work on ISO 28560. UHF technology could not have been used universally a few years ago, because it was only recently approved by radio regulators in different regions of the world. There are still significant differences in performance capabilities based on regional and national radio regulations.

Although there are other UHF technologies, I am assuming that the discussions are about ISO/IEC 18000-6C tags (also known as EPCglobal Class 1 Gen 2). If we consider some of the features not mentioned in Lori’s e-mail, we might identify some of the challenges that libraries will face in selecting this technology:

* Some tags only support a 96-bit identifier with no additional user memory, so there is no step forward from this tag being an electronic bar code.

* Even those tags that have additional memory currently do not support selective locking.

* Not all the tags support a unique serial number of the chip itself.

There is a gradual move away from some of these constraints, but libraries and specialist vendors need to be aware that these constraints will be around in some products for years to come.  So selecting the tag without an understanding of its capabilities could cause problems for libraries.

Because Paul is heavily involved in ISO standardisation of the technology, the committee developing ISO 28560 has cognisance of the fact that there is the possibility of a new 18000-3 Mode 3 high frequency tag which has some of the features of the 18000-6C tag.  This has just been approved for publication and the library community needs to wait for products and a proper evaluation. So, even if we acknowledge that HF might not be the ideal platform for library RFID systems, UHF might not turn out to be the ideal replacement anyway – there may be other options to consider.

Now to some comments based on the heading of the CityU report.

* Performance will be better for UHF based on the fact that this is a new technology.  But 18000-3 Mode 3 will have bit transfer rates across the air interface that are up to four times (even eight times, if an optional feature is supported by the tag) than that of the present 18000-3 Mode 1 tags.

* An extensive read range is not always a plus feature.  When UHF was introduced in the logistics field, cross talking between interrogators at different dock doors in warehouses caused significant operational problems until fixed.  The same also applied for airline baggage handling, where the read range enabled tags on other luggage on other conveyors to be read.  Certainly, in different parts of the world, there are privacy concerns about the read range where the RFID tag might be used for tracking an individual.  These concerns are such that legislation has already been passed – expect more in Europe.

The discussion on security gates is interesting, because the more extensive read range of UHF may have a positive impact, but in reality the extended read range may create a significant no-go zone for library users which could impact heavily on space utilisation. It is also necessary to consider UHF in the context of the three security systems discussed in ISO 28560, which are:

* The main solution is to toggle between two different values of the tag’s AFI. This is possible with an 18000-3 Mode 1 tag while still permitting selective locking of the primary item identifier – a situation desired by many libraries. This strategy is not possible with an 18000-6 Type C tag, nor an 18000-3 Mode 3 tag.  This is because the AFI is an integral part of what is known as Memory Bank 01 and this has to be locked or unlocked in its entirety.

* Some of the vendors have developed proprietary EAS solutions for the 18000-3 Mode 1 tag.  This second solution is not available in 18000-6C and it is not clear yet what will happen with 18000-3 Mode 3 tags.

* The final security measure is to use a unique chip ID, which is an essential component of an 18000-3 Mode 1 tag that is at the core of the “hand-shaking” process with the communications protocol.  This unique chip ID is optional in 18000-6C and 3 Mode 3, and is not used for communication purposes.

It was interesting to read that “CityU plans to adopt the data model of the US (ISO 15962) with slight modifications but is likely to follow ISO 28560, once adopted, which supports backwards compatibility and flexibility.”  As co-Project Editor for ISO 28560-2 and Project Editor for ISO/IEC 15962, Paul is happy to assert that this solution is NOT A STANDARD, it is just another proprietary solution that will create problems of interoperability.

So, let’s take stock of what might happen in the future with ISO 28560, while we are still awaiting the final Yes/No ballot for the three standards. These standards will be implemented to different degrees by libraries with existing RFID systems, and certainly by libraries yet to embark on RFID. When the standards were being developed, the experts on the ISO committee were obviously aware of both 18000-6C (a reality) and the impending 18000-3 Mode 3 standards. One likely outcome is for the next generation of library RFID standards to be based on 18000-3 Mode 3 tags, which will require either a new part to ISO 28560 or enhancements to existing parts. The tags will be different but, because of the significant installed base, there might be a degree of interoperability in readers that can be achieved with an engineering upgrade.

Because of the laws of physics, adopting UHF will certainly require different equipment, but it might still be possible for a future part of ISO 28560 to support UHF technology. However, before this can be done, the library community needs to be clear not just on aspects of the technology, but also on potential business and competitive issues that might exist with UHF technology. To support a business case, not only does the solution need to be based on suitable technology but the supplier community must build systems that take advantage of the strengths of the technology platform in such a way as to provide a compelling case for its purchase. Particularly is this so in the context of a market heavily dominated by HF solutions which themselves continue to evolve.

As soon as libraries embark on adopting standards, the standards makers have to take into account infrastructure issues and the installed base. A balance needs to be struck between the benefits of interoperability with existing technology versus switching to new technology. This is why most railway track gauges around the world have not changed for a hundred years, because the cost of infrastructure changing is too high compared to the benefits. The GS1 bar code (previously known as EAN and UPC) that we see on most retail products including books, is based on a technology developed in 1973.  37 years later, the same technology is being used even though there are significantly “better” bar code symbologies available.  So while GS1 has added a number of new bar code symbologies, the old symbol might still make its 50th birthday!

Also, even if one is of the view that UHF is the “right” technology for libraries, the corollary that HF is the “wrong” technology does not necessarily follow. This is an important point. To miss this point is to suggest that project success and ROI in libraries cannot be achieved with HF platforms. There are simply too many successful library RFID projects around the world for this to be the case. This is not to say that library RFID systems couldn’t be better – of course they could and my own investigations suggest that implementing a UHF based platform could contribute some useful improvements. But are all library RFID systems based on HF really so bad that we should just push back and refuse to embrace the technology until something new comes along? Libraries will make their own call but I think not.

So, whatever we do in the future with the new generation HF or the existing UHF technology, recognition of the millions of Dollars (or Euros) of investment already made by libraries in RFID technology must be made. The door continues to stay open, but the work of the ISO committee must proceed with full acknowledgement of the extensive investments made by libraries over the past 12 or so years.

Kind regards,

Alan Butters and Paul Chartier

My take-away is this:  don’t be hesitant about moving to RFID because of potential developments with UHF.  Yes, the technology has some benefits over HF (that it didn’t have even a few years ago) but it still has some drawbacks that are potentially bigger drawbacks than the devil we already know (HF tags).

But.  Let’s keep demanding something better.  There is very definitely room for improvement.  I hope Alan and Paul are right that we will continue to see more improvements  in existing HF-based systems without sacrificing interoperability while maintaining some measure of backwards compatibility.  From their lips to….


May 13, 2010   Open Source Opportunities for Consortia

I’m heading off to Colorado today to talk with a library consortium about some of the exciting opportunities for expanding their services by taking advantage of open source technologies.   What I’ll be talking about is the openings created when a library migrates to an open source library system product like Koha or Evergreen.

Here’s my starter list of the things library consortia can be (okay, I mean should be) doing:

    1. Saving or re-investing license costs:  moving to a shared open source catalog reduces the overall costs of a shared system- a lot – savings can be passed on to members or re-invested (p.s. I vote for re-investing….see below)
    2. Providing services that used to be provided by the Vendor:  ”sales,” project management, training, support, migration, hosting, customization.
    3. Serving as liaison between consortia  members and OSLS (open source library system, e.g. Koha or Evergreen) community providing services such as: developing software development priorities for consortia, submitting feature requests to OSLS development community, writing software specifications, contracting with programmer(s), developing new features, fixing bugs
    4. Developing institutional expertise in open source technologies to expand their development, integration and support roles.

    That last one is key.  Once the consortia starts developing in-house skills in open source technologies like PHP, MySQL, Perl, and the various Linuxes….they can expand into all sorts of other areas.  Why not move all of your consortia’s public computers over to Ubuntu with Open Office and save even more money for your members (imagine no Microsoft licensing fees for all those desktops….).  Maybe you need a metasearch tool…there’s plenty of open sources ones you can experiment with.

    Some consortia are already grabbing the bull by the horns and taking advantage of this growth opportunity.  Bibliomation and NEKLS come immediately to mind.  They were doing fine as consortia before they plunged into open source, but now they are ROCKING!

    I hope to encourage other consortia to follow their lead.

    April 10, 2010   Library as Pantry

    I had the thought recently that libraries are like pantries. Sure, they are full of things we get at Costco (just like everyone else) but once they are in our pantry, they feel different somehow. Once they are in my pantry, they are mine. Even though that can of tuna sitting on my shelf was one of hundreds of identical tuna cans at the grocery store, it feels special to me now that it is on my pantry shelf (I’ve also got a Little Prince vibe going here but I’m going to try to stick to this pantry metaphor if I can).

    Library books work the same way. Whether the library gets them from a Baker & Taylor or from a library across town or a library across the state, once that book is on my library’s shelf, it feels different from all the other books just like it. When that book I’ve requested arrives, it is mine. Even though it is just one of hundreds of identical copies of that book, it feels special to me now that it is on my library shelf.

    Just like that can of tuna on my pantry shelf, that library book is mine until I consume it.

    Somehow making this connection to library as pantry helped explain something to me that I knew intuitively was important, but I couldn’t quite put words to. It comes up around the issues of holds, ILL and physical delivery of library material. Is it really worth all our efforts? We know we can never compete with Amazon in terms of how fast the item can get delivered to the customer. And we cannot offer the breadth of items Amazon can. But, even if we can’t compete in those areas, it is important to keep working on getting the right items on our pantry shelves because it really means something to have them there.

    Behind the scenes, we may still be getting our food and books from the big box stores but once we place them in our pantries for our people, they are transformed. Those books become our shared bounty. They are there to delight and nourish us.

    We can count on that magic to give us the edge over Amazon. All of our efforts to move library material from place to place is worthwhile because when your person comes in and finds just what they wanted right there on their special library shelf, they feel taken care of. They feel special.

    And I guarantee you, no one ever feels that way when they buy a book online.

    April 8, 2010   NISO Physical Delivery Webinar May 12th

    If you care about physical delivery of library material (and I do), you may want to catch this webinar being produced by NISO.

    It’s in the Mail: Improving the Physical Delivery of Library Resources
    May 12, 2010
    1:00 – 2:30 p.m. (Eastern Time)

    I’m going to open the session with a broad discussion of delivery issues in libraries. So, in my twenty minutes, I’m thinking I’ll talk about the increased demand on libraries to provide access to anything anywhere and to do so quickly. The open source trend is providing new opportunities to respond to this demand with better discovery tools and more sharing of systems. Shared systems make the “find and request” side of resource-sharing a slam dunk but this in turn puts a heavier burden on physical delivery. RFID has a role to play too. As the US gets closer to having a data model standard, there are opportunities to use RFID tags to speed up the movement of material and to track and sort it better.

    If you have opinions about something I should address, let me know!

    March 17, 2010   Work begins on open source ILL product: FulfILLment

    Equinox has been talking about it for quite some time but there appears to be actual movement on a true open source ILL module for linking not just open source library systems but all ILS products (pending some standards compliance issues I imagein).

    The name of the product is FulfILLment and the website says “it will provide library users seamless access to materials owned by libraries using FullfILLment—no matter which integrated library system his or her library uses.”

    Go to http://fulfillment-ill.org/ for more info and to sign up for the mailing list. This is great news for anyone interested in true resource-sharing across all systems.

    March 3, 2010   Check out RSCEL!

    I have been very busy writing and posting blog entries but alas, the content is all living elsewhere. Much of what I write is for clients and these reports sometimes find their way to this site. But not always. For now, take a peek at a new website I’m working on with King County Library System and the other rascals involved in moving libraries to open source library systems.

    The website is http://rscel.org and it is for the Resource and Sharing Cooperative of Evergreen Libraries. Its just getting going and the effort is largely funded by a three year grant from the IMLS. You just may want to get yourself involved….

    January 18, 2010   How to Install Koha on Debian

    Thomas Krichel of Palmer School of Library and Information Science has developed, and is sharing, course material for an intensive course he developed in which students, without any previous system admininstration experience, installed debian, and then installed Koha.

    http://openlib.org/home/krichel/courses/lis508p10w/

    All 17 of his students were successful…wanna give it a go?

    January 13, 2010   VolunteerMatters – Now Available Through TechSoup

    Closerware has teamed with TechSoup Stock to make its web-based VolunteerMatters operations management and outreach software available to nonprofit organizations and public libraries. Organizations that make use of volunteers can use VolunteerMatters to schedule shifts, maintain contact information, publish an online directory, send email and postal mail communications, and generate various kinds of reports.

    You can get the product for only $79 if your library meets these conditions:

    Check it out!

    Neekdesign