Stopped doing logs because for the last 2-3 weeks we have been so busy and working so hard on the upgrade full time that I forgot/couldnt come to add everything here. Eric Ewen spent 43 hours on site during the upgrade, Bryan Brown spent almost as many remotely fixing problems. We are converted and ironing out some posting bugs, but as a whole the migration is on the up and up. It took much more time and effort than most expected primarily because of the many custom functionalities and uses of UMBC.

Bryan is now leading up the remaining issues because Jeremy has left. There is only one main task left to do, along with a few for me to test.

Bryan has communicated with me several times on getting the tasks for Milestone 2 completed. Payment for Milestone 2 should be released to DaySpring soon.

Substantial work has started again.

Milestone 2 completion is nearing. See the Milestone 2 Completion Requirements.

Jeremy Brenner will be replaced as the lead programmer by Bryan Brown, Nick Stuckey and John Marx.

Eric Ewen came to UMBC for 5 days of training various employees and troubleshooting upgrade problems.

Milestone 1 completion is nearing or past.

• Speedup of the application by indexing the data tables, and separating data into different smaller tables.
• custom UMBC fields to be added

Custom workflow fields in database are being added.

Workflows data architecture (on database backend) is going to be setup differently.

• 1 major workflow table (called )

• 1 active workflow table (called )
• 1 archived workflow table (called )

• 1 pending workflow tabled (called )
• 1 active workflow table (called )
• 1 archived workflow table (called )

The difference between the new workflow types are .

Raw data export from live production database to new server was started.

To get it going, Dayspring requested full DB access. Nick Yeates forwarded the request to UMBC OITs Todd Haddaway and discussed it with Betty Douglass and Janet Rutledge of the Graduate School.

Partial full access (catalog access?) was given by Haddaway, and the problem was solved. Exporting proceeded.

Since coming on line, we performed a code update to apply updates not in the standard distribution. We do this as they occur for existing customers until such time as a new distribution is created (about every 3 - 6 months).

We also performed a system lock down, blocking unused ports and limiting connectivity to known “friendly” networks for certain services, file sharing for example, since your systems are Internet facing.

We also put in place protection techniques for systems that are Internet facing such as your, to include firewalling and anti-denial-of-service tools.

Currently you are in the queue to begin the conversion. We are wrapping up some other projects and will queue yours up in the coming couple of weeks.

• Database and Sample data import from the custom production system to the new off-the-shelf production system.
• Database element analysis to identify and resolve discrepancies between the customized production system and the new off-the-shelf production system.
• Software programming code copy from the custom production system to the new off-the-shelf production system.
• Software programming code element analysis to identify and resolvediscrepancies between the customized production system and the new off-the-shelf production system.