super ruper by nnnnic Attribution-NonCommercial-NoDerivs License
I’ve been trying to post information about the glow blogs migration here when I can, but still getting a few questions, via email, twitter etc. Here is a series of DMs:
Hi John. Been following the progress of GlowBlogs and reading your own blog. Question: Can I go ahead and set up a class blog using…
‘Old Glow’ and get class using it….then it’ll transfer across to ‘New-Glow’ with the bells and whistles in he coming weeks (months) ?
I (and other member of staff) really want to get cracking on this. How would we ensure the old style blog ‘goes accross’? Need to tell..
someone where it is?
Quite a few folk have asked the same sort of thing, can/should I set up a glow blog/e-portfolio now or wait?
The answer is: Yes if you set up a glow blog now it will be migrated to the new service.
There will be a procedural content freeze, and the possibility of downtime if we do not make the 3rd of October deadline (we are working very hard to ensure we will).
The database and files that make up the blogs are currently on RM servers, this need to be moved to new servers. Given the size of the data this will involve copying onto a portable disk. The copy will be encrypted. The disks need to be moved, the encrypted data securely moved to the new setup, unencrypted and verified. The new system then need to be thoroughly tested.
During this time the old blogs will be up and running, but any content added to them will not be migrated and new blogs setup during the content freeze through the old glow Sharepoint portal will not be migrated.
I am not sure how long the content freeze will be but it looks like being a week or so.
We will publicize the content freeze as much as possible, telling Glow Key Contacts in each Local Authority, publishing on Glow Connect and I’ll post here and tweet.
We also hope to be able to add a warning message on the dashboards of all the current glow blogs, but that solution needs to be created and tested.