Because logging modifications to items has so much overhead, it is not recommended that CataloguingLog be enabled. If we split off modifications to items into a separate system preference CataloguingLogItems, then libraries can at least log modifications to records without taking a large processing hit.
Created attachment 54869 [details] [review] Bug 17195 - Split logging of item modifications from CataloguingLog into separate system preferences Because logging modifications to items has so much overhead, it is not recommended that CataloguingLog be enabled. If we split off modifications to items into a separate system preference CataloguingLogItems, then libraries can at least log modifications to records without taking a large processing hit. Test Plan: 1) Apply this patch 2) Run updatedatabase.pl 3) Disable CataloguingLog and CataloguingLogItems 4) Edit a record and edit an item 5) Note no action logs are produced 6) Enable CataloguingLog 7) Edit a record and edit an item 8) Note only a record edit action log is produced 9) Disable CataloguingLog, enable CataloguingLogItems 10) Edit a record and edit an item 11) Note only an item edit action log is produced 12) Enable both CataloguingLog and CataloguingLogItems 13) Edit a record and edit an item 14) Note an action log is created from both edits This test plan can be repeated with creating and deleting items/records as well.
Hi Kyle, Everything was working well until Step 9. I am still seeing the record edit action log with CataloguingLog turned off. Everything else works as expected though
Is this still valid? I think that this might have been something that we were working on because of cataloging log getting spammed by circulation, which was fixed in Bug 18816.
(In reply to Barton Chittenden from comment #3) > Is this still valid? I think that this might have been something that we > were working on because of cataloging log getting spammed by circulation, > which was fixed in Bug 18816. Agreed, both bugs aimed to solve the same basic problem. *** This bug has been marked as a duplicate of bug 18816 ***