[Cosmo-dev] recurrence and triage status

Randy Letness randy at osafoundation.org
Tue Jul 24 12:01:11 PDT 2007


Jeffrey Harris wrote:
> I pulled my hair out for a while trying to figure out a way to fix this.
>  It would be easy to fix with a Morse Code schema change, but it really
> seems late for that.
>
>   

I'm trying to understand this issue.   So is this a problem because the 
server doesn't store anything about occurrences, just modifications?  So 
when you mark an occurrence as "done", nothing really gets stored on the 
server because its just an occurrence.  But chandler does keep track of 
the "done" for an occurrence I assume?

> We could fix step 3. above by storing the date of the most recent DONE
> occurrence in the master's triage status field.  Then it would be clear
> (after a bit of calculation) whether a non-existent occurrence on the
> server was actually an inbound change from NOW to DONE, or if the event
> in question ought to be triaged NOW.
>   

Ok I'm lost again.  But, I think cosmo and cosmo ui don't use 
triageStatus on the master event so if you want to use it to represent 
something else that seems fine to me.  It just needs to be documented.

-Randy


More information about the cosmo-dev mailing list