2. SAKAI 3 MICHAEL KORCUSKA March 2009

3. Why Sakai 3?  Changing expectations  Google docs/apps, Social Networking, Web 2.0  Success of project sites = Sakai beyond courses  New technologies  Standards-based, open source projects JCR (Jackrabbit) Open Social (Shindig)  Client-side programming JavaScript/AJAX

4. Content Tagging & Management Sakai 3 Themes Content Authoring Academic Networking Breaking the Site Boundary Academic Workflows, not (just) Tools Sakai, Thick or Thin Sakai Everywhere

5. Content Authoring  Content Basics:  Simple page creation (wiki- like)  WYSIWG Editing  Template-based authoring  Versioning  Interactive Widgets

6. Tagging & Management  Everything is content  Classic “resources”  Discussion post, user profile, test questions  Taggable, searchable, linkable, portable  Unified content repository  Content not tied to site  Everything in one storage area  BUT: Sakai is not a full Content Management System

7. Sakai 2 Site A Site B Finding something requires knowing which site it belongs to. ? ?

8. Tags: System, Organizational & User Search Sakai 3 Smart Folders

9. Benefits  Web 2.0 “search” interaction supported  Tagging & content search  Smart Folders retain hierarchical structure if desired  Folders for each site, each user and more  Portfolio and other “cross-site” needs  Tags allow simple aggregation of diverse content  Organizational & User tag systems support multiple portfolio requirements

10. Academic Networking  Academic Networking  People are important, but “friends” aren’t enough  Content-based – Who is reading the same articles?  Activity based – Who has taken the same classes?

11. Sakai 2: Users & Sites Site A Site B Group A1 User 1 User 2 User 3 User 4 User 5. User N Group B1 User 1 User 2 User 3 User 4 User 5. User N Users and groups exist within the context of a site.

12.  Groups & Sites managed separately Member of a group – People with something in common Access to a site– Collection of content & functionality Support for hierarchy Sakai 3 Groups & Sites Site A Site B Site C Group 2 Group 3 Group 1 Group 1.1 Site AA Site AB Group 1.2

13. Academic Workflow  Beyond Tool Silos  Academic work flows often cross tool boundaries Anything can be graded! Anything can be discussed!  This is beginning to appear in Sakai 2 But more needs to be done  Example: Instructor puts into syllabus an assignment to create a discussion post that will be graded.  4 tools for both instructors and students!

14. Kernel Tool Sakai 2 Architecture Kernel Service Facilitates independent tool development Resists intuitive workflows Contributes to inconsistent user experience Kernel

15. Sakai 3 Architecture Kernel Workflow Kernel Service Kernel Workflows built across services Encourages presentation & service separation Services need to respond to more customers UX oversight is more complicated

16. Workflow Example WeekReadingsActivities & Assignments 1Course Policies Textbook Chapter 1 2Textbook Chapter 2 Jackson Article Write a response to Jackson article & post to discussion forum Create Assignment… Name: Jackson Reading Response Due Date: September 10, 2009 Points: 10 (of 150) Type: Individual Description: Respond to the Jackson article in no more than 500 words. Post that response to the class discussion forum. Link To: Select... Create CancelAdvanced Options… Select text & click “Create Assignment” Edit Assignment Information Link to Something All Media Images Videos Audio Forums Tests Site Pages Polls Choose New… Forums Jackson Response Forum (3 posts) Class Intro Forum (27 posts) Some Other Forum (0 posts)

17. Student View WeekReadingsActivities & Assignments 1Course Policies Textbook Chapter 1 2Textbook Chapter 2 Jackson Article Write a response to Jackson article & post to discussion forum Assignment: Jackson Reading Response Due Date: September 10, 2009 ( due tomorrow) Status: Not submitted Points: 10 possible (of 150). Description: Respond to the Jackson article in no more than 500 words. Post that response to the class discussion forum. Read more… Link(s): Jackson Response Discussion Forum (Create Post…)

18. Student View, Graded WeekReadingsActivities & Assignments 1Course Policies Textbook Chapter 1 2Textbook Chapter 2 Jackson Article Write a response to Jackson article & post to discussion forum Assignment: Jackson Reading Response Due Date: September 10, 2009 (due date passed) Status: Submitted and Graded Points: 9/10 (of 150). View feedback Description: Respond to the Jackson article in no more than 500 words. Post that response to the class discussion forum. Read more… Link(s): Jackson Response Discussion Forum (go to Forum now)

19. Sakai, Thick or Thin  Multiple Configurations  Sakai as CMS  Sakai as Collaboration System  Sakai as Portfolio System  Sakai Integrations  Google Applications  Social Networks (Open Social, Facebook)

20. Sakai Everywhere Kernel Service Kernel iGoogle Windows/Mac Widgets Mobile Apps Facebook Documented data feeds allow Sakai to appear anywhere

21. http://3akai.sakaifoundation.org Sakai 3 Demo

23. Sakai 3 Technology Goals  Scalability  Remove bottlenecks from Sakai 2  Improve cluster support  Developer Productivity  Faster builds  UX & back-end development separated  Code Quality & Maintenance  Reliance on other open source efforts  Increase unit testing  Easier to install/build  To improve initial experience for new developers

24. JCR as Content Store  Standards-based  JSR 170  Ships with Apache Jackrabbit, but can be changed  Everything as content  Discussion post, User profile information, etc.  Components put Content into JCR Content store  Sakai Kernel creates relational indices in DB Component doesn’t need to do anything Automatic tracking of most events by kernel

25. JSON  Sakai Kernel supports JSON microformat  Components use REST calls to interact with Kernel  Again, standards based  JAX-RS currently in Kernel (JSR 311)  Benefits  Back-end services stay Java-based  UX programmers more often skilled in JavaScript Easier UX developers can work on Sakai  Tools like GWT can be used for Java-based UI  Components can be written using other languages

26. Sakai 3 Participation  K2 Working Group  http://groups.google.com/group/sakai-kernel  UX Design Work  UX list  http://groups.google.com/group/3akai  How would you like to be involved?  Development Java & JavaScript  Design Conceptual, interaction and visual

27. When  Q1 2009: Sakai 2.6  Q3 2009: Sakai 2.6.#  A maintenance release for fall production  2010  Q1: Sakai 2.7 (New assignments tool and gradebook?)  Later: First versions of Sakai 3 Not functionally equivalent to 2.7 Suitable for new adoptions “Hybrid” version for existing Sakai schools  2011  Sakai 3 as full replacement  Maintenance releases for Sakai 2.7 through 2013  No version 2.8

28. Thank You!