A Strategy for Moving from Commercial to an Open Source Environment Jeshua Pacifici, GEDI Assistant Director and Learning Systems Consultant
Notice Copyright Jeshua Pacifici, This work is the intellectual property of the author. Permission is granted for this material to be shared for non- commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of the authors. To disseminate otherwise or to republish requires written permission from the authors.
Learning Systems at VT
Blackboard at VT
Know Thyself Identify what currently makes you successful using a commercial product: Stability and reliability of online learning environments Provide product functionality (needed tool sets) Product ease of use (user interface) Data integration (user and course data) with institutional systems
Know your strengths What is working? System-wide support: Help desk, help pages, documentation Training program for users Relationship with vendor support manager and support team Ability to leverage your university’s technical teams (database, systems, etc.)
How you could improve if you adopted the open source environment? Customize tools to better meet diverse pedagogical and research needs Flexible tools that adapt to administrative needs More control over local support improving responsiveness Improve product migration and system performance Increase integration and leverage with institution’s academic and IT resources Better serve institutional goals to broaden access to education
Specific advantages of the the open source environment Localization of UI: ability to modify and customize functionality and interface Partnerships with other similar institutions and within your own institution (e.g. - EE Dept) Interoperability and proprietary code limitations Consistent vision: vendor’s direction is often incompatible with your institution’s direction Forego vendor license/hosting fees
Surveying the terrain? Gap analysis between Sakai and commercial product Usability: user interface comparative analysis Cost benefit analysis User evaluation tool (survey measuring efficacy)
3 Levels of engagement 1.Hosted Sakai/open source environment (Rsmart, Unicon, etc.) 2.Explore Sakai community and become involved with community development projects (match your needs with needs of similar Sakai institutions) 3.Become fully involved in the Sakai community: development, testing, migration, transition -----> collaboration
Considerations for moving to open source Considerations and Resources: Development staff: voyeurs or volunteers Coordination of developers and QA: conflicting skills, interests, schedules, and objectives Skilled QA staff Support and training staff Collaborative environment demands new skills, often higher paid skills, and patience Need for “overarching” vision integrating tools Migration of current course data from legacy to open source environment Locally integrated admin tools Documentation
Open source is not free. Well how much not free (refer back to cost benefit analysis)? Collaboration involves time and effort and resources as you are taking an active role in the evolution of your institution’s learning systems. It is challenging and exciting; it engages creative energies and provides you with adapted learning environments for your faculty, students, and staff. Biggest expectation?
Summary Know Thyself Target early adopters (faculty, students, staff) & work with them throughout the process (grassroots approach) Focus on your strengths Find a niche (low hanging fruit) to contribute Partner with other depts within your institution (eg. CS) Partner with similar institutions and develop ways to share knowledge, experience, and resources
Questions & Answers Contact Information: Jeshua Pacifici, Assistant Director Graduate Education Development Institute Learning Technologies Virginia Tech Blacksburg, VA (540) Images: Digital Vision