...
There is a number of things that happen in smaller organizations where
Sakai becomes more of a general purpose resource - sometimes Sakai is
the only place on a small campus that everyone ends up with an account
- so Sakai effectively becomes a SSO system for a small organization.
I see Kuali Student and other Kuali projects in the future expanding
this general purpose role on small schools but for now Sakai is kind
of a beachhead in those schools.
Some schools even use Sakai as their campus "portal" - the place where
people have a personalization area - this is not their main outreach/
marketing campus page - just the main page for folks to log into.
...
Via Clay Fenlason
Anecdotally I think these contribute:
- bureaucratic hurdles to getting "approval" for other lists, which
we've consciously avoided in our Sakai implementation. It's simply
easier to create a new site and add people in an ad hoc way than to
follow the steps of other campus services. If other campus services
had not been so controlling, this probably wouldn't have been
perceived as a benefit of Sakai. As it is, we have the appearance of
innovation. Hey, I'll take what we can get
- the power of a unified environment: this is the same place where
your course sites are, etc. Isn't it nicer to have all my
collaboration stuff in one place rather than navigating across several
systems?
-----------------------
Via Sean DeMonner
Michigan has been tracking the evolution of project site usage on our
campus for some time now (anyone can create a project site in our
instance). In fact last Summer in Vancouver Stephanie Teasley and
Emilee Rader participated in a panel along with Wendy Morgaine Jeff
Narvid tp present some findings on the topic. Slides from that panel
are here:
...