Just In Time Acquisitions versus Just In Case Acquisitions

Posted on 7 minute read

× This article was imported from this blog's previous content management system (WordPress), and may have errors in formatting and functionality. If you find these errors are a significant barrier to understanding the article, please let me know.

What of a service existed where the patrons selected an item they needed out of our library catalog and that item was delivered to the patron even when the library did not yet own the item? Would that be useful? With the growth of online bookstores, our users do have the expectation of finding something they need on the web, clicking a few buttons and having it delivered. When such expectations of what is possible exist, where is the first place a patron would go to find recently published items -- the online bookstore or their local library catalog? Does your gut tell you it is the online bookstore? Would it be desirable if the patron's instinct were to be the local library catalog?

A savvy patron looking for a recently published item will likely try the local library catalog to see if the item has been selected, purchased, received, cataloged, processed, and shelved (hereafter "SPRCPS") by the staff — in other words, gone through the traditional process libraries use for acquiring items. If not, the patron has one of three choices (that I can think of):

  1. make a request for the item to be SPRCPS'd with a hold placed on the item so that the patron is notified when it is ready;
  2. start an Interlibrary Loan process to try to get the item from another site that has SPRCPS'd the item faster than your library; or
  3. pay a cost premium — buy the book themselves and have it delivered.

Looking at this from the perspective of elapsed time, #1 is likely many weeks, #2 is likely a few weeks, and #3 is likely a few days. Looking at this from the perspective of direct cost to the patron, #1 is the cheapest, #2 may be free or some nominal ILL transaction cost (depending on local policy), and #3 is the most expensive. All-in-all, reasonable tradeoffs.

But what if our libraries offered a service that had the speed of #3 and the cost of #1? Do you think that would be an appropriate service to our users?

Local Catalog Display

In my mind, such a system would be predicated on four factors. First, our local catalog would need to display some record of items that are not yet held but could be acquired on an expedited basis. If the savvy patron is going to start at the library catalog to determine if we already have the item, thereby executing the cheapest (no direct cost to the patron) and likely fastest (hop down to your local branch and pick it up) path to getting the item in hand, there needs to be a way to show patrons that the item could be added to the library's collection on an expedited basis. Here in OhioLINK and with other similar consortial catalog systems, that expectation is already being set. "Can't find the item in your local catalog? Push this button and see if it is available from one of our consortial members. If so, push this other button and we'll transport it from that library to here for you."

In terms of the mechanics of getting these records into our systems, it seems that we need a new form of MARC record loads into our systems. The most likely source? How about what booksellers use now -- the ONIX format "that publishers can use to distribute electronic information about their books to wholesale, e-tail and retail booksellers, other publishers, and anyone else involved in the sale of books." A feed of ONIX records from publishers, filtered through a selection criteria, converted into MARC21, and loaded into our local catalogs would do the trick.

Automated "Request This Item" Function

Second factor -- a highly automated process to get the requested book to the library. Again, those familiar with OhioLINK and other similar consortial borrowing/lending systems know that there is a ubiquitous "Request This Item" button ("RTIB" hereafter) for objects that are not in the patron's own library but can be requested from a consortial partner. In this new Just-In-Time acquisition based on the ONIX record in our catalog, that RTIB would need the addition a second workflow: the buy-this-item-and-deliver-it-to-my-library workflow. Like a business-to-business transaction, the RTIB would trigger the purchase of the item to be expedited to the patron's library.

Speedy Copy Cataloging and Shelf Prep

Third factor -- the item must get through copy cataloging and shelf prep quickly. When a RTIB item reaches the library loading dock, there must be a workflow and a commitment by copy catalogers and shelf prep staff to turn the item around in four hours for patron pick up. If the RTIB immediately buys the item from the distributor, the distributor turns it around for same-business-day shipping, and the item arrives on our doorstep via an expedited courier (no "library rate postage" here, please), then the only place where we have an influence on the time it takes to get the item into the hands of the user is right here -- in our own technical services processes. And there are a number of short-cuts that can be made here as well,

  • Use "on the fly" circulation procedures to lend the book out immediately. When it is returned route the item through technical services for formal copy cataloging (or decide that the Onyx data is acceptable as is for the copy cataloging).
  • Use a distributor that will delivery the item shelf-ready. Just yesterday, through an LISnews posting, I learned that Amazon is now one such distributor:

    Amazon offers a wide array of library processing options. In addition to mylar jackets on hard-cover books, Amazon also offers MARC records, spine labels, and barcodes. By partnering with leading cataloging companies and organizations, Amazon is also able to offer you highly customized MARC records, spine labels, and barcodes that meet your specific needs.

New Roles for Staff

The fourth factor is the hardest -- the humans involved in the process. And I don't think it is the patrons that would have as big of an issue with this Just-In-Time acquisitions process. Here in Ohio a user expectation exists to tolerate receipt of an item in 24 to 48 hours via consortial borrowing services. I think it will be the library staff who would need first convincing then time to adjust to this new way of selecting and purchasing items. Some initial thoughts on new roles:

  • Selectors/bibliographers still have front-end work to do. They are the ones to tune the profile of "items that could be purchased" records (informed by the requesting patterns from users) that are loaded into the system and to buy items not yet requested that round out a collection. This is modestly akin to the approval plan systems we use now.
  • Copy cataloging staff may have a reduced workload for items that come in through the RTIB process — particularly if the distributor selected does much of the shelf prep and copy cataloging work already. This, too, is nothing new: we have been outsourcing more of our technical services work and assigning the copy cataloging and shelf prep staff to work on other areas of the collection.

Summary

Let's take one more look at the traditional SPRCPS process and see how things would change under a Just-In-Time acquisitions model.

Selected
An initial round of selection is done by the bibliographers and collection managers. They decide which broad categories of ONIX records from publishers/distributors will be represented as "items-to-be-acquired" in the local catalog. Patrons, then vote with their fingers and mice clicks as to which items meet their needs.
Purchased
An entirely automated business-to-business transaction. Once the user decides the item is what they need, our library computer talks directly to the publisher/distributor computer and buys the item.
Received
The publisher/distributor doesn't dally -- they ship the item to us for next-day or second day delivery. When it arrives in our mail room, we need to act fast.
Cataloged
Copy cataloging could be done by us, we could receive copy catalog records from the publisher/distributor, or we could decide that — at least for now — that the ONIX data is good enough and that like an "on-the-fly" transaction the formal copy cataloging will happen after the item is returned.
Processed
Choices here, too. Will our staff do the shelf-prep work or is that something we contract with the publisher/distributor? In any case quick processing here, too because...
Shelved
...we want to get the item in the hands of the user who requested it. "Shelved" in this case could be the hold-pickup shelf, or it could be a local physical delivery service that sends the item to the patron.

Can we do this as fast as it would take the patron to get the item directly from the online bookseller? Maybe not -- we do have some necessary processing steps that a direct patron purchase process does not have. Can we make that delay short enough so that the patron considers it acceptable as compared to the direct price premium of ordering it themselves?

Do we want to?

The text was modified to update a link from http://www.bisg.org/onix/index.html to http://www.bisg.org/activities-programs/activity.php?n=d&id=15&cid=2.

The text was modified to update a link from http://lisnews.org/article.pl?sid=06/08/01/023238 to http://lisnews.org/node/19233 on January 13th, 2011.