This may be old news to others, but I finally have my copy of the new “Sakai Courseware Management” book (courtesy of the folks over at Packt) and more surprisingly have even been able to carve out time to read the contents. For people who may not have been aware, this is the book that Alan Berg & Michael Korkuska have spent the last many months of their lives churning out.

After looking through “Sakai Courseware Management”, I’d say if you’re a technical staff member working with Sakai it’d be invaluable. Finally, much of the community knowledge and resources have been distilled into a single volume, greatly shortening the learning curve — and with enough topics that even old-Sakai hands will likely see some new bits, courtesy of the deep knowledge of Alan & Michael.

To get a feel for what’s in the book, check out: http://www.packtpub.com/article/sakai-courseware-management-the-official-guide-table-of-contents. Chapters 1-14 are a pretty straightforward introduction to the Sakai CLE. Chapters 15-19 are a bit off the beaten track, encapsulating a bunch of items that might be considered – “meta-Sakai” – things like community, teaching, and people that differentiate Sakai from some of the more traditional corporate LMS offerings.

Some nuggets you might not get a feel from the ToC, but that are items of note, the book is full of:

• non-official “Contrib” or extended tools and how they can be integrated with Sakai (e.g. embedding JFlash to let Sakai support online Flashcards for instance)
• pointers to product wikis, email lists, and docs — in many ways the entire book could be seen as a ToC for the broader SakaiWeb/Community
• references to people and institutions — providing a connection to the key players in the space

