LMS Selection Project: Update to STAC

LMS Selection Project: Update to STAC 03June 2010 Andrea Chappell, for the project team

Update topics • Project timeline (DRAFT) • RFI results • RFP status • Open Systems - issues, policy decisions, etc. • Canadian universities: Why, 3rd party support, migration • Communications – web site coming! • OLE student survey results

Project timeline (DRAFT) • Phase I – end with recommendation to UCIST Feb. 2011 • RFI: April – June 2010 • RFP: June – Oct 2010 (submit end June, review by Oct) • Info collection and amalgamation: June – Oct 2010 (Contact similar sized schools, what add-on tools, etc.) • Policy decisions: June 2010 – Jan 2011 (open systems, dev, hosting, procedures changes, etc.) • Phase II – implementation planning, pilot, migration, to May 2012 • Pre-pilot? (small group): Winter 2011 • Pilot (real use): Mar. 2011 – July 2011 • First wave of migration: July – Aug 2011 (for Sep 2011) • Final migrations: Sept 2011 – March 2012

RFI: 8 proposals

RFI: Costs and Functionality • Costs hard to decipher; Wide range of responses • Vocabulary and packaging • Lots of “To Be Determined” • Functionality – companies claim to be able to do the job, and not much to eliminate them so far

Technology and Standards • System software and hardware • # of instances allowed • Servers/virtual machines recommended • Browser support! • Hosted vs. locally installed? • Standards • IMS • Accessibility

Integration • Campus systems (AuthN, Quest, etc.) • Applications: Wimba, <i Clicker, TurnItIn, Ares. Other campus systems, e.g., Drupal, Dspace? • Additional system of interest • ePortfolio • Content management (versioning, roll-back) • Other: specific mention of mobile platforms

RFI next steps • Questions to vendors • Re-develop criteria • Other data collection • Other schools’ experiences • Questions/inputs to RFP

RFP - status • As noted, re-develop criteria • Develop demo scenarios (putting vendors and products through their paces) • Assessment grid, e.g. (not real!) • Cost 25% • Functionality 25% • Migration 25% • Support 25%

Open system: Who/what • Western: RFI in fall, consider Bb NG, open source. • UVic: Moodle since 2007, from Bb (WebCT since 4.1). Small pocket of Sakai. • Queen’s: To Moodle from WebCT after a year in 2 pilots, 10+ courses, 1000’s students. • Windsor: Sakai 2.5 since 2006, to 2.7 in Fall; moved from homegrown Notes app. • Virginia Tech: Had Sakai for 1-2 years for collab and project groups. To be sole LMS in Fall 2010.

Open system: Why (drivers)? • No vendor lock-in • Customization • No license fee (but adoption not free) • Products adhere to industry standards • Development contributes to global benefit • Philosophical alignments • Poor support from Blackboard (VTech, UVic)

Open system: Use of 3rd party • Not much use of 3rd party company for implementation, migration, support • Almost all in-house, using own staff • Not much development happening, only Windsor, donated to the community

Migration (not unique to OS) • Drain on resources. • Main obstacles are differences in structure, data format, modules. • Most data type not converted. Quizzes, discussion forums must be recreated. Significant course redesign. • Used existing staff, some student hires, varied a lot. Generally, need lots of help!

Communications web page • Increase transparency! • Web site under development, then a launch and keep up to date with progress

OLE student survey results Not ready yet, but sneak peak … • Look and feel (some awkwardness of interface) • Tech (frames are so 90s, Javascript) • Integration with Quest, Nexus(hm, portal-like) • Access to materials (all syllabi, materials from other courses, access after end of course) • Discussion forums not as good as others outside ANGEL • Mobile access • More from calendar (integrated with other calendars) • Better live/synchronous tools, such as chat

Other note • Shahed’sManSci course project (option)

Questions or Comments?

LMS Selection Project: Update to STAC