In Items search(Home › Catalog › Item search ) it is possible to insert personal indexes based on MARC tags and subfields. Those indexes are managed by Item search fields (Home › Administration › Item search fields). But now in master indexes based on 245$c (and others tags like 260, 001, etc.) doesn't work. If I use it, the system doesn't do any filter on data; it list all records with an item.
The same happens for fields like 952$x. I just tested on master and it also gives back all results instead of filtering. We think this used to work sometime prior to 3.22.10.
This renders the whole configuration options useless, upping severity a bit.
Created attachment 58242 [details] [review] Bug 17743: Item search - Fix indexes build on MARC Searching items by custom search fields does not work because these fields are not correctly processed in JS. In case of custom search field, the parent of the option is not the select but the optgroup element. Test plan: Create a custom search field on 245$c for instance On the items search form, select this field and launch a search => Without this patch, the results will not be filtered and you will get all your items => With this patch applied, the results should be correctly filtered
Created attachment 58383 [details] [review] Bug 17743: Item search - Fix indexes build on MARC Searching items by custom search fields does not work because these fields are not correctly processed in JS. In case of custom search field, the parent of the option is not the select but the optgroup element. Test plan: Create a custom search field on 245$c for instance On the items search form, select this field and launch a search => Without this patch, the results will not be filtered and you will get all your items => With this patch applied, the results should be correctly filtered Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Created attachment 58386 [details] [review] Bug 17743: Item search - Fix indexes build on MARC Searching items by custom search fields does not work because these fields are not correctly processed in JS. In case of custom search field, the parent of the option is not the select but the optgroup element. Test plan: Create a custom search field on 245$c for instance On the items search form, select this field and launch a search => Without this patch, the results will not be filtered and you will get all your items => With this patch applied, the results should be correctly filtered Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de> Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
Pushed to master for 17.05, thanks Jonathan!
This patch has been pushed to 16.11.x, will be in 16.11.01.
Pushed to 3.22.x for 3.22.14
Pushed to 16.05.x, for 16.05.07 release