Summary of Ruth Sabean's contribution to the "OSS and OER in Education Series." In this 2 part interview, Ruth Sabean, assistant vice provost for educational technology in UCLA’s College of Letters and Science, discusses the evaluation process she managed at UCLA that resulted in the selection of the open source application Moodle.
Ruth saban interview summary
The first installment in the Impact of Open Source Software Series was an interview with Ruth Sabean, assistant vice provost for educational technology in UCLA’s College of Letters and Science and director of educational technology in the university’s Office of Information Technology. We discussed UCLA’s adoption of Moodle. Some of the major points and themes of the interview included:
- The prime mover for UCLA’s decision to evaluate and select a new learning management environment was to help provide a common infrastructure to promote sharing and innovation across units at UCLA. The selected technology was offered on an opt-in basis for academic units.
- The process started with a commitment to adopting an Open Source technology and the field of applications was quickly reduced to Moodle and Sakai
- UCLA committed to Open Source because they wanted to benefit through contributing to and learning from a global partnership that holds values of access and cooperation matching those of UCLA.
- UCLA had little interest in being tied to large commercial vendors who are guided by larger market forces that have little to do with UCLA teaching, learning, and collaboration needs.
- UCLA fully anticipates contributing actively to the Moodle community and to the larger dialog around interoperability.
- Ruth saw some of the challenges to contributing to Moodle as UCLA’s independent streak and lack of experience contributing to an Open Source community, but felt that Moodle was an inviting community.
- Ruth indicated that when making a good decision about Open Source or commercial software, you need to understand your requirements, understand how the software will meet them, and evaluate your options based on those criteria.
- Although Sakai and Moodle had both advantages and disadvantages, it was product maturity, community strength, and progress during the past 5 years, that swayed the evaluation committee to select Moodle.
- Ruth suggested that some of the most important factors in a successful evaluation and selection process is to really understand your organization, have faculty drive the process, and actively seek feedback from colleagues at other institutions.
There were a number of comments and responses made during the days following Ruth’s post. There were at least two central themes that were generated from the comments.
- There was a fair amount of discussion about some of the perceived trade-offs between Sakai and Moodle and a larger set of issues about the potential for a service-oriented architecture sitting at the center of a learning management environment. The UCLA and SUNY experience suggested that at least conceptually Sakai offered a fair amount of promise for tool interoperability, but that it failed to deliver in some critical ways and lacked much of the community involvement that is one of the remarkable achievements of Moodle. Some discussion about Moodle’s architectural flexibility was offered during the dialog. The discussion rests within the context of universities seeking a learning environment that best meets the needs of teachers and learners within unique contexts.
- There was a second theme that focused on cultural acceptance of Open Source software within UCLA and UCLA’s interest in and ability to contribute to the Moodle community
