<!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>LOExtractor - Rapid Authoring Tool to Support Workflow-Embedded Authoring</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Oleg Rostanin</string-name>
          <email>oleg.rostanin@dfki.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Markus Ludwar</string-name>
          <email>markusludwar@gmx.de</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>German Research Center for Artificial Intelligence (DFKI)</institution>
          ,
          <addr-line>Kaiserslautern</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>University of Kaiserslautern</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <fpage>17</fpage>
      <lpage>20</lpage>
      <abstract>
        <p>Creation of reusable learning content in the process of work is a challenging but promising trend in e-learning and knowledge management. Whereas well established authoring methodologies like instructional system design seem to be too complicated to be used by employees during their work, new authoring methods using rapid authoring tools do not provide content quality that is enough to support goal-oriented adaptive learning. To overcome the shortcomings of the rapid authoring tools, the authors designed and implemented an alternative authoring tool LOExtractor that is aimed to support learning content authoring in workflows.</p>
      </abstract>
      <kwd-group>
        <kwd>workflow embedded authoring</kwd>
        <kwd>rapid authoring</kwd>
        <kwd>concept map</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>2</p>
    </sec>
    <sec id="sec-2">
      <title>SLEAM Authoring Process</title>
      <p>
        SLEAM stands for Search, Learn, Extract, Annotate, Map that are the main
phases of the proposed authoring process. The SLEAM authoring process is
based on the reuse of document parts as LOs. The output of the process are
reusable LOs that are annotated with metadata and mapped to corresponding
concepts in the concept map. The output of the SLEAM processes provides a
basis for automatic goal-oriented compilation of learning programmes that are
adapted to the user’s needs and skills [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. On fig. 1 the main phases of SLEAM
are shown in the working context:
1. After a user starts a new task, a knowledge gap preventing the user to
perform the task might be identified. Identification of the knowledge gap can
be done by the working environment (e.g. workflow management system, see
[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]) or by the user herself.
2. Search: After identifying a knowledge gap the user starts looking for the
necessary information in the internet, intranet or in the corporate DMS.
3. Learn: After the user found the relevant information, the process of learning
is started. If the found information does not satisfy current user’s needs the
process of search is repeated. If the user satisfied his information needs she
can return to the task and complete it.
4. Extract: The system asks user whether the found information can be reused
by other team members in the context of similar tasks and offers her to
extract reusable LOs from the documents. If the user agrees, a
contextaware rapid authoring tool is started that allows the user easily to extract
parts of documents or web pages as reusable LOs.
5. Annotate: After the LO extraction the user is proposed to annotate extracted
LOs with metadata. User context information should be used to assist the
user in annotating LOs with metadata (author, task name, search query).
6. Map: In order that the LOs could be efficiently used in the process of the
workflow-embedded e-learning, they have to be mapped to the ontology of
learning concepts or the concept map(see [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]).
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Prototypical Implementation of a Rapid Authoring</title>
    </sec>
    <sec id="sec-4">
      <title>Tool - LOExtractor</title>
      <p>To support the SLEAM process, an experimental authoring tool called
LOExtractor was implemented. The tool helps knowledge workers to selectively
transform the information that they found and used during their work into reusable
LOs and map them to the corresponding concepts in the concept map.</p>
      <p>LOExtractor (see fig. 2) allows authors browsing in the hierarchical structure
of the documents to be transformed (e.g. a HTML page or PDF document), see
content of the document nodes in the detail pane (see upper right frame). The
detail pane consists of three view types: text view, image view and table view to
display plain text nodes, images and tables in the document respectively. The
author can also concatenate document nodes, delete them or choose for extraction.
The document nodes that will be extracted as LOs can be annotated with
simple metadata (author, title, keywords, language) and mapped to a corresponding
concept from the imported concept map (see lower right frame). After mapping
the tree nodes to the concepts, the author initiates LO extraction procedure by
clicking the corresponding menu in the LOExtractor GUI.</p>
      <p>
        LOExtractor is build using Eclipse RCP plattform5 and has an open
pluginbased architecture. The tool can be extended by providing input filter plugins
and extractor plugins that allow to import different types of information and
export extracted LOs in different formats. At the moment, input plugins for
MediaWiki6 content and HTML content and extractor plugin for SCORM and
DaMiT7 formats are realized. MediaWiki was chosen as a source of LOs, because
it is a outstanding representative of wikis8 that are commonly used tools for
capturing the tacit knowledge in companies [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] that can be valuable source for
creating reusable LOs.
4
      </p>
    </sec>
    <sec id="sec-5">
      <title>Conclusion</title>
      <p>The objective of this paper is to present a novel rapid authoring tool
LOExtractor that is aimed to overcome weaknesses of rapid e-learning tools by assisting
5 http://www.eclipse.org/home/categories/rcp.php
6 http://www.mediawiki.org/wiki/MediaWiki
7 http://damit.dfki.de/
8 http://en.wikipedia.org/wiki/Wiki
authors at extracting reusable LOs from the existing documents, helping to
annotate them with metadata and bind them to the concept from an individual
or collaborative concept map. The ongoing step will be to evaluate the SLEAM
approach and LOExtractor tool that will be done in 3 steps: 1)usability test for
creating a project management course for self-study; 2)internal group usage at
DFKI in parallel with using workflow-embedded e-learning; 3)dependently on
the results of the step 2) a case with external partner can be conducted. The
main goal of the planned case studies will be to check the feasibility of the
approach, find new requirements and opportunities to better intergrate the tool
into the process of work.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Mohan</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Daniel</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <article-title>The Learning Objects Approach: Challenges and Opportunities</article-title>
          .
          <source>Proceedings of the E-Learn</source>
          <year>2004</year>
          , Washington,
          <fpage>2512</fpage>
          -
          <lpage>2519</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Rostanin</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ludwar</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>From Informal Learner to Active Content Provider: SLEAM Approach</article-title>
          .
          <source>In proceedings of the second European Conference on Technology Enhanced Learning, ECTEL 07</source>
          ,
          <year>September 2007</year>
          , Crete, Greece.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Rostanin</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shirru</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <article-title>Identification of User's Learning Goals in Workflows</article-title>
          .
          <source>In proceedings of the Joint Workshop on Professional Learning, Competence Development and Knowledge Management</source>
          ,
          <year>October 2006</year>
          , Crete, Greece
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Rostanin</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ulrich</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Holz</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Song</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Project</surname>
            <given-names>TEAL</given-names>
          </string-name>
          :
          <article-title>Add Adaptive e-Learning to your Workflows</article-title>
          .
          <source>In proceedings of IKNOW</source>
          <year>2006</year>
          ,
          <volume>6</volume>
          -
          <fpage>8</fpage>
          Sept. Graz.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Decker</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ras</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rech</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Klein</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hoecht</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <article-title>Using Wikis to Manage Use Cases: Experiences and Outlook</article-title>
          .
          <source>In proceedings of the international Workshop on Learning Software Organizations and Requirements Engineering (LSO+RE</source>
          <year>2006</year>
          ),
          <source>March 27th - 28th</source>
          ,
          <year>2006</year>
          , Hannover, Germany.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>