7-10-2009 Sakai 3 Overview (Michael Korcuska)

721 views

Published on

See title.

Published in: Education, Spiritual
1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total views
721
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
28
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

7-10-2009 Sakai 3 Overview (Michael Korcuska)

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

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

  3. 3. Why
Sakai
3?
 FuncKonality
&
User
 Experience
 Technology
and
 Developer
Experience
 Community
PracKces
and
 Culture

  4. 4. Why
Sakai
3
Now?

 The
Kme
to
repair
the
roof
is
when
the
sun
is
 shining.
 John
F.
Kennedy

  5. 5. Why
Sakai
3?
 USER
PERSPECTIVE

  6. 6. Sakai
3
for
Users
 •  Changing
expectaKons
 •  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. 7. Sakai
3
Themes
 Content
Tagging
&
 Content
Authoring
 Management
 Breaking
the
Site
 Academic
Networking
 Boundary
 Academic
Workflows,
not
 The
unSakai
 (just)
Tools
 7

  8. 8. Content
Authoring
 •  Content
Basics:
 •  Simple
page
creaKon
(wiki‐ like)
 •  WYSIWG
EdiKng
 •  Template‐based
authoring
 •  Versioning
 •  InteracKve
Widgets
 8

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

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

  11. 11. Sakai
3
 Tags:
System,
 OrganizaKonal
&
User
 Smart
Folders
 Search
 11

  12. 12. Benefits
 •  Web
2.0
“search”
interacKon
supported
 •  Tagging
&
content
search
 •  Smart
Folders
retain
hierarchical
structure
if
 desired
 •  Folders
for
each
site,
each
user
and
more
 •  Porlolio
and
other
“cross‐site”
needs
 •  Tags
allow
simple
aggregaKon
of
diverse
content
 •  OrganizaKonal
&
User
tag
systems
support
 mulKple
porlolio
requirements
 12

  13. 13. Academic
Networking
 •  Academic
Networking
 •  People
are
important,
but
“friends”
aren’t
enough
 •  Content‐based
–
Who
is
reading
the
same
arKcles?
 •  AcKvity
based
–
Who
has
taken
the
same
classes?
 13

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

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

  16. 16. Architecture
 Tool
 Service
 Kernel
 Service
 Tool
 •  Facilitates
independent
tool
 •  Resists
intuiKve
workflows
 development
 •  Contributes
to
inconsistent
 user
experience
 16

  17. 17. Architecture
 Service
 Workflow
 Workflow
 Kernel
 Service
 •  Workflows
built
across
 •  Services
need
to
respond
 services
 to
more
customers
 •  Encourages
presentaKon
&
 •  UX
oversight
is
more
 service
separaKon
 complicated
 17

  18. 18. Academic
Workflow
 •  Beyond
Tool
Silos
 •  Academic
work
flows
ooen
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!
 18

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

  20. 20. Student
View
 Week
 Readings
 AcQviQes
&
Assignments
 1
 Course
Policies
 Textbook
Chapter
1
 2
 Textbook
Chapter
2
 Write
a
response
to
Jackson
arKcle
&
 Assignment:
Jackson
Reading
Response
 Jackson
ArKcle
 post
to
discussion
forum
 Due
Date:
September
10,
2009
(




due
tomorrow)
 Status:
Not
submited
 Points:
10
possible
(of
150).
 DescripQon:
Respond
to
the
Jackson
arKcle
in
no
more
than
 500
words.
Post
that
response
to
the
class
discussion
forum.
 Read
more…
 Link(s):
Jackson
Response
Discussion
Forum
(Create
Post…)
 20

  21. 21. Student
View,
Graded
 Week
 Readings
 AcQviQes
&
Assignments
 1
 Course
Policies
 Textbook
Chapter
1
 2
 Assignment:
Jackson
Reading
Response
 Textbook
Chapter
2
 Write
a
response
to
Jackson
arKcle
&
 Jackson
ArKcle
 Due
Date:
September
10,
2009
(due
date
passed)
 post
to
discussion
forum
 Status:
Submited
and
Graded
 Points:
