Your SlideShare is downloading. ×
Ja Sakai 09 V01
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Ja Sakai 09 V01

841
views

Published on

Published in: Education, Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
841
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Sakai UpdateMichael Korcuska
    March 17, 2009. Nagoya, Japan
  • 2. About Sakai
  • 3. Sakai History
    Courseware Management System
    Started in 2004
    Michigan, Indiana, Stanford, MIT (and Berkeley)
    Mellon Foundation Grant
    2.6 release in QA
  • 4. Why Start Sakai?
    5 Schools with Homegrown CMS
    Inefficient to build 5 systems
    Wanted to maintain control
    Experts in teaching and learning
    Desire to work together and share knowledge
  • 5. Why Sakai?
    Stanford wrote about 20% of the original code in Sakai. What we have received in return is five times what we have put in, a tremendous return on investment. The value of community source is very real to us.
    Lois Brooks
    Director of Academic Computing
    Stanford University
    Coursework, Stanford University
  • 6. Course Management
    Research & Collaboration
    Sakaibrary
    Portfolios
    Defining Sakai: Product Scope
    COURSE MANAGEMENT — all the tools of a modern course management system.
    RESEARCH & COLLABORATION — project sites for research and work group collaboration.
    SAKAIBRARY — Library-led component to add citations directly into Sakai.
    PORTFOLIOS — Open Source Portfolio (OSP) is a core part of Sakai.
  • 7. Defining Sakai: Community
    COMPOSITION — educational institutions & commercial enterprises working in partnership with standards bodies & other open-source initiatives.
    GOALS — work collaboratively to develop innovative software applications designed to enhance teaching, learning, research & collaboration in education.
    VALUES — knowledge sharing, information transparency, meritocracy.
    Educational Institutions
    Standards
    Bodies
    Open Source
    Commercial Affiliates
  • 8. Sakai on the ground
    200+ PRODUCTION/PILOT DEPLOYMENTS: From 200 to 200,000 users
  • 9. Sakai on the ground
    5 of top 10 Universities run Sakai
    Stanford
    Berkeley
    Cambridge
    Columbia
    Oxford
    #11 also runs Sakai (Yale)
  • 10. Sakai on the ground
    CTOOLS, University of Michigan
    First production Sakai deployment, 2004
  • 11. Defining Sakai: Code
    OPEN LICENSING — Sakai’s software is made available under the terms of the ECL, a variant of the Apache license. The ECL encourages a wide range of use, including commercial use.
    NO FEES OR ROYALTIES — Sakai is free to acquire, use, copy, modify, merge, publish, redistribute & sublicense for any purpose provided our copyright notice & disclaimer are included.
    NO “COPYLEFT” RESTRICTIONS — unlike GPL redistributed derivative works are neither required to adopt the Sakai license nor publish the source code as open-source.
    EDUCATIONAL COMMUNITY LICENSE (ECL)
  • 12. Increasing Global Diversity
    In 2006, 81% were in North America
  • 13. Defining Sakai: Foundation
    MISSION — manage & protect intellectual property; provide basic infrastructure & small staff; help coordinate design, development, testing & distribution of software; champion open source & open standards.
    GOVERNANCE — ten board members elected by member reps to serve three-year terms; Executive Director manages day-to-day operations.
    PARTNERS — over 100 member organizations contribute $10K per year ($5K for smaller institutions).
    BUDGET — funds 4-6 staffers, admin services, computing infrastructure, project coordination, conferences, Sakai Fellows Program, advocacy & outreach activities.
  • 14. Why Sakai?
    UCT decided to move to open source in 2004, migrating from WebCT & a home-grown system. Open source offers the advantages of flexibility & avoids the risks of vendor lock-in & escalating license costs. We were attracted to Sakai by the size & expertise of the community around it.
    Stephen Marquard, Learning Technologies Coordinator,
    University of Cape Town
  • 15. 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
  • 16. Sakai 3 Themes
    Content Authoring and Management
    Academic Networking
    Breaking the Site Boundary
    Academic Workflows, not (just) Tools
    Sakai, Thick or Thin
    Sakai Everywhere
  • 17. Content
    Content Basics:
    Simple page creation (wiki-like)
    WYSIWG Editing
    Template-based authoring
    Versioning
    Interactive Widgets
    Everything is content
    Searchable, linkable, portable
    Unified content repository
  • 18. Sakai2
    Site B
    Site A
    ?
    Finding something requires knowing which site it belongs to.
  • 19. Sakai3
    Tags: System, Organizational & User
    Search + Smart Folders
  • 20. Academic Networking
    Content
    People
    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?
  • 21. Sakai 2: Users & Sites
    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.
  • 22. Groups & Sites (call them spaces?) Separated
    Member of a group – People with something in common
    Access to a space – Collection of content & functionality
    Support for hierarchy
    Sakai 3 Groups & Sites
    Group 1.1
    Space AA
    Space A
    Group 1
    Space AB
    Group 1.2
    Space B
    Group 2
    Space C
    Group 3
  • 23. Kernel
    Tool
    Sakai 2 Architecture
    Kernel
    Service
    Tool
    Tool
    Service
    Service
    Kernel
    Service
    Service
    Tool
    Tool
    Service
    Tool
    • Facilitates independent tool development
    • 24. Resists intuitive workflows
    • 25. Contributes to inconsistent user experience
  • Sakai 3 Architecture
    Kernel
    Workflow
    Kernel
    Service
    Workflow
    Workflow
    Service
    Service
    Kernel
    Service
    Service
    Workflow
    Workflow
    Service
    Workflow
    • Services need to respond to more customers
    • 26. UX oversight is more complicated
    • 27. Workflows built across services
    • 28. Encourages presentation & service separation
  • 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 discussionpost that will be graded.
    4 tools for both instructors and students!
  • 29. Academic Workflow Example
    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…
  • 30. Student View
    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…)
  • 31. Student View, Graded
    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)
  • 32. 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)
    Sakai does not need to do everything for everyone
  • 33. Sakai Everywhere
  • 34. http://3akai.sakaifoundation.org
    Sakai 3 Demo
  • 35.
  • 36. 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
  • 37. 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
  • 38. 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
  • 39. 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
  • 40. 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
  • 41. ありがとうございました