Michael Korcuska's presentation on Sakai 3 from the 10th Sakai Conference

1. Friday Session Notes 9:30-10:30am College of the Redwoods - World's fastest Sakai deployment? Formerly Radford Don’t forget about the closing remarks at 3:15 Room Notes Empress is on 14th Floor Charles View is on 16th Floor

2. Sakai 3What and why and when and how? March 2009 Michael Korcuska

3. Why Sakai 3? Functionality & User Experience Technology and Developer Experience Community Practices and Culture

4. Why Sakai 3 Now? The time to repair the roof is when the sun is shining. John F. Kennedy

5. User perspective Why Sakai 3?

6. Sakai 3 for Users 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 6

7. Content Tagging & Management Sakai 3 Themes 7 Content Authoring Academic Networking Breaking the Site Boundary Academic Workflows, not (just) Tools The unSakai

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

9. 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 9

10. Sakai2 ? Site B Site A Users find things by remembering what site they added it to 10

11. Sakai3 Tags: System, Organizational & User Smart Folders Search 11

12. 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 12

13. 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? 13 Content People

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

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

17. Resists intuitive workflows

19. UX oversight is more complicated

20. Workflows built across services

21. Encourages presentation & service separationWorkflow

22. 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 Examples: Open Syllabus, Assignments 2 But it is too difficult and more needs to be done Example: Instructor puts into syllabus an assignment to create a discussionpost that will be graded. 4 tools for both instructors and students! 18

23. Workflow Example 19 Select text & click “Create Assignment” All Media Images Videos Audio Forums Tests Site Pages Polls Jackson Response Forum (3 posts) 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... Class Intro Forum (27 posts) Forums Edit Assignment Information Some Other Forum (0 posts) Create Cancel Advanced Options… Link to Something Choose New…

24. Student View 20 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…)

25. Student View, Graded 21 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)

26. The unSakai Multiple Configurations Sakai as CMS Sakai as Collaboration System Sakai as Portfolio System Sakai Integrations Google Applications Social Networks (Open Social, Facebook) 22

27. The unSakai 23 Kernel Service Service Service iGoogle Facebook Kernel Service Service Service Documented data feeds allow Sakai to appear anywhere Mobile Apps Windows/Mac Widgets

28. unSakai Economics We want to position Sakai for a transition to the “we don’t need no stinking LMS” We don’t care about “owning” the enterprise We aren’t afraid of eroding license fees because other applications take over “core LMS” features

29. Sakai 3 Demo http://3akai.sakaifoundation.org 25

30. Sakai 3 Technology Why Sakai 3?

31. 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 27

32. 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 28

33. The Point Don’t write our own code Criteria: Functionality License-compatible open source Open standard Approachable community

34. 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 30

35. Timelines and adoption

36. Timelines 32 2009 2010 2011 2012 2013 Sakai 2.5 Sakai 2.6 Sakai 2.7 Hybrid Mode Sakai 3.0 Official Releases Previews Sakai 2.8?

37. New Adoptions: 2 or 3? It Depends! Of Course On what? Your production timeline Your appetite for running “.0” software Your functional needs

38. Adopting 2 or 3? 2.6 or 2.7 Sakai 2 works well today 3 doesn’t exist yet The best path to 3 will be through 2 Bb/WebCT migration to 3 is undefined Bb/WebCT migration to 2 is well known Many will be migrating from Sakai 2 to 3 Straight to 3 You don’t have a CMS or you are using something like SharePoint Your production timeline is 2012 or later

39. Adopting 2 or 3? Maybe the wrong question Adopt both! Hybrid mode Sakai 2 for courses, Sakai 3 for project collaboration Gradually move users to Sakai 3

40. Community Practices

41. Community Practices Functional Leadership Design First Minimize Technology Frameworks Quality Focused Unit (and other) Tests

42. Get involved!