Goals and Objectives

• Get a first iteration of the dashboard in front of users so we can get feedback asap.

Summary of Changes

• User problems addressed by changes:
  • Getting information out of my face so that I can maintain focus on the task(s) at hand (without losing track of information). This includes Triage and Tickling.
  • Processing information and making sure it ends up in the right context, where context is defined as where something needs to be so that I trip over the right thing at the right time. (aka Stamping and Tickling).
  • Organizing information so that I can find it later (aka Tagging, Labeling, filing and linking).

• Things to do first:
  • Chandler name of My collections to Dashboard (also listed in sidebar spec)
  • Section by Triage status
  • Set Triage status in the detail view
  • Display Triage status with color and text in the table
  • Display proper triage status icon in the column header
  • Set custom-date Ticklers in the detail view
  • Display custom-date Tickler icon in the Reminder column
  • Auto-Triage Items to NOW (e.g. Newly created Items, when Ticklers and Event dates go off)
  • Sort Triage sections according to spec
  • Sort on the Task, Communications status and Reminder columns
  • Sub-sort on Triage status
  • Proper formatting and display of dates in the date column

• Things to do later:
  • Set Triage status in the table
  • Add Items to the Task list in the Task column
  • Add the communication status column
  • Mark Items as Read, Needs reply and Unread in the Communications status column
  • Activate custom-date Ticklers in the Reminder column
  • Allow users to explicit order Items in each Triage section
  • Display basic communication states: In v. Out v. Neither, Error.
  • Display the right attribute in the Who column for the basic states that have been implemented (CR, ED, FR, TO)
  • Display the right attribute in the Date column.

• Deferred to Alpha 5 if necessary:
  • Display icons for the remaining communications states in the table: Draft, Queued, Updated
  • Click in the Task, Communication status, Reminder or Triage status columns to apply a single setting to all selected Items
  • Edit dates in the Date column
  • Manual 'Purge' workflow to allow users to control when the Dashboard re-sorts

Risks and Dependencies

• Risk: The feature list for Alpha4 is very long - we may not have time to do all the work.
  • Proposal: Stage the features in order of priority so that only some of the work needs to get done and we can still have something valuable to put in front of users.
• Risk: We may not get the dashboard quite right Alpha4.
  • Proposal: This is why we need to not slip Alpha4 and get a dashboard out ASAP to inform interations for Alpha5. This is another motivation for staging this.
• Risk: Some dashboard work has dependencies on the stamping work.
  • Proposal: Minimize the dependencies and make the dashboard workable as stamping progresses. ie: Not expect to have all the communication states in place right away.
• Risk: Some reliance on wxwidgets work - clickable widgets in the table view.
  • Proposal: Work closely with engineering on options. Consider temporary widgets like a drop-down which allows us to have the base functionality.
• Risk: All the communication stuff really relies upon actually being able to receive emails about items ie: notification about an event or task. We haven't yet figured out how we will solve this in the short-term and long term.
  • Proposal: All the work in the first bin is really independent of email. This can make the dashboard experiemental for shared tasks/events and individual items. By staging we have reduced the dependencies.

• DV_Triage_status_widget.png:
  

• Alarm_Notes.png:
  

• Alpha4b_Dashboard.png:
  

• Alpha4c_Dashboard.png:
  

-- SheilaMooney - 22 Jun 2006 * Alpha4a_Dashboard.png: