Check-in-then-out does not trigger holds

Bug #1656925 reported by on 2017-01-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

EG 2.10

A recent case shows that when checking out an item that is still in another patron's account, the checkin process does not check/trigger pending hold on the item.

Tina Ji
BC Libraries Co-op

Thomas Berezansky (tsbere) wrote :

I think this is intentional, with the "Check In" portion doing a "don't do any hold/transit related stuff" checkin, unless you are saying that the "Check Out Fills Related Hold" setting is enabled but not working for checking an item out that was still checked out to a different patron? (tji) wrote :

Thanks, Thomas. It makes sense when thinking of checking out an available copy with pending, but not triggered, holds (no prompt). But this scenario is slightly different. A prompt may be preferred in some situation. The item may not be found on the shelf. Two patrons may request to swap the item from one account to another. If staff use check_in_then_out, she/he may skip someone's hold without knowing it. Tina

Thomas Berezansky (tsbere) wrote :

So, if I understand correctly, you want a new feature that would prompt before non-renewal checkout if an active hold with no pull list target (aka, no on-shelf copies) could be filled by the copy in the case of checkout attempt from a non-standard status (more generic than "checked out")?

Not 100% sure I get your goal, or that I stated it well. (tji) wrote :

I think I would like to see a prompt (with options to capture or not to capture the hold) when the Normal (Forgive)check_in_then_check_out button is hit, in case there is an active hold that can be filled by the copy. In another word, the checkin process follows mostly the regular checkin procedure, except throwing a prompt instead of capturing the hold(sending item in transit) directly. Staff are prompted and given an opportunity to choose how to proceed.

Regarding whether the active hold has no pull list target, I think the behaviour should be in line with the regular checkin.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers