[Bug 16821] New: Facets: home libraries, locations, item types
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 Bug ID: 16821 Summary: Facets: home libraries, locations, item types Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt@gmail.com Reporter: cbrannon@cdalibrary.org QA Contact: testopia@bugs.koha-community.org It is my understanding that facets are built off the first page of search results. It seems that home libraries, locations and item types are all facets that should be completely available regardless of the first page of results, especially when you click "Show more". I would suggest this be changed to include all the fixed facets rather than being random. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 Agnes Rivers-Moore <arm@hanover.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arm@hanover.ca --- Comment #1 from Agnes Rivers-Moore <arm@hanover.ca> --- Well, that explains a few things - like why "show more" does not always appear, seemingly at random. When there are more than 5 facets in a category within search results, but if the first page has only 5 or less the "Show more" link is missing. The searcher is not offered a way to use the facets found in the rest of the search results. It raises the question - why are the facets built from the first page only? Is there an unacceptable performance hit? This is certainly something the average user would not expect, and gives the impression that the system is not finding facets they would want to use. Yes item type and location, but also series ... -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 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> --- There are currently 2 ways, but both have issues: 1) Use Zebra facets - the whole result set is used to build the facets, but unfortunately we found it too slow on big databases to be usable. (see 136659 2) Use Koha facets - you can use the maxRecordsForFacets system preference to choose how many records are used for the facets (20 = first page is the default). But the higher you set the number, the longer it will take. What option is used is set in the koha-conf.xml file. You are both right - the situation now is far from being good, but at the moment to my knowledge there is no real good way at least for bigger databases to make this work nicely. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 --- Comment #3 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Typoed the bug number in 1) - the bug is bug 13665. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 --- Comment #4 from Agnes Rivers-Moore <arm@hanover.ca> --- OK, would it be possible for "Show More" to appear for all categories, regardless of the number of facets retrieved, and the rest of the facets be generated from all search results only when Show more is clicked? That way there is not increased performance hit for the first page, but all possible facets can be accessed if needed. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 --- Comment #5 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hm, it could work a little better than it does now that way. But with elastic search around the corner I am not sure someone will give rewriting the facets code a go. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 jmbroust <jean-manuel.broust@univ-lyon2.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jean-manuel.broust@univ-lyo | |n2.fr -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 --- Comment #6 from Christopher Brannon <cbrannon@cdalibrary.org> --- I think having Koha add a complete list of facet for some categories (this should be an option), rather than the database building these particular facets, would be more reliable, and maybe even faster, as the database does not have to compile and generate them. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 --- Comment #7 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I guess you could always display, say, all item types, but we couldn't display the number of records behind it then and also it would show item types that are not part of the search result. Would be interesting to get some idea how well this works with Elastic at the moment. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 Marjorie Barry-Vila <marjorie.barry-vila@collecto.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marjorie.barry-vila@collect | |o.ca -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Facets: home libraries, |Display complete facets for |locations, item types |home libraries, locations, | |item types -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 --- Comment #8 from Marjorie Barry-Vila <marjorie.barry-vila@collecto.ca> --- +1 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 Agnes Rivers-Moore <arm@hanover.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|arm@hanover.ca | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 Koha collecto <koha@collecto.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |koha@collecto.ca -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 Katie Bliss <kebliss@dmpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kebliss@dmpl.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 --- Comment #9 from Christopher Brannon <cbrannon@cdalibrary.org> --- This issue has cropped again. It is not evident to staff or patron why certain branches don't appear. It would be helpful to make the branches all show. Perhaps when it is generated, it compares the library facet list to the complete list of libraries, and then fills the missing ones in with a (0) next to it. But that is not accurate either. While having a number of results next to the branch might seem helpful, it is also deceptive and actually useless if the number is based off a number of results define in the maxRecordsForFacets setting that neither staff nor patron are aware of. It seems this number is not indicative of results in the entire inventory, and is therefore arbitrary. I would say that these numbers are useless, and should be done away with. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 --- Comment #10 from Christopher Brannon <cbrannon@cdalibrary.org> --- And I say they should be done away with as they are keeping us from showing useful and complete facets. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 --- Comment #11 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Christopher Brannon from comment #10)
And I say they should be done away with as they are keeping us from showing useful and complete facets.
Are you using Zebra or Elasticsearch? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 --- Comment #12 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- The limitations you describe should only apply to Zebra. The number of results shown for Elasticsearch facets should be correct. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 --- Comment #13 from Christopher Brannon <cbrannon@cdalibrary.org> --- ElasticSearch. Well, if it is the correct number despite the maxRecordsForFacets, then that is misleading to those of us setting this up. Regardless, not all library branches show, and they should. Our at least we should be given that option. Along with consideration for locations and item types. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nick@bywatersolutions.com --- Comment #14 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Christopher Brannon from comment #13)
ElasticSearch. Well, if it is the correct number despite the maxRecordsForFacets, then that is misleading to those of us setting this up. Regardless, not all library branches show, and they should. Our at least we should be given that option. Along with consideration for locations and item types.
I'd argue that showing all would not be the desired outcome for everyone. As long as the missing of the facet indicates correctly that there is no result for this setting. @Nick can you confirm that maxRecordsForFacets is not relevant for Elasticsearch or when using Zebra facets maybe? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16821 --- Comment #15 from Christopher Brannon <cbrannon@cdalibrary.org> --- (In reply to Katrin Fischer from comment #14)
(In reply to Christopher Brannon from comment #13)
ElasticSearch. Well, if it is the correct number despite the maxRecordsForFacets, then that is misleading to those of us setting this up. Regardless, not all library branches show, and they should. Our at least we should be given that option. Along with consideration for locations and item types.
I'd argue that showing all would not be the desired outcome for everyone. As long as the missing of the facet indicates correctly that there is no result for this setting.
@Nick can you confirm that maxRecordsForFacets is not relevant for Elasticsearch or when using Zebra facets maybe?
I can promise you, I would not be going down this path if that were the case. We have items at locations we know exist and those locations are not showing up in the facets because they are not within the range of the maxRecordsForFacets. I also understand that you feel that it might not be the desired outcome for everyone, which is why I requested that this be an OPTION. -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org