<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Conceptual Design of EduFeedr - an Educationally Enhanced Mash-up Tool for Agora Courses</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Hans Põldoja</string-name>
          <email>Hans.Poldoja@tlu.ee</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mart Laanpere</string-name>
          <email>Mart.Laanpere@tlu.ee</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Tallinn University, Institute of Informatics</institution>
          ,
          <addr-line>Narva mnt 25, 10120 Tallinn</addr-line>
          ,
          <country country="EE">Estonia</country>
        </aff>
      </contrib-group>
      <fpage>98</fpage>
      <lpage>101</lpage>
      <abstract>
        <p>The use of blogs in online courses has become increasingly popular. Current RSS feed readers lack special features to monitor the process of collaborative knowledge building in these agora type of courses. In this paper we present the conceptual design of an educationally enhanced feed reader and mash-up tool that is work-in-progress. 1 LeMill. http://lemill.net</p>
      </abstract>
      <kwd-group>
        <kwd>mash-up learning environments</kwd>
        <kwd>feed readers</kwd>
        <kwd>scenario-based design</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>Increasing number of educational institutions are making their courses openly
available in the Web. However, open course could be a confusing term because
openness can have several meanings: open access to static content such as in MIT
OpenCourseWare, use of an open learning environment based on Web 2.0 tools or a
course in traditional LMS with an open registration. In this paper we are focusing on
specific kind of open courses that share all of the following three criteria: (1) openly
accessible content, (2) open personal learning environment, and (3) free and open
registration for participation. We propose to use a new term — agora course — while
referring to courses of this kind. Agora is a Greek word for a place for assembly or an
ancient marketplace.</p>
      <p>
        In spring 2008 the author of this paper was teaching an agora course in University