9/10
(of
150).
View
feedback
 DescripQon:
Respond
to
the
Jackson
arKcle
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)
 21

  22. 22. The
unSakai
 •  MulKple
ConfiguraKons
 •  Sakai
as
CMS
 •  Sakai
as
CollaboraKon
System
 •  Sakai
as
Porlolio
System
 •  Sakai
IntegraKons
 •  Google
ApplicaKons
 •  Social
Networks
(Open
Social,
Facebook)

 22

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

  24. 24. unSakai
Economics
 •  We
want
to
posiKon
Sakai
for
a
transiKon
 to
the
“we
don’t
need
no
sKnking
LMS”
 •  We
don’t
care
about
“owning”
the
 enterprise
 •  We
aren’t
afraid
of
eroding
license
fees
 because
other
applicaKons
take
over
“core
 LMS”
features

  25. 25. htp://3akai.sakaifoundaKon.org
 SAKAI
3
DEMO
 25

  26. 26. Why
Sakai
3?
 SAKAI
3
TECHNOLOGY

  27. 27. Sakai
3
Technology
Goals
 •  Scalability
 •  Remove
botlenecks
from
Sakai
2
 •  Improve
cluster
support
 •  Developer
ProducKvity
 •  Faster
builds
 •  UX
&
back‐end
development
separated
 •  Code
Quality
&
Maintenance
 •  Reliance
on
other
open
source
efforts
 •  Increase
unit
tesKng
 •  Easier
to
install/build
 •  To
improve
iniKal
experience
for
new
developers
 27

  28. 28. JCR
as
Content
Store
 •  Standards‐based
 •  JSR
170
 •  Ships
with
Apache
Jackrabbit,
but
can
be
 changed
 •  Everything
as
content
 •  Discussion
post,
User
profile
informaKon,
etc.
 •  Components
put
Content
into
JCR
Content
store
 •  Sakai
Kernel
creates
relaKonal
indices
in
DB
 •  Component
doesn’t
need
to
do
anything
 •  AutomaKc
tracking
of
most
events
by
kernel
 28

  29. 29. The
Point
 •  Don’t
write
our
own
code
 •  Criteria:
 •  FuncKonality
 •  License‐compaKble
open
source
 •  Open
standard
 •  Approachable
community

  30. 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
ooen
skilled
in
JavaScript
 •  Easier
UX
developers
can
work
on
Sakai
 •  Tools
like
GWT
can
be
used
for
Java‐based
UI
 •  Components
can
be
writen
using
other
languages
 30

  31. 31. TIMELINES
AND
ADOPTION

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

  33. 33. New
AdopQons:
2
or
3?
 •  It
Depends!
 •  Of
Course
 •  On
what?
 •  Your
producKon
Kmeline
 •  Your
appeKte
for
running
“.0”
sooware
 •  Your
funcKonal
needs

  34. 34. AdopQng
2
or
3?
 2.6
or
2.7
 Straight
to
3
 •  Sakai
2
works
well
today
 •  You
don’t
have
a
CMS
 •  3
doesn’t
exist
yet
 or
you
are
using
 •  The
best
path
to
3
will
 something
like
 be
through
2
 SharePoint
 •  Bb/WebCT
migraKon
to
 •  Your
producKon
 3
is
undefined
 Kmeline
is
2012
or
 •  Bb/WebCT
migraKon
to
 later
 2
is
well
known
 •  Many
will
be
migraKng
 from
Sakai
2
to
3

  35. 35. AdopQng
2
or
3?
 •  Maybe
the
wrong
quesKon
 •  Adopt
both!
 •  Hybrid
mode
 •  Sakai
2
for
courses,
Sakai
3
for
project
 collaboraKon
 •  Gradually
move
users
to
Sakai
3

  36. 36. COMMUNITY
PRACTICES

  37. 37. Community
PracQces
 •  FuncKonal
Leadership
 •  Design
First
 •  Minimize
Technology
Frameworks
 •  Quality
Focused
 •  Unit
(and
other)
Tests

  38. 38. GET
INVOLVED!


×