https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22456
--- Comment #35 from Tomás Cohen Arazi <[email protected]> --- (In reply to David Nind from comment #30) > Hi Tomás. > > I have tested this, and it all works fine except for these two things: > > 1. Test fails for prove t/db_dependent/Koha/Hold.t Fixed! > 2. I'm not sure of the workflow in the staff interface or the reason why > there is a "Reject cancellation" option > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > If I: > > 1. Request cancellation in the OPAC (Request cancellation button) it changes > to a non-clickable button (Cancellation requested). > > 2. Reject cancellation in the staff interface (Holds awaiting pickup > Holds > with cancellation requests tab, and select "Reject cancellation". > > The result is: > - In OPAC the button for the hold changes to "Cancellation rejected" > (non-clickable) > - In the staff interface it goes back into the "Holds waiting" tab > - I have to click "Cancel hold", then it is removed from the OPAC and holds > awaiting pickup > Holds waiting tab Yes, I agree this is a bit weird. I tried to submit this as early as possible to get some feedback. I'm not sure this moderation step is required. The original proposal was to just have a way to let the librarian know the user requested cancellation. I can remove the whole 'cancellation request status' thing. The main reasoning was that it was not clear to me how should cancellation requests count towards max reserves and friends (until they actually get acknowledged). We could just mark them as cancelled, actually. But just mark them as user-cancelled... I'm open to ideas. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
