Bug 35703 - Setting borrower Lost Card to yes (borrowers.lost = 1) does not block holds via API
Summary: Setting borrower Lost Card to yes (borrowers.lost = 1) does not block holds v...
Status: RESOLVED DUPLICATE of bug 39657
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low minor
Assignee: Tomás Cohen Arazi (tcohen)
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-04 16:27 UTC by Kristi
Modified: 2025-06-11 18:46 UTC (History)
6 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments
PatronAccountFlags (6.64 KB, image/png)
2024-01-04 16:27 UTC, Kristi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kristi 2024-01-04 16:27:04 UTC
Created attachment 160547 [details]
PatronAccountFlags

On a patron's account page, under Library use > Patron account flags, the description above the account flags reads "Setting a value here will prevent patron from circulating materials and placing holds on the OPAC" 

We have found that setting the Lost card flag does not prevent a patron from placing holds. 

Ideally, the functionality of the flag should be updated so that holds are prevented by this flag, or the description of the flag should be updated to remove mention of holds. 

Having the ability to prevent patrons with a particular designation (restricted, lost, etc.) from placing holds as well as checking out or renewing would be helpful.
Comment 1 Kristi 2024-03-14 13:55:53 UTC
After speaking with Nick at ByWater, part of the issue with the lost/stolen setting is that it needs to work better with the API. The hold check needs to be the same on the OPAC and API.
Comment 2 Andrew Fuerste-Henry 2025-04-28 19:51:15 UTC
When borrowers.lost=1, holds can be placed via the intranet without issue but any attempt to place a hold via the OPAC results in the message 
"Sorry, you cannot place holds.

Your library card has been marked as lost or stolen.
If this is an error, please take your library card to the circulation desk at your local library and the error will be corrected.

We should have the option to similarly block these holds from being placed via API.

Might some libraries have some API accounts for which such a hold should be blocked, but other API accounts for which such a hold should be allowed?
Comment 3 Andrew Fuerste-Henry 2025-06-11 18:46:22 UTC
Handling this as part of a larger change on another bug.

*** This bug has been marked as a duplicate of bug 39657 ***