Post-Migration Planning/Sustainability


Last updated September 27, 2014.

Based on previous experience, the Library is well aware of the possibility of system instability during the first few weeks of production. Library staff will be forewarned of this; contingency plans allow the Library to resume using Horizon or Millennium if that should become necessary. “Hope for the best and plan for the worst” is a prudent guiding principle for any new software implementation.

During the first few months of production, Library staff will undoubtedly find bugs and discover gaps in our training. ILS staff will be prepared to spend most of its time with intensive troubleshooting.

The Kuali OLE software development schedule calls for an implementable version to be completed in late spring 2014 and for patches to be available during the summer of 2014 for the two early implementer libraries. Experience of the other Kuali projects has been that early implementers developed a number of bug fixes and customizations for local implementations that were difficult to eventually include in the codebase. As a result, the OLE project will plan to support and merge the patches for the early implementers into the 2015 version of the software that will include additional functionality desired by all of the partner libraries. Implementation at the University of Chicago is planned with the intention of continuing to participate in development and testing of this next version. For the first year, the approach for local functionality to supplement Kuali OLE features will rely on helper applications separate from OLE, rather than modifications to the code itself.

Procedures for code contributions are being developed by the Kuali OLE Technical Council, and it is anticipated that there will be ways to do this by the time more partners implement in 2015. Appendix E contains the draft of these procedures. These processes are already in place for VuFind software and the library has contributed code where appropriate during the customization of VuFind for local use. While it has always been the plan to customize VuFind for local usage, early and intense involvement with the OLE development has resulted in a strategy to rely on local customizations as little as possible in the ILS implementation.

Our training plan calls for staff meetings about a month after the initial production date, organized by functional areas, to provide an opportunity for training refreshers and discussion of any ongoing issues. Additional follow-up meetings may be required, depending on the volume of issues.

Once Kuali OLE is reasonably stable, ILS staff will need to migrate seven years’ worth of past acquisitions data from Millennium to a database of some kind. Horizon historical circulation data will also be migrated to a data warehouse to support reporting. The intention is to reactivate a project to implement a data warehouse and a more sophisticated system for reports and analytics in the year following implementation of Kuali OLE.

During the six months after implementation, any remaining useful data will be moved from Horizon and Millennium. Those systems will cease to be updated at the time of cutover. They will be available for consulting until they are retired in January 2015. HIP and AquaBrowser will be unavailable once the cutover to OLE happens, as they do not point to OLE. They will be retired as soon as the OLE system is stable.