[Cosmo-dev] Re: etag change

[Morgen Sagen]

On Apr 19, 2007, at 9:32 PM, Brian Moseley wrote:

> On 4/19/07, Morgen Sagen <morgen at osafoundation.org> wrote:
>
>> Well, I have always been assuming that it will Chandler that migrates
>> a collection from dav to mc (since only Chandler understands the
>> existing XML): in other words:
>>
>> 1. Chandler subscribes to dav collection,
>> 2. Chandler unsubscribes from dav collection (leaving the collection
>> in the local Chandler repository),
>> 3. Chandler publishes collection over mc
>>
>> Step 2 could be an *unpublish* if the user is daring.  :-)
>>
>> Is there another way to migrate to morsecode?
>
> not that i know of. this is how i understood dav->mc migration to work
> too. however, might there not be a step 1.5 where the user makes local
> changes in chandler that aren't synced to the server? wouldn't those
> get overwritten on the desktop if the user tried to sync them to the
> server before doing step 2?

Let's expand the steps a bit:

1. Chandler user has been syncing with osaf.us running Cosmo 0.6.0.1
2. Chandler user should sync all changes to osaf.us, just prior to  
Cosmo 0.6.1 upgrade of osaf.us; an announcement should go out telling  
people not to make local changes until after they have performed step #4
3. osaf.us gets upgraded from 0.6.0.1 to 0.6.1
4. Chandler user syncs, unfortunately pulling down every item, but if  
they were careful not to make local changes between #2 and #4, they  
won't lose anything
5. Chandler user unsubscribes (or unpublishes if daring) from dav  
collection (leaving the collection in the local Chandler repository)
6. Chandler user sets up "Chandler Hub Sharing" (aka morsecode)  
account in their Accounts dialog
7. Chandler user republishes collection using morsecode account, gets  
back new "pim" urls to hand out to people

How's that sound?

~morgen