r7 - 09 Feb 2007 - 16:16:05 - MimiYinYou are here: OSAF >  Journal Web  >  MimiYin > TestScenarios

Major workflow areas

Sharing

  • Conflict management UI:
    • ConflictResolution
    • http://lists.osafoundation.org/pipermail/design/2006-December/006003.html

Communications and Edit/Update Workflows

  • Send / Edit / Update - (Email text + .ics attachment) + (Chandler attributes)
    • Triage status is not shared via Email
  • Forward - (Email text + un-parsed .ics attachement)
  • Reply, Reply All - Just text in an email

  • From is de-coupled from the Sender
    • Supports delegation: e.g. Esther can send an

  • Item byline in the Dashboard: displays the last thing to happen in an item's history

  • Communications status column in the Dashboard
    • Read / Unread / Needs reply
    • Draft / Queued / Sent-Received / Error
    • First time / Update
    • Inbound / Outbound

  • Who column in the Dashboard
    • Created by
    • Edited by
    • From (From-ness overrides To-ness)
    • To
    • Updated by

Triage Workflows

  • Explicitly mark triage status in the Dashboard or Mark-up bar and Purge workflow
  • Auto-triage Scenarios
    • Creating new items
    • Adding and Changing Alarms to items
    • Adding and Changing event date/times
    • Time passing and Alarms and Event date/times firing
    • Items with Errors
  • Recurring events
    • 1 instance per Triage status section (as applicable)
    • Instances with 'exceptions' also appear in their own row
    • Any 'extra' instances that are created are 'pruned' whenever possible
  • Shared triage status
    • Real triage status versus Section triage status
    • Updates on items that are shared via collections that share Triage status appear at the top of the NOW section for sharees, however, appearing at the top of the NOW section does NOT change the Real triage status on the item.

Stamping

  • Addressing stamp
    • Individual instances and This and Future instances of a recurrence series CANNOT be addressed. The addressing fields ALWAYS APPLY TO THE ENTIRE SERIES.
  • Task stamp
    • Task stamp in the Dashboard
    • Individual instances and This and Future instances of a recurrence series can be stamped as a Task
  • Calendar stamp
    • Reminder and Date columns in the Dashboard work in tandem
    • Date column always displays a Tickler or Event date if there is one
    • If an item has both Tickler and Event dates, the Date column displays the NEXT important date
    • If there is NO NEXT IMPORTANT DATE, the Date column displays the most recent important date
    • If an item has neither Tickler nor Event dates, the Date column displays the most recent date from the following pool of dates:
      • Date created
      • Date edited
      • Date sent/received

Calendaring

  • Recurring events: http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/Dashboard-0.7.html
    • Triage status and the Dashboard: 1 occurrence per Triage status section as applicable + all occurrences with exceptions
    • Communications / Edit / Update:
      • Addressing stamp always applies to the entire series.
      • The entire series is always sent/received.
    • Communications status: Read, Unread, Needs reply: Applies to the entire series.

  • TimezonesTestScenarios
    • Prompt users when subscribing to shares with timezones to turn on time zone support
    • Prompt users when sharing collections to turn on time zone support

Managing collections

* Navigating between App areas and collections * In and Out are defined by whether any of the user's email addresses appear in the TO/CC/BCC or FROM/SENDER fields. In and Out can have inclusions and exclusions. * Mine versus Not-Mine * Overlays and Navigation * Trash / Deletion / Remove

Setting up and managing sharing

  • Setting up your Cosmo account
  • Setting up your Outbound Email account
  • Setting up your Inbound IMAP account (with special Chandler headers and/or IMAP folders)
  • Setting up your Inbound POP account
  • New and improved Collection menu, completely new Share menu
  • No more partial shares! All app areas are shared for all shared collections.
  • More attributes can be opted in/out of the sharing cloud:
    • Triage status
    • Alarms
    • Event status
    • If users shares Triage status, they have to share Alarms as well

