https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28726
--- Comment #31 from Katrin Fischer <[email protected]> --- (In reply to Michael Hafen from comment #30) > Making it a free text field doesn't work for me. In my opinion having a > free text input doesn't work well for a filter field on a search page; > especially in my case where the librarians don't control that field, it's > controlled by LDAP. > > Katrin mentioned the Patron Statistics Wizard. Looking at that, what's done > for the sort2 column is to pull distinct values limited to 200. That would > work for me, that should be well under what my librarians would encounter in > that field. > > Would doing that instead be acceptable? It won't work for any library that stored an identifier or unique value in there that has more than 200 patrons. They would see an incomplete pull down. Also: a 200 entry pull down is not really nice to use? Actually I was not aware the wizard did that :( we should fix it as well. I'll claim the patron form then as the example and the batch patron modification templates (sorry). Why will a free text not work? If they have no idea what they are looking for, will also not be very helpful? I think it's a specific use case we are dealing with here that I'd like to understand better. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
