[Koha-bugs] [Bug 28128] New: Cataloging Record Uploading Process

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

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28128

            Bug ID: 28128
           Summary: Cataloging Record Uploading Process
 Change sponsored?: ---
           Product: Koha
           Version: 20.05
          Hardware: All
                OS: All
            Status: NEW
          Severity: critical
          Priority: P5 - low
         Component: Tools
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: cmkelleymls at gmail.com
        QA Contact: testopia at bugs.koha-community.org

About three months ago, my library moved its Koha ILS to a new machine. The
transition was not ideal but it was smooth enough.

    We still catalog a bit on the old machine and last week we extracted and
uploaded a bunch of records to the new machine. The upload process stalled.

    After days of trying to find out why the uploading process would stall, I
noticed that the 952 $7 in a few records was miscoded as a 952 $9 instead. Once
I reverted the 952 $9 to 952 $7, all was well.

    This also happened when a transfer record had a 999 field. If the record
number in 999 $c and 999 $d did not exist, the uploading processing would
stall. So I deleted the 999 fields or corrected them to what was in the other
copy of the ILS; and again all was well.

    I have been reading online about this phenomenon and I haven't found a
reason or solution to the stall. Mind you, other operations continue to run:
the editing of existing records and the entry of new records; circulation;
calendar changes, etc. It's just the automatic record uploading through the
user interface that stalls.

    Well, here are two possible solutions: check for 952 $9 fields and 999
fields in the records that are to be uploaded. They may be the source of stall.
Their presence may not be the only source, mind you, but their presence is a
possibility.

    P. S. It would be nice if instead of stalling, the uploader would write the
MARC record to some sort of upload log with a reason; and then try uploading
the next record.

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