|
From the view of the user (not from a technical view)- What are the main differences between searching and filtering data, in order to get specific results? i.e.- in both cases the user is looking for specific data so why should he care which method is used to find it?... would you say these two methods are mostly the same (in the eyes of the user)? If not- when would you use each? |
||||
|
|
|
Very short answer (time pressed!): Filtering takes an existing full list, and removes items based on criteria that match/don't match. Search takes a blank slate and adds to it based on criteria that match/don't match. |
|||
|
|
|
Another take: in most circumstances, particularly when the task is not a known-item query, searchers don't know the precise keywords they need to type in order to acquire their target. So although the mechanism or function they are using is a "search", actually they want to explore and browse the information space. Jared Spool and UIE have explored this topic Filtering - if we are talking about iterative, faceted search - allows users to enter a vague term and then iteratively refine it. This is the "Paradox of the active user" in action. These "active users" don't have time to learn about the information space so they go ahead and search anyway. When the results are received for that search, they then start learning about the information space and refine/restart their query. The design principle of timely feedback works all the way through this experience, so "Spotlight-style" results all go towards helping make the query reflective of the information space and of the person's original intention. For a good example of both these techniques at work, try to find yourself a new TV at John Lewis or any number of e-commerce sites. |
|||
|
|
|
I like Alastair's answer, but to add a bit to it. Filter: Only filters based on a single criteria, such as the name and leaves the ordering intact. Search: Applies all metadata and complex algorithms to the search such as boosting. Search is more complex, because you have to rank the best results first. (example: Google) Filtering doesn't care about that. |
|||||||
|
|
Data filtering has been around in spreadsheet and database software for decades; filtering is generally where you start with a full dataset and then filter it down to relevant results. The filter criteria should correlate with the data model. As far as the form goes, yes a keyword-only filter is essentially the same as a search, and an advanced search could be similar to a filter form ... but I guess it just comes down to where you're starting from - are you starting with results and then subtracting, or starting with no results and then displaying only relevant ones? |
|||
|
|
|
Interesting question. IMO - filter subsets data usually on the screen whereas search is used to find data from a larger universe. I guess even without thinking of the size of the universe. One retrieves a subset based on criteria, whereas the other returns results based on matches. |
|||
|
|
|
You search when you know what you want to find. Search is active You filter when you don't know what you don't know about what you are searching for. Filtering is passive I explore it a little bit in my essay Slaves of the feed - This is not the real time we've been looking for |
|||
|
|
|
I guess filtering provides a specific impression whereas searching provides a generic impression. What I mean by impression is the human impression a user gets while performing the said action. For example: lets say to pick an apple from a basket full of fruits and vegetables;
|
|||
|
|
|
I think we can apply the law of Pareto (20/80) on fields filters and Search:
regards, |
|||||
|
