We had a productive, albeit slightly confused meeting today :o) and
came away with some solid next actions for implementing 'smarter'
auto-triaging in Chandler. To summarize the decisions that we made:
Rules for Auto-triaging based on User actions:
1. New items have their 'Color triage status' set to NOW and are
placed in the NOW section.
2. New items have their 'Has been explicitly triaged by user' flag
set to False.
3. When/if an user sets an alarm date/time or event date/time on the
item, the item is auto-triaged according to the IMPORTANT DATE on
that item (using the same logic we use today to figure out which date
to display in the Date column).
4. When/if an user explicitly sets triage status on an item, auto-
triaging based on the user setting alarm and event date/times stops.
(More on what 'explicitly sets triage status' means below.)
For Preview:
1. We are NOT going to attempt to treat triaging in the Calendar
view context differently from triaging in the Dashboard view. This
essentially translates into: ignore the 'Calendar' column in the table.
2. We are NOT going to auto-triage events to DONE when the end
date/time passes.
3. We are NOT going to support user preferences for deciding
whether you want to see newly created items and recently edited items
in the NOW section of the Dashboard view on any given collection.
4. We are NOT going to try and figure out a way to re-activate
auto-triaging based on alarm and event dates set by the user, once
the user has explicitly set triage status on an item.
We ARE going to:
1. Attempt to auto-triage items based on the alarm and event date/
time information users set on the item; EXCEPT WHEN
2. Users explicitly triage an item by either clicking on the
triage status button in the Dashboard view or in the markup bar of
the Detail view; OR
3. Items are 'tickled' into the NOW section because of an alarm
date and/or event date.
NEXT ACTION: Jeffrey and Bryan need to go away and figure out how to
define #2 and 3.
In Sharing-related scenarios:
1. Newly created, recently edited, updated items and items with
errors will all be placed at the top of the NOW section. The Color
Triage status will be set by whatever auto-triaging rules apply.
NEXT ACTION: Bryan Stearns needs to investigate sharing the right
triage status. Currently we share the 'Section triage status'. We
should probably be sharing the 'Color triage status'.
*NEXT ACTION:* PPD update Dashboard spec.
Am I missing anything? This info has also been added to the wiki
proposal: http://wiki.osafoundation.org/Journal/AutotriageRules
Mimi
On Jan 29, 2007, at 8:59 AM, Mimi Yin wrote:
Tuesday Jan 30 from 2:30-4PM PST in Whoville.
I will be broadcasting my drawing tablet on channel 0.
Sheila, can we use your bridge?
http://wiki.osafoundation.org/Journal/AutotriageRules
As per Philippe's suggestion on: https://bugzilla.osafoundation.org/
show_bug.cgi?id=7899, I have put together a proposal in the form of
a table of all the various ways in which items in Chandler can be
auto-triaged.
There are a few open issues to reckon with. I don't think we need
to come to a consensus on the design list about the 'right
behavior' for Preview. We should just pick what is most expedient
to implement at this point and rely on dogfood feedback to navigate
our way to the right design solution.
The proposal attempts to cover the myriad cases for auto-triaging
and what to do for both the 'color' or 'unpurged' triage status AND
the 'section' triage status. There is also a column for how to set
the 'section' triage status if the triage status is set in the
detail view when the user is in the Calendar view / App area.
There is also a workflow write-up for how to auto-triage newly
created items, as well as a section dedicated to recurrence issues
(Jeffrey please review that section).
Thanks!
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
