https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35591
--- Comment #1 from Katrin Fischer <[email protected]> --- Overall this doesn't sound like intended behavior. Koha did not always replace 001 with the authid, in the distant past it kept the imported 001. I could imagine the behavior made more sense back then, but does much less now. I see 2 different bugs here: * It breaks importing for everyone that imports data with an existing 001 that is somewhat numerical and can clash with the authids in Koha that are added to 001 on import. * The guess is not even exact. I assume this is because of using the search index, but maybe there should be an additional Perl check if they are really equivalent before overlay? I would not be opposed to change the behavior here or make it a legacy switch that needs to be chosen actively. The current behavior appears quite dangerous. Some other thoughts: Could it make sense to forgo GuessAuthId when another match-rule is used? And maybe have a separate bug for making the match more exact/smarter. -- You are receiving this mail because: You are the assignee for the bug. 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/
