Migration data in searchable dropdowns
Morgan
Harsh and I spoke about the concerns around the number of records being migrated and its effect on the performance of searchable dropdowns.
We have agreed that for searchable dropdowns across the admin side the search will only be performed once the user has input 3 characters. This means the matching results will be presented immediately after the user types 3 characters rather than a delay occurring due to the load of all records (in some cases 6000+) as the user types the first few characters.
This suggestion was acceptable to me but wanted to confirm on your end.
Mel
3 characters seems like a lot. This would be a problem for entries that only have two character. For example, we have a handful of people that have two character surnames:
What would the performance results be if we limited the search to 2 characters?
Also, doesn't this seems out of sync with market for searchable dropdowns? These days, I find it rare to have character limits before a search is performed, and other sites don't seem to have performance issues. What are they doing that we're not?
Finally, by imposing a character limit, is that going inhibit the user's ability to select and browse for the relevant result without entering any characters in the field? If that's the case, I don't want a character limit, and perhaps we need to investigate a loading system within the menus (or some other solution) to ensure the user can both search and browse entries in the list without encountering any noticeable loading issues.
Note this issue is very important to resolve, because we'll need to ensure we have a very effective searchable dropdown for the Legal Analytics reporting tools.
Thanks,
Morgan
Further to the discussion above, I'm adding this to the agenda for discussion during Thursday's meeting, but could you please review the above and put some thought into some proposed solutions.
Note that this should consider the changes I have requested for dropdown menus here:
Thanks,
Morgan
This is the closest example I have found so far that demonstrates the desired behaviour.
Perhaps this example will help with our discussion.
I found this here: https://semantic-ui.com/modules/dropdown.html under the heading 'Multiple Search Selection'
Mel
Yes, that's what I'm looking for. I think there might be slightly different behaviour for non-multi search dropdowns as well, which I posted in the to-do above.
Morgan
Morgan