Bug 17195 - Split logging of item modifications from CataloguingLog into separate system preferences
Summary: Split logging of item modifications from CataloguingLog into separate system ...
Status: RESOLVED DUPLICATE of bug 18816
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Kyle M Hall
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-25 12:06 UTC by Kyle M Hall
Modified: 2018-10-17 16:54 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Bug 17195 - Split logging of item modifications from CataloguingLog into separate system preferences (10.49 KB, patch)
2016-08-25 13:22 UTC, Kyle M Hall
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall 2016-08-25 12:06:52 UTC
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.
Comment 1 Kyle M Hall 2016-08-25 13:22:13 UTC
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.
Comment 2 Aleisha Amohia 2016-08-29 04:09:43 UTC
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
Comment 3 Barton Chittenden 2018-10-15 17:15:29 UTC
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.
Comment 4 Kyle M Hall 2018-10-17 16:54:47 UTC
(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 ***