[Koha-bugs] [Bug 28491] New: field 003 not updated after import
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Mon May 31 14:06:41 CEST 2021
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28491
Bug ID: 28491
Summary: field 003 not updated after import
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: MARC Authority data support
Assignee: koha-bugs at lists.koha-community.org
Reporter: domm at plix.at
QA Contact: testopia at bugs.koha-community.org
I import some authority data from e.g. dnb.de, which contains:
<controlfield tag="001">11915725X</controlfield>
<controlfield tag="003">DE-101</controlfield>
After the import, the local authority data looks like
<controlfield tag="001">35</controlfield>
<controlfield tag="003">DE-101</controlfield>
So 001 now contains the internal Koha id (good), but 003 still points to DE-101
(i.e. dnb.de), which I think is bad, because if I look up the ID '35' in the
linked DB DE-101, I will now get a bad result.
I assume that 003 should be set to my MARCOrgCode
Looking at the code, I find (in C4::AuthoritiesMarc, AddAuthority, 568ff)
if (!$record->field('003')) {
$record->insert_fields_ordered(
MARC::Field->new('003', $marcorgcode),
);
}
So this behavior seems intentional? If so, I still find it very unlogical and
buggy. I assume that both 001 and 003 should be overwritten with data pointing
to the current Koha instance, and the original 001/003 "archived" in 035 and/or
040
I could easily provide a patch that changes this behavior, but I'm not sure if
this would cause confusion / failing tests / etc.
Maybe add an option to allow a force-overwrite of 003?
Greeting,
Thomas
PS this seems slightly related to #25603
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
More information about the Koha-bugs
mailing list