[Bug 19485] New: Limiting by title-series (se) broken on ES
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19485 Bug ID: 19485 Summary: Limiting by title-series (se) broken on ES Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching - Elasticsearch Assignee: david.bourgault@inlibro.com Reporter: david.bourgault@inlibro.com When filtering/limiting search results by Series title, the limit field name passed to ES is 'title-series' but it expects 'se', causing no results to be found. This is particularly confusing as the page URL clearly says limit=se:XYZ. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19485 David Bourgault <david.bourgault@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19485 --- Comment #1 from David Bourgault <david.bourgault@inlibro.com> --- Created attachment 68260 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=68260&action=edit Bug 19485 - Don't transform se: limit for ES This removes the field name conversion for the Series title. Before it would transform 'se' into 'title-series', now in won't since ES indexes as 'se' by default. TEST PLAN: 0) Create a record with a "Series title" tag (440$a or 490$a in MARC21) 1) In the OPAC, do a search which would include the record from step 0) 2) In the left facet selection, click on the series title. <==== Without patch 3) No results will be shown, the breadcrumbs show the limit as 'title-series' ====> With patch applied 3) Results will show correctly, breadcrumbs show the limit as 'se' -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19485 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #2 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I finally got Elasticsearch working but seem to be missing the mappings - facets are not showing and the administration page is empty. Can you help me with a hint? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19485 --- Comment #3 from David Bourgault <david.bourgault@inlibro.com> --- The mappings are supposed to be located in admin/searchengine/elasticsearch/mappings.yaml -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19485 Séverine Queune <severine.queune@bulac.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |severine.queune@bulac.fr -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19485 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |In Discussion CC| |nick@bywatersolutions.com --- Comment #4 from Nick Clemens <nick@bywatersolutions.com> --- This works, but I am not sure it is the best solution - bug 19575 fixes things the other way, providing a friendlier name to the index - can you think of benefits to ths approach over the other? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19485 David Bourgault <david.bourgault@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from David Bourgault <david.bourgault@inlibro.com> ---
can you think of benefits to ths approach over the other?
No I can't. David Gustafsson's approach is much better. I used my solution only because I wasn't confident enough with ES to make big changes. I'm not sure what the correct status is, I'll set it to RESOLVED DUPLICATE. *** This bug has been marked as a duplicate of bug 19575 *** -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org