<?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=112&amp;sort_field=added" accessDate="2026-05-05T19:29:49+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>112</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1112" 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="22089">
                <text>Shuib, Munir</text>
              </elementText>
              <elementText elementTextId="22090">
                <text>Abdullah, Amelia</text>
              </elementText>
              <elementText elementTextId="22091">
                <text>Azizan, Siti Norbaya</text>
              </elementText>
              <elementText elementTextId="22092">
                <text>Gunasegaran, Thenmolli</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="22093">
                <text>2015-01-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22094">
                <text>English is the most important second language in most non-English speaking countries, including Malaysia. A good English proficiency comes from good grasp of grammar. To conquer the problems of low English proficiency among Malaysians, it is important to identify the key motivators that could facilitate the process of grammar learning.  In this digital age, technology can play a very important role and mobile technology could be one of it. Thus, this study aims at designing a mobile learning tool, namely the Intelligent Mobile Learning Tool for Grammar Learning (i-MoL) to act as the “on-the-go” grammar learning support via mobile phones. i-MoL helps reinforce grammar learning through mobile phone with game-like applications, inquiry-based activities and flashcard-like information. The intelligent part of i-MoL lies in its ability to map the mobile-based grammar learning content to individual’s preferred learning styles based on Felder-Silverman Learning Style Model (FSLSM). The instructional system design through the ADDIE model was used in this study as a systematic approach in designing a novel and comprehensive mobile learning tool for grammar learning. In terms of implications, this study provides insights on how mobile technologies can be utilized to meet the mobility demand among language learners today.</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="22095">
                <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="22096">
                <text>https://online-journals.org/index.php/i-jim/article/view/4238</text>
              </elementText>
              <elementText elementTextId="22097">
                <text>10.3991/ijim.v9i1.4238</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22098">
                <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="22099">
                <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="22100">
                <text>https://online-journals.org/index.php/i-jim/article/view/4238/3362</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22101">
                <text>Copyright (c) 2017 Munir Shuib, Amelia Abdullah, Siti Norbaya Azizan, Thenmolli Gunasegaran</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="22102">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 9 No. 1 (2015); pp. 41-46</text>
              </elementText>
              <elementText elementTextId="22103">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22104">
                <text>Mobile learning</text>
              </elementText>
              <elementText elementTextId="22105">
                <text>English language</text>
              </elementText>
              <elementText elementTextId="22106">
                <text>grammar</text>
              </elementText>
              <elementText elementTextId="22107">
                <text>learning styles</text>
              </elementText>
              <elementText elementTextId="22108">
                <text>FSLSM</text>
              </elementText>
              <elementText elementTextId="22109">
                <text>instructional system design</text>
              </elementText>
              <elementText elementTextId="22110">
                <text>ISD</text>
              </elementText>
              <elementText elementTextId="22111">
                <text>ADDIE</text>
              </elementText>
              <elementText elementTextId="22112">
                <text>higher learning institutions</text>
              </elementText>
              <elementText elementTextId="22113">
                <text>graduates</text>
              </elementText>
              <elementText elementTextId="22114">
                <text>Malaysia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22115">
                <text>Designing an Intelligent Mobile Learning Tool for Grammar Learning  (i-MoL)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22116">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="22117">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="22118">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1113" 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="22119">
                <text>Zarour, Karim</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="22120">
                <text>2015-03-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22121">
                <text>Nowadays, in the networked health, mobile tools are increasingly important, to provide care, educate patients or to transmit remote information. Telehomecare evolves constantly. It can aid disabled persons, increase patient compliance, enhance caregivers’ effectiveness, and connect socially isolated individuals to their care providers. In this perspective, the agent paradigm proposes interesting concepts for the development of telehomecare information systems, such as the control autonomy, decentralization and coordination. This paper describes an architecture of telehomecare based on agents and mobile tools.</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="22122">
                <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="22123">
                <text>https://online-journals.org/index.php/i-jim/article/view/4245</text>
              </elementText>
              <elementText elementTextId="22124">
                <text>10.3991/ijim.v9i2.4245</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22125">
                <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="22126">
                <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="22127">
                <text>https://online-journals.org/index.php/i-jim/article/view/4245/3447</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22128">
                <text>Copyright (c) 2017 Karim Zarour</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="22129">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 9 No. 2 (2015); pp. 31-36</text>
              </elementText>
              <elementText elementTextId="22130">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22131">
                <text>Telehomecare</text>
              </elementText>
              <elementText elementTextId="22132">
                <text>Inter-Agent Communication</text>
              </elementText>
              <elementText elementTextId="22133">
                <text>Electronic Medical Record</text>
              </elementText>
              <elementText elementTextId="22134">
                <text>Information and Communication Technologies</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22135">
                <text>Agent and Mobile Tools for Telehomecare in Developing Countries: An Architecture Approach</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22136">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="22137">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="22138">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1114" 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="22139">
                <text>Al-Mahadeen, Bassam M</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="22140">
                <text>2015-01-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22141">
                <text>Numerous studies have reported the rapid increase in the number of individuals who use smartphones. However, smartphones appear to be increasingly used by healthcare workers, particularly physicians and nurses. Therefore, this study aims to investigate the readiness of medical doctors and patients with chronic conditions in using and adopting smartphones for communication. This study employs the Technology Acceptance Model to examine the behavior of people in using smartphones from the perspectives of trust and rural areas. To realize our objective, we conducted a questionnaire survey that involved medical doctors and patients with chronic conditions. Our particular focus was Al Qunfudhah City in Saudi Arabia. More than 200 questionnaires were distributed to people belonging to different healthcare sectors in the rural areas of Al Qunfudhah City. Our aim was to include every possible scenario and to obtain excellent perspectives. The results that we eventually analyzed indicated that trust factor and rural areas significantly influence the readiness of people belonging to the healthcare sector toward using smartphones. The results of our study concur with the findings of other studies. Our results indicate that smartphones and other high-technology gadgets are now necessary and accepted devices in the different healthcare fields. However, further studies should explore the challenges and effects of smartphone use in the healthcare sector.</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="22142">
                <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="22143">
                <text>https://online-journals.org/index.php/i-jim/article/view/4279</text>
              </elementText>
              <elementText elementTextId="22144">
                <text>10.3991/ijim.v9i1.4279</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22145">
                <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="22146">
                <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="22147">
                <text>https://online-journals.org/index.php/i-jim/article/view/4279/3363</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22148">
                <text>Copyright (c) 2017 Bassam M Al-Mahadeen</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="22149">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 9 No. 1 (2015); pp. 47-52</text>
              </elementText>
              <elementText elementTextId="22150">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22151">
                <text>Healthcare</text>
              </elementText>
              <elementText elementTextId="22152">
                <text>Individual Factors</text>
              </elementText>
              <elementText elementTextId="22153">
                <text>Rural Area</text>
              </elementText>
              <elementText elementTextId="22154">
                <text>Saudi Arabia</text>
              </elementText>
              <elementText elementTextId="22155">
                <text>Smartphone</text>
              </elementText>
              <elementText elementTextId="22156">
                <text>TAM.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22157">
                <text>Factors Affecting the Readiness of Medical Doctors and Patients with Chronic Conditions toward the Usage of Smartphones in the Saudi Arabian Healthcare Sector</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22158">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="22159">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="22160">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1115" 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="22161">
                <text>Tossell, Chad</text>
              </elementText>
              <elementText elementTextId="22162">
                <text>Kortum, Philip</text>
              </elementText>
              <elementText elementTextId="22163">
                <text>Shepard, Clayton</text>
              </elementText>
              <elementText elementTextId="22164">
                <text>Rahmati, Ahmad</text>
              </elementText>
              <elementText elementTextId="22165">
                <text>Zhong, Lin</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="22166">
                <text>2015-03-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22167">
                <text>This study examined smartphone user behaviors and their relation to self-reported smartphone addiction. Thirty-four users who did not own smartphones were given instrumented iPhones that logged all phone use over the course of the year-long study. At the conclusion of the study, users were asked to rate their level of addiction to the device.  Sixty-two percent agreed or strongly agreed that they were addicted to their iPhones. These users showed differentiated smartphone use as compared to those users who did not indicate an addiction. Addicted users spent twice as much time on their phone and launched applications much more frequently (nearly twice as often) as compared to the non-addicted user. Mail, Messaging, Facebook and the Web drove this use. Surprisingly, games did not show any difference between addicted and non-addicted users. Addicted users showed significantly lower time-per-interaction than did non-addicted users for Mail, Facebook and Messaging applications. One addicted user reported that his addiction was problematic, and his use data was beyond three standard deviations from the upper hinge.  This study provides unique insight, as use data in previous studies has been self-reported, and this study used a naturalistic, non-intervention data logging approach over the course of a year.</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="22168">
                <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="22169">
                <text>https://online-journals.org/index.php/i-jim/article/view/4300</text>
              </elementText>
              <elementText elementTextId="22170">
                <text>10.3991/ijim.v9i2.4300</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22171">
                <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="22172">
                <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="22173">
                <text>https://online-journals.org/index.php/i-jim/article/view/4300/3448</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22174">
                <text>Copyright (c) 2017 Chad Tossell, Philip Kortum, Clayton Shepard, Ahmad Rahmati, Lin Zhong</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="22175">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 9 No. 2 (2015); pp. 37-43</text>
              </elementText>
              <elementText elementTextId="22176">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22177">
                <text>Smartphones</text>
              </elementText>
              <elementText elementTextId="22178">
                <text>Addiction</text>
              </elementText>
              <elementText elementTextId="22179">
                <text>Human Behavior</text>
              </elementText>
              <elementText elementTextId="22180">
                <text>Technology Social Factors.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22181">
                <text>Exploring Smartphone Addiction: Insights from Long-Term Telemetric Behavioral Measures</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22182">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="22183">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="22184">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1116" 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="22185">
                <text>Sifat, Shabnam Shahreen</text>
              </elementText>
              <elementText elementTextId="22186">
                <text>Sabbir, Ali Shihab</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="22187">
                <text>2015-03-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22188">
                <text>Mobile banking has become immensely popular among customers as a suitable method for money transaction. Banks are assertively adopting this mode. It is playing a vital role in availing banking services in remote areas where placing branch or ATM booth is not economically feasible. Mobile banking is so far the easiest way of expanding banking coverage. But there is huge possibility of fraud in case of mobile banking as authentication &amp; all type of transaction information is provided via mobile phone including pin. So mobile banking is not intended to be used for big transactions where ATM transactions are suitable because of its two layer authentication system. In this paper, a new system is introduced that provides ATM service without traditional booths but two layer authentications with a tiny OS independent device has been introduced named VATM. This paper discusses how this system works using a low cost device made of micro-controller &amp; CDMA module for communicating with bank for authentication which is used as an alternate of Automated teller machine for providing two layer authentications.</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="22189">
                <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="22190">
                <text>https://online-journals.org/index.php/i-jim/article/view/4314</text>
              </elementText>
              <elementText elementTextId="22191">
                <text>10.3991/ijim.v9i2.4314</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22192">
                <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="22193">
                <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="22194">
                <text>https://online-journals.org/index.php/i-jim/article/view/4314/3486</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22195">
                <text>Copyright (c) 2017 Shabnam Shahreen Sifat, Ali Shihab Sabbir</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="22196">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 9 No. 2 (2015); pp. 44-49</text>
              </elementText>
              <elementText elementTextId="22197">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22198">
                <text>Agent assisted Banking</text>
              </elementText>
              <elementText elementTextId="22199">
                <text>Electronic Banking</text>
              </elementText>
              <elementText elementTextId="22200">
                <text>Mobile Banking</text>
              </elementText>
              <elementText elementTextId="22201">
                <text>Secured Banking</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22202">
                <text>Virtual ATM: A Low Cost Secured Alternative to Conventional Mobile Banking</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22203">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="22204">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="22205">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1117" 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="22206">
                <text>Teklehaimanot, Hailay Kidu</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="22207">
                <text>2015-03-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22208">
                <text>Introduction:
