https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891 --- Comment #4 from Sally <sally.healey@cheshiresharedservices.gov.uk> --- Hi Katrin, I was one of the people who requested this - hopefully this bit of background might be useful. We have over 40 sites where books can be transferred to/from. We only use biblio level holds, we use the Transport Cost Matrix to choose the 'optimal' library to fill the hold, and the Holds Queue to generate the list of items for the staff to look for. As we have so many libraries, a lot of stock, and all of our holds are biblio level, there can be crossovers, i.e. The holds queue is generated by Koha at 1pm. BBB library's holds queue shows a request for item 005 on record QQQ for a patron at AAA library. A patron at AAA library coincidentally returns item - 002 - from QQQ record. 002 item on QQQ record is trapped for the hold at AAA library. Staff at BBB library start working through the holds queue using the information generated at 1pm. They locate item 005 on QQQ record and scan it in. Koha informs them that the item is no longer required. I realise that when you write it out like this, it's easy to think, "Wow, that scenario must be fairly rare!" ...but it happens constantly (on a daily basis) because we use biblio level holds and because we have so many items / libraries. It is a real source of frustration for the staff - if they've been sent to find 60 items and 10 of them are no longer required because they were filled half an hour earlier, it's a bit galling. It also affects us because holds queue is one of those jobs which is scheduled - but if the library is quiet, many staff will load it up and see if they can fill any, because we put a lot of emphasis on filling and transferring holds as quickly as possible. This is a common scenario: Holds queue - built at 5pm. Staff do holds queue - it has 50 items on, and they find 25. Staff change shifts. It's quiet at 5.45pm so a staff member loads holds queue. There are still 50 items as it hasn't refreshed. Staff start to look for items, not realising that half of them have already been filled. We mitigate that by asking the staff to share print outs, and informing them when it refreshes. Despite this, it's a source of confusion for the staff, because they don't understand why the request isn't instantly removed from the holds queue once it's been filled / been made missing / is no longer required. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.