As a developer, it’s often hard to get out of a mindset where your response of “It’s simple silly, you just search for a portion of the word, not the whole word.” to the question of a particular search not providing a user’s expected results.

This type of response may come from a user when they mention they know the user “Petrowsky” is in the database but it doesn’t come across verbally that they’re really searching for “Petrowski” - which obviously doesn’t match the version ending in a “y” instead of an “i”.

This level of understanding, that you can simply enter “petrow” in order to search for both variations, isn’t inherently obvious to all users. So the next best solution is to provide some type of filtering process. Something where the user can narrow down their list of choices to find out where the disconnect is happening.

In this video, we look at a sublimely simple script which makes this type of task an utter piece-of-cake. If you’ve got users who need to make routine selections on filtered subsets of data then the knowledge contained within this video will pay dividends beyond just knowing how to filter based on an alphabet letter!