Summary: | Group locations for advanced search | ||
---|---|---|---|
Product: | Koha | Reporter: | Séverine Queune <severine.queune> |
Component: | Searching | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | koha, marjorie.barry-vila, r.delahunty |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Attachments: |
Add a goup Locations option - Advanced search.png
Add a goup Locations option - Facets |
Created attachment 116879 [details]
Add a goup Locations option - Facets
We have been trying to use javascript to group a bunch of Koha location codes AND also include a branch limit in the same search and add it to OpacUserJS at the end of the single-location searches, without 100% success. I call these composite or canned searches as one branch has 4 locations where it stores 'special collections material'. So I want a 4-locations plus one branch composite. No joy so far (after a LOT of work). Work has also highlighted that searching on the Locations tab AND including the Branches at the bottom tile of Advanced Search produces quite unexpected (to me wrong) results. |
Created attachment 116878 [details] Add a goup Locations option - Advanced search.png Like the option exists for itype with ITEMTYPECAT authorized value, it could be useful for users if we would group locations into several categories in OPAC advanced search and facets. For example, we have 29 different storage location only accessible to staff and 4 public locations in our catalog, which are quite confusing descriptions for opac users.