Summary: | Add separate column for administrative locked patron | ||
---|---|---|---|
Product: | Koha | Reporter: | Marcel de Rooy <m.de.rooy> |
Component: | Patrons | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | gmcharlt, jonathan.druart, katrin.fischer, kyle.m.hall |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21336 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25947 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
Marcel de Rooy
2019-05-06 06:46:52 UTC
Any more feedback, Jonathan? I think we could have only 1 more column: the reason of the lock. If NULL, the account is not locked. The field could be an ENUM with the different reasons. I think that changing the pref resulting in unlocking users makes sense to me. You might figure out you don't want to use the feature after all, so setting a high value will help. Having 2 columns will allow to have an administrative lock and a too_many_attempts lock at the same time... but it makes me wonder if we could just have 1 new column for the administrative lock as boolean? And keep the failed_attempts behaviour. |