| Summary: | Retire the patron account flags | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
| Component: | Patrons | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | anneli.osterman, gmcharlt, kyle |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| 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: | |||
|
Description
Christopher Brannon
2025-12-10 23:35:29 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. 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. |