Mobile learning refers to the use of mobile and handheld IT devices such as Personal Digital Assistants (PDAs), mobile telephones, laptops and tablet PC technologies, in teaching and learning. It is a new form of learning, using mobile network and tools, expanding digital learning channel, gaining educational information, educational resources and educational services anytime, anywhere.  Learning a language requires explicit learning of vocabulary and language rules. This can be supported by mobile learning. An initial survey of this project showed me most foreigners consider Tigrigna language as a barrier to be involved in different local activities of Tigray Tigrigna speakers and no one is developed Tigrigna language tool before. 
Objective: 
To develop Mobile based Tigrigna Language Learning Tool.
Methods: 
This project develops a Mobile based Tigrigna Language Learning Tool to support Tigrigna Language speaking, listening and writing for foreigners in a Tigrigna’s environment. The main emphasis is to teach beginners, the basic alphabets, words and common conversation they might come across. To achieve this goal, the main effort of this project is based on three aspects: designing and delivering Tigrigna alphabets, words and conversation lessons, by integrating audio and picture for the words, alphabets and common conversations. By giving exercises for each the lessons and allowing the user to keep track of his/her profile. 
The Tool contains three modules like Tutorial management module, Exercise Module and User Profile Module each of the modules are contained different components and functionalities it also includes a scenario-based fulfilling activities associated of learners and it encourages users to speak, listen and write in Tigrigna through the mission tasks of the project .This Tool may increase learners’ motivation to continue their Tigrigna learning. Besides, mobile devices provide the opportunity to learn Tigrigna outside the classroom and to interact directly with a genuine living environment.

