About bloody time! I have been able to migrate the Luminis III data to Luminis IV. There are some fine touches that need to yet be done. Specifically:
- migrate mb_topics by hand
- migrate calendar data
- migrate the group and course files and photos
- put back the custom CAR files
Those were given issues from the outset of this process, which I will work on, on Monday. Now the data present in this system goes back to June of last year.
Perhaps I should not shout from the rooftops just yet, but I was actually able to log in and see a fairly functional portal unlike previous attempts where the bulk of the channels were broken.
The url for those that monitor this blog is http://lumnext.cc.umanitoba.ca
Today I continued work on building an application that will filter out old events from our calendar files. It appears to have been successful against my ical file. I am lacking the various proeprty settings at the top of an iCal file but that will be tomorrows task.
The plan is to use the same property data in the orignal file for the new one, minus any non America/Chicago timezone properties.
I had forgot to mention that yesterday I produced a list of JUMP users where the course population job was wishing to change the id the courses should be attached to according to the policy that was worked out between Brian and myself. A number of these were because the id initially chosen are technically no longer eligible for an account while the others are eligible for either just that the id selected is not the preferred one according to the policy. This has been forwarded off to Brian for his thoughts on how best to proceed.
As for today I worked with Sandy, Jennifer, and Lloyd to troubleshoot a recent problem where some employees are unable to sign into JUMP Lite to renew their parking. At this point there is a discussion that parking services will need to have with HR to potentially alter the rules for access. This will be transparent to the code that authenticates JUMP Lite users.
I have begun work on developing an application that will be used to migrate the calendar data from Luminis III to IV. Part of the cleanup will be to remove a custom timezone that we had added when we went live with JUMP, as well as a routine to clear out any calendar events that are older then two years. The hope will be that the calendar pruning will be able to be ran more regularly. At this point the code is in an early stage so there is not much to report here.