I'm with Musea, working on the openacs.org redesign/upgrade, and more
specifically this week, on the bboard migration. Since this is a
general oacs upgrade problem, I'd thought I'd get feedback, see if
i've missed anything. Hopefully this will also start some discussion
and work on general live-site upgrade procedures and scripts. I see
most of the data migration as being done with tcl pages on the 4.0
site, with an extra database pool to talk to the old data.
The outline for bboard migration assumes that user migration has been
done. User migration is pretty straightforward, at least the part
required for bboards, which is just name, email, and password.
(Anyone care to volunteer to write full user migration pages?) The
main idea is to reuse module/package code, and keep track of *_id
mapping through *_migration_map tables. The map tables will also
allow you to check to see if something's already been done, so you can
use the pages to refresh the upgraded site during beta. I left all
those ifs out for brevity.
The outline is here:
http://museatech.net/misc/bb_migrate.txt
if anyone sees something critical i'm missing, or mapping wrong,
please let me know!
