http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10827
--- Comment #16 from bondiurbano <[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. Jonathan, a tip: now, when a reserve with priority "Waiting" is deleted or cancelled you can check-in the item AGAIN, Koha will ask for confirmation and next reserve in the holds queue is updated correctly!! Yes, it is possible to check-in items not issued but with reserves in holds queue... 1) Delete or cancel "Waiting" priority reserve 2) Check-in the item again 3) Confirm reserve for next patron 4) Priority for next patron reserve is updated correctly. -- 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/
