[Koha-bugs] [Bug 12734] New: Authority 001 should be set to authid in AddAuthority()

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12734

            Bug ID: 12734
           Summary: Authority 001 should be set to authid in
                    AddAuthority()
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: MARC Authority data support
          Assignee: gmcharlt at gmail.com
          Reporter: dcook at prosentient.com.au
        QA Contact: testopia at bugs.koha-community.org

In AddBiblio() (and other Biblio functions), we use _koha_marc_update_bib_ids()
to set/reset the 999$c and 999$d to the biblionumber and biblioitemnumber.

In AddAuthority(), there is some handling for adding the authid to the 001, but
it only happens if no $authid is supplied to the function, or if an $authid is
provided and the record to be added doesn't have a 001.

Most of the time, this doesn't seem to matter...because the auth_header.authid
value is used a lot of the time in Koha.

Moreover, rebuild_zebra.pl will reset the 001 for a record to
auth_header.authid or zebraqueue.biblio_auth_number (depending on how the
record is being indexed), so searching Zebra using the authid value will still
work.

However, that means that the 001 in the MARC in the MySQL database can be
different from the 001 in MARC the Zebra database.

This is a common scenario if you upload authorities using "bulkmarcimport.pl
-keepids=035a". The 001 from the record will be moved to the 035$a leaving the
record without a 001.

The authid (whether it's from a matched record or a newly calculated value)
will be set in the database column and in the 001 in Zebra...but not in the
MARC in MySQL.

-- 
You are receiving this mail because:
You are watching all bug changes.