[Koha-bugs] [Bug 27365] Koha doesn't check marcxml field size is < 10000 and fails in various places

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

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

--- Comment #20 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
(In reply to Eric Phetteplace from comment #18)
> Created attachment 142786 [details]
> example MARC record
> 
> (In reply to David Cook from comment #16)
> > (In reply to Blou from comment #15)
> > > We have the problem in searches (opac/staff).  ES indexes without any
> > > problem.  I see the data returned when turning on trace_to in koha-conf.xml.
> > > 
> > > But somewhere in Koha or MARC library, something breaks.  The records with a
> > > 505$a longer than 9999 characters are not displayed correctly in the results.
> > > 
> > > Actually, NO data shows up.  But there's an empty entry in the results.  The
> > > other records are listed without problem.
> > > 
> > > Considering that the xslt for the results never infer to 505 the slightest,
> > > it seems to me its the marcxml that breaks down.  Somewhere, somehow.
> > 
> > Are you able to reliably reproduce that problem? If so, attach a copy of
> > that record here with the steps needed to reproduce it. Someone might be
> > able to take it somewhere then. 
> > 
> > Long ago, I locally customized the Zebra indexing to only index 5000
> > characters for the notes fields, as I think that 9999+ notes fields were
> > causing us problems, but I think the original record would still be
> > retrieved and used in Koha. Since you're using ES, that's probably not
> > relevant.
> > 
> > Sounds like more investigation is needed, but also sounds like an edgecase,
> > so perhaps more of a support issue...
> 
> We're able to recreate this bug with the attached record. If you search for
> it on the staff side, a broken search result appears with the cover image in
> the left-side column and the list of action links (hold, add to cart,
> etc...) in the second column, no metadata. The public search results show an
> analogous problem. To fix it, we split the long 505 field in two; that
> record works fine.
> 
> We're on Elasticsearch. I tried retrieving the record with the API as well
> as going to its detail views pages on the public and staff sides; all of
> those are OK. So the problem is specific to search results. I did not test
> on Zebra.

Not sure if this is good or bad news, but I imported the attached record into
my  dev installation without problem. The record is searchable and display on
detail page and in result list looks ok too. (Maybe something changed since
this was filed initially?)

If someone could confirm, we might be able to close this?

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