[Design] [Cosmo][Desktop] Making sure the server never ends up with a big pile of untriaged Chandler items

[Morgen Sagen]

On May 30, 2007, at 10:40 PM, Philippe Bossut wrote:

> Mimi Yin wrote:
>> The best proposal we were able to come up with in the meeting was:  
>> Remove the sharing filter options from the Publish dialog (for  
>> Preview) so that users always push triage status to the server  
>> when they publish. However, after they publish, desktop users can  
>> go to the Manage share... dialog to adjust the sharing filters.  
>> This preserves the ability to manipulate sharing filters on the  
>> desktop end, but ensures that the server never gets a big pile of  
>> untriaged items.
> I see 2 problems here:
> 1. it makes sense when sharing with others *not* to share the  
> triage status. I mean, triage is really something that's relevant  
> to my work status (I want to work on this "Now" doesn't mean that  
> everyone has to work on this "Now"... on the contrary, they'll be  
> happy to put that "Later"). So changing the default to always  
> sharing this is somewhat killing the purpose of triage existing at  
> all (in a collaborative environment that is), or limiting it to a  
> sort of global "urgency status" shared by all.
> 2. once I adjust my sharing filters, won't this "big pile of  
> untriaged items" grow all by itself eventually? i.e. aren't we  
> simply delaying the problem? or just making it less likely because  
> not the default behavior?

Ditto what Phillipe said, plus:

Why wouldn't the server know how to triage items?  What will the  
triage status be for items that are created via the Web UI?  Or from  
a CalDAV client?

The server is going to need to be able to support a "big pile" of  
items that all have the same triage status (which seems like it would  
cause the same "clogging up of traffic" for the web client), so how  
is that different than a "big pile" that have no triage status?