e-Literate

Present is Prologue

Tag: Moodle

  • Moodle for iPhone Demo

    Here’s an interesting (and unusually high production value) video of an iPhone mobile interface for Moodle:

    Moodle also has a Java-based cross-platform mobile client which is not as pretty but seems to have decent functionality. (My impression is that this is fairly similar to the state of affairs with Blackboard’s mobile clients.) You can see screen shots here.

    In the long run, we’re going to need to think seriously about creating more teaching and learning affordances that are mobile-specific rather than just creating mobile interfaces to existing LMS capabilities, but this is still a good step down the road.

  • Sakai 3: The Benefits of 'Everything is Content'

    One of the more radical departures that Sakai 3 makes from traditional LMS design is that everything in the system is treated as content. A traditional LMS is an aggregation of tools—discussion boards, grade books, test engines, wikis, assignment drop boxes, etc.—each of which has its own data model in a relational database. It’s really a hodgepodge of separately designed tools that are knitted together through a user interface layer and a few common services. In contrast, Sakai 3 is being built on top of the Apache Jackrabbit reference implementation of the Java Content Repository (JCR) standard. Everything is treated as content, including grades, test questions and answers, discussion threads, syllabi, personal profiles, chat messages, and so on.

    This approach has some benefits in terms of shoring up common weaknesses in LMS designs. But, more profoundly, it also leads to some pretty fundamental changes in the way that learning environments can work, thanks in large part to the strong and growing adoption and maturation of useful content integration standards.

    (more…)

  • IMS Learning Information Services: The State of the Union

    Regular e-Literate readers know that I am a big booster of the IMS Learning Information Services specification. (For an overview of the basics of the specification, see my posts here, here, and here.) There has been a lot of news recently about adoption, and I thought it would be worthwhile to pull together a unified post of who is doing what. I’m going to divide vendors and projects into a few different categories based on their released code, public commitments, etc.

    (more…)

  • Blackboard's Response to Open Source: Fear, Uncertainty, Doubt

    Blackboard has not been having a good time in the state of North Carolina. As I noted recently, the University of North Carolina (a Blackboard customer) reported highly favorable results of their pilot study of Sakai, with an outcome of further investigation into Sakai as a full replacement of Blackboard as their primary LMS. It turns out that this was following on the heels of a similar study done by the North Carolina Community College system favorably comparing Moodle to Blackboard. The details were different but some of the underlying dynamics were the same: the open source system in each case was found to be functionally equivalent to Blackboard for all practical purposes, the open source platforms did roughly as well as Blackboard (in the Moodle evaluation) or better than Blackboard (in the Sakai case) in usability evaluations, and Blackboard was deemed to be expensive relative to the alternatives.

    What’s interesting in the Moodle evaluation is that Blackboard wrote a response, which was published by the North Carolina Community College System (NCCCS). And the heart of the response is a swipe at open source with many claims that are…factually and logically questionable.

    Unfortunately, the PDF has some sort of copy protection on it that prevents copy/paste. (I thought Blackboard was on an openness kick….) So I have laboriously retyped the section of the response entitled “Top Five Risks to Consider When Evaluating Open Source” so that we can weigh the strengths of Blackboard’s arguments together. I apologize for any mistranscriptions.

    Here we go:

    (more…)

  • Moodle, Wave, and Widgets (Oh my!)

    Scott Wilson , Paul Sharples, Dai Griffiths and Kris Popat have an article up on their work embedding Wave-enabled widgets into Moodle using Wookie. (Try saying that ten times fast.) What they envision is very similar in a lot of ways to what my former SUNY colleagues and I were thinking about when we proposed a Learning Management Operating System. Of course, that was 2005, so we were thinking about portlets rather than widgets. The lower barrier to entry and client-side nature of widgets are game changers.

    Anyway, it’s a very good piece, well worth reading. A couple of points jumped out at me. First:

    Rather than just being a like-for-like replacement, the Widgets update in real-time without any page refresh, and this affects user behavior. Rather than clicking links to launch tools or to view content, the Widgets encourage more of a “monitoring” mode of operation, with users navigating to a course page, then leaving it open in the background, occasionally bringing it into focus to see if any new conversations were happening in the chat widget, or the voting results had changed.

    If this finding bears out with further research, it could be a fairly big deal. For one thing, it has the potential of making the learning environment a lot stickier and more Facebook-like (in a good way). At the same time, it should force some pretty substantial refactoring of core LMS tools, which simply aren’t designed for monitoring. The two models are likely to clash.

    Here’s another interesting—and problematic—bit:

    Another consequence of Widgets is that far less tracking information is available at a micro-level, as interactions with Widgets are not made available to the VLE. This implies that a new model for tracking will need to be developed for such systems; this may be a useful opportunity to reconsider tracking in more sophisticated terms than page views and hits. For example, it may be useful to separate out measures of attention, using something like APML[12], and measures of user effort, using something like User Labor Markup Language (ULML[13]).

    The thing is, we’re  just now beginning to develop models where we can identify at-risk students and, more importantly, help them self-identify and self-remediate based on the data from the learning environment. The fact that this trend is in direct tension with the whole Web-2.0-in-the-learning-environment trend is underappreciated. We need to solve this problem.

  • Blackboard vs. Moodle: North Carolina Community Colleges Assessment

    A while back, I wrote a post giving advice to small schools about selecting a new LMS. That post turned out to be reasonably popular. Today somebody sent me a link to a study done by the North Carolina Community College System comparing Blackboard to Moodle and, in particular, talking about the experience of some small colleges that had migrated from the former to the latter. The results are pretty consistent with the advice I gave.

    Here are the highlights, along with their correlations to my earlier points: (more…)

  • Great Little Conference in Upstate New York

    My buddy Patrick Masson is running his second annual 2-3-98 conference in Delhi, NY on August 6th and 7th. The first day is all about open source in higher education with a keynote by Bob Sutor, IBM’s Vice President of Open Source and Linux. The second day is a Moodlemoot. Last year’s conference was great—good presentations, interesting attendees, and good food. If you get a chance, you should go to this conference. It’s good—and good for you!