Data Bite

Best Practices

Overview

Data bites help page users quickly find answers in a single highlighted value.  They provide a way to aggregate data into a single value to focus attention and provide textual context about that value.  When used inside a dashboard, data bites provide calculated summary information that react to dashboard level filtering as an interactive page element.

As a reusable Data Visualization module, these data bites can be reused across a site and updated in a single editor.

Note: This initial release provides a technical foundation for data bites.  This first iteration meets some immediate business needs. However, feedback from our users will determine the functionality for future business needs.  With the foundation established, we will continue to expand the functionality in upcoming releases.

The picture below is an example featuring the elements of a data bite.  Go to examples at the bottom of this page to see some of the additional layout and data configuration options.

Visualization

Screen Capture of the Data Bite Data Visualization Type

1. Calculated Data Display

This visually customizable number reflects the calculated amount of the data selections made in the Visualization Editor.  Style and location variations are available.

2. Message

This information clues the viewer further into the information you’ve showcased.  Context and additional insight can be manually entered in the Editor.

3. Image

An image can be added to the data bite with limited customization.  Any image selected should emphasize the importance or give context for the data.

Usage

Data Bites provide a way to aggregate data into a single value and provide manually created textual context about that value.
Use:
  • When one number represents a significant perspective.
  • To create visual interest within a series of textual elements.

Don’t Use:

  • If isolating one point of data tells an incomplete perspective.
  • If the supporting text needs to be more than three lines.

Other Guidance

  • Dashboard Title:  Good titles are invaluable. Your data bite title should be long enough so that your audience can make sense of the relationships between the elements.   A glance at the title should clearly convey what the data bite contains.
  • Visual Clutter:  If an image or a graphic isn’t needed, select the cleanest layout possible.
  • Data Source:  The data source makes your graphic more reputable. It also allows those who are interested to dig deeper.
  • Data Series:  Follow the best practices provided for each visualization to build the data best supported by each element selected for the dashboard.

Customization

Customizations exist for colors, font, and imagery in the Visualization Editor.  If a series of data bites are presented together, it is recommended to make similar visual selections across the series for coherence.

Most inline styling can be applied to the Title, Message, and Subtext portions of the Data Bite text.

  • photo icon
    Go to ExamplesSee examples on this page that illustrate key options.

Examples

Data Bites are a static data visualization type, unless used in a dashboard.  Each example shows a different way visual information can be arranged through different layouts and data configurations.

Calculated Average

This data bite shows the graphic on left calculating the average of the filtered data.

Max Value

This data bite displays the maximum value of the filtered data inline with the description text.  The image is provided using a linked URL.

Sum of Data

This data bite is calculating the sum of all data in the selected column.  The graphic was set to display above the description.

Calculated Average with Picture

This data bite reflects the calculated average amount displayed above the description text.  The image was added using a URL to set to display to the left .

Data Bites as an Interactive Element using a Dashboard

Data Bites can be added to a dashboard to allow a user to customize the data view.

Page last reviewed: August 18, 2021
Content source: WCMS / Template Team