|Summary:||Authorities: Replace authority with Z3950 does not update existing record when duplicate check is triggered|
|Product:||Koha||Reporter:||Marcel de Rooy <m.de.rooy>|
|Component:||MARC Authority data support||Assignee:||Bugs List <koha-bugs>|
|Status:||RESOLVED DUPLICATE||QA Contact:||Testopia <testopia>|
|Priority:||P1 - high||CC:||abales, andrewfh, gveranis|
|Change sponsored?:||---||Patch complexity:||---|
|Documentation contact:||Documentation submission:|
|Text to go in the release notes:||Version(s) released in:|
Description Marcel de Rooy 2020-10-22 06:46:03 UTC
When trying to replace an existing auth record in the Authorities module via Z3950, it seems that I can only add new imported records but not replace an existing one. If I get the warning "Duplicate suspected", it only offers me to edit the existing record or add a new one. But I want to replace the old one.
Comment 1 Katrin Fischer 2020-10-22 10:40:02 UTC
That work ok for me. - Edit any existing authority record - Replace with Z39.50 - Search, select and import - Page reloads, record is replaced - Save Could it be that the problem only appears when you replace with an authority record that triggers the duplicate check?
Comment 2 Marcel de Rooy 2020-10-22 11:09:37 UTC
(In reply to Katrin Fischer from comment #1) > That work ok for me. > > - Edit any existing authority record > - Replace with Z39.50 > - Search, select and import > - Page reloads, record is replaced > - Save > > Could it be that the problem only appears when you replace with an authority > record that triggers the duplicate check? I think so.
Comment 3 Andrew Fuerste-Henry 2021-10-01 19:20:38 UTC
I can confirm this is still true in 21.05 and is still a point of frustration. We need an option to replace the existing authority with what we've just fetched from z39.50
Comment 4 Amber Bales 2021-10-07 21:54:32 UTC
Our library upgraded to 21.05 and I'm running into this problem. It wasn't an issue before, and adds extra steps. Clicking "Yes: Edit existing authority" does not replace the record, clicking "No: save as new authority" creates a new authority that is not attached to any record(s), so you have to merge the authority records, or choose the new record and delete the record that is not attached. It's quite tedious.