[Koha-bugs] [Bug 22833] Block suspend and cancel on holds

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

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

Magnus Enger <magnus at libriotech.no> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #98649|0                           |1
        is obsolete|                            |

--- Comment #8 from Magnus Enger <magnus at libriotech.no> ---
Created attachment 98650
  -->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=98650&action=edit
Bug 22833 - Block suspend and cancel on holds

Swedish ILL uses a hold as part of the ILL workflow. It is problematic if
patrons
suspend or cancel those holds before the ILL request is received. This patch
makes it possible to configure, on the itemtype level, if it should be possible
to suspend or cancel holds.

Since a record can have items with different itemtypes, the record level
itemtype
is used to determine if holds connected to a record can be suspended and/or
cancelled.

If suspension is blocked for an itemtype, holds connected to records with that
itemtype can not be
- individually suspended by patrons in the OPAC (The "Suspend" button is not
  shown in the table of active holds in the "Holds" tab in "My summary".)
- suspended as part of a "suspend all" operation in the OPAC
- suspended as part of a "suspend all" operation in the staff client (but
  individual holds can still be suspended by staff)

If cancellation is blocked for an itemtype, holds connected to records with
that
itemtype can not be
- individually cancelled by patrons in the OPAC (The "Cancel" button is not
  shown in the table of active holds in the "Holds" tab in "My summary".)

To test:
- Apply the patch and make sure the atomic database update is run
- Make sure you have two different itemtypes and records with those itemtypes
at
  the record level (field 942$c in MARC 21).
- Toggle the two new settings on the itemtypes, and make sure the behaviour is
  in line with the behaviour described above.

Update 2020-02-10: Minor rebase

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