Unified Search 3

Unified Search

Unified Search

What Problem Does This Solve?

Single line search aggregates results from multiple different data sources, presenting a single disambiguated set of search results.

When to Use This Pattern

As data (e.g. weather information, social feeds, deals, coupons, etc.) becomes more distributed across providers and services a user should be able to enter a keyword or phrase without having to know where the results come from.

What’s the Solution?

Provide the capability to import and manage content from different sources that can be searched through a single search field. Aggregate and disambiguate the results from different content sources into a single set of search results.

Why Use This Pattern?

The key to a great search experience is to present a single set of results that is free of any duplicates but gives the user easy access to the diverse information contained by the different sources of data.

Special Considerations

It is important to disambiguate the results in a meaningful and logical way that includes removing potential duplicates, weighting results by relevance or importance, indicating the source or nature of the result, and removing excess results completely.
Not every result has a spatial component (geometry) attached to it and needs to be related to an extent or feature somehow else, e.g. liechtenstein searching for the name of a person in a directory should pull up the employee but clicking on this person needs to be related to the actual office location of this employee which requires a relation and subsequent query.

Related Patterns


Unified Search

Unified Search

Unified Search (maps.google.com)

Unified Search (maps.google.com)

Unified Search (GIS Day App)

Unified Search (GIS Day App)

References and further reading

. .

3 thoughts on “Unified Search

  1. Pingback: Focal Point ← Map UI Patterns

  2. Pingback: Route Positioning ← Map UI Patterns

  3. Pingback: Data-Ink Ratio ← Map UI Patterns

Leave a Reply