https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36434 Aleisha Amohia <aleisha@catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|oleonard@myacpl.org |aleisha@catalyst.net.nz Status|NEW |ASSIGNED Change sponsored?|--- |Sponsored -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36434 --- Comment #1 from Aleisha Amohia <aleisha@catalyst.net.nz> --- Created attachment 163969 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=163969&action=edit Bug 36434: Use a keyword that will be secretly included in all OPAC bibliographic and authority searches When a keyword is provided to the new OPACAlwaysSearchKeyword system preference, Koha will secretly add this to all OPAC searches (both bibliographic and authority) to help limit results. Note: This will have unexpected results if authority searches are done with 'starts with' or 'is exactly'. It is only designed to work with 'contains'. To test: 1. Install database updates and restart services. 2. Do a standard OPAC search using the main search bar for 'this that'. Notice the number of results. 3. Do an advanced OPAC search, specify keyword: 'this' and keyword: 'that'. Notice the number of results. 4. In the staff interface, do a biblio search for 'this that'. Edit the first two records, and put your test keyword somewhere in the MARC, perhaps a note field 5XX. 5. Go to the Koha Administration -> System preferences and search for OPACAlwaysSearchKeyword. Add your test keyword to the syspref and Save. 6. Repeat steps 2 and 3. Confirm results are returned, and there should only be your two records which you added the test keyword to. 7. Remove the test keyword from OPACAlwaysSearchKeyword and Save. 8. Do an OPAC authority search for 'series'. Notice the number of results. 9. In the staff interface, do an authority search for 'series'. Edit the first two records, and put your test keyword somewhere in the MARC, perhaps in the 040$f. 10. Repeat step 5. 11. Repeat steps 8 and 9. Confirm results are returned, and there should only be your two records which you added the test keyword to. 12. Click on 'Welcome, your name' in the top right of the OPAC and go to your search history. Confirm the test keyword added to OPACAlwaysSearchKeyword does NOT show in your history, for both catalog and authority searches. 13. Confirm all results are returned as normal when OPACAlwaysSearchKeyword is empty. Sponsored-by: Auckland University of Technology -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36434 --- Comment #3 from Anneli Österman <anneli.osterman@koha-suomi.fi> --- Or with OpacSuppression system preference and suppress information in biblio record's 942$n field? -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36434 Lucas Gass <lucas@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lucas@bywatersolutions.com --- Comment #5 from Lucas Gass <lucas@bywatersolutions.com> --- Can you explain the use case for this a bit more? Personally Im not a fan of "secertly" doing things that effect patron's searches. I think this hurts findability/disoverability for patrons. Maybe outlining a use case for us will help understand why this is needed. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36434 Esther Melander <esther.melander@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |esther.melander@bywatersolu | |tions.com --- Comment #7 from Esther Melander <esther.melander@bywatersolutions.com> --- The concern with this approach is the potential for abuse over time. Search engines have been accused of such things for years. OpacHiddenItems can hide the one collection in the Koha OPAC. What is available for display/use in the Discovery Layer depends on how the discovery layer handles the OpacHiddenItems flag. It is perhaps better handled at the discovery layer level and not Koha directly. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36434 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nick@bywatersolutions.com --- Comment #9 from Nick Clemens <nick@bywatersolutions.com> --- Just curious, what is the keyword you are using/where is it stored in the MARC record? Koha technically does use a forced hidden keyword in searching for suppressed records - we append 'suppress=0' for opac searches. Maybe if this cannot be handled through the current suppression module, the development could extend the fields used to define suppression and allow for another field/value to be suppressed? At least with Elasticsearch this should be easily configurable out of the box -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36434 --- Comment #11 from Owen Leonard <oleonard@myacpl.org> --- "This will have unexpected results if authority searches are done with 'starts with' or 'is exactly'. It is only designed to work with 'contains'" What are the unexpected results? That sounds scary. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36434 --- Comment #13 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- Created attachment 189692 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189692&action=edit Bug 36434 [alternate WIP]: Specify a search index and value to limit results on the opac Similar to suppression, this patch adds two new system preferences OPACAlwaysSearchIndex and OPACAlwaysSearchValue which will be used to add a limit to the search results when OPACSuppression is enabled This is only done for Elasticsearch and only for biblios currently, not authorities, but could be extended This also shows up in your search history, as suppression currently does (maybe a syspref to hide it?) The test plan below is simple, but ideally you would add a new index and use that, and probably not make it generally searchable Handling this in the query builder routines makes it testable, which I think is nice To test: 1 - Have a Koha using Elasticsearch 2 - Install database updates and restart services. 3 - Do a standard OPAC search using the main search bar for 'a' and note the resuls 4 - Do an advanced OPAC search, specify keyword: 'a' and homebranch: 'CPL'. Notice the number of results. 5 - Go to the Koha Administration -> System preferences and search for 'OPACAlways'. 6 - Note the two new preferences and add 'homebranch' for ..Index and 'CPL' for ..Value and Save. 7 - Repeat steps 2 and 3. 8 - Confirm results are returned, the basic search should now return results of the advanced search 9 - The advanced search should not change. 10 - Remove the test keyword from OPACAlwaysSearchKeyword and Save. -- You are receiving this mail because: You are watching all bug changes.