Thoughts on learning and work

Day 9 of 180 Days of Data Viz Learning #jfdi

Advertisements

I’m doing some form of data visualization learning for 180 days straight because I need to #JFDI.  See post explaining how and why I’m doing this.

Visualization Worked On or Created: 

N/A Today  – > Having my last Saturday in LA and good-bye festivities.  Also placing priority on finishing Scott Murray, Treehouse, and Udacity tutorials so I’ve had enough repetition practice for application before I move next week/start my new job.

Decomposition of a Visualization:

The Global Extremes of Population Density

Code Learning:

Udacity Problem Set One Finished – On section 2a Design Principles

Three Takeaways:

Treehouse Using Time Scales in D3.js

Three Takeaways

Reading and Learning Data Visualization Theoretically/Critically:

The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations.Ben Shneiderman (PDF) from 7 Classic Foundational Vis Papers

Three Takeaways:

  • A useful starting point for designing advanced graphical user interfaces is the Visual InformationSeeking Mantra: Overview first, zoom and filter, then details-on-demand. In all seven data types (1-, 2- , 3-dimensional data, temporal and multi-dimensional data, and tree and network data) the items have attributes and a basic search task is to select all items that satisfy values of a set of attributes.
    • Overview : Gain an overview of the entire collection.
      Zoom : Zoom in on items of interest
      Filter: filter out uninteresting items.
      Details-on-demand: Select an item or group and get details when needed.
      Relate: View relationships among items.
      History: Keep a history of actions to support undo, replay, and progressive refinement.
      Extract: Allow extraction of sub-collections and of the query parameters.
  • Network: sometimes relationships among items cannot be conveniently captured with a tree structure and it is useful to have items linked to an arbitrary number of other items. While many special cases of networks exist (acyclic, lattices, rooted vs. un-rooted, directed vs. undirected) it seems convenient to consider them all as one data type. In addition to the basic tasks applied to items and links, network users often want to know about shortest or least costly paths connecting two items or traversing the entire network. Interface representations include a node and link diagram, and a square matrix of the items with the value of a link attribute in the row and column representing a link
  • History : Keep a history of actions to support undo, replay, and progressive refinement. It is rare that a single user action produces the desired outcome. Information exploration is inherently a process with many steps, so keeping the history of actions and allowing users to retrace their steps is important. However, most prototypes fail to deal with this requirement. Maybe they are reflecting the current state of graphic user interfaces, but designers would be better to follow information retrieval systems which typically preserve the sequence of searches so that they can be combined or refined.
Advertisements