The OpenDocument XML.org web site is not longer accepting new posts. Information on this page is preserved for legacy purposes only. For current information on ODF, please see the OASIS OpenDocument Technical Committee.
So it’s been a few months since version 1.0 of the CSL specification was finally released. Where do we stand now?
- We’ve got a completely 1.0-compliant CSL processor in the form of Frank Bennett’s citeproc-js, which is backed up by an extensive test suite. This has just recently been folded into the Zotero trunk code, so should be rolled out to Zotero users in the coming months.
- The Mendeley team is also planning to use citeproc-js, though I haven’t heard any update on timeline.
- Mendeley has also started work on a WYSIWYG online style creator. This is really important.
- Ron Jerome has been working on a PHP port for use in his Drupal biblio module; it’s not done, but he’s made good progress
- Sente has support for CSL import
- a new app called Peaya has CSL support, though I know no details (in fact, hadn’t ever heard of it until just a bit ago, which bothers me)
- Andrea Rossato is updating his wicked fast Haskell implementation to be 1.0-compliant; usable, among other things, with the really nice markdown processor Pandoc
So here’s my vision of where I’d like to be in another year or two:
- “CSL support” is considered an important feature by users
- A complete and beautifully functional online CSL creation application is up and running, and the result is an explosion of good, correct, and up-to-date styles. Right now we have a bit over 1,100 the last I checked; I’d like to see this increase to cover virtually all current journal styles. To do this right means it has to be really easy to both create new styles, and comment on and subsequently edit existing styles.
- Wide and deep (e.g. fully compliant) support for CSL across a range of applications and application types (online, desktop, etc.). This not only includes correct formatting, but also making it really easy to find and use the styles noted above (and passing around files by email does not count).
- I’d also like to see progress on the thorny problem of document interoperability, as well as adding RDFa support to formatted bibliographies for full round-tripping
But there’s still some distance between that idea and the current reality. For one thing, there’s not as much collaboration on CSL among developers as I’d like. Ideally, everyone that implements CSL should have some sort of public commitment to, and benefit from, future CSL development. At minimum, this should involve participating in development discussions. But beyond that, we need people to help with:
- web design for the citationsyle.org site
- finishing the style creation application and repository (PHP and JQuery skills needed!), and figuring out how best to exploit this in applications
My institution is entering the Sakai community at a time that is both awkward and exciting. Sakai is now a two-product world. Sakai 2 is well-developed and stable: the LMS we have now. Sakai 3, on the other hand, is the emergent next-generation LMS: incredibly promising, but not yet ready for wide-scale deployment.
Given our roadmap to transition over the next year or so and have Sakai fully deployed in the Fall of 2011, the obvious question all of us that attended the Sakai 2010 conference were asking was: should we just look to jump straight to 3? Ultimately, after all the discussions, we ended up with about four different possibilities:
- do Sakai 2, and effectively ignore Sakai 3
- do Sakai 3, and ignore Sakai 2
- run Sakai 3 for the nice new social-networking features to act as a kind of portal with Facebook-like features, but run Sakai 2 in “hybrid mode” for the more traditional LMS functionality that may not be ready when we need it
- similar to the above, but run the two instances completely separately
I got the feeling that our group was more attracted to the last two options, both of which would present faculty and students with the new face and the unique features of Sakai 3, and allow a more incremental and seamless transition to the next-generation LMS functionality as it became available. I also personally gathered that the ultimate decision will have to come down to facts on the ground, as they evolve. In short, we probably ought to concentrate on Sakai 2 now, but monitor the progress of Sakai 3. If the project moves at the pace projected in the roadmap then running 2 and 3 together in hybrid mode may well be a viable option. If not, running them separately initially might make more sense.
Another related important question will be what we use for portal functionality. Sakai 3 could hypothetically serve as a nice, flexible, portal interface. It is substantially more ambitious than the traditional LMS model. Certainly some of our people were thinking about this idea. And other institutions have as well. UC Berkeley, for example, is deploying Sakai 3 as its portal system for the coming Fall. But such a move at my campus would likely require a rethink of what our portal functionality should provide, and unlike Berkeley, we already have a portal constituency on campus. So I can imagine some political challenges as well.
Having just recently been involved in Miami’s decision to move from Blackboard to Sakai, I was asked to attend the annual Sakai conference along with our some of our IT and instructional design staff. I just got back last night. Here’s some thoughts and impressions.
For some background, I’m an academic whose focus has nothing to do with technology. Nevertheless, I have years of experience in working with open source communities on issues related to academic (mostly research) authoring (see, for example, my work on CSL, which is an outgrowth of work for OpenOffice). But because this work is not central to my academic position, I have tended to avoid investing cash and time resources in attending related technology conferences. With Sakai, though, it’s a little easier to justify my involvement, since it has direct impact on my teaching, and on the broader teaching and learning community at my institution. Aside from a talk I gave at a Code4Lib conference a few years ago, then, this is my first edu technology conference.
So what did I think in a nutshell? I was deeply impressed. The Sakai community is diverse, smart, passionate, and energetic. The sense of mission the community has is almost palpable. It is clear that there is a lot of deep thinking that happens in this world, and that there is a lot of discussion and community engagement around that. At the same time, this seems to be a quite pragmatic community as well. They know what they want to do, and they seem to know how to get there.
In particular, my respect for the Sakai 3 effort continues to grow. Before we made the decision to go with Sakai, I had already spent a lot of time looking at the project: downloading and running the current code, looking at the technical design, reading through the more user-oriented design documents, and talking to the Sakai product manager (Clay Fenlason) about the process by which they were realizing this ambitious vision for a next-generation LMS and collaboration system. So I was already really impressed with Sakai 3 before the conference. But at the conference, you can see how all this works is materialized.
I watched a demo of the NYU pilot project (see, for example, this session description), for example, that will be going live in the coming months. Because the lead Sakai 3 UI designer was in the room as well, we could have a collective discussion about details of the work, both now and in the future. What became clear in these and other discussion is that there are some really sharp people working on this project. At no time did a question come up where I got the impression that these people had anything but an absolutely clear focus on what they were doing.
I also went to a session that explained all the work and thinking behind this diagram.
This diagram represents a year of intense work of pedagogical experts from around the world, trying to imagine (and re-imagine) the core principles that should drive the design of a next-generation LMS. The idea is that nothing concrete moves forward with Sakai 3 without justification in these principles.
Here’s an image from the session:
The session drew broad participation. It wasn’t just instructional designers or pedagogy people in the room. The guy you see in the right foreground with the dark blue shirt is Clay, the product manager. There were also a number of programmers in the room involved in the discussion as well. This is really good to see, as there are sometimes obvious disconnects between more user-focused design people, and programmers. There were even a number of faculty participating in the session as well. This is what the Sakai world means when they say that Sakai is by educators for educators.
I was also struck that the design principles noted above, and the way that Sakai 3 is proceeding more concretely, is fully consistent with the educational mission of Miami. This is software that should beautifully enable more student-centered, integrative, learning and research collaboration in ways that are simply not possible in current generation LMSs. So my hope is that my institution fully embraces these possibilities, and contributes what it can to realizing them. Now is the time to think big!
Last week, I was part of a meeting that decided on a recommendation for Miami University’s LMS transition over the next year or so. We ultimately chose among four options:
- Blackboard 9 (stay with Blackboard, but move to next version)
Our ultimate choice was Sakai. I can’t say exactly what it was that ultimately organized the consensus around the choice, but my own argument in the meeting was roughly as follows:
- all of the current LMSs are more alike than not
- the open source options (both Moodle and Sakai) give the institution greater control over our own destiny going forward, with more options for support, for influencing the direction of the software, and for deciding when we want to transition to new versions
- Sakai in particular has a really smart forward-looking roadmap in v3 which is shaped by the right, pedagogically-oriented, vision
For me personally the plans for Sakai 3 were a primary differentiator. The tight coupling of a new architecture placed at the service of a shiny new interface that is easy-to-use and flexible, and which is designed based on user-testing from the beginning, is, I think, the right direction. The widget and template-based approach has the potential to make it easier and quicker for new users to get going. The devil will be in the details of exactly how well they implement these ideas, but I am looking forward to seeing how Sakai 3 evolves.
Now the real work will start for the IT staff here. They’ll have to figure out the best way to transition course content from Blackboard, to train faculty and students in how to best make use of Sakai, and set up some kind of governance structure to manage our relationship with this new technology. I’m hoping this can include some mechanism to get IT services staff and interested faculty involved in the Sakai community, and contributing in different ways to its future evolution.
Earlier, I covered some interesting new characteristics of Sakai 3, but want here to add another. Existing LMSes are hamstrung by a number of assumptions and limitations. To sum them up, today’s LMS tends to be both course-centric and tool-centric. If, for example, students that share two or three related courses want to setup a group, they can’t do it; the LMS assumes students are part of courses (or in some cases, non-course sites). Similarly, the LMS experience is constrained by a focus on discrete tools. If you want students to reflect on some ideas, and then host a discussion on them, you need them to go to two separate places: some webpage-like thing that describes the ideas, and then a separate forum where the discussion may happen. If the student wants to refer back-and-forth between the two areas, they need to do awkward things like open two windows or tabs, or do the browser back-and-forward button thing. This is a totally artificial limitation that has real consequences.
Thankfully, Sakai 3 does away with these limitations. Groups, for example, may exist independently of course and sites, and so will allow more flexible sorts of online sociability and collaboration among students, researchers, and so forth. On the tools front, Sakai 3 breaks down the walls that have previously divided them. If you want to host a discussion on some content, you can simply create your page, add the content, and then at the bottom of the page add a “discussion” widget. Upon doing so, a discussion thread will be available at the bottom of the page for students to view and contribute to.
The current UI has widgets for a variety of common features: polls (complete with a nice instant-view graph of the results), comments, quizzes, etc. But it also has some clever new ones, such as a Google Maps widget that allows you to embed a live Google Map (though as I geographer, I have to say that I’d really like to see more here, like the ability to ask for a country, and have it understand what I mean; this might be more a limitation of Google Maps though).
Here’s an example of what this looks like with the polling widget. First, we decide to add a poll to our page. We go to the “insert more” drop-down on the right side of our editor …
Once we select “poll” we get a dialog to set it up.
Note that this dialog pops up in place; no need to go to some separate page to manage this. Once we have it all ready and click “insert widget”, and save the page, we then see this, which is also what students will see …
When a student comes across this, again, they don’t have to go to some separate place to take the poll; they simply click their choice in place. Even more cool, once they’re done, the live widget presents the results of the survey in a graph view.
In turn, this graph will continuously update as other students take the poll!
A couple of months ago, Lance Speelmon at Indiana University presented a demo of this at a Sakai conference in Japan. You can see that starting at about the 23 minute mark or so of this video:
So let’s pause for a second and ponder the implications of this: I will be able to create a page for some topic in a class. I can add some text to present the issues for the topic and link to some background readings. I can then embed any other widget I want right there in the page! Bigger picture, this widget architecture is designed to be easy to work with for developers. So if I have some idea for a great new widget, any on-campus developer with basic web development skills could hypothetically help me create that widget.
When I started pondering what I want in a next-generation LMS, this is exactly the sort of thing I was imagining!
So in trying to come to a conclusion on Moodle vs. Sakai, it’s easy to get wrapped up in the minutia of feature comparisons and such. It seems to me, however, it’s important to keep in view the larger, longer-term, picture. In this case, that in part involves the strategic directions for these two projects, which will give us a sense of where they might be in five years. To wit, below is my understanding of Moodle 2 and Sakai 3. Am in a bit of a hurry with end of semester chaos, so please correct me if I have anything wrong here, or if I’m missing important details.
As I read it, Moodle 2 is a significant change to the platform, but a largely incremental one. The primary change appear to be the addition of a repository API, which provides a flexible way to add access to different kinds of resource repositories. For example, there is a plug-in that uses this API to make it easy for users to browse and insert images from Flickr from within the standard Moodle editing tools. In addition, there is work on new features, many of which are outlined in the following video:
In other news, there appears to be independent work on making Moodle friendly for mobile devices. Here’s a video of one such example:
From what I can tell, Moodle 2.0 will be ready for deployment sometime later in 2011.
Sakai 3, on the other hand, is a more radical change: effectively a complete rewrite of the platform. This rewrite involves building the Sakai-related functionality on top of other, more generic, open source code. The new core code, and hence what the Sakai community is responsible for maintaining, is dramatically less than the old; at present a reduction of close to 90% of the code base! In addition, one of the core developers on the new Sakai core has also become a developer on the Apache Sling project on which the Sakai 3 core is based. This reflects some smart strategic decisions, and should provide a focused, easy-to-develop and maintain foundation.
Following are a few examples we can glean of what this might look like from the design wireframes (visual mockups, not necessarily running code at this point) and the running demo code.
Example: Everything is Content
Michael Feldstein does a good job explaining what this all means. But perhaps some pictures will make the implications more immediately apparent. Consider search. Because existing LMSs are both organized based on courses and tools, its quite awkward to search for content (forum posts, blog posts, assignment or page content, etc.) globally. On the other hand, consider this proposed search UI for Sakai 3: So one does not go into, say, a forum and search the forum. Rather, one has a search interface that is the same whether you search the entire university’s content, or an individual course. That integrated search interface looks beautiful, and will be instantly familiar to anyone used to using contemporary web interfaces.
A few more screenshots follow below, these all from the actual current Sakai 3 demo server.
Example: Widgets for Integrating Different Content
The new interface is based on widgets, which allows you to quickly add different blocks of features, and move them around as well. Because of the new core foundation, these widgets are also designed to be really easy to develop, so that it’s much easier to add new functionality. In this view, for example, you see a “widget” I’ve added to access my Google Docs documents from within Sakai.
One design priority for Sakai 3 is to make editing content much easier. Here we see the clean new editing interface.
In addition, all content is versioned, so that you can easily step back through changes, and see who made what changes. Since all content is treated uniformally in Sakai 3, there are no artificial limitations in how this versioning support can be applied. Here’s what it looks like the UI currently:
What I get out of all of this is that Sakai 3 will be more scalable (faster), more flexible, more elegant and easier-to-use: a brand new LMS designed for the needs of the 21st century. The devil will still be in the details of exactly how they implement specific features (gradebook, assignments, etc.) on top of this new core, but I am also really encouraged by what I am seeing of the design process. It demonstrates an attention to detail that is necessary to do this right.
The current roadmap is that it should be ready for large-scale deployment sometime in mid-to-late 2011 [I corrected the year from 2012, per comment below]. Also, there’s some work going on (at Indiana?) in allowing mixed 2-3 deployment; using v2 tools within a v3 context for example.