[Koha-bugs] [Bug 24835] New: Bad PCDATA explodes search with a Software ERROR.

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

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

            Bug ID: 24835
           Summary: Bad PCDATA explodes search with a Software ERROR.
 Change sponsored?: ---
           Product: Koha
           Version: 19.11
          Hardware: All
                OS: All
            Status: NEW
          Severity: critical
          Priority: P5 - low
         Component: Searching
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: Lisa.Beinhoff at ttuhsc.edu
        QA Contact: testopia at bugs.koha-community.org

Searching in the public library catalog for a record with bad PCDATA, causes
the following error to appear:

Software error:
Invalid data, cannot decode object (id=75430, format=marcxml, schema=MARC21,
decoding_error=':94: parser error : PCDATA invalid Char value 27
construction of the Metacarpal Hand -- 21. The Mutilated Wrist -- 22.
Krukenberg
                                                                               
^
:94: parser error : PCDATA invalid Char value 27
struction of the Metacarpal Hand -- 21. The Mutilated Wrist -- 22.
Krukenbergb2
                                                                               
^')
For help, please send mail to the webmaster ([no address given]), giving this
error message and the time and date of the error.


Error generated in staff view is:

There is an error with this bibliographic record, the view may be degraded.
Error: Invalid data, cannot decode object (id=75430, format=marcxml,
schema=MARC21, decoding_error=':94: parser error : PCDATA invalid Char value 27
construction of the Metacarpal Hand -- 21. The Mutilated Wrist -- 22.
Krukenberg ^ :94: parser error : PCDATA invalid Char value 27 struction of the
Metacarpal Hand -- 21. The Mutilated Wrist -- 22. Krukenbergb2 ^')


Editing the record and saving the bibliographic error seems to clear the error,
for some unknown reason.  But I need a way to identify the bad records, so they
can be corrected.  About 1 in 20 records in our databases is generating this
error.

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