<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://igi.indrastra.com/items?output=omeka-xml&amp;page=159&amp;sort_field=Dublin+Core%2CCreator" accessDate="2026-05-10T23:12:28+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>159</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1340" public="1" featured="0">
    <collection collectionId="36">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27119">
                <text>Maloku, Valdrin</text>
              </elementText>
              <elementText elementTextId="27120">
                <text>Ebner, Markus</text>
              </elementText>
              <elementText elementTextId="27121">
                <text>Ebner, Martin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27122">
                <text>2018-09-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27123">
                <text>The didactic method of digital, game-based learning includes integrating educational content or learning standards into video games with the objective to engage pupils. The method combines instructional content with computer or video games and can be used with all subjects and at all ability levels. Exponents of digital game-based learning argue that it provides learning opportunities which involve learners in interactive teaching and encourages them to take part in the technological society of the 21st century. The necessity of digital, game-based learning arose in the last decades of the 20th century as world-wide improvements in innovation took place. Today's learners live their lives with easy access to technology. This paper discusses the need for, motivation for and adjustment of digital, game-based learning to meet the needs of contemporary and the future generations of learners. Specifically, a game prototype for pupils of 9 to 10 years of age was implemented and evaluated. A simple mathematical game was created to help children practice mathematical skills in a fun, logical, thoughtful, enjoyable, amusing and light-hearted way. The results of the evaluation showed that children were interested in using mobile devices to learn mathematics, and especially the multiplication table. During the study, children tried both to achieve positive results and enjoyed the game. Our findings indicate that using mobile-based games encourages a positive mental outlook in pupils toward mathematics, ensures their dynamic, noteworthy participation and supports the acquisition of mathematical knowledge.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27124">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="27125">
                <text>https://online-journals.org/index.php/i-jim/article/view/8961</text>
              </elementText>
              <elementText elementTextId="27126">
                <text>10.3991/ijim.v12i5.8961</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27127">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="27128">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="27129">
                <text>https://online-journals.org/index.php/i-jim/article/view/8961/5170</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27130">
                <text>Copyright (c) 2018 Valdrin Maloku, Markus Ebner, Martin Ebner</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="27131">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 12 No. 5 (2018); pp. 81-96</text>
              </elementText>
              <elementText elementTextId="27132">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27133">
                <text>digital learning</text>
              </elementText>
              <elementText elementTextId="27134">
                <text>game-based learning</text>
              </elementText>
              <elementText elementTextId="27135">
                <text>video games</text>
              </elementText>
              <elementText elementTextId="27136">
                <text>mobile devices</text>
              </elementText>
              <elementText elementTextId="27137">
                <text>degree of competence</text>
              </elementText>
              <elementText elementTextId="27138">
                <text>flic buttons</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27139">
                <text>A Mobile Application for School Children Controlled by External Bluetooth Devices</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27140">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="27141">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="27142">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1676" public="1" featured="0">
    <collection collectionId="36">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34819">
                <text>Kühnel, Johannes</text>
              </elementText>
              <elementText elementTextId="34820">
                <text>Ebner, Markus</text>
              </elementText>
              <elementText elementTextId="34821">
                <text>Ebner, Martin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34822">
                <text>2020-11-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34823">
                <text>Chatbots have gained enormous popularity in recent years. IT giants such as Microsoft, Google and Facebook have taken an interest in automated conversations. Messaging apps like WhatsApp and Facebook Messenger are playing an increasingly important role in smartphone usage and communication in general - perfect conditions for chatbots. This paper provides an introduction of recent chatbot development in general and in customer environments. As part of this work, a chatbot was developed for the Austrian IT company CodeFluegel GmbH. The chatbot, named Theodore, provides information about CodeFluegel via Facebook Messenger and webchat, similar to the existing company website. The design process and implementation of the chatbot as well as architectural considerations are explained throughout this document. In a user study, participants perform typical tasks with the website and the chatbot. The usage of both platforms is evaluated in order to identify advantages and disadvantages as well as differences compared to the other technology and to draw conclusions. Findings to this study indicate promising prospects for chatbots as alternative touchpoints for customers and others and a way to replace and enhance traditional websites.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34824">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="34825">
                <text>https://online-journals.org/index.php/i-jim/article/view/13433</text>
              </elementText>
              <elementText elementTextId="34826">
                <text>10.3991/ijim.v14i18.13433</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34827">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="34828">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="34829">
                <text>https://online-journals.org/index.php/i-jim/article/view/13433/8123</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34830">
                <text>Copyright (c) 2020 Johannes Kühnel, Markus Ebner, Martin Ebner</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="34831">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 18 (2020); pp. 18-33</text>
              </elementText>
              <elementText elementTextId="34832">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34833">
                <text>chatbots</text>
              </elementText>
              <elementText elementTextId="34834">
                <text>messenger</text>
              </elementText>
              <elementText elementTextId="34835">
                <text>websites</text>
              </elementText>
              <elementText elementTextId="34836">
                <text>natural language understanding</text>
              </elementText>
              <elementText elementTextId="34837">
                <text>brand representation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34838">
                <text>Chatbots for Brand Representation in Comparison with Traditional Websites</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34839">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34840">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34841">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2372" public="1" featured="0">
    <collection collectionId="36">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50976">
                <text>Kabiljagić, Mirza</text>
              </elementText>
              <elementText elementTextId="50977">
                <text>Wachtler, Josef</text>
              </elementText>
              <elementText elementTextId="50978">
                <text>Ebner, Markus</text>
              </elementText>
              <elementText elementTextId="50979">
                <text>Ebner, Martin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50980">
                <text>2022-09-08</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50981">
                <text>In the recent years, as technology grew, so did the chatbot technology. More and more companies and people are using and reaping the benefits from them. This paper shows how a chatbot for mathematical tasks, named mathbot, was developed. The chatbot uses mathematical exercises from the “Schulapps” of the LearningLab of Graz, University of Technology and combines them with textual questions to provide a useful utility for practicing. It is shown that such a chatbot could be useful for pupils and teachers by evaluating a test run in an elementary school.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50982">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="50983">
                <text>https://online-journals.org/index.php/i-jim/article/view/33351</text>
              </elementText>
              <elementText elementTextId="50984">
                <text>10.3991/ijim.v16i17.33351</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50985">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="50986">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="50987">
                <text>https://online-journals.org/index.php/i-jim/article/view/33351/11957</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50988">
                <text>Copyright (c) 2022 Mirza Kabiljagić, Josef Wachtler, Markus Ebner, Martin Ebner</text>
              </elementText>
              <elementText elementTextId="50989">
                <text>https://creativecommons.org/licenses/by/4.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="50990">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 16 No. 17 (2022); pp. 75-87</text>
              </elementText>
              <elementText elementTextId="50991">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50992">
                <text>Chatbot</text>
              </elementText>
              <elementText elementTextId="50993">
                <text>learning analytics</text>
              </elementText>
              <elementText elementTextId="50994">
                <text>mathematics</text>
              </elementText>
              <elementText elementTextId="50995">
                <text>children</text>
              </elementText>
              <elementText elementTextId="50996">
                <text>education</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50997">
                <text>Math Trainer as a Chatbot Via System (Push) Messages for Android</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50998">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="50999">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="51000">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1062" public="1" featured="0">
    <collection collectionId="36">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21063">
                <text>Ebner, Martin</text>
              </elementText>
              <elementText elementTextId="21064">
                <text>Maierhuber, Martin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21065">
                <text>2013-10-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21066">
                <text>Near Field Communication (NFC) is deemed to be a future technology with a lot of potential in many areas. One of those areas, learning and teaching, will be covered in this article, showing possible usages of NFC with teaching and learning materials. With a lot of new NFC capable devices presented recently, this technology can be utilized in many areas, including the arbitrarily growing field of mobile learning. 
