[Bug 22557] New: Delayed authority merges looses the user in the action_logs
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 Bug ID: 22557 Summary: Delayed authority merges looses the user in the action_logs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs@lists.koha-community.org Reporter: tomascohen@gmail.com QA Contact: testopia@bugs.koha-community.org Target Milestone: --- -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs@lists.koha-commun |tomascohen@gmail.com |ity.org | -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |9988 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9988 [Bug 9988] Leave larger authority merges to merge_authorities cronjob (pref AuthorityMergeLimit) -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|tomascohen@gmail.com |koha-bugs@lists.koha-commun | |ity.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs@lists.koha-commun |m.de.rooy@rijksmuseum.nl |ity.org | -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 --- Comment #1 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- Is it really a bug? If the merge is delayed, the user did not (technically) execute the merge so we could argue that he should not be listed as such in the log. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #2 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- But the user did the action that triggered the merge by changing the authority - I think it makes sense to record those. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 --- Comment #3 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- (In reply to Katrin Fischer from comment #2)
But the user did the action that triggered the merge by changing the authority - I think it makes sense to record those.
Yes, but the authority change itself has been recorded as such. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 --- Comment #4 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Yes, but it will not be so easy to see if the change recorded caused a merge (main heading was changed). I was just saying I see advantages of tracking the number. I haven't checked how the merges show up in the logs, but I assume they might as updates on bibliographic records? (UPDATE?) Or can you see it was a merge caused update somehow? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 --- Comment #5 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- (In reply to Katrin Fischer from comment #4)
Yes, but it will not be so easy to see if the change recorded caused a merge (main heading was changed). I was just saying I see advantages of tracking the number.
I haven't checked how the merges show up in the logs, but I assume they might as updates on bibliographic records? (UPDATE?) Or can you see it was a merge caused update somehow?
Differentiating them might be interesting and perhaps another solution direction? I am not against passing the user to the automatic merge process, but not wanting to spend time on something that most people wont care about. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 --- Comment #6 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Marcel de Rooy from comment #5)
(In reply to Katrin Fischer from comment #4)
Yes, but it will not be so easy to see if the change recorded caused a merge (main heading was changed). I was just saying I see advantages of tracking the number.
I haven't checked how the merges show up in the logs, but I assume they might as updates on bibliographic records? (UPDATE?) Or can you see it was a merge caused update somehow?
Differentiating them might be interesting and perhaps another solution direction?
I agree, if you know the changes are 'heading merges' that might be enough. You could then check on the last change of the record that caused it. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 --- Comment #7 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I believe we are using the background jobs here now - has this changed the situation? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 --- Comment #8 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- (In reply to Katrin Fischer from comment #7)
I believe we are using the background jobs here now - has this changed the situation?
No this is not done via background jobs. Separate cron job. Report is still valid. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 Martin Renvoize (ashimema) <martin.renvoize@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |22794 CC| |martin.renvoize@openfifth.c | |o.uk Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22794 [Bug 22794] Improve and extend staff accessible logging in Koha -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org