http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2720 --- Comment #3 from Owen Leonard <oleonard@myacpl.org> --- (In reply to comment #2)

Since there are numerous reasons for debarment, not just fines, but overdues, or a manual debarment

Automatic debarment happens only through overdue triggers. Fines may block certain actions, but those checks are made based on the fine amount and fine-related system preferences ( OPACFineNoRenewals, maxoutstanding, noissuescharge). Unless I'm missing something?

If a borrower has a least one row in this table, they will be debarred.

Will this affect the suspension in days feature? Will the debarred column in the borrowers table stop being used, and all checks for patron debarment be referred to this new table? Is this going to significantly affect performance?

This would require modifying all code that involves debarring, in particular C4::Overdues::CheckBorrowerDebarred, the borrower editing page, and the circulation pages.

If we keep borrowers.debarred, I suppose checkout performance doesn't have to be affected. I am concerned that this is going to slow down check-in. Upon each check-in Koha will have to query the borrower_debarment table to see if the patron should have the restriction removed? -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.