sakai project overview n.
Skip this Video
Loading SlideShow in 5 Seconds..
Sakai Project Overview PowerPoint Presentation
Download Presentation
Sakai Project Overview

Sakai Project Overview

220 Views Download Presentation
Download Presentation

Sakai Project Overview

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Sakai Project Overview Mellon Retreat NYC March 28, 2005 Joseph Hardin, University of Michigan, School of Information, Sakai Board Chair (University of Illinois alum – Go, Illini) KYOU / sakai Boundary, Situation

  2. The Sakai Project “The University of Michigan, Indiana University, MIT, Stanford, the uPortal Consortium, and the Open Knowledge Initiative (OKI) are joining forces to integrate and synchronize their considerable educational software into a pre-integrated collection of open source tools.” Sakai Project receives $2.4 million grant from Mellon

  3. Sakai Funding • Each of the 4 Core Universities Commits • 5+ developers/architects, etc. under Sakai Board project direction for 2 years • Public commitment to implement Sakai • Open/Open licensing – “Community Source” • So, overall project levels • $4.4M in institutional staff (27 FTE) • $2.4M Mellon, $300K Hewlett (first year) • Additional investment through partners

  4. Why: All the simple reasons These are core infrastructures at our Universities • Economic advantages to core schools, partners • Higher ed values – open, sharing, building the commons – core support for collaboration tech • We should be good at this – teaching, research are our core competencies; collab essential • Maintains institutional capacity, independence • Ability to rapidly innovate – move our tools within/among HE institutions rapidly Based on goals of interoperability - Desire to harvest research advances and faculty innovation in teaching quickly

  5. But, What is Sakai? • Sakai is a project - a grant for two years. • Sakai is an extensible framework - provides basic capabilities to support a wide range of tools and services – teaching and research • Sakai is a set of tools - written and supported by various groups and individuals • Sakai is a product - a released bundle of the framework and a set of tools which have been tested and released as a unit • Sakai is a community – an emerging group of people and resources supporting the code and each other, and learning how as we go

  6. Sakai Project Deliverables Sakai Community – Committed and active Working Code – CMS/CLE- Collaboration and Learning Environment – Sakai 1.0 • Course management system – core tools plus • Quizzing and assessment tools, [ePortfolio from OSPI], etc • Research collaboration system • Portal (uPortal 2.3, 3.x) Modular tools - also pre-integrated to work out of the box Tool Portability Profile • Specifications for writing portable software to achieve application ‘code mobility’ among institutions – modular tools and services Synchronized development, adoptions at Michigan, Indiana, MIT, Stanford – Sakai 1.0 is the next generation for CourseWork, CHEF, Oncourse, Stellar

  7. Supporting the Class

  8. Supporting the Lab

  9. CHEF-Based NEESGrid Software NEES Chef -> Sakai 07/05

  10. NMI / OGCE NSF National Middleware Initiative Indiana, UTexas, ANL, UM, NCSA

  11. Bringing the lab to the classroom

  12. Student Student Student Staff 1 Staff 2 Staff 3 Portal Middle East News Feed Discussion Forum Discussion Forum Resource Management Collaborative Project Portlet ASUC Middle East Discussion Portlet What is SAKAI? • Sakai ≠Course Management System • Sakai = Collaboration & Learning Environment Use for teaching/learning/research and many other online group activities.

  13. Software Progress to date • Releases on time 1.0 (2004), 1.5 (last month) • Production and pilots underway, in pipeline; • 2.0 forming up nicely for June; recent meeting between Tools Team, Architecture Team and Board very good • Processes being developed - organizational methods evolving rapidly; release engineering, distributed QA, contributions acceptance models, definition of enterprise bundle, methods for OS Core

  14. Sakai in Production at UM, IU Now • We have about 25,000 people using CTools in at least one course at UM. That is about ~54% of candidate users at University of Michigan. • There are over 1000 course sites representing nearly 2000 sections this term. • First semester of transition from CourseTools Classic; transition complete Fall 2005, CTC ‘turned off’; then we are all Sakai/Ctools at UM • Running on big cluster of commodity Dell boxes; allows us to optimize as we provide stable service to large community; frequent rolls for updates Doing fine…

  15. In production use With >25,000 users at U Michigan Full Indiana Univ production pilot started in January ~4-5000 users On to Stanford, UC-Berkeley, Foothill, MIT in 2005

  16. Boston University School of Management Carleton College Foothill-De Anza Community College District Indiana University Johns Hopkins University Lübeck University of Applied Sciences, Germany Massachusetts Institute of Technology Northwestern University Rutgers Stanford University University of California, Berkeley University of California, Merced University of Cape Town, SA University Fernando Pessoa, Portugal University of Lleida, Spain University of Michigan University of Missouri University of Virginia Whitman College Yale University Known Pilots and Production

  17. SEPP In Production

  18. Ctools – Production Sakai at University of Michigan

  19. Ctools – List of Worksites – Classes, Projects

  20. Site/class home page

  21. Site Resources area

  22. Discussion tool – Forums

  23. Email Archive

  24. Site Info – class list

  25. Sakai Community Activities • Developer and Adopter Support SEPP - Sakai Educational Partner’s Program Community for ongoing dev, adoption, support • Commercial Support – SCA, IMS, maybe SPA Based on open-open licensing – open source, open for commercialization- see ECL at SCA – Fee-based services from vendors include… • Installation/integration, on-going support, training • Think of as “Sakai Red Hats” IMS – working with other CLE/CMS vendors on interoperability between frameworks

  26. Sakai Educational Partner’s Program Developing the Community that’s Directing the Source. • Membership Fee: US$10K per year ($5K for smaller schools), 3 years • Access to SEPP staff • Community development liaison • SEPP developers, documentation writers • Invitation to Sakai Partners Conferences • Developer training for the TPP, tool development • Strategy and implementation workshops • Software exchange for partner-developed tools • Seat at the Table as Sakai Develops The success of the SEPP effort will determine The long term success of the project.

  27. Arizona State University Boston University School of Management Brown University Carleton College Carnegie Foundation for Advancement of Teaching Carnegie Mellon University Coastline Community College Columbia University Community College of Southern Nevada Cornell University Dartmouth College Florida Community College/Jacksonville Foothill-De Anza Community College Franklin University Georgetown University Harvard University Johns Hopkins University Lubeck University of Applied Sciences Maricopa County Community College Monash University Nagoya University New York University Northeastern University North-West University (SA) Northwestern University Ohio State University Portland State University Princeton University Roskilde University (Denmark) Rutgers University Simon Fraser University State University of New York Stockholm University SURF/University of Amsterdam Tufts University Universidad Politecnica de Valencia (Spain) Universitat de Lleida (Spain) University of Arizona University of California Berkeley University of California, Davis University of California, Los Angeles University of California, Merced University of California, Santa Barbara University of Cambridge, CARET University of Cape Town, SA University of Colorado at Boulder University of Delaware University of Hawaii University of Hull University of Illinois at Urbana-Champaign University of Minnesota University of Missouri University of Nebraska University of Oklahoma University of Texas at Austin University of Virginia University of Washington University of Wisconsin, Madison Virginia Polytechnic Institute/University Whitman College Yale University In Process University of Melbourne, Australia University of Toronto, Knowledge Media Design Institute Sakai Educational Partners - Feb 1, 2004

  28. The Sakai Community • Main site:– outward looking • Bugs: – open, active • Sakai-wide collaboration area •; sakai work sites, discussion lists, resources areas; working instance of Sakai • – open mail list, active • – open mail list, active • Sakai Educational Partners (SEPP) • Separate mailing lists, discussion areas; for internal use • Dedicated staff – technical and admin support • Two conferences per year; regular VTCs, phone calls

  29. Working as a larger community - Question Comes from the Public: -- Messaggio Originale – From: [] Sent: Wednesday, November 24, 2004 7:20 AM To: sakai-dev Subject: Re: Add tools to a site Antonio Palermo wrote: I've developed a sakai tool ad I've registered it. To add this tool in a site I manually added it in the file /usr/local/sakai/db/site.xml. Now all works well. Does exist a better way for adding tools to a site?

  30. Subject:     RE: Add tools to a site Date:     Wed, 24 Nov 2004 12:54:05 -0500 (EST) From:     Trevor Bradley <>To:     sakai-dev <>Hello Antonio, I was going through the exact same problem several weeks back.  I also got trapped into the "Worksite Setup" tool, which looks like it's hard-coded only to add a few set, sakai core tools. The procedure to add a new tool is: Log in to your sakai server as admin/admin Create a new site: Click "Sites" at the left sidebar, and fill in the data fields Create a new page: *Before* clicking Save, click the pages button. (… and so on …) Answer comes from a SEPP Partner. Common occurrence now.

  31. Sakaipedia – Home Page Filling growing need for info, and To distribute effort of generating it.

  32. Top Level Structure

  33. Goals • Provide an easy to maintain source of information on Sakai in all of its aspects. • Engage the Sakai community in creating and maintaining content. • Organize information to enable browsing as well as keyword search. • Establish a dialog around Sakai topics.

  34. Sakai KB – Experimenting with a local success

  35. Discussion GroupsCore of the OS Community • Discussion Groups are the high level organizational, and organizing, foci • They are established as members show interest by supporting and participating, and running them • They are your responsibility • SEPP Staff is focused on support of these If you want to see something happen, then make it happen – Start out with the Discussion Group

  36. Importance of Discussion Groups • Transparency • Coordination • Seed ground of ideas • Competitive filter for ideas – peer review of suggestions • High level chunking of interests and functional relationships • Spawning ground of Work Groups – where focus is narrowed, and actual development stream begun – also where efforts like support are centered (not all activities are software development) • WGs should be associated with a more general DG to help communication – eg, UI Review Team (a WG) should participate in the User Interface DG

  37. SEPP DG Leads • SEPP Content and Authoring – Dirk Herr-Hoyman, University of Wisconsin • SEPP Cross Language – Tom Lewis, University of Washington • SEPP Development – Mark J. Norton, Senior Technical Consultant • SEPP Library & Digital Repositories – Bill Parod, Northwestern University and Jim Martino, John Hopkins University • SEPP Migration Strategy – Robert Catalano, Columbia University • SEPP Requirements – Mara Hancock, University of Cal, Berkeley • SEPP Strategy & Advocacy – Chuck Powell, Yale University • SEPP User Interface – Malcolm Brown, Dartmouth University • SEPP User Support - TBD The people with the cool, unique logo on their shirts…

  38. Some Sakai Partner Projects

  39. The Berkeley Grade Book University of California, Berkeley funded development of an on-line grade book. The UC Berkeley grade book is now in pilot on the Berkeley campus as a stand alone tool, and moving into pilot at IU. It is part of the 1.5 release.

  40. Grad Tools The University of Michigan’s Grad Tools provides doctoral students a way of tracking their degree progress from the point of choosing an advisor to degree conferral. Doctoral students create their own site, which contains an automatically personalized dissertation checklist based on data from their department and from the graduate school. Students control access to their Grad Tools site, and use collaboration features common to CTools, including file storage, group email, email notification, structured discussion, and more.

  41. Samigo – Testing and Assessment Part of 1.5 release

  42. Melete – Online Lesson Authoring Tool Foothill College’s Melete, an online lesson authoring environment, is the classroom component of ETUDES (Easy to Use Distance Education Software) that is being rewritten in Java for Sakai-based ETUDES-NG. Melete offers instructors the ability to author online learning modules. Melete features extra controls to assist online teachers/learners, such as the ability to set prerequisites and the pacing of material. The Hewlett Foundation funded deployment of Sakai for the District-based service provided to 48 California community colleges. Part of 2.0 release

  43. Foothill College – Work with Sakai Effort led by Vivian Sinou, Dean of Distance & Mediated Learning • Tools Development • Skins Design • Adoption & Implementation • Pilots & Migration • Training Workshops • Performance Testing Foothill College With support from The William & Flora Hewlett Foundation

  44. ETUDES Consortium – Sakai Pilots to Production 300 faculty from 17 community colleges (highlighted in red on next slide) from the ETUDES Alliance have committed to a pilot of ETUDES-NG (Sakai 1.5 + Samigo + Melete) in the spring and summer of 2005. Three colleges will go into production in the fall. More to follow in the spring. All colleges will migrate to Sakai by July 1, 2007.

  45. ETUDES Consortium – Sakai Pilots College of the Siskiyous Members Outside CA • Stephen F. Austin State University, TX • Harcum College, PA Mendocino College Santa Rosa Junior College Lake Tahoe Community College Vista College Chabot College Laney College College of Alameda Skyline College Foothill College De Anza College Merritt College San Joaquin Delta College West Valley College Porterville College Gavilan College Bakersfield College West Los Angeles College Los Angeles South West Los Angeles ITV Los Angeles City College Los Angeles Harbor College Los Angeles Pierce College Los Angeles Mission College Los Angeles Trade Tech Los Angeles Valley College East Los Angeles College Taft College Antelope Valley College Cerro Coso Community College Crafton Hills College San Bernardino Community College El Camino College Glendale College Long Beach CC Coastline Community College Imperial Valley College Mira Costa College * 300 faculty from 17 community colleges (highlighted in red) from the ETUDES Alliance have committed to a pilot of ETUDES-NG (Sakai 1.5 + Samigo + Melete) in the spring and summer of 2005. Three colleges will go into production in the fall. More to follow in the spring. All colleges will migrate to Sakai by July 1, 2007.

  46. College Brand Skins at Portal Level