[Koha-bugs] [Bug 24683] New: Holds on biblios with different item types: rules for holds allowed are not applied correctly if any item type is available

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

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

            Bug ID: 24683
           Summary: Holds on biblios with different item types: rules for
                    holds allowed are not applied correctly if any item
                    type is available
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: Hold requests
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: hans.palsson at hkr.se
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com

Created attachment 99257
  -->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=99257&action=edit
An example of a biblio with mixed itemtype items.

When having different rules for placing holds for each item type, having both
item types on one biblio "breaks" these rules.

As shown in the attachment: Smart rules for item type "Course literature"
allows patrons to place holds on items. The smart rules for the item type
"Dayloan" does not allow patrons to place holds on the items. 

When having both item types on one biblio, it should in theory be possible to
place a hold on biblio level even if the dayloan item type is available.
Setting the option "AllowHoldItemTypeSelection" to allow does not solve the
problem. Various other options have been tried, but as long as there is an
available item that is not "not for loan", then placing holds is not possible.

This is troublesome for us, since holds must be placed manually by staff. The
Dayloan item type is for having a copy available for many students and should
not be placed on hold.

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