Hi Brian,

Thanks for bringing these scenarios to light. I have a few question in-line...

On Feb 9, 2007, at 6:33 PM, Brian Moseley wrote:

there are often times that cosmo creates items on its own rather than
having them synced up from chandler:

* an event is uploaded with caldav

To a shared collection in Chandler?

* 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.

* 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.


when this happens, there are several attributes that are not set:
triage status, triage status changed, last modified by, created on.

should any of these attributes be set by cosmo when creating items? if
so, what rules do we use to set them? when is it important that we
make this happen - 0.6.1 (uses new sharing protocol along with
chandler a5), preview, post-preview?

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?

Obviously, sometimes the created by...will be anonymous. Although we discussed having an editable field to allow CC's to identify themselves.

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

Reply via email to