of Art and Design Helsinki. On that course Wikiversity was used as a central
component of the learning environment [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Other tools that were used in the course
contained teachers’ blog in Wordpress.com, students’ blogs on various blogging
platforms, social bookmarking service (Delicious) and Web 2.0 environments for
sharing content that was created by the participants (LeMill1, photo sharing websites,
podcast hosting websites and video sharing websites). The course started with more
than 50 participants who signed up on a wiki page. Number of people who sign up for
the open course may grow rapidly if the course receives attention in the blogosphere.
For instance, more than 1200 people signed up for an open course Connectivism and
Connective Knowledge in summer 2008 [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>While setting up a course wiki (e.g. at the Wikiversity portal) is a simple task, it
does not cover all the functionalities needed for smooth and effortless management of
teaching and learning activities. This paper addresses the challenges of designing one
of the central components of a mash-up personal learning environment for agora
courses: an educationally enhanced mash-up tool that supports planning, monitoring
and analyzing learning activities which cross the borders of different Web 2.0
applications.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Aggregating News Feeds in Mash-up Learning Environments</title>
      <p>Large number of participants who all post in their personal blogs (which, in most
cases, are using different hosting providers and blog software) and use various Web
2.0 environments for other type of content creates a challenge for a facilitator: how to
reduce the overhead work while trying to follow the activities that take place on the
course and to provide feedback for all the participants.</p>
      <p>Currently the authors have used Pageflakes online feed reader for creating shared
pages that display all the blog posts and comments. These pages are useful to get a
quick overview but the recent changes are not specially emphasized. Therefore a
standard desktop RSS reader was also used. During these courses it came out that
standard feed readers lack several features that would be important for online courses.
For example in RSS readers typically new posts are emphasized, but in a course with
many participants it is equally important to notice when somebody is left behind. It is
also important for the facilitator to see in one glance the "big picture" of the activities
taking place on the course, especially the feedback given by one student to another (in
order to monitor the intensity of collaborative knowledge building). These special
features have been always present in traditional learning management systems, but if
we want to keep our agora courses as open as possible, we should allow our students
to use their own personal learning environments.</p>
      <p>
        There have been some studies and developments in the similar direction such as
MUPPLE [
        <xref ref-type="bibr" rid="ref3 ref9">3</xref>
        ], simple aggregating mash-up The Wire [
        <xref ref-type="bibr" rid="ref10 ref4">4</xref>
        ] and knowledge discovery
application PALADIN [
        <xref ref-type="bibr" rid="ref11 ref5">5</xref>
        ], but none of these are addressing exactly the needs.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Conceptual Design of EduFeedr</title>
      <p>
        Our study is based on the design-based research methodology [
        <xref ref-type="bibr" rid="ref12 ref6">6</xref>
        ], involving iterative
scenario-based design [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] and lightweight prototyping [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>In order to clarify the design requirements a lightweight prototype was built using
Bento personal database application for Mac OS X. All the blog posts and comments
that were written by the participants were stored in Bento database in webarchive
format. It was possible to browse posts and comments by the participant, write short
notes about the blog posts and add ratings. The prototype was used in a course that
had quite detailed assessment scheme. Final scores for all the students were calculated
automatically based on the ratings. Some students decided to delete their blogs soon
after the course was over. Complete archive of course discussions was still available
in the database. The main limitation of Bento database was lack of RSS reader. All
the blog posts had to be saved manually. Because of these limitations it was decided
to design an online tool that would function both as a feed reader and database for
managing course discussions.</p>
      <p>This new tool called EduFeedr had the following initial design requirements: (1) it
should aggregate information from all major blogging platforms using open standards
(RSS, Atom, trackback, pingback); (2) it should not require any special plug-in on the
student blogs; (3) the scope of EduFeedr is limited with aggregating and annotating
the feeds from both teacher’s and students’ PLE’s and visualizing the process of
knowledge building; (4) only teacher has an user account in EduFeedr, which allows
her to modify the EduFeedr settings; (5) anyone has read access to aggregated course
content.</p>
      <p>In the second iteration of the design we wrote a set of scenarios that describe the
main features of EduFeedr. Six scenarios covered typical use cases such as setting up
the course, writing a blog post, browsing the blog posts, writing comments and
archiving the course. The scenarios were published in a wiki where other people were
able to post their comments2. An example scenario is presented in figure 1.</p>
      <p>John has been using EduFeedr for a few weeks. For him the most exiting feature is the way
how connections between the blogs are presented. EduFeedr has a visualization where all the
blogs are displayed as nodes. Lines between the nodes show the links between the blog posts.
All the students have linked to the course blog. Some of the student blogs have a lot of
connections while others have not been so active.</p>
      <p>It is possible to switch on a different view and see who has commented which blog. This
time John finds out that some student blogs have actually more comments than his blog.</p>
      <p>The same information is also displayed as a table where it is easy to see how many
pingbacks and comments each participant has made. EduFeedr has also aggregated all the
comments. It means that John can see all comments that one student has made on a same page
without visiting all the blogs. This will save him a lot of time, because commenting is part of
his grading scheme and students get points for that.</p>
      <p>In order to start using the EduFeedr a course must be created by the teacher. The
students can use any blogging platform that they like. It is suggested to create a new
category for course related blog posts or a special blog for the course. Instead of
adding their blog addresses to the wiki page the students will submit their blogs on the
course page in EduFeedr. The facilitator can also specify tags that have a specific
meaning. For example it is possible to make all blog posts with a tag “urgent” to stand
out in the feed.</p>
      <p>One of the complicated aspects of blog-based courses is connecting students’ blog
posts with the assignments. One approach is to connect blog posts with assignments
by the date when the post was published. This does not require any special input from
the student but unfortunately it would work only when all students submit their posts
in time. Another approach is to agree a special tag for each assignment. Our
experience with using tags shows that it is quite common to misspell or leave out the
tag. In EduFeedr scenarios we decided to use a third approach. Students are asked to
2 EduFeedr scenarios. https://wiki.mozilla.org/EduFeedr_Blueprint
include a link to the original assignment in their blog post. This is a common blogging
practice to refer to another blog. Course blog will receive a notification comment
using trackback or pingback method. EduFeedr can connect assignments with blog
posts based on these notifications. This approach has also some limitations. Blogger
blogging platform do not send trackback or pingback notifications to other blogs. That
can be solved by parsing all student blogs with Trackback ‘em All script3.</p>
    </sec>
    <sec id="sec-4">
      <title>4 Conclusions and Future Work</title>
      <p>This paper described the work that is still in progress. The next step is to choose a
suitable open source platform to be used for developing and validating EduFeedr
prototype. Potential candidates are POSH4, rawdog5 and Tornado6.</p>
      <p>Acknowledgments. This study was funded by MER targeted research grant No.
0130159s08.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Leinonen</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vadén</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Suoranta</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>Learning in and with an open wiki project: Wikiversity's potential in global capacity building</article-title>
          .
          <source>First Monday</source>
          <volume>14</volume>
          (
          <issue>2</issue>
          ), (
          <year>2009</year>
          ). http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2252/2093
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Siemens</surname>
          </string-name>
          , G.:
          <article-title>MOOC or Mega-Connectivism Course</article-title>
          . (
          <year>2008</year>
          ). http://ltc.umanitoba.ca/connectivism/?p=
          <fpage>53</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Wild</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mödritscher</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sigurdarson</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Designing for Change: Mash-Up Personal Learning Environments</article-title>
          .
          <source>eLearning Papers 9</source>
          , (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Schmidt</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>The Wire (pre alpha) - aggregate blog posts and comments</article-title>
          . (
          <year>2009</year>
          ). http://bokaap.net/open-edu/
          <article-title>the-wire-pre-alpha-aggregate-blog-posts-and-comments/</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Klamma</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Spaniol</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dimitar</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>PALADIN: A Pattern Based Approach to Knowledge Discovery in Digital Social Networks</article-title>
          . In: Tochtermann,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Maurer</surname>
          </string-name>
          , H. (eds.).
          <source>Proceedings of I-KNOW '06, 6th International Conference on Knowledge Management, Graz, Austria, September 6 - 8</source>
          , pp.
          <fpage>457</fpage>
          --
          <lpage>464</lpage>
          . Springer, Heidelberg (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hannafin</surname>
            ,
            <given-names>M. J.</given-names>
          </string-name>
          :
          <article-title>Design-based research and technology-enhanced learning environments</article-title>
          .
          <source>Educational Technology Research and Development</source>
          ,
          <volume>53</volume>
          (
          <issue>4</issue>
          ),
          <fpage>5</fpage>
          --
          <lpage>23</lpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Carroll</surname>
            ,
            <given-names>J.M.</given-names>
          </string-name>
          :
          <string-name>
            <given-names>Making</given-names>
            <surname>Use</surname>
          </string-name>
          .
          <article-title>Scenario-Based Design of Human-Computer Interactions</article-title>
          . The MIT Press, Massachusetts (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Heyer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brereton</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Reflective Agile Iterative Design</article-title>
          . In: International Workshop on Social Interaction and
          <string-name>
            <given-names>Mundane</given-names>
            <surname>Technologies</surname>
          </string-name>
          , Cambridge (
          <year>2008</year>
          ). http://mundanetechnologies.com/goings-on/workshop/cambridge/papers/HeyerBrereton.pdf
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>3 Trackback 'em All. http://scott.yang.id.au/code/trackback-em-all/</mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>4 POSH. http://sourceforge.net/projects/posh/</mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          <article-title>5 rawdog</article-title>
          . http://offog.org/code/rawdog.html
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>6 Tornado. http://www.tornadoweb.org</mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>