Bug 41430 - Retire the patron account flags
Summary: Retire the patron account flags
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-10 23:35 UTC by Christopher Brannon
Modified: 2025-12-15 17:10 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-12-10 23:35:29 UTC
It seems odd to have two very specific account flags on patron accounts.  We can accomplish the same task with patron restrictions (debarments).

I would suggest we retire the patron account flags, and migrate any active flags to restrictions.

Furthermore, we could create predefined restrictions, much like we have with predefined notes.
Comment 1 Anneli Österman 2025-12-15 13:08:22 UTC
How does this idea affect the integrated systems connected via SIP2 or API? I think the lost flag prevents checkouts when using SIP2 but I'm not sure if restrictions do the same.
Comment 2 Christopher Brannon 2025-12-15 17:10:14 UTC
I don't currently have a SIP2 setup to test against, but I do believe restrictions do prevent checkouts.  We use restrictions all the time.  Blocking checkouts is the primary function of a restriction.

I just tested both side by side on the staff interface, and they seem to function identically.  If they differ via SIP2 or API, I am not aware, nor would I understand why.