Hi,
I'm not convinced we should make a difference between Email and Sharing
as far as notifications is concerned, so no "N" or "n" notification:
- item updates or creations on a share are as important than Email (or I
wouldn't bother subscribing to the share)
- I'm afraid that users will send an email "just to make sure" the
notification is received, drowning the recipient a little bit more in
incoming flow
I think that, ideally, we'd like to wean people of using email for
everything but rather have email be one tool among others. If we do
sharing of tasks and events correctly, I can imagine cases where I would
hardly send/receive emails, relying instead on the notification
mechanism so that whoever needs to know will know. Somewhere, I think an
RSS-like workflow is the best one. If the UI could visually discriminate
between new and updated items, that would be perfect.
Also, having things appearing automatically in NOW is somewhat counter
intuitive to me. NOW is a triaged section of carefully selection stuff I
want to give my immediate attention. Incoming stuff (emails,
notifications, etc...) are not triaged yet and should be parked
somewhere else, in a "non-triaged" section.
Cheers,
- Philippe
Mimi Yin wrote:
Sheila has asked me to write a summary of how the Dashboard design
we're planning on implementing in the Alpha 3/4 timeframe will support
notifications use cases.
My question to the list is:
Does the Dashboard design satisfy basic use cases for notifications?
Are there are other scenarios we need to consider that fall outside of
the realm of the Dashboard workflows? (e.g. I need to be able to see
sharing notifications from outside of Chandler, in my email Inbox or
my RSS reader).
*Support for Notifications in the Dashboard Design*
===
For each collection in the sidebar, users will be able to see the
following in the summary table view:
Unread items marked with an Unread icon in the Communications Stamp
column.
Unread items are defined as:
+ Newly received items via Email, aka capital-N notifications.
+ Newly created items via Sharing, aka small-n notifications.
+ Recently edited items via 'Updates to emailed items', aka capital-N
notifications.
+ Recently edited items via Sharing, aka small-n notifications
New Emails and 'Updates to emailed items' show up automatically in the
NOW section of each collection.
Newly created/edited items that haven't been Emailed don't show up
automatically in the NOW section of each collection.
To view all Unread items in each collection, regardless of whether
they were Emailed or not, sort the table by the Communications column.
All Unread items will be grouped together at the top/bottom depending
on sort order.
To view all Unread items across all of your MINE collections, sort on
the Communications column in the 'All' collection.
In Alpha 3 there will also be a separate log that users can access
from the Test menu that displays all changes to shared collections in
a unified log list.
This can eventually turn into a more polished Activity Viewer that
logs all user interactions (sharing-related or otherwise).
In the Beta timeframe, a nice to have for the log list is the ability
to click on a log item and get taken to the item in the Chandler UI in
the appropriate view.
Thx, 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