Results:
This project is viewed by the institution of Tigrigina language and litrature Addiss Ababa University and they are interested on the tool. I deployed on the actual device it works exactly as expected and different beginner Tigrigna learners are using the tool.
Conclusion:-
I believe that Tigirigina mobile learning are personalization of learning environment, learning Experience outside the classroom, learning by recording, organizing over time, taking advantage of the benefits of an information, be more motivated, no more forced to use PC as the only Objects to have access to materials and 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="22209">
                <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="22210">
                <text>https://online-journals.org/index.php/i-jim/article/view/4322</text>
              </elementText>
              <elementText elementTextId="22211">
                <text>10.3991/ijim.v9i2.4322</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22212">
                <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="22213">
                <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="22214">
                <text>https://online-journals.org/index.php/i-jim/article/view/4322/3450</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22215">
                <text>Copyright (c) 2017 Hailay Kidu Teklehaimanot</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="22216">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 9 No. 2 (2015); pp. 50-53</text>
              </elementText>
              <elementText elementTextId="22217">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22218">
                <text>Mobile Learning</text>
              </elementText>
              <elementText elementTextId="22219">
                <text>Mobile language Learning</text>
              </elementText>
              <elementText elementTextId="22220">
                <text>Mobile Learning Application</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22221">
                <text>A Mobile Based Tigrigna Language Learning Tool</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22222">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="22223">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="22224">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1118" 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="22225">
                <text>Wiklund-Engblom, Annika</text>
              </elementText>
              <elementText elementTextId="22226">
                <text>Hartvik, Juha</text>
              </elementText>
              <elementText elementTextId="22227">
                <text>Hiltunen, Kasper</text>
              </elementText>
              <elementText elementTextId="22228">
                <text>Johansson, Marléne</text>
              </elementText>
              <elementText elementTextId="22229">
                <text>Porko-Hudd, Mia</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="22230">
                <text>2015-07-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22231">
                <text>Abstract—Students work in sloyd [slöjd] class represents unique areas of learning.  The creative, hands-on design work, as well as a mix of both individual and collaborative processes, provide options for developing multiple skills.  But these multilevel learning processes are difficult to capture.  This study explores how a mobile application, the Talking Tools (TT), are used for documenting students own reflections during sloyd class.  The study targets what, why, and when a group of teacher students (N=11) use TT for microblogging about their work.  Their subjective reflections from a questionnaire using open-ended questions are used for validating earlier analysis of their blogs created using TT.  As TT is still under development, the objective of exploring students’ documentation behaviour with the application, is to understand what the added value of TT could be for capturing various areas of learning.  Suggestions for teacher guidelines for implementing TT are discussed based on the findings.  The article also describes the development of the application in terms of the inter-disciplinary cooperation and collaboration.  The TPACK framework is used for illustrating the know-how transcendence between collaborators in the TT application development.</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="22232">
                <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="22233">
                <text>https://online-journals.org/index.php/i-jim/article/view/4325</text>
              </elementText>
              <elementText elementTextId="22234">
                <text>10.3991/ijim.v9i3.4325</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22235">
                <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="22236">
                <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="22237">
                <text>https://online-journals.org/index.php/i-jim/article/view/4325/3539</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22238">
                <text>Copyright (c) 2017 Annika Wiklund-Engblom, Juha Hartvik, Kasper Hiltunen, Marléne Johansson, Mia Porko-Hudd</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="22239">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 9 No. 3 (2015); pp. 11-17</text>
              </elementText>
              <elementText elementTextId="22240">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22241">
                <text>app development</text>
              </elementText>
              <elementText elementTextId="22242">
                <text>learning process</text>
              </elementText>
              <elementText elementTextId="22243">
                <text>mobile documentation</text>
              </elementText>
              <elementText elementTextId="22244">
                <text>mobile learning</text>
              </elementText>
              <elementText elementTextId="22245">
                <text>sloyd</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22246">
                <text>Process Documentation in Sloyd: Pilot Study of the ‘Talking Tools’ Application</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22247">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="22248">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="22249">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1119" 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="22250">
                <text>Meenakshi, Avanthika</text>
              </elementText>
              <elementText elementTextId="22251">
                <text>Sundar, Shyam</text>
              </elementText>
              <elementText elementTextId="22252">
                <text>Nancy, Silviya</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="22253">
                <text>2015-01-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22254">
                <text>Mobile phones are used in almost all aspects of life by people. But in the case of visually impaired, they are still a step behind in using smart phones for various purposes. Having interactive android OS, navigation and travel aiding apps using sensors and voice user interfaces (VUI) or the voice response systems, we are still a step lagging in giving them an application for educational purposes. This paper proposes a complete new idea of having a portal where they can store audio books aided with interactive system so that they can use them whenever needed.</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="22255">
                <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="22256">
                <text>https://online-journals.org/index.php/i-jim/article/view/4326</text>
              </elementText>
              <elementText elementTextId="22257">
                <text>10.3991/ijim.v9i1.4326</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22258">
                <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="22259">
                <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="22260">
                <text>https://online-journals.org/index.php/i-jim/article/view/4326/3366</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22261">
                <text>Copyright (c) 2017 Avanthika Meenakshi, Shyam Sundar, Silviya Nancy</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="22262">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 9 No. 1 (2015); pp. 64-66</text>
              </elementText>
              <elementText elementTextId="22263">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22264">
                <text>visually impared</text>
              </elementText>
              <elementText elementTextId="22265">
                <text>educational</text>
              </elementText>
              <elementText elementTextId="22266">
                <text>audio books</text>
              </elementText>
              <elementText elementTextId="22267">
                <text>portal</text>
              </elementText>
              <elementText elementTextId="22268">
                <text>VUI</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22269">
                <text>An Interactive Mobile Application for the Visually Impaired to Have Access to Listening Audio Books with Handy Books Portal</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22270">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="22271">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="22272">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1120" 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="22273">
                <text>Zimmer, Thomas</text>
              </elementText>
              <elementText elementTextId="22274">
                <text>Billaud, M.</text>
              </elementText>
              <elementText elementTextId="22275">
                <text>Pic, M.</text>
              </elementText>
              <elementText elementTextId="22276">
                <text>Geoffroy, D.</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="22277">
                <text>2015-03-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22278">
                <text>This paper presents a new approach for the use of an already existing remote lab in the field of electrical engineer education. About 70 experiments representing a wide domain of electronic functions are easily accessible and can be incorporated in an existing teaching environment by an easy copy/paste action of a dedicated URL. The corresponding data base structure is explained and a typical result is given highlighting the procedure to follow.</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="22279">
                <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="22280">
                <text>https://online-journals.org/index.php/i-jim/article/view/4346</text>
              </elementText>
              <elementText elementTextId="22281">
                <text>10.3991/ijim.v9i2.4346</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22282">
                <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="22283">
                <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="22284">
                <text>https://online-journals.org/index.php/i-jim/article/view/4346/3443</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22285">
                <text>Copyright (c) 2017 Thomas Zimmer, M. Billaud, M. Pic, D. Geoffroy</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="22286">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 9 No. 2 (2015); pp. 13-16</text>
              </elementText>
              <elementText elementTextId="22287">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22288">
                <text>Laboratory experiments</text>
              </elementText>
              <elementText elementTextId="22289">
                <text>Remote labs</text>
              </elementText>
              <elementText elementTextId="22290">
                <text>Reuse of remote labs</text>
              </elementText>
              <elementText elementTextId="22291">
                <text>Engineering education</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22292">
                <text>Remote Lab Experiments in Electronics for Use and Reuse</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22293">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="22294">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1121" 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="22295">
                <text>Ennetta, Ridha</text>
              </elementText>
              <elementText elementTextId="22296">
                <text>Nasri, Ibrahim</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="22297">
                <text>2015-03-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22298">
                <text>Remote labs that enable students to conduct real-world experiments at a distance using a computer and Web-based tools can be the only realistic method of performing practical experiments in the context of distance learning.
