https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27365
--- Comment #32 from Thomas Klausner <[email protected]> --- (In reply to David Cook from comment #30) > With the Elasticsearch issue, the shortest path is probably to store the > MARCXML Which already happens in some cases. And it would be easy to just completely switch to MARCXML > instead of the ISO 2709 MARC, although overall I think it's madness > that we store the whole record in the indexing engine and we shouldn't do it > at all. No, it does make sense. When we have the whole record we can render it in the result list without hitting the database. I guess that's the intention here, though I haven't checked if Koha actually renders the list only based on the ES response, or if it already does hit the DB (which it might have to do to check if an item is currently available) But if it's worth it (the storage costs of the whole record vs the runtime cost of retrieving it from the DB) is something that could be up for discussion. -- 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/
