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

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Tue Mar 24 20:26:20 CET 2020


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

Koha Team University Lyon 3 <koha at univ-lyon3.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Needs Signoff               |In Discussion
                 CC|                            |koha at univ-lyon3.fr

--- Comment #57 from Koha Team University Lyon 3 <koha at univ-lyon3.fr> ---
Hi,
I've tested following the test plan and I added a case when a items is in
transit (T status in reserves table) for an hold.
When you are in the first table in the deletion items tool, there's the column
called "holds" where you can see :
1/1 : if there's an item-level-hold on this item OR if the item is waiting to
serve a hold OR the item is in transit to serve a hold
0/1 : if there's a biblio-level-hold but that this item isn't waiting or in
transit for this hold
0 : if there's no hold

It's not a really clear notation, but I have nothing better to offer..

In this table, you can't tick nor the items with the waiting or transit status
nor the one where is a biblio-level-hold but only one item on this biblio.

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.

It works as described in the test plan but, for me, it isn't consistent to
block the deletion of an item because there's a biblio-level-hold on it but not
block the deletion of an item with a item-level-hold on it.

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

I must admit that I haven't read all the comments above but I can't see a good
reason to allow deletion of item with an item-level-hold if you don't allow the
deletion of a biblio-level-hold.

I hope that my explanations are clear..

Sonia BOUIS

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


More information about the Koha-bugs mailing list