UW-Madison Moodle Mike Litzkow and Jeff Bohrer

Moodle History at UW-Madison  Started in schools and colleges for different reasons  Delegated authority, support for right-to-left languages, math notation  Utilized by several TEL grants  Installations were separately hosted and managed  Different Moodle versions, plug-ins, policies  Moodle council  Place for Moodle service providers to collaborate and cooperate  Common source code repository – proposed and implemented  Challenged by then CIO Ron Cramer to propose an “enterprise” Moodle

Enterprise Moodle  Received permanent funding from CIO office in spring of 2012  “Enterprise” (campus level) service with no direct cost to our users  Managed by personnel in College of Engineering  Runs on hardware and hosting services at College of Engineering  Funded by SITI funds plus supplement from College of Engineering  Began serving “Moodle experienced” campus units in fall of 2012

Service Coordinator (Mike Litzkow) Director of Wendt Commons (Deb Helman) Director of Computer Aided Engineering (Rob Kohlhepp) Governance Executive Committee CIO Vice Provost T&L Vice Provost EM CoE Dean Vice Povost Lifelong Learning Steering Committee CAE Dir Wendt Dir Moodle Council (3) DoIT AT Vice Provost Lifelong Learning Support Team (Sajia Kopp) Platform Team (Mike Litzkow)

Current Status – Fall 2013  Available for all timetable classes  About 500 courses/semester  About 17,000 students in timetable courses (31,000 unique enrollments)  Courses in 73 departments from Accounting to Zoology

Distributed Support Structure  First level support – DoIT Help Desk  Second level support – DoIT EAST  Pedagogical support  In-unit by those units who historically supported own Moodle  DoIT Academic Technology in those units without historical Moodle support  High-level tech support – the “platform” team

Relationship with Mutually supportive relationship  We work in a very similar space  We communicate and share ideas regularly Joint projects  Piazza  McGraw-Hill  Communications  Regular, coordinated LMS workshops

Moodle on home page

Non-credit  Non-credit providers still running own Moodle instances  EPD, Pharmacy, SoE  Reasons  SITI funding not appropriate  Campus IT infrastructure not ready to support this  Not currently in purview  Non-credit IT Initiative  Project sponsored by outreach deans  Propose solutions for getting non-credit students and courses into LMSs  Status – architecture proposed, embarking on cost and requirements analysis

Ongoing Activities  Platform maintenance, security patches  Platform upgrades (new versions of Moodle)  Third party plug-in evaluation and maintenance  (7 under evaluation for spring 2014)  Internal plug-in projects  Feedback Manager  Box integration  Drawing tool