[Koha-bugs] [Bug 8132] Batch delete tool deletes items with holds on them

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

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8132

--- Comment #58 from Jonathan Druart <jonathan.druart at bugs.koha-community.org> ---
Thanks for testing Sonia!

What this change does basically is:
* Improve feedback to the end user: why this item cannot be deleted
* Block deletion of the last item for a biblio on which a hold is placed on, to
avoid phantom holds (original issue reported)

(In reply to Koha Team University Lyon 3 from comment #57)
> When you confirm the deletion, you have an alert for the case of the
> biblio-level-hold with 2 items that were selected for deletion : "Last item
> for bibliographic record wich biblio-level hold on it" and another message
> saying "At least one item blocked the deletion. The operation rolled back
> and nothing happened! "
> So the deletion is cancelled for all the items selected.

Yes, the problem is that we cannot (easily) know that we are going to remove
the last item on the biblio if we are going to remove several items from this
biblio. We only know it when we remove the last one. That is why everything is
rollbacked and no deletion was effective.

> Could we not prevent to tick all the 1/1 case in the first table in addition of > what exists already?

If we want to change the behavior on item's level holds, I think it should be
decided on a separate bug report, unless everybody agrees.

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