http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10827
--- Comment #17 from Kyle M Hall <[email protected]> --- (In reply to bondiurbano from comment #14) > (In reply to Jonathan Druart from comment #13) > > (In reply to bondiurbano from comment #12) > > A biblio-level hold is a reserve on the next available item. > > An item-level hold is a reserve on a specific item. > > Ok Jonathan, thanks for the information. The important matter is that > priority "Waiting" always refers to an item because an item has just been > checked-in. Look at the document I uploaded: step 2 says "next available" > but step 4 ("Waiting" priority) says barcode 200. So when a reserve in > priority "Waiting" for barcode 200 is deleted or cancelled next reserve in > the holds queue should be updated to priority "Waiting" for barcode 200 for > the next patron. There's no confusion about it. At this point difference > between biblio or item level should be irrelevant. The program must > procedure at item level. If I am interpreting your assertion correctly, you are incorrect. You are only looking at a single possible scenario. What if the next hold is for pickup at a different library, what if the next hold is cannot be filled by this item because of issuing rules? We cannot simply assume the next hold can be filled automatically by a canceled waiting hold item. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