Creating new items

  • Quick item entry
  • New item menu and corresponding keyboard shortcut (Cmd/Ctrl - N) is now context sensitive, by App area

UI Elements

  • Detail view
    • Mark-up bar
    • Byline
  • Dashboard / Table
  • Sidebar
  • Menus/Dialogs/Keyboard shortcuts


Below is a Usage Scenario Perspective on the Workflows outlined above

Processing Information: Dashboard & Stamping

  • Getting email into Chandler - Email spec: http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/Email-0.7.html
  • Creating new items in Chandler - QuickItemEntryProposal
  • Triaging items
  • Tickling items
  • Putting items on the Calendar
    • On the calendar canvas
    • From the Dashboard using the Date/time fields in the Detail View: ExpandoDateTimeFields
  • Putting items on the Task list
  • Addressing items: ModalAddressingFields
    • Addressing an item to attach people to the item
    • Addressing an item to send an item
    • Sending addressed items
      • Checking for correctly formatted email addresses
      • Error notifications
      • Canceling Send?
  • Marking items as Needs reply
  • Adding more details to an item

Ad-hoc Collaboration: Collaborating on individual items with Edit/Update

  • Stamping Spec: http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/Stamping-0.7.html
  • Sending out a notification
  • Collaborating on a draft
  • Call for feedback

Routine Collaboration: Collaborating on collections with Sharing

Usage Scenarios

  • Managing day-to-day home life
  • Helping to manage somebody else's life
  • Planning an event together

Workflows

  • Sharing a collection
  • Sharees subscribing to the collection via Cosmo UI
    • http://lists.osafoundation.org/pipermail/design/2006-December/005984.html
    • Spec forthcoming
  • Scheduling appointments
  • Scheduling meetings
  • Recording personal commitments on the calendar
  • Collaborating on a task list: http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/Dashboard-0.7.html
    • Triaging tasks
    • Assigning tasks to each other
    • Updating status on tasks
    • Scheduling tasks
  • Keeping track of communications that need to sent out / responded to / followed-up on

We're NOT supporting the following workflows:

  • Managing information / research for projects
  • Keeping track of people (ie. RSVPs, dietary restrictions, special needs, relationship, call log, presents, thank yous, etc)

Data migration and Setting up Accounts and Preferences

  • Setting up a sharing account

  • Email: http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/Email-0.7.html
  • Setting up email to send
  • Setting up email to receive
    • Emails with special Chandler headers
    • Special Chandler IMAP folders

  • Timezones
    • Turning on timezones, unprompted
    • Turning on timezones, prompted: http://lists.osafoundation.org/pipermail/design/2006-December/005866.html
      • Prompting users to turn on timezones when they are subscribing to a share with timezone metadata
      • Prompting users to turn on timezones when they are sharing

Tricky UI elements to look out for:

  • Anything to do with Recurrence: DashboardSharingCommunicationsRecurrence
    • Display in the Dashboard
    • Marking Triage status
    • Marking Read/Unread/Needs reply status
      • For Preview: Read/Unread/Needs reply status applies to all items in the series
      • Ideal design: Read/Unread/Needs reply status applies to all items in the series that look exactly like the recurrence instance that is being marked
    • Addressing, Sending, Editing and Updating
  • Conflict notifications

Byline in the Detail View

  • Created by
  • Edited by
  • Send as
  • Sent as
  • Updated by

Dashboard columns in the Summary pane

  • Communications status
  • Who column
  • Date column
  • Relationship between Date column and Reminder column
  • Sort order of the Triage status column

  • Triage and Purge workflow

Documentation

  • StampingStoryboards
  • Stamping Spec: http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/Stamping-0.7.html
  • Dashboard Spec: http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/Dashboard-0.7.html
  • Email Spec: http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/Email-0.7.html

-- MimiYin - 15 Dec 2006

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r7 < r6 < r5 < r4 < r3 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.