Mobile devices, especially smartphones, can help to close the gap between printed media and online media. Several methods, e.g. two-dimensional barcodes, have already been used to connect the digital world with printed media but almost all of them caused inconveniences or difficulties. NFC presents an easy to use way to share and communicate directly between capable devices or tags that can be applied almost anywhere.
In this publication a first insight to the potential of NFC for teaching and learning content is given. A prototype is programmed to allow data transformation between the print media and the smartphone. It can be summarized that NFC will be the logical successor of QR-Codes.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21067">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="21068">
                <text>https://online-journals.org/index.php/i-jim/article/view/3019</text>
              </elementText>
              <elementText elementTextId="21069">
                <text>10.3991/ijim.v7i4.3019</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21070">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="21071">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="21072">
                <text>https://online-journals.org/index.php/i-jim/article/view/3019/2837</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21073">
                <text>Copyright (c) 2017 Martin Ebner, Martin Maierhuber</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="21074">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 7 No. 4 (2013); pp. 9-14</text>
              </elementText>
              <elementText elementTextId="21075">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21076">
                <text>Mobile Tagging</text>
              </elementText>
              <elementText elementTextId="21077">
                <text>NFC</text>
              </elementText>
              <elementText elementTextId="21078">
                <text>QR-Code</text>
              </elementText>
              <elementText elementTextId="21079">
                <text>Technology Enhanced Learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21080">
                <text>Near Field Communication - Which Potentials Does NFC Bring for Teaching and Learning Materials?</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21081">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="21082">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="21083">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1078" public="1" featured="0">
    <collection collectionId="36">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21402">
                <text>Ebner, Martin</text>
              </elementText>
              <elementText elementTextId="21403">
                <text>Lexow, Stefan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21404">
                <text>2014-04-05</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21405">
                <text>This paper evaluates and describes the usage of plastic cards, coated with conductive paint, as an input device for capacitive touchscreens. By using the developed card prototypes it should be proofed, that usage of this new kind of input device can be handled by primary school pupils in a collaborative learning game. For this reason an educative digital learning game has been developed which can be controlled by the card prototypes. The game asks questions of general knowledge and the answer can be given by putting the proper plastic card on the touchscreen.
