Archive

Posts Tagged ‘course’

daily summary(moorewj)

May 20th, 2009 No comments

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.

Daily summary (moorewj)

May 15th, 2009 No comments

Today I spent some time looking into our recent migration attempt of Luminis III to Luminis IV. This was manily an exercise to try and find where in the migration code base it was picking up the old LDAP server’s base DN. Sadly more time will be needed here to track down this issue.

I also deal with bugzilla tickets 3422 and 3429. For Ticket 3429 I created a new Bugzilla component for JUMP called ‘Course: Duplicate PIDM’ as a means to track course population issues that are caused by the duplicate PIDM problem.

Worked with Lonnie on working out some of the aspects to this blog.