Tuesday 4th June, 2013
2:00pm to 2:45pm
Upgrading Sakai might seem hard. Upgrading while ensuring your custom changes are intact might seem even harder. Doing all of this without faculty noticing a major upgrade is taking place? It's not as impossible as you might think.
The purpose of this session is to provide a roadmap for institutions that want to upgrade Sakai while minimizing risk. We will describe how the University of Dayton made the jump from Sakai 2.6 directly to 2.9 in one academic year, and brought five years of custom code changes along with us. Although we have a small staff, our goal was to make this large upgrade "quiet"; we wanted to avoid the hiccups that normally accompany an upgrade, and make the transition as invisible and seamless as possible.
We will also cover how we cultivated a pilot group of faculty and students that used a beta server for a semester, and the benefits of soliciting feedback from this group. We will also explain how we plan to stay current with the community's code moving forward.
E-Learning Specialist and Adjunct Faculty of Psychology (HCI, UCD, and Persuasive Technology) at The University of Dayton a
Sign in to add slides, notes or videos to this session