On 2/12/07, Mimi Yin <[EMAIL PROTECTED]> wrote:
On Feb 9, 2007, at 6:33 PM, Brian Moseley wrote:
> * an event is uploaded with caldav To a shared collection in Chandler?
yes.
> * a file is uploaded with webdav Well, I think if we can identify what kind of file it is e.g. an .ics file and it corresponds to a Chandler item Kind, we can manage to figure out how to integrate that into the PIM universe, as we've defined it today. Anything more than that will probably have to wait to post-Preview because we haven't implemented an end-user model for things like spreadsheets, documents, media in Chandler.
based on philippe's earlier comments, i've already made it so that items we don't "understand" don't get synced to chandler. so i guess we don't have to worry about these for now.
> * an event is created in the cosmo ui Both this and the first scenario get to the heart of the open issues around Auto-triaging for Cosmo Dashboard. The thinking right now is that all of this would be taken care of by the Chandler client and that Cosmo would have a default like: All New items are triaged to NOW. Users can explicitly triage them...but if they don't, they will be triaged when synced with a Chandler client by Chandler.
okay.
I think we need all of them. Other than triage status, are there open issues around how to set last modified on and created on? and created/ edited by?
i dunno, haven't been following any of those conversations or reading those specs ;) in particular, i don't know how "triage status changed" is calculated or what a reasonable default should be. also, i don't know what the value of "last modified by" is intended to be. the cosmo account username? what do we do if the item was created with a ticket - just leave that field blank? we can certainly set triage status to NOW and created on to the current timestamp. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