The evaluation of the game by two groups of four children pointed out, that the cards can be easily used to identify a specific user. Although evaluation shows that the card control has weaknesses to reliably detect the correct answer during the game phase. All pupils enjoy to play the game and they additionally state, that they like the usage of the cards.
Beside the problems with a reliable card recognition the evaluation shows that the collaborative concept of the game is promising due to the fact that the pupils are always working together on finding a solution for the answer. Further they support each other in handling and understanding the plastic cards which leads to a deeper understanding of the technical backgrounds.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21406">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="21407">
                <text>https://online-journals.org/index.php/i-jim/article/view/3543</text>
              </elementText>
              <elementText elementTextId="21408">
                <text>10.3991/ijim.v8i2.3543</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21409">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="21410">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="21411">
                <text>https://online-journals.org/index.php/i-jim/article/view/3543/3113</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21412">
                <text>Copyright (c) 2017 Martin Ebner, Stefan Lexow</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="21413">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 8 No. 2 (2014); pp. 10-14</text>
              </elementText>
              <elementText elementTextId="21414">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21415">
                <text>conductive</text>
              </elementText>
              <elementText elementTextId="21416">
                <text>elearning</text>
              </elementText>
              <elementText elementTextId="21417">
                <text>game based learning</text>
              </elementText>
              <elementText elementTextId="21418">
                <text>card</text>
              </elementText>
              <elementText elementTextId="21419">
                <text>mobile learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21420">
                <text>Development of a Collaborative Learning Game Using External Plastic Cards as an Input Device on an iPad</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21421">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="21422">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="21423">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1100" public="1" featured="0">
    <collection collectionId="36">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21846">
                <text>Marneanu, Iulia</text>
              </elementText>
              <elementText elementTextId="21847">
                <text>Ebner, Martin</text>
              </elementText>
              <elementText elementTextId="21848">
                <text>Roessler, Thomas</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21849">
                <text>2014-10-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21850">
                <text>Augmented Reality (AR) is the evolution of the concept of Virtual Reality (VR). Its goal is to enhance a person's perception of the surrounding world. AR is a fast growing state of the art technology and a variety of implementation tools thereof exist today. Due to the heterogeneity of available technologies, the choice of the appropriate framework for a mobile application is difficult to make. These frameworks implement different tracking techniques and have to provide support to various constraints.   This publication aims to point out that the choice of the appropriate framework depends on the context of the app to be developed. As expected, it is accurate that no framework is entirely the best, but rather that each exhibits strong and weak points. Our results demonstrate that given a set of constraints, one framework can outperform others. We anticipate our research to be the starting point for testing of other frameworks, given various constraints. The frameworks evaluated here are open-source or have been purchased under Academic License.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21851">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="21852">
                <text>https://online-journals.org/index.php/i-jim/article/view/3974</text>
              </elementText>
              <elementText elementTextId="21853">
                <text>10.3991/ijim.v8i4.3974</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21854">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="21855">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="21856">
                <text>https://online-journals.org/index.php/i-jim/article/view/3974/3295</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21857">
                <text>Copyright (c) 2017 Iulia Marneanu, Martin Ebner, Thomas Roessler</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="21858">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 8 No. 4 (2014); pp. 37-44</text>
              </elementText>
              <elementText elementTextId="21859">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21860">
                <text>Augmented Reality</text>
              </elementText>
              <elementText elementTextId="21861">
                <text>framework</text>
              </elementText>
              <elementText elementTextId="21862">
                <text>Android</text>
              </elementText>
              <elementText elementTextId="21863">
                <text>Software evaluation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21864">
                <text>Evaluation of Augmented Reality Frameworks for Android Development</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21865">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="21866">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="21867">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1255" public="1" featured="0">
    <collection collectionId="36">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25236">
                <text>Lausegger, Georg</text>
              </elementText>
              <elementText elementTextId="25237">
                <text>Spitzer, Michael</text>
              </elementText>
              <elementText elementTextId="25238">
                <text>Ebner, Martin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25239">
                <text>2017-07-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25240">
                <text>Colorblind people or people with a color vision deficiency have to face many challenges in their daily activities. Their disadvantage to perceive colors incorrectly leads to frustration when determining the freshness of fruits and the rawness of meat as well as the problem to distinguish clothes with confusing colors. With the rise of the smartphone, numerous mobile applications are developed to overcome those problems, improving the quality of live. However, smartphones also have some limitations in certain use cases. Especially activities where both hands are needed do not suit well for smartphone applications. Furthermore, there exist tasks in which a continuous use of a smartphone is not possible or even not legally allowed such as driving a car. In recent years, fairly new devices called smart glasses become increasingly popular, which offer great potential for several use cases. One of the most famous representatives of smart glasses is Google Glass, a head-mounted display that is worn like normal eyeglasses produced by Google. This paper introduces an experimental prototype of a Google Glass application for colorblind people or people with a color vision deficiency, called OmniColor and meets the challenge if Google Glass is able to improve the color perception of those people. To show the benefits of OmniColor, an Ishihara color plate test is performed by a group of 14 participants either with, or without the use of OmniColor.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25241">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="25242">
                <text>https://online-journals.org/index.php/i-jim/article/view/6922</text>
              </elementText>
              <elementText elementTextId="25243">
                <text>10.3991/ijim.v11i5.6922</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25244">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="25245">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="25246">
                <text>https://online-journals.org/index.php/i-jim/article/view/6922/4538</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25247">
                <text>Copyright (c) 2017 Georg Lausegger, Michael Spitzer, Martin Ebner</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="25248">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 11 No. 5 (2017); pp. 161-177</text>
              </elementText>
              <elementText elementTextId="25249">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25250">
                <text>Google Glass</text>
              </elementText>
              <elementText elementTextId="25251">
                <text>colorblindness</text>
              </elementText>
              <elementText elementTextId="25252">
                <text>color vision deficiency</text>
              </elementText>
              <elementText elementTextId="25253">
                <text>color perception</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25254">
                <text>OmniColor – A Smart Glasses App to Support Colorblind People</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25255">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="25256">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="25257">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1297" public="1" featured="0">
    <collection collectionId="36">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26151">
                <text>Rabko, Michael</text>
              </elementText>
              <elementText elementTextId="26152">
                <text>Ebner, Martin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26153">
                <text>2018-03-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26154">
                <text>Nowadays, computers and mobile devices play a huge role in our daily routines; they are used at work, for private purposes and even at school. Moreover, they are used as support for different kinds of activities and task, like for example, learning applications. The interaction of these applications with a computer is based on predefined input methods, whereas a touchscreen facilitates direct input via handwriting by using a finger or a pen.This paper deals with the invention of a mobile learning application, which is supposed to facilitate children’s learning of simple multiplication. The aim of this paper is to collect the data of children’ experiences using interactive handwriting on mobile devices. In order to gain this data, a school class of the school “Graz-Hirten” was tested and afterwards for evaluational purposes interviewed. The results of these usability tests have shown that children perceived handwriting via finger on screen as quite positive.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26155">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="26156">
                <text>https://online-journals.org/index.php/i-jim/article/view/7714</text>
              </elementText>
              <elementText elementTextId="26157">
                <text>10.3991/ijim.v12i2.7714</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26158">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="26159">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="26160">
                <text>https://online-journals.org/index.php/i-jim/article/view/7714/4866</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26161">
                <text>Copyright (c) 2018 Martin Ebner, Michael Rabko</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="26162">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 12 No. 2 (2018); pp. 69-79</text>
              </elementText>
              <elementText elementTextId="26163">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26164">
                <text>handwriting recognition</text>
              </elementText>
              <elementText elementTextId="26165">
                <text>convolutional neural network</text>
              </elementText>
              <elementText elementTextId="26166">
                <text>multiplication table</text>
              </elementText>
              <elementText elementTextId="26167">
                <text>learning</text>
              </elementText>
              <elementText elementTextId="26168">
                <text>children</text>
              </elementText>
              <elementText elementTextId="26169">
                <text>mobile learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26170">
                <text>1x1 Trainer with Handwriting Recognition</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26171">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="26172">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="26173">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1584" public="1" featured="0">
    <collection collectionId="36">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32699">
                <text>Prott, David</text>
              </elementText>
              <elementText elementTextId="32700">
                <text>Ebner, Martin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32701">
                <text>2020-02-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32702">
                <text>Obtaining customer opinions and customer wishes is increasingly becoming an important part of any entrepreneurial activity for determining customer satisfaction and, subsequently, optimizing products and services as well as strengthen customer loyalty. In catering, there are several ways to capture the guest’s satisfaction or dissatisfaction, as well as customer preferences and customer needs across different channels. One way to obtain a customer’s opinion is to provide a digital online questionnaire. Unfortunately, the participa-tion of guests in such surveys is usually low. In addition, many online question-naires are aborted prematurely, and questions which require an individual text answer are often left unanswered. Gamification is a process to use game ele-ments, game techniques and game mechanics from games in a different context in order to motivate and force people to do certain activities. This paper dis-cusses whether the use of game elements in an existing gastronomical online questionnaire enhances the engagement of users and whether customer satisfac-tion remains the same. Based on an existing gastronomical online questionnaire from the company ITELL.SOLUTIONS GmbH a gamified questionnaire vari-ant has been developed. Game elements such as points, badges, avatar, story, progress bar and instant feedback have been included. The investigation showed that the use of gamification in questionnaires on open questions did not worsen the involvement of users. The customer satisfac-tion remained unchanged by the embedding of game elements too. Users of the expanded game questionnaire tended to give more precise and longer answers. The completion time also slightly increased for the gamified questionnaire. A direct comparison between the two variants of the questionnaire, showed that users preferred the design of the gamified questionnaire.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32703">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="32704">
                <text>https://online-journals.org/index.php/i-jim/article/view/11695</text>
              </elementText>
              <elementText elementTextId="32705">
                <text>10.3991/ijim.v14i02.11695</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32706">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="32707">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="32708">
                <text>https://online-journals.org/index.php/i-jim/article/view/11695/6455</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32709">
                <text>Copyright (c) 2020 David Prott, Martin Ebner</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="32710">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 02 (2020); pp. 101-118</text>
              </elementText>
              <elementText elementTextId="32711">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32712">
                <text>gamification</text>
              </elementText>
              <elementText elementTextId="32713">
                <text>mobile</text>
              </elementText>
              <elementText elementTextId="32714">
                <text>questionnaire</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32715">
                <text>The Use of Gamification in Gastronomic Questionnaires</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32716">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="32717">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="32718">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="297" public="1" featured="0">
    <collection collectionId="26">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="2304">
                  <text>Artha Journal of Social Sciences</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5740">
                <text>Ghasemian, Daryoush</text>
              </elementText>
              <elementText elementTextId="5741">
                <text>Ebrahimi, Sedigheh</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5742">
                <text>2021-09-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5743">
                <text>The present study reports assessment of anxiety levels and its relationship with spirituality among postgraduate students of Mysore University. A total of 100 (66 male + 34 female) students studying in management and humanities were randomly selected for the study. They were administered IPAT anxiety scale (Cattel &amp;amp; Scheier, 1963) and Spirituality scale (Piedmont, 1999). Results revealed that an alarming 43% of the students suffer from morbid anxiety and only 4% of them were found to be secure. Demographic variables like gender, age and course did not have influence over anxiety. Further, students with different levels of anxiety did not differ in their spirituality scores. A general discussion on anxiety reduction techniques were also described at the end.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5744">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="5745">
                <text>https://journals.christuniversity.in/index.php/artha/article/view/874</text>
              </elementText>
              <elementText elementTextId="5746">
                <text>10.12724/ajss.11.5</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5747">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="5748">
                <text>Centre for Publications, CHRIST (Deemed to be University), Bangalore</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="5749">
                <text>https://journals.christuniversity.in/index.php/artha/article/view/874/624</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5750">
                <text>Copyright (c) 2017 Artha - Journal of Social Sciences</text>
              </elementText>
              <elementText elementTextId="5751">
                <text>http://creativecommons.org/licenses/by-nc/4.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="5752">
                <text>Artha Journal of Social Sciences; Vol. 6 No. 2 (2007): Artha Journal of Social Sciences; 38 - 45</text>
              </elementText>
              <elementText elementTextId="5753">
                <text>0000-0000</text>
              </elementText>
              <elementText elementTextId="5754">
                <text>0975-329X</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5755">
                <text>"Assessment of Anxiety among Higher Education Students and Its Relationship with Spirituality "</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5756">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="5757">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="5758">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
