http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2720 --- Comment #6 from Kyle M Hall <kyle@bywatersolutions.com> --- (In reply to comment #5)
(In reply to comment #4)
I would say we keep borrowers.debarred, but convert it to a boolean value.
Convert it *back* to a boolean value! And move the date information into borrower_debarment?
Yes. It will just be a quick check to know if the borrower is currently debarred without checking the debarments table.
We can then have that value updated each time the debarments table is altered.
Which is when? Is there a line in borrower_debarment for each overdue item which is past the limit? And the table is reviewed each time an item is renewed or checked in?+
Each time a debarment is added to the borrower_debarments table, or a debarment is removed from the borrower_debarments table, a check will then be performed to determine if the borrower is currently debarred or not, and borrowers.debarred will be updated accordingly.
I believe we will then need a nightly cronjob to remove expired debarments and update borrowers.debarred.
I don't understand. Are we talking about a cron job or is this something which updates each time something is checked in or renewed?
Right now, Koha checks the debarment field as a date to see if it is still valid. This will no longer be effective, as we will be able to have multiple debarments with different expiration dates. We can have a cronjob that runs nightly to remove any expired debarments, and reset the borrowers.debarment field to 0 if the borrower no longer has any active debarments. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.