Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Sakai 3 Boston

1.186 Aufrufe

Veröffentlicht am

Michael Korcuska's presentation on Sakai 3 at the 10th Sakai Conference in Boston.

Veröffentlicht in: Bildung, Business
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

Sakai 3 Boston

  1. 1. Friday Session Notes<br />9:30-10:30am College of the Redwoods - World&apos;s fastest Sakai deployment?<br />Formerly Radford<br />Don’t forget about the closing remarks at 3:15<br />Room Notes<br />Empress is on 14th Floor<br />Charles View is on 16th Floor<br />
  2. 2. Sakai 3What and why and when and how?<br />March 2009<br />Michael Korcuska<br />
  3. 3. Why Sakai 3?<br />Functionality & User Experience<br />Technology and Developer Experience<br />Community Practices and Culture<br />
  4. 4. Why Sakai 3 Now? <br />The time to repair the roof is when the sun is shining.<br />John F. Kennedy<br />
  5. 5. User perspective<br />Why Sakai 3?<br />
  6. 6. Sakai 3 for Users<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 />6<br />
  7. 7. Content Tagging & Management<br />Sakai 3 Themes<br />7<br />Content Authoring<br />Academic Networking<br />Breaking the Site Boundary<br />Academic Workflows, not (just) Tools<br />The unSakai<br />
  8. 8. Content Authoring<br />Content Basics:<br />Simple page creation (wiki-like)<br />WYSIWG Editing<br />Template-based authoring<br />Versioning<br />Interactive Widgets<br />8<br />
  9. 9. Tagging & Management<br />Everything is content<br />Classic “resources”<br />Discussion post, user profile, test questions<br />Taggable, searchable, linkable, portable<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 />9<br />
  10. 10. Sakai2<br />?<br />Site B<br />Site A<br />Users find things by remembering what site they added it to<br />10<br />
  11. 11. Sakai3<br />Tags: System, Organizational & User<br />Smart Folders<br />Search<br />11<br />
  12. 12. Benefits<br />Web 2.0 “search” interaction supported<br />Tagging & content search<br />Smart Folders retain hierarchical structure if desired<br />Folders for each site, each user and more<br />Portfolio and other “cross-site” needs<br />Tags allow simple aggregation of diverse content<br />Organizational & User tag systems support multiple portfolio requirements<br />12<br />
  13. 13. Academic Networking<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 />13<br />Content<br />People<br />
  14. 14. Sakai 2: Users & Sites<br />14<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 />
  15. 15. 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 />Site A<br />Group 1<br />Group 1.1<br />Site AA<br />Site AB<br />Site B<br />Group 1.2<br />Group 2<br />Site C<br />Group 3<br />15<br />
  16. 16. Kernel<br />Tool<br />Architecture<br />16<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
  17. 17. Resists intuitive workflows
  18. 18. Contributes to inconsistent user experience</li></li></ul><li>Architecture<br />17<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
  19. 19. UX oversight is more complicated
  20. 20. Workflows built across services
  21. 21. Encourages presentation & service separation</li></ul>Workflow<br />
  22. 22. 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 />Examples: Open Syllabus, Assignments 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 />18<br />
  23. 23. Workflow Example<br />19<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 />
  24. 24. Student View<br />20<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 />
  25. 25. Student View, Graded<br />21<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 />
  26. 26. 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 />22<br />
  27. 27. The unSakai<br />23<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 />
  28. 28. unSakai Economics<br />We want to position Sakai for a transition to the “we don’t need no stinking LMS”<br />We don’t care about “owning” the enterprise<br />We aren’t afraid of eroding license fees because other applications take over “core LMS” features<br />
  29. 29. Sakai 3 Demo<br />http://3akai.sakaifoundation.org<br />25<br />
  30. 30. Sakai 3 Technology<br />Why Sakai 3?<br />
  31. 31. 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 />27<br />
  32. 32. 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 />28<br />
  33. 33. The Point<br />Don’t write our own code<br />Criteria:<br />Functionality<br />License-compatible open source<br />Open standard<br />Approachable community<br />
  34. 34. 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 />30<br />
  35. 35. Timelines and adoption<br />
  36. 36. Timelines<br />32<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 />
  37. 37. New Adoptions: 2 or 3?<br />It Depends!<br />Of Course<br />On what?<br />Your production timeline<br />Your appetite for running “.0” software<br />Your functional needs<br />
  38. 38. Adopting 2 or 3?<br />2.6 or 2.7<br />Sakai 2 works well today<br />3 doesn’t exist yet<br />The best path to 3 will be through 2<br />Bb/WebCT migration to 3 is undefined<br />Bb/WebCT migration to 2 is well known<br />Many will be migrating from Sakai 2 to 3<br />Straight to 3<br />You don’t have a CMS or you are using something like SharePoint<br />Your production timeline is 2012 or later<br />
  39. 39. 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 />
  40. 40. Community Practices<br />
  41. 41. Community Practices<br />Functional Leadership<br />Design First<br />Minimize Technology Frameworks<br />Quality Focused<br />Unit (and other) Tests<br />
  42. 42. Get involved!<br />