Prologue as an eLearning Blog Portal
As I’ve touched on recently, I’m very interested in exploring the capacity of blogs to enhance and support the educational process, both from the standpoint of independent learning and exploration, and adaptation to more traditional classroom activities. However while the former is easily implemented, the latter requires much more consideration and there have historically been some holes in my vision that needed fleshing out.
With Monday’s launch of Prologue, a new possibility has been injected into the mix that I’d like to explore here for a moment.
Pedagogy and learning objectives aside, the main challenge for educators using blogs in their courses is how to keep track of them all. By nature blogs function completely independently of one another, so the prospect of monitoring the individual blogging activities of several dozen or more people presents a substantial time investment for instructors and students alike.
So much so that this could impact upon the effectiveness and sustainability of the exercise. Thus the need for a central blog portal is introduced.
Instructors could of course create a static web page with a full list of student names, blogs and links - but this would only act as an index. It would do nothing to aggregate the information contained in the blogs, nor establish or reinforce the feeling of a dynamic, interactive student network.
Using RSS would be another option, and is a far better one than a static blog list. However this too represents a perhaps unnecessary task, because students would be required to add the feeds of every single one of their classmates into a feed reader. Furthermore, every student would have to repeat the same process; it couldn’t be done just once.
The third, and arguably the best, option would be the creation of a Prologue blog to act as a central hub or portal. In this case the instructor would act as editor with all students added as approved contributors. This would enable several important activities:
First and most significantly, notification of student activities could be centralised. Students would be able to post and locate updates on anything from announcements of new blog posts or study sessions, questions, general anecdotes, useful links, or news stories. Instructors could also use this as a dissemination point for assignments, or a way to start discussions and answer questions.
Additionally, unlike the RSS option, the establishing of the portal would only have to be done once because it’s a shared space.
Second, Prologue features several different filtering options for locating specific subjects. For example clicking on the name of a post author will bring up all their posts, which means instructors could easily track the activities of each individual student.
Third, and in the same vein as the second point, Prologue’s tagging option enables further organization. Using this feature instructor’s could establish a naming convention for categorising posts on specific assignments, student groups, course sessions, or academic years.
Importantly, each tag is assigned a unique URL that will bring up all posts tagged with the same term. Tags are also allocated their own unique RSS feed that can be added to any feed aggregator. Students and instructors then have the choice between a single aggregated feed for the whole portal, and a narrowed feed filtered by a specific tag.
Fourth and significantly, the organisational opportunities present in Prologue have powerful implications. They highlight the fact that instructors need not create a different hub for every class, but could in fact have a single portal for all their courses. This is extremely significant from a student perspective, because it would substantially expand their potential support network and access to information by pointing them to work of their predecessors.
Over time this could be developed into a massive knowledge base of information on related subject matter.
Wednesday, January 30th, 2008

