Differences between revisions 9 and 10
Revision 9 as of 2010-10-25 02:42:10
Size: 6342
Editor: shoobe01
Comment:
Revision 10 as of 2010-10-25 02:42:23
Size: 6344
Editor: shoobe01
Comment:
Deletions are marked like this. Additions are marked like this.
Line 44: Line 44:
{{{#!wiki #f00/solid {{{#!wiki Yellow/solid

Problem

Explicitly submitted user data, or IMPLICIT???, must display the resulting narrowed dataset in a meaningful manner.

Fisheye List

Solution

The displayed page will show Returned Results in an ordered list, or displayed over other contextually relevant information (such as a map or graph).

Variations

The most common type of Returned Results is a simple Vertical List. Additional information, such as the order of results, relevance and domain. Add ons may also be used when relevant, such as Fisheye List or Thumbnail List.

The information may also be presented contextually, as an overlay or add-on to other information visualizations. The results themselves will be points, and may appear over maps, graphs, charts and similar visualizations.

Multiple types of results may be displayed on one page, as overlays, or as easily-switchable alternative displays. For example, if a visualization overlay is used, then the results may be more useful for some users as a list.

In certain cases, prioritized information may be presented within the same display type. This may be customized information (e.g. stock information when searching for a company), or paid placement results.

Even if multiple information types are offered The most relevant display type should be presented by default.

Interaction Details

Typically, items in the Returned Results list will need to be selected, either as choices for another process, in order to view more details, or to start a process (such as navigating to the selection).

The selection mechanism may be the entire item, or a specific portion of the item display area. Be sure to use the correct type of selection and selection indicator for the process; choice selection will be different from viewing details.

Pagination or Position Within controls and indicators should always be used for list-type displays, and may be relevant for contextual display.

Modifications to the parameters that resulted in the display of results (such as a text search string), should be easily accessible. They may be on the screen, available as options, or available for direct modification by going "back" to the previous screen. All parameters used, even those that were not directly selected by the user on the initial display of results, should be available for modification.

Presentation Details

Display the reason the results have been shown. If a search, for example, the search terms must be displayed.

Number (or letter) the results, so an order is clear. For devices with support for Accesskeys, make sure the numbers cannot be confused with the accesskey labels. Color, alignment and treatment (e.g. light blue and italics) are generally sufficient.

When space is available, and the relevance parameters can be clearly communicated, the relevance may be displayed as additional information with each result. This may be a relevance factor (a percentage is typical), by listing terms that are relevant, or by listing a summary of the information that is most relevant to the result; this does not count the implicit relevance of display methods such as position on a map.

If the domain is not entirely restrictive (searching only internal documents) or entirely non-restrictive (the whole internet is available) then an indicator of some sort must be placed by each result. Types of documents, when not all the same, should also be displayed, so the user is aware before they attempt to view a movie or download a file.

When information is displayed contextually, it should appear as a "poinpoint" indicator, with a pointer indicating the precise location in the contextual system, and a head which may be selected for information or contain a label of the item.

DISCUSS: This "Pinpoint" could possibly be a widget, but is almost entirely used for this exact display item. I believe that makes it too specialized to be a general widget, but am open to discussing it.

other types of display, pinpoint-type results

Paid placement results must be differentiated from the other results. They should not, for example, be numbered with the other results, or counted as a result in the Pagination or Position Within information.

Availability of the item for selection must be indicated. Whether the entire displayed area for the item is selectable, or only certain portions, an indication of selectability should be present. Each type must be differentiated, so links to view further details appear as links, and selection for a process appears as a choice.

Antipatterns

Avoid error conditions for valid entry of information. Displaying errors for no results will dissatisfy the user, so solve the problem for them. Options include

  • Expand the search parameters; for local search, change the distance until results appear.
  • Correct mis-spellings, but not unless there are few or no results.
  • Use common, similar searches to replace results
  • When no results must be displayed, make it clear there are none returned, and

In all cases, inform the user on the results display of the changes, and offer an easy method to see the original results.

Use paid placement very carefully. Advertising revenue is a way of life for many products, but make sure items within the results list are at least slightly related to the original intent of the returned results list. Do not use paid placement "results" as a replacement for no returned results. When users figure this out, they will have less faith in all results.

Avoid making parameters too difficult to discover, understand or modify. Try to explicitly state all parameters, even if they are available via other interfaces; e.g. results on a map may have the radius constrained by the zoom level of the map, but this may not be clear unless also available as a search term, or explicitly stated on the results display.

Examples

DRAW: List, as in old Sprint, ordered list

DRAW: List, as in old Sprint, with

DRAW: G-maps style presentation of pushpin-points on a field.

DRAW: Pinpoint where a LINE is the pointer for a graph, and a bubble appears off that.

Returned Results (last edited 2011-07-31 20:12:47 by shoobe01)