Summary: | Patron restriction should include a common header | ||
---|---|---|---|
Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
Component: | SIP2 | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | colin.campbell, Slodico |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Christopher Brannon
2020-09-02 19:04:52 UTC
Now that we have Patron Restriction Types, I would rather see the restriction type included in the AF response instead of the generic "PATRON RESTRICTED". We have some restrictions that don't prevent a person from accessing online resources and some that do. This includes the automatic restrictions like long overdue items or excessive fines. For example: [AF] => Array ( [0] => Greetings from Koha. -- PATRON RESTRICTED: FINES [1] => LIBA) or [AF] => Array ( [0] => Greetings from Koha. -- CONDUCT: Patron is dangerous. Call the police [1] => LIBB) Then we could build SIP rules like these: If AF includes "OVERDUES" - deny access. If AF includes "FINES" - allow access. If AF includes "CONDUCT" - deny access. If AF includes "VERMIN" - allow access. "VERMIN" means bedbugs or other creepy crawlies hitched a ride on the library books they returned last week, so yes, they can use the online services, no they can't check out any more books. |