1 / 39

Sakai Deployment at University of Michigan: From Legacy Systems to Modern Collaboration Tools

This presentation, by John Leasia from the University of Michigan, covers the historical evolution of Sakai, detailing its deployment, the transition from legacy systems like UM Coursetools to contemporary platforms, and the features of CHEF-Based systems. It highlights the increase in user engagement, rollout timelines, and support structures implemented to enhance the educational experience. Key developments from 1999 to 2005 are discussed, along with the integration of collaborative tools that have transformed course management and project organization.

roary-kirk
Télécharger la présentation

Sakai Deployment at University of Michigan: From Legacy Systems to Modern Collaboration Tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Sakai Deployment University of Michigan John Leasia jleasia@umich.edu SEPP Baltimore Conference June 8-10, 2005

  2. UM Sakai deployment • History – ‘classic’ to Chef to CTools • Usage • Fall rollout of 2.0 • Config files

  3. CHEF 1 CHEF 2 Worktools (Notes Based) WTNG CTNG Coursetools (Notes Based) 1991 - 1997 2000 1998 2004 2002 2005 2001 1999 2003 Collaboration @ UM Sakai NMI Grid Portal NEESGrid Science of Collaboratories SPARC

  4. Historical Background • Fall 1999 University of Michigan releases first homegrown CMS, UM Coursetools, built in Lotus Notes • Fall 2000 UM releases first project management system, UM WorkTools, built in Lotus Notes

  5. CHEF-Based NEESGrid Software

  6. Bringing the lab to the classroom

  7. Historical Background • Growth in usage • Issues with development • 2001 - Chef project initiated Fall • 2002 (Chef beta) • 275 users, 8 class sites • Winter 2003 (Chef 1.0) • 500 users, 20 class sites

  8. Historical Background Fall 2003 • Coursetools Next Generation • Pilot comprised of 212 course sites • Approximately 8,000 users • Run concurrently with legacy system hosting 1,423 course sites

  9. Historical Background • Winter 2004 • Pilot expanded to 260 sites • Approximately 10,800 users • Heaviest usage in Engineering, Medicine, LSA • More complex usage as evidenced in faculty trying to do new and different things with the functionality • Increasing number of project sites set up

  10. Historical Background • Fall 2004 • Sakai 1.0 released in full production (UM version - CTools) • 1,645 course sites with approximately 23,818 users • 2,055 project sites (number users unknown) • Heaviest usage in LSA, Business, Engineering

  11. Sakai Users @ Michigan • Fall 2005 (Sakai 1.0 / CTools 2.0) • 15,000 users • Winter 2005 (Sakai 1.5 / CTools 2.1) • 25,000 users • 1591 course sites • 2810 project sites • Average student logs in 1.77 times a day for an average of 43 minutes per session • 5,000 users per day Friday and Saturday • 15,000 users per day Monday and Tuesday

  12. Unique Visitors by Day

  13. Fall 2004 Max Users & Site Setup

  14. Usage Stat during Fall 2004 um.Coursetools (legacy) • 891 course sites serving 1,412 sections • 67% candidate users have um.Coursetools course component • Users per day: 17,100 during peak usage CTools (Sakai) • 1,645 course sites serving 2,356 sections • 59% candidate users have CTools course component • Users per day: 12,000

  15. Winter 2005 Max Users & Site Setup

  16. Winter 2005 Session Counts

  17. Summer 2005 Max Users & Site Setup

  18. CTools Winter 05 • CTools 2.2 based on Sakai 2.0 • Roll to production June 29 • Med School requirement • Point (bug fix) releases as needed up to start of Fall term Sept 6 • QA’d critical fixes only • Legacy system turned off

  19. CTools Support • Structure • User support structured in 2 Tiers • Tier 1- Part-time graduate students cover front line requests • Tier 2- Full time employees oversee Tier 1 and coordinate support issues/resources • Resources • Full time support staff - 2.75 • Part time support staff- (90 hours temp per week) • Documentation-.75 • Training/Consultation .75

  20. CTools Support Coverage • USE Lab staffed M-F, 9 a.m. - 5 p.m with spot coverage in evening • Sat. & Sun. 9-5 coverage provided by Tier 1 staff Primary Support Methods • Email • Phone • Online feedback forms • Walk-in consultation • Training/Consulting • Documentation, tutorials, and best practice guides • Academic Technology Commons Group

  21. CTools Support • Footprints

  22. CTools Support • More info on CTools Support • Breakout session 3 – User Support Thursday 13:30 – 14:30 Stephanie Teasley Sean Demonner Hannah Reeves

  23. UM – current environment

  24. UM – current environment • 9693 total worksites • GradTools related 93 • Project worksites 3876 • Class worksites 5111

  25. UM – current environment

  26. UM – current environment Hardware config

  27. UM CTools – Sakai configurations • UMIAC • Library reserves, GradTools • User, worksite types • Tools we’ve exposed • Property overrides – sakai.properties

  28. UM CTools • External provider – Registrar roster data • Behind Cosign single sign-on authentication 1 per day As needed Ctools UMIAC Registrar

  29. UM CTools • Library Reserves tool • Specially configured News tool • GradTools • Dissertation process tracking – workflow • UM specific configurations

  30. Library Reserves Demo Thursday 17:00 – 18:30

  31. GradTools Demo Thursday 17:00 – 18:30 http://gradtools.umich.edu for info

  32. UM CTools configurations • Site types • project, course • gradToolsRackham, gradToolDept, gradToolStudent • User types • guest (friend), uniqname, colleague • Roles • Course – Owner, Instructor, Assistant, Affiliate, Student, Observer • Project – Owner, Organizer, Member, Observer • GradToolsRackham – Dean, Staff • GradToolsDepartment – Dean, Staff • GradToolsStudent – Committee_member, Student

  33. UM CTools configurations • Tools exposed in worksites (1.5) Add for 2.0 (CTools 2.2) Syllabus Gradebook Melete Pilot Test/Quizzes Configured in each tool’s registry file

  34. UM CTools configurations • My Workspace tools in 1.5 (edit the !user.<type> sites) • Adding for CTools 2.2 • Webmail • My AFS (WebContent tools pointing to UMich webmail and AFS space)

  35. UM CTools configurations • Unit skins • Affiliates • Support email address • …. • toolOrder.xml • sakai.properties 1.5 • sakai.properties 2.0

  36. UM CTools configurations • Skins

  37. UM CTools configurations • Skins

  38. UM CTools configurations • A look at CTools • Provider id • User, site types

  39. Sakai Deployment University of Michigan John Leasia jleasia@umich.edu SEPP Baltimore Conference June 8-10, 2005

More Related