Overall, the text is written in a pretty clear, narrative fashion (with lots of sidebars detailing history, or inspirations for various pieces of Sakai. Packt has posted Chapter 11: Web Services: Connecting to the Enterprise at http://www.packtpub.com/files/Sakai-Courseware-Management-sample-chapter-11-Web-Services.pdf which is a good representative of the style of the book.

Though brief, chapter 11 gives you a quick overview of web services (some background reading might be requred) then drops you into some examples in Sakai. It’s unfortunately a bit light from an example perspective (e.g. what are items the authors believe you can/should use these services to do, but it gives the reader a good set of tools to poke around and explore the environment.

Arguably the publication of a book is one of the signs that a project has “made it” and for Sakai I think this is certainly the case as well. Especially for open-source projects with tight-knit core communities, the experience for a new-comer can be daunting, no matter how congenial the atmosphere as you try to synthesize a product, community, and culture all at the same time (often while, errr… trying to get something done in the first place) In that regard, “Sakai Courseware Management” makes my life much easier, since now when people have questions about Sakai, instead of trying to enumerate the variety of community resources, articles, email lists, and code — I can drop a 485 pg. volume on their desk — not only producing a resounding “thwackt” but giving them a great post-conference read on the plane resource.

Having said that, this is clearly an introductory, technical book. It’s great for looking at setting up Sakai, poking around the various resources, and finding out what the tools do. I think if I were say a faculty member interested in effective e-Learning using Sakai, or interested more from a teaching/pedagogical side I might be a bit disappointed (though for that audience, there are some great case-studies from the Sakai Teaching Excellence awards on page 341). So, while I don’t want to take away from what this book is, and the great void it fills; I suppose we’ll have to eagerly anticipate some follow-on volumes targeted at other audiences/topics, like “Teaching with Sakai”, “Building Sakai Tools”, or “Deploying Sakai as an Enterprise CLE”.

Other Posts about “Sakai Courseware Management”

• http://sakaiblog.korcuska.net/2009/05/28/sakai-book-announced/
• http://sakaiblog.korcuska.net/2009/06/12/sakai-book-now-shipping/
• http://steve-on-sakai.blogspot.com/2009/07/sakai-book-sample-chapter-on-web.html

Google releases Wave protocol implementation source code – Ars Technica: “At the Google I/O conference earlier this year, the search giant revealed an intriguing new communication service called Wave that aims to deliver concurrent messaging and collaborative editing in a single cohesive environment. The underlying Wave Federation Protocol is designed to make it possible for third parties to host their own interoperable Wave instances. Google intends to open the source code of its own implementation in order to encourage widespread adoption of the protocol. The company took its first major steps in that direction on Friday by releasing the source code of its Operational Transform (OT) code and a simple client/server reference implementation that is built on top of the protocol. This code, which is available under the open source Apache Software License, will give developers a way to start experimenting with the protocol and potentially even building their own Wave-compatible services.”

(Via http://arstechnica.com.)

I hate to hop on the bandwagon, but I have to admit – Wave looks like the most revolutionary item I’ve seen in a while – in a full-on game changer sense. Not so much just because of the cool widgetry that Google’s built, but because it’s a protocol – with the flexibility and potential that implies.

Building on some of the interactions we’ve seen with IM, Blogging/Trackbacks, Twitter, and other messaging, Wave looks to standardize, federate, and embed real-time, multiparty communications to the point where it will become part of the fabric of the web. If Web 2.0 = comments and trackback conversations – this feels a lot more like Web 2.5 – the implementation we really wanted when we first tried to take the web from a document-based publishing platform to a conversation-enabled collaborative medium.

And… Open-Source production-quality reference implementation – what could be better. I have to say, not an small number of my off-work hours are going to be spent looking at embedding Wave into… everything… Particularly given that Federation (though still a little nebulous) is a first-class citizen in the platform.

In Dallas at the Jasig Conference, getting ready for the Board meeting where we’ll be looking at licensing, incubation, and some other strategic concerns related to open-source in HigherEd. Already had some great conversations about CAS & credential replay, Peoplesoft integration, and open-source economics & dynamics.

P.S. Ian Dolphin clarified over beers last night that he has not actually hit 2 million miles, and that’s a meme that Chuck Severance has propagated through the net space

ландшафт. the exhaustion that was the combined CampusEAI Portlets2008 and Annual conference is now behind us, and it seems like time for some reflections and observations. Hopefully some of these items will be items which I expand upon at a future date, but in no particular order, dumped straight from my brain:

• JSR-168 is here! Everyone really wants to write good standards compliant portlets. Architecture and engineering is a harder sell (or at least the time/cost trade-off) but there’s wide consensus that standard portlets are the way forward — at least excepting a couple of us widget fans
• SOA is something people are interested in, but that there’s been relatively little forward progress on. Some is governance. Some is tools (SOAP, WSDL, and what’s this REST thing?). Some is just that it’s big and strategic, and there’s many tactical must haves. I suspect some of it is also that much of our interesting data/services are locked in vendor platforms that have shown little interest in opening up. Though, a small trend does exist of creating SOA-style services to reach into vendor platforms and extract data from them
• Mobile wasn’t as big as I thought it would be. Not sure why. Most people seem to be interested in the abstract, but with few concrete plans. Maybe my iPhone has clouded my vision, but I do wonder if we’re going to get blindsided come fall — our target demographic is basically 18-22 year olds, afterall…
• AJAX in portlets is still hard. There are some tricks like wrapper divs, namespacing, and builtin support and integration patterns, but it’s still not a common practice.
• Identity Management is big. Governance is a big thorny issue, though many IT departments are rolling out vendor products from big players (Oracle, Sun, a little IBM) in the interim, tho ugh the exact scope of those items is somewhat unclear.
• Oracle is really putting portlets in lots of interesting places. Webcenter. Product mashups. Inside BI tools, and other GUI devices. I think they’ve probably embraced the architecture more than any other major vendor which is an interesting trend.
• Lots of awareness, and wanting to look at uPortal 3. Ooohs and ahhs over both the AJAX D&D, and maybe more importantly the new content adding UI — good going Jen!
• Really beautiful portals — some, though not all new portals really seem to be breaking out of the lots of boxes approach, or at least wrapping it in neat functionality like Boston College’s Agora design. Nifty trend. Sign of maturity?
• Community Development is hard. Aligning roadmaps, agreeing on implementation strategies, and putting all the pieces together is challenging. Even more so, justifying “doing it right” (and fit to share) versus quick and dirty, or getting a student up and running was a big trend. Makes my inner-engineer quail, but my inner-economist says that throw-away code lowers the barrier for solving problems, which is a good thing. Evolution isn’t always pretty and all that.
• Lots of desire for training, best practices, and advice on policy and governance. Real role for communities of practice, not just code and software.
• Increasing interest in “Enterprise Learning Management”. Lots of worries about migration, but the beginning of seeds wondering whether our current platforms are sufficient for a foundation for the next 10-15 years, and University strategic goals. Of course, some of this is the “enterprise IT guys” getting pulled into the LMS discussion for perhaps the first time in many places.
• Good beer is key to facilitating interesting non-session discussion. Content is king on the program, but largely only because it gets people in one place and produces interesting spontaneous interactions. Hands-on is something everyone wants, but it’s not clear a conference composed of many 1 hour sessions is the right format to deliver it.
• University IT teams wear many, many hats.
• British Universities seem to have a much richer and more abundent IT project management structure than (most) American schools. Really interesting thread about Imperial College in London blending ITIL and Agile methodologies.

I started this entry while I was riding a train back from the Laguardia ePortfolio Conference I’m endeavoring to reflect upon and synthesize threads from various (enlightening) presentations I’ve seen, and discussions I’ve had the privilege of participating in. First a brief plug: the content from the conference was fantastic — many congratulations to the folks from Laguardia Community College for organizing such a wonderful event.

Sakai has amazingly broad potential. The energy and excitement in the community and among those who have been watching Sakai make it clear that we’re really realizing the benefit of contributor’s blood, sweat, and tears in the form of some exciting tools for teaching and learning. Sakai seems uniquely positioned to become the base of a whole ecosystem of tools supporting different facets of the academic experience ranging from instruction, to assessment, to facilitating interactions between learners. I think we may be at a crossroads in terms of positioning, particular as we evolve towards explaining the product, beyond the project & community. Laguardia’s conference and discussions, especially those related to “Sakai vs. OSP” really focused my thinking on various opportunities for Sakai to support different areas of teaching, and learning.

A statement: I think the the common usage of Sakai to discuss both a specific set of tools supporting course/learning management (Sakai CMS/LMS?) and a platform/environment upon which those tools can be built and deployed has resulted in some confusion. I have heard many questions recently in the vein of “do you have to use Sakai to use OSP?” or “we’re a Blackboard school, and aren’t going to switch, does that mean OSP is out?” The fact that OSP is a toolkit built on top of Sakai (the platform) seems to be a confusing point for many who don’t currently have plans to deploy Sakai as a CMS/LMS.

To clarify, yes: it is quite reasonable to deploy OSP as a system exclusively dedicated to portfolios, completely separate from the other tools. Inputting text, adding reflections, uploading evidences, and managing assessment are all perfectly capable of being performed in a stand-alone environment. In the same way that past releases of Sakai downloaded from sakaiproject.org “stealthed” (hid) the portfolio tools an institution could choose to leverage the OSP piece of the Sakai ecosystem without forcing your users to adopt the entire environment — one advantage of the platform’s open-ness and customization capabilities.

In fact, I think this scenario illustrates a very real way to explain Sakai. If Sakai is a platform upon which bundles of tools (courseware, OSP, etc.) can be built, then we have a product with many facets. Each facet (LMS, OSP, Collaboration) supports a different interaction scenario, part of a greater whole of learning. Going forward, perhaps explicitly separating that greater platform from its concrete manifestations (particularly as courseware) would help emphasize Sakai’s potential as a learning suite or system — with facets focused on all aspects of a learner’s experience: courses, co-curricular’s, career advising, libraries & research, collaboration, and personal expression for a start. This thinking was really influenced by listening to many people talk about OSP — as a toolkit for building concrete artifacts: resumes, co-curricular transcripts, certification documents, personal expressions — all leveraging the same tools, but in many respects separate endeavors linked only by

I think there’s a danger that we could allow ourselves to slot Sakai into a box defined by the products that came before. though that’s where many adoptors initial exposure came from. The example of OSP illustrates the clear potential of Sakai’s modular architecture to enable assemblage of higher-level environments supporting particular styles of teaching or interaction. A common environment lets us both build on previous work, and also focus on integrating the experiences for out students and teachers, participants and leaders. My programmer’s mind sees this as being much the same potential as is now playing out in the Eclipse eco-system.

So the question I think this brings up is: if we focus on this broader picture, and think about these “bundles” as being the real deliverable, could we better frame this relationship by rebranding (consistent with recent thoughts about relaunching) the Sakai courseware tools as a separate entity within the Sakai umbrella — “Sakai Classrooms” maybe? Leaving room for thinking of the ecosystem as bundles, which you can mix and match: “Sakai Portfolios”, “Sakai Communities”, “Sakai Social Networking”. Different bundles of functionality built on the same platform, possibly using the same individual tools, but illustrating some of the broader possibilities.

Well the questions are pouring in (mostly due to my tardiness in writing this kind of announcement) and so, without farther ado…

What Happened?

While it still feels a little strange to say it, as of 2 Fridays ago (2/8) I am no longer employed at Rutgers University. Over the last 9 years as first a student, then staff member, I’ve had the chance to: first study under, and then work with some incredible people. I’ve gotten to watch projects and services grow and evolve into solutions that are used every day by tens of thousands of students, faculty, and staff.

Before addressing my personal situation, I feel the need to speak a bit about the Rutgers Sakai deployment which up until now has occupied so much of my thoughts and energy. I was fortunate enough to see myRutgers grew into a service providing tools and services to every student at Rutgers. Sakai usage is currently somewhere on that curve, with usage growing by leaps and bounds. This Spring’s semester in many ways feels like a qualitative shift in the nature of the service — marked by a huge increase in the number of students asking “where’s my class’s Sakai site.” This semester these questions are particularly significant, as many of them are coming from students in classes where either:

1. Class was not yet in session. This is a big change from the dynamic in previous semesters where students typically visited the first meeting of their class, and were then directed to visit the Sakai site. Now students are looking to visit the Sakai site to see the syllabus, readings, and get a leg up on going to that first class.
2. Their instructor had not created a site. Sakai seems poised to make the jump into ubiquity, as in some students minds it’s already there.

Now to handle the really common question — if the Rutgers Sakai deployment is so clearly poised for greatness, where am I going and why? Well…

Starting this past monday (2/11) I have taken a position with the CampusEAI Consortium, where I will be serving as the Director of Open Source Solutions. Recent years have seen a huge upswing in the popularity, and visibility of open and community source solutions in Higher Education. Sakai, uPortal, CAS, Kuali, and othes have garnered attention, awards, and deployments. Due to significant interest expressed by member institutions, CampusEAI is looking to complement its existing strengths on the Oracle platform with broader offerings in the open-source space.

Answers to some personal-ish questions:

Are you moving to Cleveland?

No, I’m going to be based out of NJ, though Continental is certainly getting a good chunk of my time for the next few months as I schlep back and forth.

What does Lisa think?

She’s excited. Well, more excited when I’ve been gone < 2 days as opposed to > 3 days…

What do the kids think?

The kids are still getting used to not picking me up at Rutgers. They think it’s really funny that daddy works somewhere they can’t see. Sunday nights are hard. Phone calls are bittersweet. Coming back is good.

Aren’t you on the JA-SIG Board?

Yes. When my career change became definite I notified the board at the January video call. JA-SIG has always been a community of volunteers (stellar volunteers more often than not) and particular given my new employer’s willingness to continue backing my involvement in JA-SIG it was felt that there were no significant barriers to my continuing to serve in this capacity. As always, JA-SIG

So… is your Rutgers job open?

Yes. Though (see below) I’m hiring too…

What’ll I be doing?

So what does this mean in concrete terms? My personal definition is pretty simple. We’re looking to help members deploy solutions built on open source software. Given my background, Sakai, uPortal, CAS, and maybe even Kuali are obvious possibilities. I think however, that it’s a broader story than just support for deploying a few specific products. Many institutions have experienced challenges in building around open-source due to shortages in staffing or specific skill-sets. Others have successfully deployed open-source solutions, but been burned trying to deepen integration, or due to staff turnover (a problem which I should note also happens around commercial solutions). So the goal of this new unit is to make deploying solutions built on open-source:

1. Easy
2. Cost Effective
3. Low Risk
4. Sustainable
5. Did I say easy?

Basically the goal is to allow schools to leverage the strengths inherent in the open-source development model:

• Try before buy
• Rational licensing and cost-containment (instead of getting wracked with heavy licensing burdens as you get “too successful”)
• Open implementations, generally of open standards
• Economy of scale versus custom developed institution-specific software
• Freedom from vendor roadmaps and strategy shifts — even to go as far as obtain competitive bids from multiple vendors on the same solutions
• Peer interaction with really bright people working hard to solve the same problems you see

So that’s the goal. Make open-source easier, removing barriers for schools large & small — the kind of topics that have continually been commented on lists, in journals, and at conferences. Reducing installation pain. Helping with patch management. Providing support and training. Taking the pain and risk out of going open-source, all while working to make strategic contributions to enable the production of more good software.

It should be exciting.

P.S. Did I mention we’re hiring? Drop an email talking about your love for open-source, and how you really want to join in making it easier: jason_shao@campuseai.org. Oh, and mention you saw the posting in my blog

Sitting on a flight, returning from the Sakai conference — still trying to take everything in. There’ll probably be more musing on the significance of specific items coming up, but things that struck me enough to want to brain dump were:

• There was wide consensus during the planning sessions that there’s a desire to focus on quality: reliability, testing, performance, and other traits, over new feature development.
• The community is moving from a development -> production mindset. The transition of many of the core schools from pilots or development efforts into full-blown production instances has certainly changed priorities and outlooks.
• Increased desire to pick up open-standards in preference to inventing our own. JSR-168 (Unicon demoed a cool Portlet-Tool for Elluminate integration), JSR-170 and the good work Ian is doing to integrate with repositories like Jackrabbit and Xythos, CAS Authentication (vis-a-vis Dan M.’s sweet CAS-embedding UserDirectoryProvider)
• There’s a lot of commercial activity around Sakai. RSmart, Unicon, Oracle, IBM, bit players like Mark Norton & Zack Thomas. I sat in a presentation about the work I did with FIDM for CampusEAI. I even talked with another developer who has already resigned (as of Jan 1) from his university to join his part-time venture (with others) full-time. Certainly a large, vibrant marketplace.
• Many sub-groups are organizing around Sakai. In addition to our very own NYC Regional group, there are groups in California, Australia, the Netherlands, and other places. They’re holding events, sponsoring training, and moving forward.
• It’s not just regions — there are an increasing number of functionally aligned teams. Developers, Designers, and Managers are the best organized and served. I also saw a lot of User Support people or academic technologists as well. This is the group I suspect may be the next to organize — a CAFE track focused on bringing user support people up to speed or sharing experiences/resources would probably be really valuable.
• Lots of parallel activities. Many examples of SIS integrations, library integrations, documentation & training, tool development. Unfortunately, communication barriers and other difficulties seem to be producing several duplicate/parallel efforts (e.g. Yale’s SignUp tool, EDIA’s signup tool, Stanford’s efforts around this space) though there is a desire to collaborate.
• Some stuff is still too hard: authentication integration, CourseManagement integration, libraries work, documentation, training are all pain points, especially for smaller teams/schools.
• Strong community. It’s easy to get lost in a group of smart, affable people moving towards a common purpose. Had an excellent time, and there’s a good sense of camaraderie weaving throughout the community. People are friendly and helpful.
• Twitter – yeah, it’s kind of narcissistic, but at an event or convention it can certainly be a lot of fun. Both to do self-organizing (e.g. dinner?) and to pull in people who are in the circle, but not present.

I just sat on a panel talking about some of the ongoings at the regional groups around Sakai — California, Australia, the Netherlands, and of course NYC. Sounds like there’s starting to be a lot of activity around certain areas. It was interesting to see that many of the regional organizations were very event-focused, almost mini-conferences. The Netherlands group seems similar to the NYC one in that they have regular meetings (more regular than us) and are building a continuous series of events in an area community.

Slides below.

| View | Upload your own

Just got off the plane and am at the hotel for the Sakai Conference (explains the flurry of blogging — no distracting internet, so time to write )

I’ll be out in Newport Beach, CA from Fri 11/30 – Fri 12/6. If you’re around (esp. Fri night) and looking for something to do give me a holler. Especially if you’re from around NYC — I’m trying to work out a NYC Sakai User Group meetup sometime, maybe wed or thu night. JA-SIGers feel free to give a holler too.

<

p>The Ed Techie: What Mailbox limits reveal:

<

p>

Grainne posted recently about the frustration of continually getting the ‘Your mailbox is over its size limit’ in our OU email accounts. I can’t tell you how annoying this – sometimes I am just trying to send a quick response to someone before I have to dash out of the door, but it won’t let me because I have to find and delete any attachment over 2K to free up space. Grrrr.

(Discovered this site through the Edublogs Awards.)

It’s interesting to see the comments on the gist of this article — in terms of how reasonable the restriction or attitude behind it are. IT usage restrictions always seem to generate two separate camps of apologists and critics. Apologists focus on the rational behind it, the need to balance services with resources, and limitations of the technology or workflow. Critics tend to express frustration over inconvenience, limitations, or restrictions that make their work harder, or prevent them from performing a specific action, or in a particular way.

While I can’t claim to have a solution to IT limits (regrettably, my superpowers don’t seem up to the task) I do notice that we seem to have an opportunity for dialog. IT Governance is an increasingly hot topic, particularly with institutions struggling to prioritize during lean budget years. We clearly have a pool of customers who are more than willing to tell us what they think is important.

I think the need to create dialog highlights one of the reasons a number of us found Collier’s MyUMBC feedback feature so compelling. By integrating feedback submission forms into every page, portal visitors are encouraged to communicate their reactions and thoughts (even about email quotas ) making the barrier to contribution very low. At the same time, while many of us have feedback forms that email teams, the MyUMBC example of integrating the admin panel & tools to ease followup/contact make it easy to go back, and mine through the data, or engage customers in dialog regarding their experiences with the product or service.

I’m happy to say that Jenn’s work on the feedback portlet stemming from the JA-SIG Unconference seems likely to move uPortal (and maybe someday Sakai or other portlet containers ) further in the direction of built in mechanisms to collect these user sentiments and provide information so we can work to better address our users concerns, experiences, and frustrations.