Bug 39674 - Self Check blocks decreaseLoanHighHolds items
Summary: Self Check blocks decreaseLoanHighHolds items
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Self checkout (show other bugs)
Version: Main
Hardware: All All
: P5 - low major
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-17 22:51 UTC by Christopher Brannon
Modified: 2026-01-23 17:30 UTC (History)
3 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2025-04-17 22:51:51 UTC
Currently decreaseLoanHighHolds blocks checkout in SCO, with no explanation or option.  This is frustrating to patrons and doubles work.

It would be preferable if the SCO had admin settings to 

A) Allow checkout and highlight the reduced loan period.  

B) Allowed the patron to see a modal with the reduced loan time and choose to check the item out or not.  

C) Allow to block the checkout with a defined message.
Comment 1 Christopher Brannon 2025-04-17 22:52:51 UTC
If this effects SIP as well, it would be good to allow the same options for SIP.
Comment 2 Christopher Brannon 2025-04-25 22:07:06 UTC
I'm waiting for another library to confirm, but I think Self Checks via SIP allow the item to go through on the shortened loan period without a block or warning.  I would like to at least mimic this behavior on the built in self check.
Comment 3 Christopher Brannon 2025-06-20 16:03:59 UTC
I have confirmed that 3rd party self checkouts do not block high demand items like Koha's self check does.

This behavior is inconsistent depending on if you are using SIP self check vs Koha self check.

I am going to change this from enhancement to a bug.

I think the desired behavior is to not hinder the patron, and let them check out, even if they are unaware that the checkout period is shorter.

However, information on the screen and receipts would give them that information.  The developers could always post a warning on the screen or require interaction in these cases, but I think Koha's self check should fall in line with current SIP behavior.
Comment 4 Owen Leonard 2025-06-20 17:57:35 UTC
I agree that this is a bug, and it sound correct to me that self-checkout should not block the checkout. I disagree that this is a blocker based on our bug reporting guidelines https://wiki.koha-community.org/wiki/Bug_Reporting_Guidelines#Severity
Comment 5 Christopher Brannon 2025-12-19 18:10:07 UTC
Thank you Owen.  I do hope we can get some traction on this.  This is a circulation issue, and being that about 50% or more of our traffic is through self checks, it does impact us quite a bit.  And the added fact that it gives the patron no indication as to what is wrong, it makes the patron more leery of using it.
Comment 6 Christopher Brannon 2026-01-22 16:08:21 UTC
I would like to see more discussion or movement on this.  As it is, we have a large number of items walking out of the library because patrons don't read the warning on the self check out screen that tells them that they can't check out a high demand item from that station.  There is absolutely no reason for this.

1) SIP does not block check outs of these items.  Why is SCO different?
2) There is no good reason to block or warn patrons or staff about this adjustment.  There are plenty of items in systems that check out for various periods of time.
3) We could implement a setting that would allow this block to be overlooked at SCO.
4) We could implement an option of whether or not staff need to be alerted to the checkout period change.
5) As is, this behavior is a HUGE PAIN IN THE BUTT.  All it does is cause libraries to lose track of items or frustrate patrons.
Comment 7 Lucas Gass (lukeg) 2026-01-22 19:50:43 UTC
Does this warrant a new system preference to control SCO behavior? decreaseLoanHighHoldsBlockSCO
Comment 8 Christopher Brannon 2026-01-23 17:30:37 UTC
(In reply to Lucas Gass (lukeg) from comment #7)
> Does this warrant a new system preference to control SCO behavior?
> decreaseLoanHighHoldsBlockSCO

I wouldn't think so if the goal is to match SIP behavior.  It does change from previous behavior, but it has been deemed a bug, and if we need new settings to deviate from that behavior, it should probably be added in a new bug.  I don't know that this is a behavior anyone wants.  If they speak up in this bug, then perhaps yes.  Otherwise, it should be treated as a bug only, IMO.