CLE Building knowledge and communities of practice

Overview CLE 2.0 components Timeline and process Key issues

CLE Today 3 years old Adopted by all professional schools plus … 1,300 courses 3,000 logins per month MyAccess authentication since 2011 Integrates several systems/tools –Moodle, UCSF Portfolio, Ilios, Lecture Capture –Registrar/SIS data for enrollment

CLE 2.0 for Fall 2012 Core applications – Moodle 2.x – Ilios 2 – Learning objects repository Integrated course, instructor, learner data New hosting model Integrated tools/apps Mobile access 4 CLE LORIlios 2Moodle

Key Benefits Campuswide, integrated learning environment Moodle 2 is on the critical path to achieving: –Mobile –Integration with other campus systems –Resource sharing between courses, schools; IPHE –Support for collaborative and public sites Leverages MyAccess –Single sign-on experience for CLE apps –Integration of Library resources/services into CLE 5

Timeline Spring – Fall 2011Evaluation of Moodle 2.1 Summer – Fall 2011Launch planning process, Planning Advisory Group June 2011 – Dec 2011Test implementation available for sandbox use Early 2012System available for training, course development May – Sept 2012Migration, training July/Sept 2012Students using new system for new courses Moodle 1.9 runs concurrently with older courses Ongoing development 6

Stakeholders Students Faculty Curricular Deans School ed tech support units/staff Library Registrar SAA/ETS ITS 7

CLE 2 Project CLE 2 Project Advisory Group –Gail Persily (lead), Rich Trott, Brian Warling, Tina Brock, Gwen Essex, Xinxin Huang, Chandler Mayfield –Advise on proposed solutions –Consensus on key decisions/priorities Communication –Presentations to stakeholders –Wiki space to follow the processWiki space –Advisory Group communicates within their schools – updates to key stakeholder groups School participation –Mini project teams –Testing, evaluation/review 8

Major Challenges Defining interactions between LOR/Ilios/Moodle Integrating user and course data 9

Integrating course and user data Objectives: –Free up staff time to focus on curriculum and education –Create standards and consistency in our systems for better interoperability Automate enrollment for all schools. Automate group enrollments for all schools. Auto create courses. Create other automatic linkages, e.g. lecture capture 10

Data needs Single source of learner data for CLE Single source of instructor data beyond FOR – who is teaching in which courses? Better identity data for students and instructors –Identity-based group enrollments 11

Project Advisory Group Members: Representatives from each school, plus Library's implementation team. Provide input into planning process, priorities and key decisions. Serve as key communication conduit to/from the schools. Sample issues for discussion: –Prioritization of CLE 2 projectsPrioritization of CLE 2 projects –Defining user requirements for features such as Learning Objects Repository –Moodle 2 theming/branding –Release cycle for upgrades –Service Level Agreement –Course Lifecycle Management 12

CLE 2 – thru Dec 2011 Focus on LOR/Ilios/Moodle integration Educate schools and stakeholders Resolve hosting decision Develop plan for automating enrollments Tackle High priority, Low difficulty Prioritize remaining tasks 13