One of the most important concepts in the LMOS Project Vision and Mission Statements is the service broker. In fact, it may very well be the most important concept. But it can be a little abstract, especially for non-technologists (like me). In the next couple of posts, I’m going to do my best to explain what it is and why it could make a very big difference in the evolution of learning management systems.
Tag: Moodle
-
Towards an Education Inflected Architecture
The title of this post was also the title of a talk by Barbara Taranto, the Director of the Digital Library Program at the New York Public Library at yesterday’s FIT conference. I just love it. An “education inflected architecture” is exactly what I crave. But beyond that, Barbara poses exactly the right challenge:
For faculty and the organizational structures that support their work, it has been a bit of a rough ride –mastering new tools for collecting, analyzing and organizing information and at the same time accepting the responsibility of managing the outcome of all the collecting, analyzing and organizing activities that so persistently carry on. But for software developers, including some very prominent academic ones, it has been a free-for-all, an ideal market for real life R&D. Every week, or perhaps even every day, there is a new tool or a “better way” to do one’s job, a new piece of software to have and to learn and to use, a new widget, gadget, and for some, a new toy that needs no marketing other than to say it is a solution to a problem we didn’t know we had. And so for a very long time the focus of administrative activity has been on this shifting, volatile environment and how best to adapt to the “new student” and how best to create the “new university” in order to meet the needs of the “users”, generic-faced as they may be, even when the idea of the new university is not even well articulated by its greatest proponents.
But amidst all the busyness, the balance and direction of the academe seems to have moved beneath our feet. The lauded best practices of instruction and research are often driven by software development and the overbearing individualist psychology of the consumer rather than by any higher purpose. We are encouraged qua instructors to describe our work –even our passion– as a “service” to others, and to proscribe future work as a functional unit –an economic widget; and qua researchers, to insist on further resources to meet our individual needs. In my mind, the model is dysmorphic and very possibly unsustainable–certainly undesireable. I suggest that for education practice to right itself, to flourish and evolve, and for students and academics to get back to the work of learning we need to shed the technology carapace and develop a new education inflected archtecture.”
To sum up, we have to stop deciding what we’re trying to accomplish based on what our tools make easy (or hard) to do and start deciding what our tools need to look like in order to help us with what we’re trying to accomplish. That’s…well…a lot harder than it sounds. Because computers are essentially stupid, they force us to explicitly map out even the very basics of what we’re trying to do. It’s easy to make these maps incompletely or even inaccurately, in part because some of what we’re trying to articulate explicitly is inherently tacit knowledge.
So what to do? I think we need to fundamentally change our software development practices. Agile development, a family of development techniques that seeks to tighten the feedback loop for developers so they don’t drift too far into theory land, certainly gets us part of the way there. My experience with software development teams creating applications for which they themselves are not the primary users is that they are best not left unsupervised for long periods of time. But I think we need more, too. Barbara is right: we need an education inflected architecture. Or, to put it another way, we need an architecture that can be inflected (or influenced, or evolved) by educators.
In a recent four–part interview, JotSpot CEO Joe Kraus gives us some hints as to what that might mean. (more…)
-
The Portal is the Platform, Part II
This post is part of a series on the concept of a Learning Management Operating System.
Ben Brophy raised an important point in his comment on my last post in this series regarding the different ways in which portals can be used with an application. As he points out, My Yahoo! just provides windows to external applications , while some other portals actually pull the entire applications into the portal itself. To be clear, I favor the latter approach over the former for LMOS designs. In other words, an LMOS should not just have a portal; it should essentially be a portal. There are a variety of technical, cultural, and usability reasons for this, some of which I won’t get into in this post, but the main one is related to the history of LMS design and why I think they generally have sucked so badly for so long. (more…)
-
Now, That's What I'm Talkin' 'bout!
An excerpt from Sakai’s press release regarding a demonstration of the IMS Tool Interoperability (TI) standard:
The demonstration included four LMS systems including BlackBoard, WebCT, Sakai, and Moodle. The demonstration included three applications: Concept Tutor, Samigo(Sakai), and QuestionMark. All LMS/Application combinations worked and were demonstrated at the meeting which validates the interoperability of the IMS TI specification.
The demonstration was the culmination of nine months of significant co-design and engineering between all of the participants.
Now that the interoperability demonstration is complete, the standard is expected to be published Fall 2005. As long as the standard is finalized in time, we expect that this feature will be present in the Sakai 2.1 release in the Fall 2005.
-
Course Management Systems and Pedagogical Models
By way of edTechPost, we find this article at Dublin City University. Beyond the fact that this is a fairly large program adopting Moodle and bringing it into the big leagues, there’s this noteworthy observation embedded in DCU’s white paper:
Another problem in adopting a commercial VLE was that it might constrain us to its inherent pedagogical model. Like many commercial products, WebCT is driven by an American/Canadian pedagogical paradigm; there is nothing intrinsically wrong with this model, but it is not entirely compatible with UK and Irish teaching and learning methodologies.
Open source software is usually developed as a public collaboration and the source code is freely available for users to modify. Adopting an open source VLE would enable DCU to contribute to the development of the software and hence to take a leadership position in the academic development and understanding of e-learning, opportunities which would be significantly weaker if we simply deployed a closed source, proprietary, VLE.
First, their point that interface is not instructional design-neutral is vital. These systems provide more than just URLs for locating content; they provide containers that shape both content and experience. Whether you use Blackboard, Moodle, or MovableType to host your class, you are making choices about the affordances that you can or cannot leverage as part of your pedagogy. And, of course, no system has all plusses and no minuses. This is about engineering. It’s about trade-offs and best fit between course environment and the instructional philosophies of the teachers and the institution as a whole.
Furthermore, the DCU folks clearly realize that contributing to an Open Source platform means contributing best pedagogical practices to the educational community in form of source code. Being able to see and duplicate how other teachers set up their classrooms (whether virtual or not) is valuable to teachers.
Good stuff.
