Bug 30980 - Make patron selection more consistent
Summary: Make patron selection more consistent
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Staff interface (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 30578
Blocks:
  Show dependency treegraph
 
Reported: 2022-06-16 15:11 UTC by Martin Renvoize
Modified: 2022-07-15 20:04 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Renvoize 2022-06-16 15:11:24 UTC
We have a number of places where one can select a patron as part of a process... but these selects vary wildly.. some are 'autocomplete', others allow for full search.

I proposed using select2 consistently for the forms one's when reviewing bug 30578.

It's worth investigating.
Comment 1 Jonathan Druart 2022-06-17 07:08:14 UTC
But then we will lose the ability to use the different filters?
Comment 2 Martin Renvoize 2022-06-29 16:36:51 UTC
So go the other way and for all forms ensure we fall through to a full search window if autocomplete isn't enough ;P

The point is I'd like to see some consistency around this.
Comment 3 Jonathan Druart 2022-07-04 12:23:25 UTC
I don't know, I guess we should ask end users.

Adding the complete forms will add more clicks (open popup, search, select).
Comment 4 Katrin Fischer 2022-07-15 18:47:48 UTC
I like the idea of auto-complete in combination with opening a full search if needed. But we might need to try it out to see if that works. I know that there have been complaints about auto-complete from very big library systems with a lot of similar user  names as the pull downs usually limit to x visible entries.
Comment 5 Martin Renvoize 2022-07-15 20:04:14 UTC
Limiting pull downs would be a thing of the past if we use infinite scrolling in select2 which I've trialed in a few places.

It's the filtering down further after doing an initial search which isn't so well handled.  Must admit, I've never seen the need in real life myself, but Jonathan assures me theres a real need for these advanced secondary filters.