38
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 14 th Floor Charles View is on 16 th Floor

Sakai 3 Boston

  • View
    1.803

  • Download
    1

Embed Size (px)

DESCRIPTION

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

Citation preview

Page 1: Sakai 3 Boston

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

Page 2: Sakai 3 Boston

Sakai 3What and why and when and

how?March 2009

Michael Korcuska

Page 3: Sakai 3 Boston

Why Sakai 3?

Technology and Developer Experience

Functionality & User Experience

Community Practices and Culture

Page 4: Sakai 3 Boston

Why Sakai 3 Now?

The time to repair the roof is when the sun is shining.

John F. Kennedy

Page 5: Sakai 3 Boston

USER PERSPECTIVEWhy Sakai 3?

Page 6: Sakai 3 Boston

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

Page 7: Sakai 3 Boston

7

Content Tagging & Management

Sakai 3 Themes

Content Authoring

Academic Networking Breaking the Site Boundary

Academic Workflows, not (just) Tools The unSakai

Page 8: Sakai 3 Boston

8

Content Authoring

• Content Basics:• Simple page creation (wiki-

like)• WYSIWG Editing• Template-based authoring• Versioning

• Interactive Widgets

Page 9: Sakai 3 Boston

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

Page 10: Sakai 3 Boston

10

Sakai 2

Site A Site B

Users find things by remembering what site they added it to

?

Page 11: Sakai 3 Boston

11

Tags: System, Organizational & User

Search

Sakai 3

Smart Folders

Page 12: Sakai 3 Boston

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

Page 13: Sakai 3 Boston

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?

Content People

Page 14: Sakai 3 Boston

14

Sakai 2: Users & Sites

Site A Site B

Group A1

User 1User 2User 3User 4User 5...User N

Group B1

User 1User 2User 3User 4User 5...User N

Users and groups exist within the context of a site.

Page 15: Sakai 3 Boston

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

15

Site A

Site B

Site C

Group 2

Group 3

Group 1Group 1.1Site AA

Site AB Group 1.2

Page 16: Sakai 3 Boston

16

Kernel

Tool

ToolTool

Tool

Tool

Tool

Architecture

Kernel

Service ServiceService

Service

Serv

iceSe

rvice

• Facilitates independent tool development

• Resists intuitive workflows• Contributes to inconsistent

user experience

Kernel

Page 17: Sakai 3 Boston

17

Architecture

Kernel

Workflow

Workflow

WorkflowWorkflow

Wor

kflow

Workflow

Kernel

Service ServiceService

Service

Serv

iceSe

rvice

Kernel

• Workflows built across services• Encourages presentation &

service separation

• Services need to respond to more customers• UX oversight is more

complicated

Page 18: Sakai 3 Boston

18

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 discussion post that will be graded.• 4 tools for both instructors and students!

Page 19: Sakai 3 Boston

19

Workflow Example

Week Readings Activities & Assignments

1 Course PoliciesTextbook Chapter 1

2 Textbook Chapter 2Jackson Article

Write a response to Jackson article & post to discussion forum

Create Assignment…Name: Jackson Reading ResponseDue Date: September 10, 2009Points: 10 (of 150)Type: IndividualDescription: Respond to the Jackson article in no more than 500 words. Post that response to the class discussion forum.Link To: Select...

CreateCancelAdvanced Options…

Select text & click “Create Assignment”

Edit Assignment Information

Link to Something

AllMedia

ImagesVideosAudio

ForumsTestsSite PagesPolls

ChooseNew…

Forums

Jackson Response Forum (3 posts)

Class Intro Forum (27 posts)

Some Other Forum (0 posts)

Page 20: Sakai 3 Boston

20

Student View

Week Readings Activities & Assignments

1 Course PoliciesTextbook Chapter 1

2 Textbook Chapter 2Jackson Article

Write a response to Jackson article & post to discussion forumAssignment: Jackson Reading Response

Due Date: September 10, 2009 ( due tomorrow)Status: Not submittedPoints: 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…)

Page 21: Sakai 3 Boston

21

Student View, Graded

Week Readings Activities & Assignments

1 Course PoliciesTextbook Chapter 1

2 Textbook Chapter 2Jackson Article

Write a response to Jackson article & post to discussion forum

Assignment: Jackson Reading ResponseDue Date: September 10, 2009 (due date passed)Status: Submitted and GradedPoints: 9/10 (of 150). View feedbackDescription: 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)

Page 22: Sakai 3 Boston

22

The unSakai

• Multiple Configurations• Sakai as CMS• Sakai as Collaboration System• Sakai as Portfolio System

• Sakai Integrations• Google Applications• Social Networks (Open Social, Facebook)

Page 23: Sakai 3 Boston

23

The unSakai

Kernel

Service ServiceService

Service

Serv

iceSe

rvice

Kernel

iGoogle

Windows/Mac Widgets Mobile Apps

Facebook

Documented data feeds allow Sakai to appear anywhere

Page 24: Sakai 3 Boston

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

Page 25: Sakai 3 Boston

25

SAKAI 3 DEMO

http://3akai.sakaifoundation.org

Page 26: Sakai 3 Boston

SAKAI 3 TECHNOLOGYWhy Sakai 3?

Page 27: Sakai 3 Boston

27

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

Page 28: Sakai 3 Boston

28

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

Page 29: Sakai 3 Boston

The Point

• Don’t write our own code• Criteria:• Functionality• License-compatible open source• Open standard• Approachable community

Page 30: Sakai 3 Boston

30

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

Page 31: Sakai 3 Boston

TIMELINES AND ADOPTION

Page 32: Sakai 3 Boston

32

Official Releases

Timelines

Sakai 2.6

Sakai 2.7

Sakai 3.0

2009 2010 2011 2012 2013

Previews

HybridMode

Sakai 2.5

Sakai 2.8?

Page 33: Sakai 3 Boston

New Adoptions: 2 or 3?

• It Depends!• Of Course

• On what?• Your production timeline• Your appetite for running “.0” software• Your functional needs

Page 34: Sakai 3 Boston

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

Page 35: Sakai 3 Boston

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

Page 36: Sakai 3 Boston

COMMUNITY PRACTICES

Page 37: Sakai 3 Boston

Community Practices

• Functional Leadership• Design First• Minimize Technology Frameworks• Quality Focused• Unit (and other) Tests

Page 38: Sakai 3 Boston

GET INVOLVED!