[Design] [Chandler][Cosmo] Cosmo-Chandler Dashboard-Sharing issues

[Mimi Yin]

We had a Design Session today about our plans to incorporate the  
Dashboard into Cosmo for Preview. http://lists.osafoundation.org/ 
pipermail/design/2007-February/006241.html

The prospect of undertaking this work is very exciting as it will  
allow us to demonstrate end-to-end, the collaboration workflows we've  
talked about so much between Chandler users and Casual Collaborators.

As usual, introducing new functionality into the Chandler 'Ecosystem'  
means re-adjusting how things work today to make sure we have  
workflows that actually flow, uninterrupted by usability hiccups. So  
I'm starting a thread to collect issues we need to watch out for. A  
few came out in the meeting, please respond with any others that come  
to mind.

+ If Cosmo doesn't do any auto-triaging on its own, how do we ensure  
that items created in Cosmo don't flood the Dashboards of Chandler  
users with tons of un-triaged items? e.g. 3 Casual Collaborators each  
create 3 new events on a shared calendar. Cosmo doesn't auto-triage  
these events. When Helen the Hub syncs her Chandler, she sees 9 not- 
auto-triaged events in her the NOW section of her Dashboard.

+ If Chandler is somehow able to figure out how to 'ignore' Cosmo's  
not-auto-triaged events and take on the burden of 'auto-triageing'  
the items for Cosmo, how do we ensure that items that were  
'explicitly triaged' by Cosmo users don't get overwritten by over- 
zealous Chandler clients auto-triaging items that shouldn't be auto- 
triaged? (This is only a problem if users are sharing Triage status.  
This is actually a problem for Chandler-to-Chandler sharing as well.)

+ Recurrence: Cosmo will most likely display all instances of a  
recurring event within some arbitrary date range PLUS any modified  
instances.  Is it a problem if Cosmo doesn't do the 'smart pruning  
behavior' Chandler does when displaying recurring events in the  
Dashboard?

+ Is it a problem that Cosmo won't have conflict resolution UI and  
won't have a way to 'quarantine' conflicting pending changes? In  
other words, whatever changes the Cosmo user makes will overwrite  
anything any Chandler user has synced to the server in the meantime.

What else should we look out for?

Mimi