http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8015
Julian Maurice <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA CC| |[email protected] --- Comment #49 from Julian Maurice <[email protected]> --- Hi, I tested some simple use cases and found some errors/things that can be improved: The bibliographic record used for these tests has only one field 200 with various subfields (5abefg) and no field 300. 1/ Copy field 200 to 300 => Problem: No 300 field is created. Is this a bug or a missing feature? Same remark for 'Move' 2/ Copy field 200 to 300$a => Problem: 300$a = "MARC::Field::HASH(0x...)" Same for 'Move' 3/ Copy field 200$a to 300 => Problem: No 300 field is created but maybe not a bug. Same for 'Move' 4/ Copy field 200$a to 300$a => Problem: Two fields 300 are created, one is correct with 300$a = <value of 200$a> but one has just an empty 'a' subfield. Same for 'Move' but the empty 'a' subfield is now a subfield that contains the string "don't_erase". 5/ Add/Update field 200 with value 'blob' => Problem: create a subfield 'b' with value 'lob' 6/ There is also a problem with Regex. If they contain '\' characters, they are removed from text input when editing the action. So if I edit an action and update it without changing anything, regex like "/(word)/\U$1\E/" are saved as "/(word)/U$1E" Failing QA for 2, 4 and 6. For 1, 3 and 5 it would be great if Koha prevent the user to enter invalid action. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
