Comment 12 for bug 1306666

Given this some more thought and considering Michele's comment about doing a circulation, I have a slightly different idea.

My thought is to alter my branch a bit more so that a copy's status is only changed to reshelving when the copy has an in transit status and the transit is aborted at the organization that "owns" the copy, i.e. the copy's circ lib.

My thinking behind this is that we cannot count on much of anything if the transit is aborted somewhere other than at its home. Usually, transits are aborted by someone who has the copy in hand, but that is not always the case. Typically, if the copy is in some "limbo" state after having the transit aborted, a check in will clear it up. Some more testing may be required to verify this.

I'm not inclined to have the abort transit code try a check in because that could possibly lead to more problems depending on the other variables.

Also, it may be tricky to have check in clear hanging transits. Part of the check in process is to look for transits and hold transits to see if the book should be routed elsewhere. When checking in a book at a library other than the source or the destination of a transit, it could be difficult for the software to figure out what to do. It could happen that a copy was delivered to the wrong library, maybe it fell into the wrong bin or something, and needs to be routed somewhere else.

So, I'll update the branch a bit later with the change mentioned above. Does that better meet the need identified in the initial report?