https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39541 Bug ID: 39541 Summary: Do we need to store the whole MARC record in Elasticsearch? Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs@lists.koha-community.org Reporter: domm@plix.at QA Contact: testopia@bugs.koha-community.org Currently the whole MARC Record is stored in the ElasticSearch Record. At the Koha Hackfest 2025 I learned that one reason for this is to be able to search the whole record (Bug 22258). Another reason might be to avoid hitting the DB when displaying search results. But: * We sometime encounter problems with very large records (due to limits with UNIMARC) * The code to store the whole record is rather convoluted (involes encoding/decoding the record, checking for errors, falling back to other encoding methods..) * It bloats the ES index (if it's not needed) So I will investigate: * would displaying search results work without the whole MARC record? * aren't we hitting the DB anyway during displaying search results * in OPAC * in Staff * in API If it seems easy to optionally not add the whole record to the index, I would suggest * Adding a new Option "Don't store" to syspref ElasticsearchMARCFormat * If it is set, skip adding the whole MARC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.