https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39054
--- Comment #13 from Lisette Scheer <[email protected]> --- (In reply to Katrin Fischer from comment #12) > 1) Log editor > > "Merge" is now doubled up in the list of actions. Yes, also we already have a merge for biblios, so it would be better to do something different if a different action is the way to go. > 2) How best to make the differentiation? > > I can see why this change would be useful, but I wonder if we should adjust > the naming of the action or even move the information into the "info" or > another place instead of changing the action. > > Some thoughts on this: > > - Merge [MERGE] could be easily misread as meaning the action of merging 2+ > bibliographic records. > - It will potentially 'break' reports that look for just Modify. Depending > on what you use them for this might be a breaking change for some processes. > An example might be a report that is used to export changed records for an > external database. > It already breaks the link from the record and doesn't show the changes because it's a hardcoded modify link. A flag in the info or like a different interface or something could be helpful? Like yes it was triggered from the staff interface, but it was edited by an automation that was triggered, so maybe an interface for those things so it would be easy to filter them out if you had a lot but could also easily tell it was from the authority update? > These action logs are still pretty "old school", the info appearing as: > > biblio $VAR1 = { '_marc' => { '001' => '4327601', '005' => > '20200129130616.0', '008' => '880222s1988 mnu s000 0 eng ', '010' => [ ' $a > 88004763 ' ], '020' => [ ' $a 0816617112 : $c $19.95', ' $a 0816617120 > (pbk.) : $c $9.95' ], '040' => [ ' $a DLC $c DLC $d DLC' ], '041' => [ '1 $a > engpor' ], '050' => [ '00 $a PQ9697.L585 $b P313 1988' ], '082' => [ '00 $a > 869.3 $2 19' ], '100' => [ '1 $a Lispector, Clarice.' ], '240' => [ "10 \$a > Paix\x{e3}o segundo G.H. \$l English" ], '245' => [ '14 $a The passion > according to G.H. / $c Clarice Lispector ; translation by Ronald W. Sousa.' > ], '260' => [ ' $a Minneapolis : $b University of Minnesota Press, $c > c1988.' ], '300' => [ ' $a ix, 173 p. ; $c 22 cm.' ], '440' => [ ' 0 $a > Emergent literatures' ], '500' => [ " \$a Translation of: A paix\x{e3}o > segundo G.H." ], '906' => [ ' $a 7 $b cbc $c orignew $d 1 $e ocip $f 19 $g > y-gencatlg' ], '942' => [ ' $c BK' ], '999' => [ ' $c 438 $d 438' ] }, > 'author' => 'Lispector, Clarice.', 'biblionumber' => 438, 'copyrightdate' => > 1988, 'datecreated' => '2015-01-05', 'frameworkcode' => 'BKS', 'notes' => > "Translation of: A paix\x{e3}o segundo G.H.", 'opac_suppressed' => 0, > 'seriestitle' => 'Emergent literatures', 'title' => 'The passion according > to G.H. /', 'unititle' => "Paix\x{e3}o segundo G.H." }; > > With the recent work on improving the logs I nwonder if there is another > option we could use to include the information about "auto-authority > updates" in another way? > > Adding Lisette for second opinion. The diff does look nice, which is the more modern view (column is currently hidden by default and needs to be reloaded after it's turned on, need to file a followup for that) -- 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/
