Sakai 3 V07
Upcoming SlideShare
Loading in...5
×
 

Sakai 3 V07

on

  • 4,052 views

The latest version of my Sakai 3 presentation. Haven't actually given the presentation with this deck yet. Very similar in content/structure to the one I gave at the 10th Conference in Boston.

The latest version of my Sakai 3 presentation. Haven't actually given the presentation with this deck yet. Very similar in content/structure to the one I gave at the 10th Conference in Boston.

Statistics

Views

Total Views
4,052
Views on SlideShare
4,005
Embed Views
47

Actions

Likes
4
Downloads
72
Comments
1

5 Embeds 47

http://www.udel.edu 24
http://www.slideshare.net 18
https://www.udel.edu 2
http://www.apurva.com 2
http://static.slidesharecdn.com 1

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • More information is available on the managed Sakai 3 project to deliver Sakai 3.0 by the end of
    June 2011. http://confluence.sakaiproject.org/display/SAKDEV/Sakai+3
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Sakai 3 V07 Sakai 3 V07 Presentation Transcript

  • Sakai 3: An Overview
    Michael Korcuska
    Executive Director
    Sakai Foundation
  • Sakai 3: Why?
    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
    Fluid Project
    2
  • Why Now?
    Proto by Hubert Stoffels
    The time to repair the roof is when the sun is shining.
    John F. Kennedy
    View slide
  • What?
    Photos by Hobvias Sudoneighm,Massimo Valiani, and Mathieu Plourde
    Functionality & User Experience
    Technology and Developer Experience
    Community Practices and Culture
    View slide
  • End User perspective
    Sakai 3
  • Everything is Content
    Sakai 3 Themes
    6
    Learning Space Construction
    Breaking the Site Boundary
    Academic Workflows, not (just) Tools
    Academic Networking
    The unSakai
  • Learning Space Construction
    Really “Academic Space” Construction
    Teaching & Learning plus….
    Research, collaboration and portfolios
    Principles
    Overall control in hands of space owner(s)
    Embrace participant content creation
    Simple integration of common academic functions
    1
    Photos by Cyprien Lomas
  • Academic Spaces: Building Blocks
    Simple Content Authoring:
    Easy page creation (wiki-like)
    WYSIWYG Editing
    Templates (page and site)
    Versioning
    Enhanced with Academic Functionality
    Interactive Widgets (e.g. assignments & feedback)
    8
  • Everything is Content
    Not just files to share
    Classic “resources” tool in Sakai (of course)
    Discussion post, user profile, test questions
    Taggable, searchable, linkable, portable, shareable
    Unified content repository
    Content not tied to site
    Everything in one storage area
    BUT: Sakai is not a full Content Management System
    No complex approval workflows
    No fancy layout capabilities
    Everyone is an author in Sakai
    9
    2
  • Content Management
    Sakai2
    Photo by Desirée Delgado
    Site A
    Site B
    Users find things by remembering what sitethey were in when they saw it.
    10
  • Content Management
    Sakai3
    Photo by Amy Veeninga
    Tags: System, Organizational & User
    Permissions: Who has access, under what conditions
    Smart Folders
    Search
    11
  • Academic Networking
    Academic Networking
    People are important, but “friends” aren’t enough
    Related content is also relevant, but not the whole story
    Activity based
    Who has taken the same classes?
    Who is reading the same articles? Participating in similar discussions?
    12
    3
    Content
    People
  • Academic Networking
    A platform for exploration
    We aren’t competing with Facebook
    We do believe we need to drive R&D in this area
    Linking networks together
    Sakai to Sakai
    Sakai, Moodle, Blackboard, D2L
    Leveraging existing networks
    Particularly LinkedIn and Facebook
    Sharing profile and activity information
    Creating apps on those platforms
    Photo by Joël-Evelyñ-FrançoisDézafit-Keltz
  • The Site Boundary
    14
    4
    All Art Students
    Studio Art 101
    User 100
    User 2
    User 3
    User 4
    User 500
    .
    .
    .
    User 1
    User 2
    User 3
    User 4
    User 5
    .
    .
    .
    Year 1 Art Students
    Year 1 Art Students
    Users and groups exist within the context of a site.
  • 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
    Art Dept.
    Art Majors
    Art Majors
    Studio 101 Students
    Studio 101
    Guest Judges
    Student Work
    15
  • Workflow & Architecture
    16
    5
    Kernel
    Tool
    Kernel
    Service
    Tool
    Tool
    Service
    Service
    Kernel
    Service
    Service
    Tool
    Tool
    Service
    Tool
    • Facilitates independent tool development
    • Resists intuitive workflows
    • Contributes to inconsistent user experience
  • Workflow & Architecture
    17
    Kernel
    Workflow
    Kernel
    Service
    Workflow
    Workflow
    Service
    Service
    Kernel
    Service
    Service
    Workflow
    Workflow
    Service
    • Services need to respond to more customers
    • UX oversight is more complicated
    • Workflows built across services
    • Encourages presentation & service separation
    Workflow
  • Academic Workflow
    Beyond Tool Silos
    Academic work flows often cross tool boundaries
    Anything can be graded!
    Anything can be discussed!
    This exists in Sakai 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
    Photo by Zoom Zoom
  • 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…
  • 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…)
  • 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)
  • 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
    6
  • 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
  • Sakai 3 Technology
    Why Sakai 3?
  • Sakai 3 Technology Goals
    Scalability
    Millions of users
    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
    25
    Photo by Luiz Castro
  • 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
    26
  • The Point
    Don’t write our own code
    Criteria:
    Functionality
    License-compatible open source
    Open standard
    Approachable community
  • JSON
    Sakai Kernel supports JSON microformat
    Components use REST calls to interact with Kernel
    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
    28
  • Community Practices
  • Community Practices
    Functional Leadership
    Design First
    Minimize Technology Frameworks
    Quality Focused
    Unit (and other) Tests
  • Timelines and adoption
  • 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?
  • Adopting Sakai
    Adopt 2 or 3?
    Not the first question to answer
    First Question:
    Yes! Or probably
    Do you want to be using Sakai (and be in the community) in the long run?
    We can help you figure out how to get there
  • Path to Sakai
    Straight to 3? Start with 2?
    It Depends!
    What did you expect?
    On what?
    Your production timeline
    Your appetite for “.0” software
    Your functional needs
    Your support model
  • Adopting 2 or 3?
    Sakai 2.6 or 2.7
    Sakai 2 works well today
    3 doesn’t exist yet
    Sakai 2 will be a good path to Sakai 3
    Bb/WebCT migration to 2 is well known
    Many will be migrating from Sakai 2 to 3
    Straight to Sakai 3
    You don’t have a CMS or you are using something like SharePoint
    Your production timeline is 2012 or later
    You have a very strong preference for Sakai 3
  • 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