Hi! The issue we wanted input on was not separating hold queues per se (separate queues = specific hold fulfillment), but rather how the queue(s) are displayed to staff and patrons. If I read your e-mail correctly, you have books in closed stacks and would like to separate these from the books you have in open collections. For one biblio, a book from the closed stacks should not fulfill a hold placed on a book from the open collection. Is this correct? If this is the case, then it is possible to achieve already today. We do it currently, with different itemtypes for items in closed stacks and open collection and the syspref AllowHoldItemTypeSelection set to allow. (For those wainting to look at the original development, look at bu 15533: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15533) I hope this is helpful in any way! Best regards, Andreas Den 2017-06-13 18:42 skrev BOUIS Sonia <sonia.bouis@univ-lyon3.fr>:

Hello, I'm rising from the dead this email because we have a similar problem. We would like to use Koha for asking books in stacks not freely available for public and we have thought that we could use holds for this. For one biblio, we have items directly borrowable and items that are in specific stacks non directly reachable. For items directly borrowable, patrons can put a hold only if the item is on loan but it's not the same for the item in stacks that could be asked for even if they are available. We could manage that with different item types. If someone asks for an item in stacks but if there's already an hold on the other item, when we will return the stack's item, it will be the patron who asked for the item on loan that will be served (as he's on priority 1) So, if we could manage different hold queues, regarding the item type, it would be better.

Do you have the same problem in your libraries ? Andreas, did manage to solve your problem ?

Cheers

Sonia

Message: 1 Date: Wed, 22 Mar 2017 21:11:28 +0000 From: Andreas Hedström Mace <Andreas.Hedstrom.Mace@sub.su.se> To: "koha@lists.katipo.co.nz" <koha@lists.katipo.co.nz> Subject: [Koha] Separate hold queues? Message-ID: <AC7E35B5-1CAA-4303-A5D2-4AC6F23AA779@sub.su.se> Content-Type: text/plain; charset="utf-8"

Hi all!

We are at Stockholm University Library experiencing some difficulties with how Koha is currently handling hold queues, and are considering development in this area. Are there any other libraries who are experiencing similar issues (see below), and would be interested in the development of separate hold queues? Or have an opinion on whether this would be a good/bad idea?

In Koha today it is possible to limit the fulfilment of holds per branch (same pick-up location as home/holding library) and item type. For us, it makes most sense to view this as several hold queues for one bibliographic record. For example: a person queuing for a book from the textbook collection (item type = ”TC”) isn’t actually queuing for books for the general collection (item type = ”GC”). But Koha handles this as one big queue. This isn’t a problem for the holds per se, as Koha only fetches the book that has the right criteria to fill the hold (i.e. the correct item type or home/holding library) but it has proven to be an issue for our patrons.

As Koha displays it as one big queue, it might seem that the queue is much bigger that it actually is. This has confused a number of patrons, and have discouraged others from placing holds. Continuing our example: a book has three patrons on hold for item type GC, when a new patron adds a hold for TC. This makes this person number four in the queue in Koha today, making the patrons believe that they will have to wait weeks or months for the book (in our library TC is 7 days, GC 28 days) when in reality it is only one week.

For us, this would better be described as two queues: One with 3 patrons on hold (General collection) One with 1 patron of hold (Textbook collection)

The same is true for hold fulfilment that require pick-up location to be the same as home/holding library (i.e. hold fulfilment per branch). Say a public library also have a school library in it’s organization, that is a special case where books from the other libraries should not be sent to the fulfil holds, or vice versa. As in our example above it would be better to display queues separately so 5 holds at the main library won’t discourage a student from placing a hold on that same book at the school library.

So my question is basically, is there are other libraries out there who are using any of these hold fulfilment features (or would like to), and would want to see a new feature to separate/split hold queues? Or who could see the benefit of such a feature.

Please note that separate hold queues would of course only come in effect if any system preference that limits hold fulfilment is set to allow. Also, this would not effect holds to pull.

I look forwards to hearing people’s opinion about this!

Best regards, Andreas

________________________________ Andreas Hedström Mace Librarian Stockholm University Library Stockholm University 106 91 Stockholm Tel: +46 (0) 8 16 49 17 su.se/english/library<http://su.se/english/library> ________________________________

*******************************