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.

Sakai 3, version 8

4,908 views

Published on

The basis for my poster session at Educause 2009 in Devner

Published in: Education, Technology

Sakai 3, version 8

  1. 1. Sakai 3: An Overview<br />Michael Korcuska<br />Executive Director<br />Sakai Foundation<br />
  2. 2. Sakai 3: Why?<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 />Fluid Project (fluidproject.org)<br />Years of hard-won knowledge<br />2<br />
  3. 3. Why Now? <br />Proto by Hubert Stoffels<br />The time to repair the roof is when the sun is shining.<br />John F. Kennedy<br />
  4. 4. What?<br />Photos by Hobvias Sudoneighm, Massimo Valiani, and Mathieu Plourde<br />Functionality & User Experience<br />Technology and Developer Experience<br />Community Practices and Culture<br />
  5. 5. End User perspective<br />Sakai 3<br />
  6. 6. Content Organization, Searching & Tagging<br />Sakai 3 Themes<br />6<br />Learning Space Construction<br />Breaking the Site Boundary<br />Customizable Workflows (No Tool Silos)<br />Academic Networking<br />The unSakai<br />Open Teaching<br />
  7. 7. Learning Space Construction<br />1<br />Photos by Cyprien Lomas<br />Really “Scholarly Space”<br />Teaching & Learning plus….<br />Research, collaboration and portfolios<br />Principles<br />Embrace participant content creation<br />Simple integration of interactive options<br />Author(s) control presentation and workflow<br />
  8. 8. Academic Spaces: Building Blocks<br />Simple Content Authoring:<br />Easy page creation (wiki-like)<br />WYSIWYG Editing<br />Templates (page and site)<br />Versioning<br />Enhanced with Academic Functionality<br />Interactive Widgets (e.g. assignments & feedback)<br />Allows integration of content and activities<br />8<br />
  9. 9. Templates<br />Templates provide scaffolding for majority of users<br />But can be bypassed for advanced needs<br />Page Templates<br />Sections with (editable) content<br />Site Templates<br />Predefined pages and dashboards<br />
  10. 10. Everything is Content<br /> Not just files to share<br />Classic “resources” tool in Sakai (of course)<br />Discussion post, user profile, test questions<br />Taggable, searchable, linkable, portable, shareable<br />Unified content repository<br />Content not tied to site<br />Everything in one storage area<br />BUT: Sakai is not a full Content Management System<br />No complex approval workflows<br />No fancy layout capabilities<br />Everyone is an author in Sakai<br />10<br />2<br />
  11. 11. Content Management<br />Sakai2<br />Photo by Desirée Delgado<br />Site A<br />Site B<br />Users find things by remembering what site they were in when they saw it.<br />11<br />
  12. 12. Content Management<br />Sakai3<br />Photo by Amy Veeninga<br />Tags: System, Organizational & User<br />Permissions: Who has access, under what conditions<br />Smart Folders<br />Search<br />12<br />
  13. 13. Academic Networking<br />Academic Networking<br />People are important, but “friends” aren’t enough<br />Related content is also relevant, but not the whole story<br />Activity based <br />Who has taken the same classes?<br />Who is reading the same articles? Participating in similar discussions?<br />13<br />3<br />Content<br />People<br />
  14. 14. Academic Networking<br />A platform for exploration<br />We aren’t competing with Facebook<br />We do believe we need to drive R&D in this area<br />Linking networks together<br />Sakai to Sakai<br />Sakai, Moodle, Blackboard, D2L<br />Leveraging existing networks<br />Particularly LinkedIn and Facebook<br />Sharing profile and activity information<br />Creating apps on those platforms<br />Photo by Joël-Evelyñ-FrançoisDézafit-Keltz<br />
  15. 15. The Site Boundary<br />15<br />4<br />All Art Students<br />Studio Art 101<br />User 100<br />User 2<br />User 3<br />User 4<br />User 500<br />.<br />.<br />.<br />User 1<br />User 2<br />User 3<br />User 4<br />User 5<br />.<br />.<br />.<br />Year 1 Art Students<br />Year 1 Art Students<br />Users and groups exist within the context of a site.<br />
  16. 16. Sakai 3 Groups & Sites<br />Groups & Sites managed separately<br />Member of a group – People with something in common<br />Access to a site– Collection of content & functionality<br />Support for hierarchy<br />Art Dept.<br />Art Majors<br />Art Majors<br />Studio 101 Students<br />Studio 101<br />Guest Judges<br />Student Work<br />16<br />
  17. 17. Workflow & Architecture<br />17<br />5<br />Kernel<br />Tool<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
  18. 18. Resists intuitive workflows
  19. 19. Contributes to inconsistent user experience</li></li></ul><li>Workflow & Architecture<br />18<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 /><ul><li>Services need to respond to more customers
  20. 20. UX oversight is more complicated
  21. 21. Workflows built across services
  22. 22. Encourages presentation & service separation</li></ul>Workflow<br />
  23. 23. 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 exists in Sakai 2<br />But it is too difficult and 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 />19<br />Photo by Zoom Zoom<br />
  24. 24. Workflow Example<br />20<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 />
  25. 25. Student View<br />21<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 />
  26. 26. Student View, Graded<br />22<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 />
  27. 27. The unSakai<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 />23<br />6<br />
  28. 28. The unSakai<br />24<br />Kernel<br />Service<br />Service<br />Service<br />iGoogle<br />Facebook<br />Kernel<br />Service<br />Service<br />Service<br />Documented data feeds allow Sakai to appear anywhere<br />Mobile Apps<br />Windows/Mac Widgets<br />
  29. 29. Open Teaching<br />Easy to make (parts of) course sites public<br />or .auth<br />Connections to OER repositories?<br />Inbound, Outbound<br />
  30. 30. Sakai 3 Functional Architecture<br />Public<br />Users<br />Groups<br />Collaboration Spaces<br />Personal Spaces<br />PLE<br />Learning<br />Research<br />Project<br />Portfolio<br />Profile<br />Meaningful Arrangements<br />Dynamic, Collaborative Pages<br />Dashboards<br />Defined & Custom Workflows<br />Fundamental Capabilities<br />Wiki-like Content Editing<br />Page Templates<br />Interactive Widgets<br />Unified Content Repository<br />Authored Pages<br />Uploaded Files<br />Contextual Content<br />
  31. 31. Sakai 3 Technology<br />Why Sakai 3?<br />
  32. 32. Sakai 3 Technology Goals<br />Scalability<br />Millions of users<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 />28<br />Photo by Luiz Castro<br />
  33. 33. Using Open Source<br />Don’t write our own code<br />If we can help it<br />Criteria:<br />Functionality<br />License-compatible open source<br />Open standard<br />Approachable community<br />
  34. 34. Sakai and Apache<br />Sakai 3 Kernel built on Apache Sling<br />RESTful web development framework for content management<br />Sling incorporates Jackrabbit and Felix<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 />30<br />
  35. 35. Sling Mindset<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 />Philosophy similar to CouchDB<br />Will require developer education<br />
  36. 36. JSON<br />Sakai Kernel supports JSON microformat<br />Components use REST calls to interact with Kernel<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 />32<br />
  37. 37. Community Practices<br />
  38. 38. Community Practices<br />Functional Leadership<br />Design First<br />Minimize Technology Frameworks<br />Quality Focused<br />Unit (and other) Tests<br />
  39. 39. Timelines and adoption<br />
  40. 40. Timelines<br />36<br />2009<br />2010<br />2011<br />2012<br />2013<br />Sakai 2.5<br />Sakai 2.6<br />Sakai 2.7<br />Hybrid<br />Mode<br />Sakai 3.0<br />Official Releases<br />Previews<br />Sakai 2.8?<br />
  41. 41. Adopting Sakai<br />Adopt 2 or 3?<br />Not the first question to answer<br />First Question:<br />Yes! Or probably<br />Do you want to be using Sakai (and be in the community) in the long run?<br />We can help you figure out how to get there<br />
  42. 42. Path to Sakai<br />Straight to 3? Start with 2?<br />It Depends!<br />What did you expect?<br />On what?<br />Your production timeline<br />Your appetite for “.0” software<br />Your functional needs<br />Your support model<br />
  43. 43. Adopting 2 or 3?<br />Sakai 2.6 or 2.7<br />Sakai 2 works well today<br />3 doesn’t exist yet<br />Sakai 2 will be a good path to Sakai 3<br />Bb/WebCT migration to 2 is well known<br />Many will be migrating from Sakai 2 to 3<br />Straight to Sakai 3<br />You don’t have a CMS or you are using something like SharePoint<br />Your production timeline is 2012 or later<br />You have a very strong preference for Sakai 3<br />
  44. 44. Adopting 2 or 3?<br />Maybe the wrong question<br />Adopt both!<br />Hybrid mode<br />Sakai 2 for courses, Sakai 3 for project collaboration<br />Gradually move users to Sakai 3<br />

×