r1 - 19 Apr 2006 - 16:25:21 - SheilaMooneyYou are here: OSAF >  Journal Web  >  ContributorNotes > SheilaMooneyNotes > DataMigrationBrainstorm20060419

Data Migration Brainstorm

In light of the upcoming alpha 2 release, Katie and Sheila met briefly to discuss the various migration scenarios, issues, assumptions etc.

Notes

Scenarios for Chandler - no sharing

  • Scenario #1: 0.6.1 -> 0.7
  • migrate data
  • calendar data only
  • easy-ish
  • options:
    • install or startup
    • tool

  • Scenario #2: 0.6.1 -> alpha 2
  • path to migrate data
  • calendar data only
  • export all ics files
  • import all ics files
  • kind of ugly

  • Scenario #3: alpha2 -> alpha 3
  • path to migrate
  • only calendar data?
  • more than calendar - we possibly need to suppport invitations, what about tasks
  • easier than manual route
  • potentially a backup and restore all

  • Scenario #4: 0.6.1 -> alpha 3, alpha 4
  • path to migrate
  • probably pretty ugly

  • Scenario #5:
  • alpha 3 -> alpha 4
  • alpha 4 -> 0.7
  • not sure yet

  • Scenario #6: alpha 2 -> alpha 4
  • probably a low priority
  • alpha 2 -> 0.7...also low priority

  • Possible incremental solutions
  • Menuitem to export all and import all
  • Install new version - convert

Sharing scenarios

  • Currently Chandler 0.6 and Chandler 0.6.1 work with Cosmo 0.2.8
  • Cosmo 0.3 will release about the same time as Chandler 0.7alpha2
  • Cosmo demo will be upgraded - 0.6, 0.6.1 and alpha2 should all work with Cosmo 0.3
  • Chandler 0.6 and 0.6.1 users can sync shares with alpha 2 users

  • Migration story for sharers
  • Any shares you have published can be restored
  • Users can resubscribe to shares using previous urls
  • This should work for more than just calendar data

  • If you have a Work collection that is shared and a Home collection that is not shared AND an event appears on both calendars, you need to do the restore before the import.
  • In general we should just tell users to restore shares before importing other calendars.
  • In the future can we have a way to restore everything in one step

Other

  • All the migration instructions will have to be added to a readme but how do we make sure people see this?
  • We probably need to change the current "old repository message" - perhaps a link to the readme
  • Check with Heikki and Bear about our options on the installer side

-- SheilaMooney - 19 Apr 2006

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.