Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Ja Sakai 09 V01


Published on

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

Ja Sakai 09 V01

  1. 1. Sakai UpdateMichael Korcuska<br />March 17, 2009. Nagoya, Japan<br />
  2. 2. About Sakai<br />
  3. 3. Sakai History<br />Courseware Management System<br />Started in 2004 <br />Michigan, Indiana, Stanford, MIT (and Berkeley)<br />Mellon Foundation Grant<br />2.6 release in QA<br />
  4. 4. Why Start Sakai?<br />5 Schools with Homegrown CMS<br />Inefficient to build 5 systems<br />Wanted to maintain control<br />Experts in teaching and learning<br />Desire to work together and share knowledge<br />
  5. 5. Why Sakai?<br />Stanford wrote about 20% of the original code in Sakai. What we have received in return is five times what we have put in, a tremendous return on investment. The value of community source is very real to us.<br />Lois Brooks<br />Director of Academic Computing <br />Stanford University<br />Coursework, Stanford University<br />
  6. 6. Course Management<br />Research & Collaboration<br />Sakaibrary<br />Portfolios<br />Defining Sakai: Product Scope<br />COURSE MANAGEMENT — all the tools of a modern course management system.<br />RESEARCH & COLLABORATION — project sites for research and work group collaboration.<br />SAKAIBRARY — Library-led component to add citations directly into Sakai.<br />PORTFOLIOS — Open Source Portfolio (OSP) is a core part of Sakai.<br />
  7. 7. Defining Sakai: Community<br />COMPOSITION — educational institutions & commercial enterprises working in partnership with standards bodies & other open-source initiatives.<br />GOALS — work collaboratively to develop innovative software applications designed to enhance teaching, learning, research & collaboration in education.<br />VALUES — knowledge sharing, information transparency, meritocracy.<br />Educational Institutions<br />Standards <br />Bodies<br />Open Source<br />Commercial Affiliates<br />
  8. 8. Sakai on the ground<br />200+ PRODUCTION/PILOT DEPLOYMENTS: From 200 to 200,000 users<br />
  9. 9. Sakai on the ground<br />5 of top 10 Universities run Sakai<br />Stanford<br />Berkeley<br />Cambridge<br />Columbia<br />Oxford<br />#11 also runs Sakai (Yale)<br />
  10. 10. Sakai on the ground<br />CTOOLS, University of Michigan<br />First production Sakai deployment, 2004<br />
  11. 11. Defining Sakai: Code<br />OPEN LICENSING — Sakai’s software is made available under the terms of the ECL, a variant of the Apache license. The ECL encourages a wide range of use, including commercial use. <br />NO FEES OR ROYALTIES — Sakai is free to acquire, use, copy, modify, merge, publish, redistribute & sublicense for any purpose provided our copyright notice & disclaimer are included.<br />NO “COPYLEFT” RESTRICTIONS — unlike GPL redistributed derivative works are neither required to adopt the Sakai license nor publish the source code as open-source.<br />EDUCATIONAL COMMUNITY LICENSE (ECL)<br />
  12. 12. Increasing Global Diversity<br />In 2006, 81% were in North America<br />
  13. 13. Defining Sakai: Foundation<br />MISSION — manage & protect intellectual property; provide basic infrastructure & small staff; help coordinate design, development, testing & distribution of software; champion open source & open standards.<br />GOVERNANCE — ten board members elected by member reps to serve three-year terms; Executive Director manages day-to-day operations.<br />PARTNERS — over 100 member organizations contribute $10K per year ($5K for smaller institutions).<br />BUDGET — funds 4-6 staffers, admin services, computing infrastructure, project coordination, conferences, Sakai Fellows Program, advocacy & outreach activities.<br />
  14. 14. Why Sakai?<br />UCT decided to move to open source in 2004, migrating from WebCT & a home-grown system. Open source offers the advantages of flexibility & avoids the risks of vendor lock-in & escalating license costs. We were attracted to Sakai by the size & expertise of the community around it.<br />Stephen Marquard, Learning Technologies Coordinator, <br />University of Cape Town <br />
  15. 15. Why Sakai 3?<br />Changing expectations<br />Google docs/apps, Social Networking, Web 2.0<br />Success of project sites = Sakai beyond courses<br />New technologies<br />Standards-based, open source projects<br />JCR (Jackrabbit)<br />Open Social (Shindig)<br />Client-side programming<br />JavaScript/AJAX<br />
  16. 16. Sakai 3 Themes<br />Content Authoring and Management<br />Academic Networking<br />Breaking the Site Boundary<br />Academic Workflows, not (just) Tools<br />Sakai, Thick or Thin<br />Sakai Everywhere<br />
  17. 17. Content<br />Content Basics:<br />Simple page creation (wiki-like)<br />WYSIWG Editing<br />Template-based authoring<br />Versioning<br />Interactive Widgets<br />Everything is content<br />Searchable, linkable, portable<br />Unified content repository<br />
  18. 18. Sakai2<br />Site B<br />Site A<br />?<br />Finding something requires knowing which site it belongs to.<br />
  19. 19. Sakai3<br />Tags: System, Organizational & User<br />Search + Smart Folders<br />
  20. 20. Academic Networking<br />Content<br />People<br />Academic Networking<br />People are important, but “friends” aren’t enough<br />Content-based – Who is reading the same articles?<br />Activity based – Who has taken the same classes?<br />
  21. 21. Sakai 2: Users & Sites<br />Site A<br />Site B<br />User 1<br />User 2<br />User 3<br />User 4<br />User 5<br />.<br />.<br />.<br />User N<br />User 1<br />User 2<br />User 3<br />User 4<br />User 5<br />.<br />.<br />.<br />User N<br />Group B1<br />Group A1<br />Users and groups exist within the context of a site.<br />
  22. 22. Groups & Sites (call them spaces?) Separated<br />Member of a group – People with something in common<br />Access to a space – Collection of content & functionality<br />Support for hierarchy<br />Sakai 3 Groups & Sites<br />Group 1.1<br />Space AA<br />Space A<br />Group 1<br />Space AB<br />Group 1.2<br />Space B<br />Group 2<br />Space C<br />Group 3<br />
  23. 23. Kernel<br />Tool<br />Sakai 2 Architecture<br />Kernel<br />Service<br />Tool<br />Tool<br />Service<br />Service<br />Kernel<br />Service<br />Service<br />Tool<br />Tool<br />Service<br />Tool<br /><ul><li>Facilitates independent tool development
  24. 24. Resists intuitive workflows
  25. 25. Contributes to inconsistent user experience</li></li></ul><li>Sakai 3 Architecture<br />Kernel<br />Workflow<br />Kernel<br />Service<br />Workflow<br />Workflow<br />Service<br />Service<br />Kernel<br />Service<br />Service<br />Workflow<br />Workflow<br />Service<br />Workflow<br /><ul><li>Services need to respond to more customers
  26. 26. UX oversight is more complicated
  27. 27. Workflows built across services
  28. 28. Encourages presentation & service separation</li></li></ul><li>Academic Workflow<br />Beyond Tool Silos<br />Academic work flows often cross tool boundaries<br />Anything can be graded!<br />Anything can be discussed!<br />This is beginning to appear in Sakai 2<br />But more needs to be done<br />Example: Instructor puts into syllabus an assignment to create a discussionpost that will be graded.<br />4 tools for both instructors and students!<br />
  29. 29. Academic Workflow Example<br />Select text & click “Create Assignment”<br />All<br />Media<br />Images<br /> Videos<br /> Audio<br />Forums<br />Tests<br />Site Pages<br />Polls<br />Jackson Response Forum (3 posts)<br />Create Assignment…<br />Name: Jackson Reading Response<br />Due Date: September 10, 2009<br />Points: 10 (of 150)<br />Type: Individual<br />Description:Respond to the Jackson article in no more than 500 words. Post that response to the class discussion forum.<br />Link To: Select...<br />Class Intro Forum (27 posts)<br />Forums<br />Edit Assignment Information<br />Some Other Forum (0 posts)<br />Create<br />Cancel<br />Advanced Options…<br />Link to Something<br />Choose<br />New…<br />
  30. 30. Student View<br />Assignment: Jackson Reading Response<br />Due Date: September 10, 2009 ( due tomorrow)<br />Status: Not submitted<br />Points: 10 possible (of 150).<br />Description:Respond to the Jackson article in no more than 500 words. Post that response to the class discussion forum. Read more…<br />Link(s): Jackson Response Discussion Forum (Create Post…)<br />
  31. 31. Student View, Graded<br />Assignment: Jackson Reading Response<br />Due Date: September 10, 2009 (due date passed)<br />Status: Submitted and Graded<br />Points: 9/10 (of 150). View feedback<br />Description:Respond to the Jackson article in no more than 500 words. Post that response to the class discussion forum. Read more…<br />Link(s): Jackson Response Discussion Forum (go to Forum now)<br />
  32. 32. Sakai, Thick or Thin<br />Multiple Configurations<br />Sakai as CMS<br />Sakai as Collaboration System<br />Sakai as Portfolio System<br />Sakai Integrations<br />Google Applications<br />Social Networks (Open Social, Facebook) <br />Sakai does not need to do everything for everyone<br />
  33. 33. Sakai Everywhere<br />
  34. 34.<br />Sakai 3 Demo<br />
  35. 35.
  36. 36. Sakai 3 Technology Goals<br />Scalability<br />Remove bottlenecks from Sakai 2<br />Improve cluster support<br />Developer Productivity<br />Faster builds<br />UX & back-end development separated<br />Code Quality & Maintenance<br />Reliance on other open source efforts<br />Increase unit testing<br />Easier to install/build<br />To improve initial experience for new developers<br />
  37. 37. JCR as Content Store<br />Standards-based<br />JSR 170<br />Ships with Apache Jackrabbit, but can be changed<br />Everything as content<br />Discussion post, User profile information, etc.<br />Components put Content into JCR Content store<br />Sakai Kernel creates relational indices in DB<br />Component doesn’t need to do anything<br />Automatic tracking of most events by kernel<br />
  38. 38. JSON<br />Sakai Kernel supports JSON microformat<br />Components use REST calls to interact with Kernel<br />Again, standards based<br />JAX-RS currently in Kernel (JSR 311)<br />Benefits<br />Back-end services stay Java-based<br />UX programmers more often skilled in JavaScript<br />Easier UX developers can work on Sakai<br />Tools like GWT can be used for Java-based UI<br />Components can be written using other languages<br />
  39. 39. Sakai 3 Participation<br />K2 Working Group<br /><br />UX Design Work<br />UX list<br /><br />How would you like to be involved?<br />Development<br />Java & JavaScript<br />Design<br />Conceptual, interaction and visual<br />
  40. 40. When<br />Q1 2009: Sakai 2.6<br />Q3 2009: Sakai 2.6.#<br />A maintenance release for fall production<br />2010<br />Q1: Sakai 2.7 (New assignments tool and gradebook?)<br />Later: First versions of Sakai 3<br />Not functionally equivalent to 2.7<br />Suitable for new adoptions<br />“Hybrid” version for existing Sakai schools<br />2011<br />Sakai 3 as full replacement<br />Maintenance releases for Sakai 2.7 through 2013<br />No version 2.8<br />
  41. 41. ありがとうございました<br />