[Bug 12722] New: Population of Authority 001 is inconsistent
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12722 Bug ID: 12722 Summary: Population of Authority 001 is inconsistent Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: gmcharlt@gmail.com Reporter: dcook@prosentient.com.au QA Contact: testopia@bugs.koha-community.org Importing New Authority: 1) Staged MARC Management && Z39.50 MARC import The 001 will be the "authid", which will be the primary key in the auth_header table. This is regardless of whether there is a 001 in the incoming record or not. (This is rather shocking, since you can SEE the 001 in the incoming record. But the incoming 001 will be dumped in favour of the "authid".) 2) bulkmarcimport.pl The 001 will be the incoming 001, and NOT the "authid"... UNLESS you use the "-keepid=FIELD" flag OR if there is no 001 on the incoming record. -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12722 --- Comment #1 from David Cook <dcook@prosentient.com.au> --- Replacing an Authority: 1) Staged MARC Managament The 001 of the replacement record will be used, even if it's not the "authid". 2) bulkmarcimport.pl I haven't tested this... but it looks like the match is done on 001 so it'll be whatever the 001 one was in the incoming and the existing record (or the incoming 001 and the YAML mapping for the existing record). -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12722 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.koha-community. | |org/bugzilla3/show_bug.cgi? | |id=12734 --- Comment #2 from David Cook <dcook@prosentient.com.au> --- When bulk importing an authority record, we should probably be moving the 001 into another field such as the 035$a, since the 001 should be storing Koha's local authid (according to how we handle the 001 for authorities in Koha, not necessarily according to the MARC specification). bulkmarcimport.pl let's us do that with -keepids=035a, but it's tempting to enforce it for all imports...because otherwise we could lose data that we need later for matching. Of course, moving the 001 to the 035$a doesn't follow MARC spec 100%. As the 035$a should be "(OldMarcOrgCode)OldControlNumber", which wouldn't be useful for matching. We'd want to just use "OldControlNumber", otherwise it wouldn't match anyway. -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org