As discussed in Marseille (Hackfest 2024) we provide a patch for item seach using select2. To test: - Apply patch - check item search form and search for - Home library - Current library - Shelving location - Item type - Collection - Status - Lost - Withdrawn - Damaged Search with multiple variations (nothing selected, only one value, multiple values, ...) If no value is selected this means that "All" values are searched - Check that the search is working well - Sign off :-)
What are the advantages of this new approach over the old one?
(In reply to Magnus Enger from comment #1) > What are the advantages of this new approach over the old one? The multiselect option is more intuitive, you can start typing and only relevant values are displayed in the drop down, you have less scrolling,... And all other advantages of select2 :-)
Created attachment 164561 [details] [review] Bug 36545: Use select2 in item search This patch modifies the multi-select fields in the item search to use the select2 framework. To test: 1. Apply patch 2. Go to staff interface -> "Item search" 3. Check item search form and search for - Home library - Current library - Shelving location - Item type - Collection - Status - Lost - Withdrawn - Damaged 4. Search with multiple variations (nothing selected, only one value, multiple values, ...) If no value is selected this means that "All" values are searched 5. Check that the search is working well Sponsored-by: Karlsruhe Institute of Technology (KIT)
Please note that there is a bug in master item search, see bug 36563
Created attachment 164861 [details] [review] Bug 36545: Use select2 in item search This patch modifies the multi-select fields in the item search to use the select2 framework. To test: 1. Apply patch 2. Go to staff interface -> "Item search" 3. Check item search form and search for - Home library - Current library - Shelving location - Item type - Collection - Status - Lost - Withdrawn - Damaged 4. Search with multiple variations (nothing selected, only one value, multiple values, ...) If no value is selected this means that "All" values are searched 5. Check that the search is working well Sponsored-by: Karlsruhe Institute of Technology (KIT) Signed-off-by: Owen Leonard <oleonard@myacpl.org>
Created attachment 164862 [details] [review] Bug 36545: (follow-up) Style tweaks for Select2 multiple fields This patch does some fine-tuning of Select2 style on fields which accept multiple selections. The patch also changes the way the form rows are displayed on this page. I thought that the Select2 fields should be wider to accpet multiple selections without the container wrapping onto another line. The patch also sets the Select2 "closeOnSelect" option to false on this page because I think that makes more sense in a situation where multiple selections might be made. To test, apply the patch and clear your browser cache. - Go to item search in the staff client - Confirm that the form looks good and adjusts well to various browser widths. - Make some selections to confirm that the style of selections looks good and that the dropdown stays open as you make multiple selections.
Created attachment 165018 [details] [review] Bug 36545: Use select2 in item search This patch modifies the multi-select fields in the item search to use the select2 framework. To test: 1. Apply patch 2. Go to staff interface -> "Item search" 3. Check item search form and search for - Home library - Current library - Shelving location - Item type - Collection - Status - Lost - Withdrawn - Damaged 4. Search with multiple variations (nothing selected, only one value, multiple values, ...) If no value is selected this means that "All" values are searched 5. Check that the search is working well Sponsored-by: Karlsruhe Institute of Technology (KIT) Signed-off-by: Owen Leonard <oleonard@myacpl.org> Signed-off-by: Michaela Sieber <michaela.sieber@kit.edu>
Created attachment 165019 [details] [review] Bug 36545: (follow-up) Style tweaks for Select2 multiple fields This patch does some fine-tuning of Select2 style on fields which accept multiple selections. The patch also changes the way the form rows are displayed on this page. I thought that the Select2 fields should be wider to accpet multiple selections without the container wrapping onto another line. The patch also sets the Select2 "closeOnSelect" option to false on this page because I think that makes more sense in a situation where multiple selections might be made. To test, apply the patch and clear your browser cache. - Go to item search in the staff client - Confirm that the form looks good and adjusts well to various browser widths. - Make some selections to confirm that the style of selections looks good and that the dropdown stays open as you make multiple selections. Signed-off-by: Michaela Sieber <michaela.sieber@kit.edu>
Hi Owen, thanks for you style tweaks :-) I like them but I am not sure if everybody is happy with the closeOnSelect: false This means that the dropdown will stay open until the user click somewhere outside the menu. For libraries with only one or few branches this behavior could feel annoying. I would love to read some feedback from libraries around the world :-)
(In reply to Michaela Sieber from comment #9) > This means that the dropdown will stay open until the user click somewhere > outside the menu. > > For libraries with only one or few branches this behavior could feel > annoying. > > I would love to read some feedback from libraries around the world :-) I didn't try it without Owen's patch (I applied the whole thing), but I like how the dropdown behaves. I understand your point, but I think it would be *more* annoying for libraries with many branches if they have to open the dropdown each time to select another branch (it would be twice as many clicks?). What I'm most concerned about is the shift from "All ..." to "empty". I don't want staff to think they have to select all the options to get the equivalent of "All ...". But I guess that's just a thing we'll have to teach and highlight on upgrade, and in the manual.
This is great! It looks so much better - and I really appreciate that it takes less space on the page. Note: like Caroline, I applied the whole thing, with Owen's changes. Wading into the "closeOnSelect" debate... I'm afraid I do not find it intuitive to have to "click out" after making my selection. I would even say that leaving the dropdown open is actually annoying if you want to make a selection for the field just below. For example, I made a selection for Item type and I now want to select some Collections. Because Collection is below Item type, the still open Item type dropdown hides the Collection selection area. So I have to click out before I can get to Collection. If I have to do that for every line it becomes a bit frustrating. I also tried making my selection by starting to type in the word - e.g., "re" to get to Reference more quickly. I was surprised that after I clicked on Reference, "re" was still appearing next to it in the selection box (until I clicked out). Is this normal? It looked a bit weird to me so thought I'd mention it :D
(In reply to Aude Charillon from comment #11) > I would even say that leaving the dropdown open is actually annoying if you > want to make a selection for the field just below. For example, I made a > selection for Item type and I now want to select some Collections. Because > Collection is below Item type, the still open Item type dropdown hides the > Collection selection area. So I have to click out before I can get to > Collection. If I have to do that for every line it becomes a bit frustrating. I agree and although we are a library with nearly 200 branches we prefer that the dropdowns close after selection, this is also the behavior we have today in our local patch. @Owen: Could you please remove the "closeOnSelect" I think then it is time for QA :-)