https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25673
Lari Taskula <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Lari Taskula <[email protected]> --- (In reply to Katrin Fischer from comment #1) > I think logging every page could get a lot pretty fast. Indeed. This is to be expected. Larger Koha instances are probably talking about millions to tens of millions of log records of the access/view-event annually. Not to forget their action_log could already be bloated. One option would be to clear these logs periodically. The libraries that worry about action_log size but still want to store it long-term, could consider other means of storage. They could achieve that with Koha plugins. There's even real world cases where Koha libraries enabled the "view" event logging, and some of them regularly move this data into a separate database. They were also the source to my log row count estimation in the first paragraph of this comment. > Maybe we could start with viewing a patron record? (accessing the detail page) Splitting this into smaller parts is probably smart since it's going to affect many pages. > We should also make sure that patron batch edits are logged correctly. + REST API + other APIs. Figuring out all the places as well as making sure that this policy applies to future changes - it's going to be a lot of careful work :) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
