[Koha-bugs] [Bug 8451] Confusing and problematic double prompt for processing transfers

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8451

Christopher Brannon <cbrannon at cdalibrary.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cbrannon at cdalibrary.org

--- Comment #2 from Christopher Brannon <cbrannon at cdalibrary.org> ---
David,
Perhaps this will help and add to the case.  I've noted a couple scenarios
related to this issue.  I think it is a bug, and needs to be addressed.  I am
copying this from reports I made to our support team, so sorry if some of the
info is redundant.

Scenario 1:
Item is placed on hold to be picked up at location A.
Item is checked in and confirmed, and now shows it is on it's way to location
A.
Before it is sent out to location A, we discover that the patron wants the hold
picked up at location B.
Hold is changed from In Transit to a priority level 1.
Pickup location is changed to location B.
Item is checked in to trigger hold and transfer.  Now TWO messages appear.  One
for the original transfer, and one for the new transfer.

Observation:
Changing the hold status from In Transit to a new status, like a priority
level, doesn't completely clean up the In Transit status.  If the item went out
the door and ended up at location A after the change, they only see one
message, which is to send it on to location B.  However, if the item doesn't go
out the door to location A, and is checked in after the change, we see a
transfer message for both location A and B.  I can go ahead and fulfill the
transfer for location B, just ignoring the first message.  I can also cancel
the transfer on the first message, and then check in the item again, and only
get the one message to transfer to location B.

Ideally, if the In Transit status is changed, Koha should clean it up
completely (essentially doing the cancel of the first transfer I could do if I
see the two messages).

Scenario 2:
Item is placed on hold to be picked up at location A.
Item is checked in and confirmed, and now shows it is on it's way to location
A.
Before it is sent out to location A, we discover that the patron wants to
cancel the hold, or has already cancelled it.  We cancel it if the patron is
telling us to.
This is not enough.  Even with the hold cancelled, the item still thinks it
needs to go to location A.
Item is checked in.  Now TWO messages appear.  One
for the transfer, and one shows a local use window.

Observation:
If we do nothing, the transfer is still stuck to the item, no matter how many
times we check it in.  You either have to make sure you check it in, and cancel
the transfer, or check it in, send it to location A and then then send it back
after they check it in.

It seems to me that the transfer should have been cancelled with the hold. 
Koha seems to be treating holds and transfers independently.  This creates a
lot of confusion and potential problems.


Hope this helps.

Christopher Brannon

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.