UC Enrollment Conference UC Davis

1
UC Enrollment ConferenceUC Davis UCLACourse
Management SystemsOctober 17, 2007

• Kirk Alexander
• Sakai Program Manager, UC Davis
• kdalex_at_ucdavis.edu
• Rose Rocchio
• POG Member CCLE Planning Team Member, UCLA
• rrocchio_at_oit.ucla.edu

2
Open SourceCourse Management systems

• UC Davis
• Deploying Sakai as Smartsite
• Migrating off of a legacy system
• UCLA
• Deploying Moodle as CCLE
• Converging from many course mgmt systems

3
UC Davis (sakai)What is SmartSite

• New Course Management and Collaboration Tools
• Easy to use and extensible tools for organizing
  work and content enables technical integrations
• A national community of programmers joined in an
  Open Source / Community Source effort
• Encourages interdisciplinary activities
• Enables research and teaching synergies
• A solution for the future

4
UC Davis (sakai) Reasons for Pursuing Sakai

• Support Community SSF
• Expandable set of Tools/features
• Ability to meet local feature requests and needs
• Need to meet Enterprise scaling (28,000
  students, 8000 CRNs / Quarter

5
UC Davis (sakai) SmartSite Timeline

• Pilot ran January 2006 thru Summer 2007
• Faculty from many different departments
  participated
• Met target to open access to any and all courses
  in Fall 2007
• Will run in parallel with legacy system
  (MyUCDavis) until Fall 2008.

6
UC Davis (sakai) Rich Contributed Tools

• Agora (Live conferencing)
• Breeze Link
• Citations Helper (Library Search)
• Configuration Viewer
• Evaluation System
• Gallery
• Home Page Tool
• ImageQuiz
• Mneme (Test Center Presentation Engine)
• Open Course Ware (OCW)
• PreferAble/TransformAble Accessibility Tools
• Recent Activity
• Reset Password
• TurnItIn integration

7
UC Davis (sakai) What have we learned from the
Pilot?

• SmartSite is viable we can continue to move
  forward..
• Faculty are sticking with it! And the word is
  spreading.
• Test Quiz is a complex subject and a
  complicated tool...more work to do here. Faculty
  input needed.
• Many uses for project sites (research,
  administrative, committee, dissertation...)
• Wiki can be used for group exercises in many
  disciplines
• User activated site creation is desirable and
  solves many issues related to combining sections
  and cross listed courses

8
UC Davis (sakai) Local resources required

• HelpDesk
• Training
• Integration Programmers
• Database Administrators
• Development Programmers

9
UC Davis (sakai) SmartSite Integration

• Live enrollment data feeds from Banner(near
  real-time)
• Staging database for system isolation
• Authentication (distauth for now)
• Course descriptions
• Final Grade Submission to Registrar
• Skin with campus color scheme

10
UC Davis (sakai) Overlaps with student affairs

• Registrar feeds enrollment
• Committees / document sharing
• Data feeds for site participants
• Project sites membership
• By department/level (e.g. 3rd year law students)
• Senate Faculty
• Authorization for such lists?
• Course Evaluations

11
UC Davis (sakai) Support Services

• The devil in the details
• Department hiring practices
• Semester vs. Quarter
• Departmental Proxies Authorization thereof
• Legacy system gaps
• Backend systems integration
• Relatively new and complicated in Sakai
• Helpdesk
• Very Important!

12
UC Davis (sakai) Example Sites at UCD

• Courses (of course)
• Research Groups
• Committees
• Departmental Uses
• Student employees
• Colloquia Materials
• Student Clubs

13
UC Davis (sakai)Most Asked for Features

• Guest Access (w/o UCDavis identification)
• Feeds of known groups (Grad students, department
  faculty or students...)
• Grading options flexibility
• Quizzing options flexibility
• Course Evaluations--available in contrib

14
UC Davis (sakai) Outstanding Questions and
Issues

• Gradebook still evolving some missing features
• Assessment Tool stable but still evolving and
  carries a learning curve (e.g. plan on
  training)Other systems have better assessment
  tools
• Site copy/archive overtime incomplete
• Student View on all tools incomplete

15
UC Davis (sakai) Major Support Resources

• ITExpress team now to answer both phone and email
  inquires
• ETPartners extended faculty hand-holding (in
  office if desired)
• 2 FTE Training and Support Staff
• Support in Classroom via CTS/ITExpress
• Weekly Faculty Support Staff Coordination Mtg
• Support Partners monthly Meeting
• Special IT Support Staff Training can be arranged

16
UC Davis (sakai) Thank You

• Contact
• Kirk Alexander (kdalex_at_ucdavis.edu)
• Steve Faith (faith_at_ucdavis.edu)
• Fernando Socorro (fsocorro_at_ucdavis.edu)
• Help (smartsite-help_at_ucdavis.edu)
• SmartSite
• http//smartsite.ucdavis.edu

17
Switching Gears to
18
UCLA (Moodle)What is the CCLE

• Common Collaborative Learning Environment
• An effort to create a consistent campus-wide
  environment
• A single environment supporting both research and
  instruction
• An open environment that supports ongoing
  development and local customization

19
UCLA (Moodle)CCLE Timeline

• Spring 2005 FCET recommends that UCLA converge on
  a single solution
• June 2006 The FSG/TSG jointly recommend that UCLA
  converge on a
• single open source solution.
• October 2006 Based on the Assessment Task Force
  Report, the FCET
• unanimously selects Moodle as the open source
  platform.
• April 2007 CCLE Alpha Project Oversight Group
  (POG) implements Alpha Moodle service.
• May 2007 CCLE Planning Team appointed to engage
  in broad campus
• consultation and to recommend the appropriate
  scope, scale,
• staffing, architecture, operation, use and
  funding for the next
• phase of the CCLE initiative.
• August 2007 CCLE Planning Team submits report
  for funding

20
UCLA (Moodle)Reasons we selected Moodle

• An international Open source community
• Mature set of course collaboration tools,
  discussion boards, quiz tools, accessibility etc
• 300 plugins already built
• A rich set of administrative features
• Three instances in use on campus already

21
UCLA (Moodle)2 CCLE Paralleled Efforts

• The CCLE Alpha Production system
• Implementation details
• Integration
• Developed Tools
• The CCLE Planning Team
• Design Principles
• Governance
• Recommendations

22
UCLA (Moodle)The Alpha CCLE Teams

• The POG (Project Oversight Group)
• Formed in October of 2006
• Meet weekly to discuss progress priorities
• 4 subgroups (Sys Ops, Dev, Functionality
  Support)
• 44 active volunteers from across the campus
• Using JIRA for issue tracking
• Using SVN for development

23
UCLA (Moodle)The CCLE Alpha Implementation

• Spring 2007
• 18 courses Moodle 1.7
• Summer sessions A C
• 30 courses
• upgraded to 1.8.2
• Fall 2007
• 81 courses
• 31 collaborative sites
• Running Moodle 1.8.2

24
UCLA (Moodle)Examples of CCLE Site types

• Courses
• Faculty Research groups and Projects
• Staff collaboration projects
• Library work groups
• Test sites

25
UCLA (Moodle)CCLE Campus Integration

• Authentication using Shibboleth (ISIS)
• Registrar - working to improve scalability
• Library built an ereserves block
• My.UCLA for syllabi
• Desired integration
• UCLA Gradebook
• UCLA Bruincard photos

26
UCLA (Moodle)CCLE Developed Tools

• Tools Built patches made
• Modified control of Switch Roles tool
• Implemented friendly URLs
• Patched a blog and forum name exploit
• In Progress
• Creating a Public/Private object toggle
• Working on a plan to implement student privacy
  preferences (for FERPA)

27
UCLA (Moodle)CCLE Alpha Support model

• Opt-in participation
• Requires local support participation
• Campus-wide Support Subgroup
• Meet weekly
• Share a support mailing list
• Make an attempt to answer inquiries w/in 24 hrs

28
UCLA (Moodle)The CCLE Planning Team

• Terry Ryan, Library, Julie Austin, SEAS myself
  (Rose Rocchio, OIT)
• Tasked to to engage in broad campus
  consultation and to recommend the appropriate
  scope, scale, staffing, architecture, operation,
  use and funding for the next phase of the CCLE
  initiative.
• Worked with the following committees, groups
  people
• The CCLE POG
• The Campus Computing Council (CCC)
• The CCLE Functional Oversight Committee (FOC)
• Faculty Committee on Educational Technology
  (FCET)
• Undergraduate Students Association Council
• The Deans

29
UCLA (Moodle)Converge on Moodle

• 26 different course management systems
• CCLE Moodle environment

Unit System
Possible Regional System
Campus-wide Shared System
30
UCLA (Moodle)Design Principles

• Recognize school / division staff and support as
  the CCLE foundation.
• Encourage broad adoption on an opt-in basis
• Make planning and governance open and
  participatory.
• Ensure that academic priorities and faculty /
  student experience drive decisions.
• Support innovation, creativity, and flexibility.
• Allow for more than one Moodle installation if
  needed.
• Choose a CCLE administrative home with strong
  academic values (OID).

31
UCLA (Moodle)Collaboration Governance
32
UCLA (Moodle)Recommendations made

• Hire CCLE Home staff
• A CCLE Coordinator
• Lead developer / integration programmer
• Testing and support lead
• Intellectual property adviser
• 25 Leader of Standards Practices Group
  (buyout).
• Reimburse local staff time for coordination
• Purchase extra hardware for shared systems.
• Award Grants for innovation enhancements

33
UCLA (Moodle)How To Find Out More

• Track updates on the CCLE Initiative Web Page
  http//www.oit.ucla.edu/ccle/
• Read the full planning team report
• http//www.oit.ucla.edu/ccle/docs/20070815_CCLE_P
  lanning_Team_Final_Report.pdf
• UCLAs Alpha CCLE
• http//www.ccle.ucla.edu/

34
UCLA (Moodle) Demo of Example Sites

• UCLA's CCLE
• Help site (activity manuals, how to videos
  lots of other helpful links)
• Course Example
• Environmental Health 100
• Project Example
• CCLE POG Site

35
UCLA (Moodle) Thank You

• Contact the Planning Team
• Rose Rocchio (rrocchio_at_ucla.edu )
• Terry Ryan(tryan_at_library.ucla.edu )
• Julie Austin(jaustin_at_seas.ucla.edu )
• Contact the CCLE POG (Julie Rose above)
• Kumar (chair) kumar_at_anderson.ucla.edu)
• Mike Franks (franks_at_ssc.ucla.edu )
• Annelie Chapman (annelie_at_humnet.ucla.edu)
• Scott Dicks (sdicks_at_sonnet.ucla.edu )
• Lisa Kemp Jones (lkemp_at_ucla.edu )
• Jim Williamson (jwjwj_at_ucla.edu )
• Stephen Schwartz (shs_at_library.ucla.edu )
• for Julie Rose see above