[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

Marcel de Rooy <m.de.rooy at rijksmuseum.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|BLOCKED                     |Failed QA

--- Comment #80 from Marcel de Rooy <m.de.rooy at rijksmuseum.nl> ---
(In reply to Marcel de Rooy from comment #79)
> "If an item is the last one of a biblio that have biblio-level hold
> placed on it, we should block the deletion."
> 
> Well, this is quite arguable. Imo probably cleanup_database could remove
> holds that make no sense like biblio level holds when there are no items.
> The same commit says:
> "Note that there is something a bit weird as we are blocking items
> from a biblio that has biblio-level holds on it (not found), but we
> do not blocking the deletion of an item with a waiting item-level hold."
> 
> Lets not push inconsistency but resolve it?

Additional thought:

Note that the user also has the choice to delete a biblio. If he wants to
delete the biblio, the biblio level hold will be deleted too. So you could say
that a choice to not delete the biblio, is a choice to keep the hold. Perhaps
new items are to be expected here and the hold can be filled later. So delete
the item.

If you choose delete biblio too, we should not block the deletion of the hold.

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