Comment 31 for bug 1676608

I'm still testing the latest branch, but I have a couple of things to report back on.

For #3, I am still getting the Star Trek alert sound and errors in my Console, regardless of the status I try to apply.

For #2, I don't agree with the expected behavior for applying a next copy status. The idea is to force this copy into that status, not to continue circulating it to people who have holds placed on the item. In the case of transits, I think it is reasonable to adopt that status if the intent of the transit is to send the item home. However, it shouldn't be going into transit to fill a hold.

The primary use case of the next-alert functionality is a scenario where a patron returns an item to a library that does not own the item and reports that there is an issue with the item (the disc needs to be cleaned, pages are falling out, it has a funky smell.) When the owning library receives that item, they can then determine if the item needs to go into mending or should be discarded or should be handled in some other way. If the pages are falling out of a book, you really don't want to circulate that item again until it has been repaired. In some cases, the next copy status is a non-holdable status, but the item will still be sent to the holds shelf or go into transit to fill a hold after that next-copy status is applied. I wouldn't want this behavior to hinge on the holdability of a status (we would want to keep mending as holdable, for example, because it might not take long to clean a disc), but we clearly don't want copies put into a non-holdable status going out to fill more holds.

For #4, I'm having second thoughts on this one. I'm thinking the best practice for next-copy-status would be to display the alert only for the owning/circulation library. However, I could see use cases where you just decide not to apply that copy status, so a follow-up bug may be worthwhile nonetheless.