eSience Tempus project "Maghreb Network of remote labs" offers an innovative pedagogical approach which integrates eLearning and is complementary to classroom learning. The main objective of this project is to create an efficient remote labs network in the Maghreb region for the modernization of higher education in technological sciences. 
The current paper summarizes the work carried out on a heat exchanger bench to be fully accessed and controlled remotely. Through this new device a student of Mechanical Engineering is introduced to many fundamental aspects of heat transfer.</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="22299">
                <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="22300">
                <text>https://online-journals.org/index.php/i-jim/article/view/4368</text>
              </elementText>
              <elementText elementTextId="22301">
                <text>10.3991/ijim.v9i2.4368</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22302">
                <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="22303">
                <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="22304">
                <text>https://online-journals.org/index.php/i-jim/article/view/4368/3441</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22305">
                <text>Copyright (c) 2017 Ridha Ennetta, Ibrahim Nasri</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="22306">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 9 No. 2 (2015); pp. 5-8</text>
              </elementText>
              <elementText elementTextId="22307">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22308">
                <text>eSience project</text>
              </elementText>
              <elementText elementTextId="22309">
                <text>heat exchanger</text>
              </elementText>
              <elementText elementTextId="22310">
                <text>Maghreb</text>
              </elementText>
              <elementText elementTextId="22311">
                <text>remote lab</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22312">
                <text>Developing a Remote Laboratory for Heat Transfer Studies</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22313">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="22314">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
