#2 - I think this should be punted into a separate bug to resolve during the beta period.
#3 - I've replaced the klaxon with a success sounds, under the assumption that with new-style copy alerts, "unexpected" copy statuses when a successful checkin has occurred can now be expected.
#4 - that settles it then... a new bug to finish discuss this :)
#5 - hmm, since April of 2016, many of the old-style copy status events are explicitly bypassed when new_copy_alerts is in effect, as is always the case in the webstaff client. See around line 3849 of Open-ILS/src/perlmods/lib/OpenILS/Application/Circ/Circulate.pm. I suggest that we ship with the status-based copy alerts active (for both new installation and during upgrades).
So...
#2 - I think this should be punted into a separate bug to resolve during the beta period.
#3 - I've replaced the klaxon with a success sounds, under the assumption that with new-style copy alerts, "unexpected" copy statuses when a successful checkin has occurred can now be expected.
#4 - that settles it then... a new bug to finish discuss this :)
#5 - hmm, since April of 2016, many of the old-style copy status events are explicitly bypassed when new_copy_alerts is in effect, as is always the case in the webstaff client. See around line 3849 of Open-ILS/ src/perlmods/ lib/OpenILS/ Application/ Circ/Circulate. pm. I suggest that we ship with the status-based copy alerts active (for both new installation and during upgrades).