<?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=221" accessDate="2026-05-15T16:13:28+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>221</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1376" 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="27933">
                <text>Rao, Santhosha</text>
              </elementText>
              <elementText elementTextId="27934">
                <text>A, Smitha</text>
              </elementText>
              <elementText elementTextId="27935">
                <text>Kulkarni, Kunal</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="27936">
                <text>2018-10-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27937">
                <text>In recent years, the proliferation of the Internet of Things (IoT) has kick started the home and office automation in a very rapid manner. The paper demonstrates a cost effective implementation of an IoT system for managing the visitors in an office environment. The automation system comprises low cost NodeMCU based Wireless Transmitter, NodeMCU based Wireless Display Unit and an android mobile phone. The mobile phone also serves as wireless Access Point to which the Wireless Transmitter and the Wireless Display Units are wirelessly connected for exchanging the messages using UDP protocol. The Wireless Transmitter and the Wireless Display Units are kept in the visitor’s waiting area. The consulting person possesses an android mobile phone in which the automation software is installed. The visitor enters a message using the Wireless Transmitter and notes down the acknowledgement token number sent by the automation software. When the consulting person checks this message, the same token number is sent to the Wireless Display Unit signaling the visitor to consult the person.</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="27938">
                <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="27939">
                <text>https://online-journals.org/index.php/i-jim/article/view/9476</text>
              </elementText>
              <elementText elementTextId="27940">
                <text>10.3991/ijim.v12i6.9476</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27941">
                <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="27942">
                <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="27943">
                <text>https://online-journals.org/index.php/i-jim/article/view/9476/5253</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27944">
                <text>Copyright (c) 2018 Santhosha Rao, Smitha A, Kunal Kulkarni</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="27945">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 12 No. 6 (2018); pp. 112-123</text>
              </elementText>
              <elementText elementTextId="27946">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27947">
                <text>Internet of Things (IoT)</text>
              </elementText>
              <elementText elementTextId="27948">
                <text>NodeMCU</text>
              </elementText>
              <elementText elementTextId="27949">
                <text>Office automation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27950">
                <text>Smart Phone based Cost Effective Visitor Management System for Smart Offices</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27951">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="27952">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="27953">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1375" 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="27906">
                <text>Yassine, Alaeeddine</text>
              </elementText>
              <elementText elementTextId="27907">
                <text>Berrada, Mohammed</text>
              </elementText>
              <elementText elementTextId="27908">
                <text>Tahiri, Ahmed</text>
              </elementText>
              <elementText elementTextId="27909">
                <text>Chenouni, Driss</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="27910">
                <text>2018-11-08</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27911">
                <text>This paper presents and discusses a new mobile application for teaching and learning programming basics. The purpose is to help students acquire competencies while having fun and using their own devices. The mobile application was designed according to cross-platform approach to reach the broadest possible audience of learners, saving time and effort of development and maintenance. The code is fully shared between mobile platforms (iOS, Android and Windows Phone) allowing learners to install the application on any device. The core application is based on a multi-agent system to make the application interactive, flexible and dynamic and provide students with tailored instructions. A prototype is presented showing the main features of the application.</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="27912">
                <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="27913">
                <text>https://online-journals.org/index.php/i-jim/article/view/9442</text>
              </elementText>
              <elementText elementTextId="27914">
                <text>10.3991/ijim.v12i7.9442</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27915">
                <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="27916">
                <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="27917">
                <text>https://online-journals.org/index.php/i-jim/article/view/9442/5274</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27918">
                <text>Copyright (c) 2018 alaeeddine yassine, Mohammed Berrada, Driss CHENOUNI, Ahmed TAHIRI</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="27919">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 12 No. 7 (2018); pp. 139-151</text>
              </elementText>
              <elementText elementTextId="27920">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27921">
                <text>Cross-platform</text>
              </elementText>
              <elementText elementTextId="27922">
                <text>Mobile Application</text>
              </elementText>
              <elementText elementTextId="27923">
                <text>Programming Basics</text>
              </elementText>
              <elementText elementTextId="27924">
                <text>multi-agent system</text>
              </elementText>
              <elementText elementTextId="27925">
                <text>Learning Outcomes</text>
              </elementText>
              <elementText elementTextId="27926">
                <text>m-learning</text>
              </elementText>
              <elementText elementTextId="27927">
                <text>Xamarin.Forms</text>
              </elementText>
              <elementText elementTextId="27928">
                <text>self-learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27929">
                <text>A Cross-Platform Mobile Application for Learning Programming Basics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27930">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="27931">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="27932">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1374" 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="27884">
                <text>Guinn, Victor</text>
              </elementText>
              <elementText elementTextId="27885">
                <text>Langhals, Brent</text>
              </elementText>
              <elementText elementTextId="27886">
                <text>Elshaw, John</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="27887">
                <text>2018-12-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27888">
                <text>Infrastructure managers require timely and accurate state information to diagnose, prioritize, and repair the substantial infrastructure assets supporting modern society.  Challenges in obtaining sufficient information can often be attributed to inadequate data collection procedures (phone calls, paper reports, etc.) or a general lack of knowledge or ability on the part of the reporting individual to accurately convey what is actually wrong with the facility.  Fortunately, modern smart-phone technology offers the potential to improve maintenance work requests by providing better geolocation and problem description accuracy.  An experiment simulating real-world maintenance requests was conducted comparing smart-phones with traditional verbal work order request systems.  Usefulness and description accuracy ratios revealed smartphone systems generated more useful information regardless of submitter background or experience.  However, interestingly the smart-phone applications did not improve asset geolocation and actually negatively impacted the ability of maintenance personnel to accurately relocate the asset needing service.  Given the ubiquitous nature of smartphone technology, the potential exists to turn any citizen into an infrastructure sensor.  This study takes a step toward understanding the benefits, as well as the limitations, of the smart-phone based work order submission systems.</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="27889">
                <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="27890">
                <text>https://online-journals.org/index.php/i-jim/article/view/9441</text>
              </elementText>
              <elementText elementTextId="27891">
                <text>10.3991/ijim.v12i8.9441</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27892">
                <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="27893">
                <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="27894">
                <text>https://online-journals.org/index.php/i-jim/article/view/9441/5363</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27895">
                <text>Copyright (c) 2018 Victor Guinn, Brent Langhals, John Elshaw</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="27896">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 12 No. 8 (2018); pp. 52-63</text>
              </elementText>
              <elementText elementTextId="27897">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27898">
                <text>mobile phone</text>
              </elementText>
              <elementText elementTextId="27899">
                <text>application</text>
              </elementText>
              <elementText elementTextId="27900">
                <text>work-order system</text>
              </elementText>
              <elementText elementTextId="27901">
                <text>infrastructure</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27902">
                <text>Evaluating Smartphones for Infrastructure Work Order Management</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27903">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="27904">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="27905">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1373" 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="27860">
                <text>Ouadoud, Mohammed</text>
              </elementText>
              <elementText elementTextId="27861">
                <text>Chafiq, Tarik</text>
              </elementText>
              <elementText elementTextId="27862">
                <text>Rida, Nouha</text>
              </elementText>
              <elementText elementTextId="27863">
                <text>Chkouri, Mohamed Yassin</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="27864">
                <text>2019-01-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27865">
                <text>The context of this work is that of designing a Instructional Management Systems - Learning Design (IMS-LD) model for collaboration space of a Learning Management System (LMS). Our work is specifically in the field or seeking to promote, by means of information technology from a distance. Our approach is to first think about the conditions for creating a real collaboration space between learners, and designing the IT environment that supports this space. In this paper, we try to adapt the IMS-LD model with a collaboration model for Learning Management System based on the social constructivism. This adaptation will go through three stages. Firstly, the development of an LMS model. Secondly, the study of correspondence between the developed model and IMS-LD model. Finally their transformation to IMS-LD model.</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="27866">
                <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="27867">
                <text>https://online-journals.org/index.php/i-jim/article/view/9440</text>
              </elementText>
              <elementText elementTextId="27868">
                <text>10.3991/ijim.v13i01.9440</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27869">
                <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="27870">
                <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="27871">
                <text>https://online-journals.org/index.php/i-jim/article/view/9440/5414</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27872">
                <text>Copyright (c) 2019 Mohammed Ouadoud, Tarik Chafiq, Mohamed Yassin Chkouri</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="27873">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 01 (2019); pp. 37-52</text>
              </elementText>
              <elementText elementTextId="27874">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27875">
                <text>LMS</text>
              </elementText>
              <elementText elementTextId="27876">
                <text>collaboration space</text>
              </elementText>
              <elementText elementTextId="27877">
                <text>IMS-LD</text>
              </elementText>
              <elementText elementTextId="27878">
                <text>eLearning platform</text>
              </elementText>
              <elementText elementTextId="27879">
                <text>designing an IMS-LD meta-model</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27880">
                <text>Generate a Meta-Model Content for Collaboration Space of Learning Management System Compatible with IMS-LD</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27881">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="27882">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="27883">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1372" 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="27837">
                <text>Sutopo, Hadi</text>
              </elementText>
              <elementText elementTextId="27838">
                <text>Samosir, Ridha Sefina</text>
              </elementText>
              <elementText elementTextId="27839">
                <text>Gatc, Jullend</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="27840">
                <text>2019-05-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27841">
                <text>This research is intended to evaluate the development of mobile multimedia based stop drug tutorial.  This tutorial as a campaign to stop drugs, that should encourage people’s ability to integrate all information on mobile application. The tutorial focuses on how people understand about drugs and what to do if someone is drugs addicted.  Stopping drug tutorial is created using ADDIE instructional development method, and during the developing stage, it is done using Multimedia Development Life Cycle according to Luther. Subjects of the research are experts in education, visual communication and information technology in the preliminary testing. Evaluation was conducted using the analytic descriptive method on mobile multimedia evaluation method, and interpreted in a narrative way based on the research findings. The evaluation of mobile multimedia application uses combination of multimedia evaluation that is used by educationalist with ISO 9126 that was used by software developer. The research findings show that mobile multimedia stop drugs application can be used with minor revision.</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="27842">
                <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="27843">
                <text>https://online-journals.org/index.php/i-jim/article/view/9436</text>
              </elementText>
              <elementText elementTextId="27844">
                <text>10.3991/ijim.v13i05.9436</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27845">
                <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="27846">
                <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="27847">
                <text>https://online-journals.org/index.php/i-jim/article/view/9436/5680</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27848">
                <text>Copyright (c) 2019 Hadi Sutopo, Ridha Sefina Samosir, Jullend Gatc</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="27849">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 05 (2019); pp. 124-136</text>
              </elementText>
              <elementText elementTextId="27850">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27851">
                <text>drugs</text>
              </elementText>
              <elementText elementTextId="27852">
                <text>evaluation</text>
              </elementText>
              <elementText elementTextId="27853">
                <text>instruction</text>
              </elementText>
              <elementText elementTextId="27854">
                <text>mobile multimedia</text>
              </elementText>
              <elementText elementTextId="27855">
                <text>tutorial</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27856">
                <text>Mobile Multimedia Evaluation: Development of Stop Drugs Tutorial</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27857">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="27858">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="27859">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1371" 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="27812">
                <text>Omotosho, Adebayo</text>
              </elementText>
              <elementText elementTextId="27813">
                <text>Tyoden, Truman</text>
              </elementText>
              <elementText elementTextId="27814">
                <text>Ayegba, Peace</text>
              </elementText>
              <elementText elementTextId="27815">
                <text>Ayoola, Joyce</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="27816">
                <text>2019-05-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27817">
                <text>The importance of students’ involvement in classroom and non-classroom university courses cannot be overemphasized in the process of learning. But, students for several reasons must be motivated to enhance their continuous participation, especially in non-classroom courses. Landmark University is an agrarian-based institution and students are expected to actively take part in at least one agricultural course irrespective of their specializations. Students commitments to Farm Practice courses are core to graduation despite many students not meeting the expected level of dedication early. Gamification is the process of using game strategies and techniques to actively engage and motivate audiences and to solve problems. Using a database of agricultural resources from Landmark University Teaching and Research Farm, a prototype for a gamified mobile app for engaging students in Farm Practice is developed. Game features such as point, leaderboard, and scoresheet were embedded. The application performance was evaluated by a total of fifty students and 70% of the students claimed that their interests in Farm Practice were positively affected after using the app for the first time.</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="27818">
                <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="27819">
                <text>https://online-journals.org/index.php/i-jim/article/view/9404</text>
              </elementText>
              <elementText elementTextId="27820">
                <text>10.3991/ijim.v13i05.9404</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27821">
                <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="27822">
                <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="27823">
                <text>https://online-journals.org/index.php/i-jim/article/view/9404/5679</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27824">
                <text>Copyright (c) 2019 Adebayo Omotosho</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="27825">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 05 (2019); pp. 94-109</text>
              </elementText>
              <elementText elementTextId="27826">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27827">
                <text>gamification</text>
              </elementText>
              <elementText elementTextId="27828">
                <text>farm practice</text>
              </elementText>
              <elementText elementTextId="27829">
                <text>participation</text>
              </elementText>
              <elementText elementTextId="27830">
                <text>user-engagement</text>
              </elementText>
              <elementText elementTextId="27831">
                <text>android</text>
              </elementText>
              <elementText elementTextId="27832">
                <text>mobile app</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27833">
                <text>A Gamified Approach to Improving Student’s Participation in Farm Practice – A Case Study of Landmark University</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27834">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="27835">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="27836">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1370" 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="27789">
                <text>Al-Emran, Mostafa</text>
              </elementText>
              <elementText elementTextId="27790">
                <text>Alkhoudary, Yahya Ashour</text>
              </elementText>
              <elementText elementTextId="27791">
                <text>Mezhuyev, Vitaliy</text>
              </elementText>
              <elementText elementTextId="27792">
                <text>Al-Emran, Mohammed</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="27793">
                <text>2019-01-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27794">
                <text>Mobile learning (M-learning) is relatively becoming a hot topic that attracted the interest of many scholars. Although M-learning is spreading rapidly across many countries in the world, studying the students and educators’ attitudes towards its usage is still in short supply. This study is considered one of the few that attempts to examine the students and educators’ attitudes towards the use of M-learning by focusing on gender and smartphone ownership differences. The data were collected through a questionnaire survey from eight different universities in Dubai, United Arab of Emirates. 141 students and 31 academics participated in the study. The results indicated that the male students and academics were more likely to use the M-learning systems than the females. Moreover, the students and academics who own smartphones were more likely to use the M-learning systems than those who do not so.</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="27795">
                <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="27796">
                <text>https://online-journals.org/index.php/i-jim/article/view/9374</text>
              </elementText>
              <elementText elementTextId="27797">
                <text>10.3991/ijim.v13i01.9374</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27798">
                <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="27799">
                <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="27800">
                <text>https://online-journals.org/index.php/i-jim/article/view/9374/5420</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27801">
                <text>Copyright (c) 2019 Mostafa Al-Emran, Yahya Al Khouadry, Vitaliy Mezhuyev, Mohammed Al-Emran</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="27802">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 01 (2019); pp. 127-135</text>
              </elementText>
              <elementText elementTextId="27803">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27804">
                <text>M-learning</text>
              </elementText>
              <elementText elementTextId="27805">
                <text>Attitudes</text>
              </elementText>
              <elementText elementTextId="27806">
                <text>Gender</text>
              </elementText>
              <elementText elementTextId="27807">
                <text>Smartphone ownership</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27808">
                <text>Students and Educators Attitudes towards the use of M-Learning: Gender and Smartphone ownership Differences</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27809">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="27810">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="27811">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1369" 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="27768">
                <text>Rojas-Osorio, Mercedes</text>
              </elementText>
              <elementText elementTextId="27769">
                <text>Alvarez-Risco, Aldo</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="27770">
                <text>2019-03-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27771">
                <text>This document is a report on the findings of a study aims to investigate human motivations affecting an adoption decision for smartphone among Peruvian university students. This research investigates smartphone users’ perception using a technology acceptance model (TAM). It is analyzed perceived ease of use, perceived usefulness and attitude toward to keep using a smartphone as determinants for behavioral intention to keep using a smartphone between Peruvian university students, evaluating them with reliability and validity and confirming the hypotheses elaborated for the study. Findings indicate that the behavioral intention to keep using a smartphone (BIU) was significantly influenced by perceived ease of use (PEOU), perceived usefulness (PU) and attitude toward to keep using a smartphone (AKUS) and also, PEOU influenced significantly to PU. This study not only provides valuable information about students´ the intention to keep using a smartphone but also enriches the current literature, focusing on Peru, which has a different commercial characteristic and cultural background as compared to North America, Europe, and Asia. According to the current literature review, this is the first study on this subject that specifically focuses on the use of smartphones by Peruvian university students.</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="27772">
                <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="27773">
                <text>https://online-journals.org/index.php/i-jim/article/view/9356</text>
              </elementText>
              <elementText elementTextId="27774">
                <text>10.3991/ijim.v13i03.9356</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27775">
                <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="27776">
                <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="27777">
                <text>https://online-journals.org/index.php/i-jim/article/view/9356/5547</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27778">
                <text>Copyright (c) 2019 Mercedes Rojas-Osorio, Aldo Alvarez-Risco</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="27779">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 03 (2019); pp. 40-52</text>
              </elementText>
              <elementText elementTextId="27780">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27781">
                <text>intention to use</text>
              </elementText>
              <elementText elementTextId="27782">
                <text>Peruvian students</text>
              </elementText>
              <elementText elementTextId="27783">
                <text>technology acceptance model</text>
              </elementText>
              <elementText elementTextId="27784">
                <text>smartphone</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27785">
                <text>Intention to Use Smartphones among Peruvian University Students</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27786">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="27787">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="27788">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1368" 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="27748">
                <text>Raghavendar Raju, L</text>
              </elementText>
              <elementText elementTextId="27749">
                <text>Reddy, C R K</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="27750">
                <text>2019-09-05</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27751">
                <text> Identifying trusted nodes for safe communication is a key challenge in mobile ad-hoc networks. Node compromises a service and leads to uncertainty in node behaviour. Computing the node trust and node management will enhance the security aspect in MANETs. This paper proposes a security improvisation based on a Node Trust Prediction Approach (NTPA).  NTPA aims to prevent the interference of an  anomalous node in a MANET. There by  improving the security and data delivery output. The NTPA calculates the node trust prediction by evaluating the four most frequent actions that are performed by a node in the communication process. Node authorization is a key aspect in the evaluation of an ad hoc network’s security. In the proposed method, we monitor the valid and Invalid Authorization of a node. Data delivery reliability is measured with Success of Packet delivery and Loss or Drop of packets. In this paper, NTPA is compared with SAR(Security-Aware Routing) and AODV (Adhoc on-Demand Distance Vector), to evaluate the efficiency in an adhoc networks. The empirical results shows that there is an increase of 25% packet delivery and  a 40% reduction in  routing overhead. � </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="27752">
                <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="27753">
                <text>https://online-journals.org/index.php/i-jim/article/view/9329</text>
              </elementText>
              <elementText elementTextId="27754">
                <text>10.3991/ijim.v13i09.9329</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27755">
                <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="27756">
                <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="27757">
                <text>https://online-journals.org/index.php/i-jim/article/view/9329/5889</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27758">
                <text>Copyright (c) 2019 L Raghavendar Raju</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="27759">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 09 (2019); pp. 40-51</text>
              </elementText>
              <elementText elementTextId="27760">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27761">
                <text>Trust Computation</text>
              </elementText>
              <elementText elementTextId="27762">
                <text>Node Trust Prediction</text>
              </elementText>
              <elementText elementTextId="27763">
                <text>MANET</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27764">
                <text>Security Improvisation through Node Trust Prediction Approach in Mobile Ad Hoc Networks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27765">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="27766">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="27767">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1367" 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="27727">
                <text>Rizki Diaz, Ivenulut</text>
              </elementText>
              <elementText elementTextId="27728">
                <text>Supianto, Ahmad Afif</text>
              </elementText>
              <elementText elementTextId="27729">
                <text>Tolle, Herman</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="27730">
                <text>2018-12-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27731">
                <text>Understanding player behavior in a game is quite important to know people model thinking. Through puzzle games, people can train spatial abilities in a geometry lesson. Spatial ability consists of five groups, one of them is perceptual speed. The Perceptual Speed factor is characterized by the speed in finding a configuration in a mess of distracting material. This research purposes to know user behavior in Tangram Puzzle game based on user data log. Analysis user behavior from two aspects: the dominant of first selecting a puzzle pieces and the correlation between the number of puzzle completion with time. And based on this research can be concluded that player will choose a shape that easily to identified and has a larger size than other to be completed first. Whereas the correlation between the number of completion and time is on a moderate level and quite significant.</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="27732">
                <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="27733">
                <text>https://online-journals.org/index.php/i-jim/article/view/9280</text>
              </elementText>
              <elementText elementTextId="27734">
                <text>10.3991/ijim.v12i8.9280</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27735">
                <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="27736">
                <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="27737">
                <text>https://online-journals.org/index.php/i-jim/article/view/9280/5369</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27738">
                <text>Copyright (c) 2018 Ivenulut Rizki Diaz, Ahmad Afif Supianto, Herman Tolle</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="27739">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 12 No. 8 (2018); pp. 123-129</text>
              </elementText>
              <elementText elementTextId="27740">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27741">
                <text>user behavior</text>
              </elementText>
              <elementText elementTextId="27742">
                <text>log data</text>
              </elementText>
              <elementText elementTextId="27743">
                <text>tangram puzzle</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27744">
                <text>Log Data Analysis of Player Behavior in Tangram Puzzle Learning Game</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27745">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="27746">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="27747">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
