Comments on: Just In Time Acquisitions versus Just In Case Acquisitions http://dltj.org/article/just-in-time-versus-just-in-case-acquisitions/ We're Disrupted, We're Librarians, and We're Not Going to Take It Anymore Thu, 11 Mar 2010 18:47:21 -0500 http://wordpress.org/?v=2.9.2 hourly 1 By: “What is a library now?”: CSU Monterey Bay Opens New Library « E-Research Library http://dltj.org/article/just-in-time-versus-just-in-case-acquisitions/comment-page-1/#comment-35253 “What is a library now?”: CSU Monterey Bay Opens New Library « E-Research Library Mon, 20 Apr 2009 20:01:56 +0000 http://dltj.org/2006/08/just-in-time-versus-just-in-case-acquisitions/#comment-35253 [...] CSUMB library did prefer electronic over print delivery of information and focused on delivering “just in time” rather than “just in case” collections.  As John Ober wrote in an essay from 2000, “While [...] [...] CSUMB library did prefer electronic over print delivery of information and focused on delivering “just in time” rather than “just in case” collections.  As John Ober wrote in an essay from 2000, “While [...]

]]> By: Disruptive Library Technology Jester :: Automating Withdrawn Actions: Maximixing the Long Tail of Acquisitions http://dltj.org/article/just-in-time-versus-just-in-case-acquisitions/comment-page-1/#comment-18599 Disruptive Library Technology Jester :: Automating Withdrawn Actions: Maximixing the Long Tail of Acquisitions Thu, 05 Jul 2007 14:49:37 +0000 http://dltj.org/2006/08/just-in-time-versus-just-in-case-acquisitions/#comment-18599 [...] for the first half of this process: approval plans, book jobber firm order systems, etc. (See the Just In Time Acquisitions versus Just In Case Acquisitions article on DLTJ for another idea about the front end of the process.) Not may seem to exist, nor [...] [...] for the first half of this process: approval plans, book jobber firm order systems, etc. (See the Just In Time Acquisitions versus Just In Case Acquisitions article on DLTJ for another idea about the front end of the process.) Not may seem to exist, nor [...]

]]> By: the jester http://dltj.org/article/just-in-time-versus-just-in-case-acquisitions/comment-page-1/#comment-2545 the jester Wed, 02 Aug 2006 16:16:52 +0000 http://dltj.org/2006/08/just-in-time-versus-just-in-case-acquisitions/#comment-2545 [quote comment="2542"]If a library opts for publishers/distributors to do shelf processing, would it be possible to develop a workflow in which the book was shipped directly to the patron, processed and ready to be returned to the library?[/quote] Wow! Now that is adventurous. The control freak in me would want to be plugged in a little deeper into the publisher/distributor's workflow process in order to get the tracking number from the shipment to the patron. Our circulation system can then periodically ask (or get updates from) the shipper as to the status of that item, then "check it out" when the shipper shows it was delivered to the patron. This is where the Library Service Oriented Architecture becomes even more critical. There could be, of course, an added cost we (or maybe the patron) would need to bear for the direct delivery service. Presumably more than one item a day would be ordered from the publisher/distributor service and we might choose to have them send us in as few shipments as possible if the cost of the actual shipping becomes a factor. If the delivery points get spread out to include the patron's own delivery locations, that economy of scale would be lost. Great idea, Jon! [quote comment="2542"]If a library opts for publishers/distributors to do shelf processing, would it be possible to develop a workflow in which the book was shipped directly to the patron, processed and ready to be returned to the library?[/quote]

Wow! Now that is adventurous. The control freak in me would want to be plugged in a little deeper into the publisher/distributor’s workflow process in order to get the tracking number from the shipment to the patron. Our circulation system can then periodically ask (or get updates from) the shipper as to the status of that item, then “check it out” when the shipper shows it was delivered to the patron. This is where the Library Service Oriented Architecture becomes even more critical.

There could be, of course, an added cost we (or maybe the patron) would need to bear for the direct delivery service. Presumably more than one item a day would be ordered from the publisher/distributor service and we might choose to have them send us in as few shipments as possible if the cost of the actual shipping becomes a factor. If the delivery points get spread out to include the patron’s own delivery locations, that economy of scale would be lost.

Great idea, Jon!

]]> By: jonvw http://dltj.org/article/just-in-time-versus-just-in-case-acquisitions/comment-page-1/#comment-2542 jonvw Wed, 02 Aug 2006 15:34:23 +0000 http://dltj.org/2006/08/just-in-time-versus-just-in-case-acquisitions/#comment-2542 If a library opts for publishers/distributors to do shelf processing, would it be possible to develop a workflow in which the book was shipped directly to the patron, processed and ready to be returned to the library? What I have in mind is something like this: When the order is shipped to the customer, the vendor sends a MARC record to the library be loaded into the automation system. The automation system generates any relevant holdings data and checks the book out to the patron based on the anticipated receipt date of the item. Meanwhile, the patron receives the item, uses it, and returns it back to the library. When the item is discharged, it's routed to the technical services team for any additional processing that might be necessary. Our vendors and automation systems might not be ready for this just yet, but it seems like something that could be just around the corner, especially now that Amazon is in the game. If a library opts for publishers/distributors to do shelf processing, would it be possible to develop a workflow in which the book was shipped directly to the patron, processed and ready to be returned to the library?

What I have in mind is something like this:

When the order is shipped to the customer, the vendor sends a MARC record to the library be loaded into the automation system. The automation system generates any relevant holdings data and checks the book out to the patron based on the anticipated receipt date of the item.

Meanwhile, the patron receives the item, uses it, and returns it back to the library. When the item is discharged, it’s routed to the technical services team for any additional processing that might be necessary.

Our vendors and automation systems might not be ready for this just yet, but it seems like something that could be just around the corner, especially now that Amazon is in the game.

]]>