LAMP: Sakai’s Shining
Light
|
|
|
Scott Siddall |
|
The Longsight Group |
|
|
|
|
|
|
Slide 2
Why Sakai?
|
|
|
|
Collaboration and learning
environment |
|
For higher education, by higher
education |
|
Strong community source model |
|
Leadership |
|
Funding |
|
Surpassed the open source
threshold |
Why Sakai?
|
|
|
Flexibility |
|
Control |
|
Cost |
|
Integration |
|
Customization |
|
Rapid bug fixes |
|
Pedagogical focus |
Why a consortial
instance?
|
|
|
Economies of scale and lower
cost |
|
Preserve institutional identity |
|
Serendipitous sharing among
disciplines |
|
Extends the tradition of
collaboration |
|
Unified training and support |
|
Reveals courses for
cross-registration |
Why Sakai as a Service?
|
|
|
Having a CLE is strategic -
running it yourself is not |
|
Effective to hire specialists |
|
Rapid startup, no capital
investment |
|
No system maintenance |
|
Lower TCO |
|
Greater reliability |
|
Opportunity to reallocate
resources |
Why Sakai as a Service?
|
|
|
Campus can reallocate staff
resources |
|
Focus resources on outcomes,
not technology |
|
Focus staff on
training/engaging faculty |
|
|
|
Technical staff gain experience
with open source |
|
Gradually take ownership of
the project |
|
|
|
Not a proprietary instance of
Sakai |
|
No vendor lock-in assures
choices |
The Sakai experience
|
|
|
Changed your teaching/learning
style? |
|
64% of faculty and 36% of
students |
|
|
|
Overall impression? |
|
83% ++ faculty and 66% ++ for
students |
|
|
|
Use Sakai again? |
|
88% of faculty and 62% of
students |
|
|
Slide 9
Slide 10
Appalachian College
Association
|
|
|
Learning Asset Management
Program: LAMP |
|
14 institutions |
|
Pilot and production uses; two
levels |
|
Many shifted from WebCT |
|
Face-to-face and online
training of support staff |
|
Week-long faculty development
workshops |
|
Strong leadership (consortium
and campuses) |
Slide 12
Slide 13
LAMP/Longsight
partnership
|
|
|
Strict adherence to pure open
source model |
|
Branding and look & feel
customizations but nothing that breaks upgrade pathway |
|
Bug fixes submitted to Sakai
developers |
|
Rights to development work are
shared |
|
New code is open sourced |
|
No lock-in to a proprietary
version of Sakai |
|
Knowledge transfer if/when
client takes over |
|
Clients retain all content
rights |
"LAMP is accessible
at http..."
|
|
|
|
LAMP is accessible at http://lamp.acaweb.org |
|
|
|
Return to home |
|
|
|
|
|
|