[Cosmo-dev] recurrence modifications and multiple collections

[Jeffrey Harris]

Hi Randy,

> Actually cosmo will only remove that modification from the collection,
> which means if that modification exists in more than one collection you
> have to remove it from all collections in order to fully remove the
> modification.  Does Chandler support modifications that exist in one
> collection, but not another?

Nope, Chandler doesn't support that.

> Actually I think this is right.  If a master event with modifications
> exists in two collections, then in order to remove the event with
> modifications from one collection, a delete for the master and a delete
> for each modification has to be sent.  This tells cosmo to remove the
> master and modifications from the collection. Otherwise you end up with
> the modifications in two collections and the master in one, which
> doesn't really make sense.  Maybe cosmo should automatically remove all
> modifications when a master is removed from a collection to prevent
> this.  And it should also interpret a remove modification as "remove
> from all collections" because cosmo can't handle modifications that
> exist in one collection, but not another.

Well, what you're doing now seems consistent and workable, so I don't
think we need to fiddle with it for preview.  Thanks for the clarification.

Sincerely,
Jeffrey