https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38270
David Cook <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=38101 --- Comment #5 from David Cook <[email protected]> --- Doing some more testing here... 1. For a record with over 99,999 characters (for example a bib record with twenty 500 fields with 5000 characters in the $a), it looks like it really does switch to using MARCXML for the marc_data in Elasticsearch and the marc_format is listed as MARCXML. All good! 2. For a record with one 500 field with 15,000 characters in the $a, it uses a marc_format of "base64ISO2709" and while it does index it... it cannot properly display the metadata from marc_data in the Koha search result pages. I suppose for all records using "base64ISO2709", we could always try to round-trip it first before storing, and failing that we could switch to MARCXML. That said, I'm still interested in the Compressed MARCXML... But... if we're reaching a scenario where we're using "base64ISO2709" but have 1+ fields that have more than 9999 chars but the overall record is < 99999 chars... then it's not going to be a huge record... 3. For a record with one 500 field with over 32766 bytes in length, you run into bug 38101 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
