<?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=138&amp;sort_field=added" accessDate="2026-05-09T21:27:31+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>138</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <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="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="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="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="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="1377" 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="27954">
                <text>Wirawan, I Made Agus</text>
              </elementText>
              <elementText elementTextId="27955">
                <text>Diarsa, I Wayan Bayu</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="27956">
                <text>2018-12-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27957">
                <text>Although it has been a lot of research recommendation of the tourist attraction, there has been no research that discusses the recommendations of tour packages from a collection of travel in the past. Therefore, in this study it is important to conduct a related study 1) The development of a mobile recommendation system using the Hybrid Method. 2) Test system accuracy in providing tour package recommendations.The study is using CBR stages in providing travel package recommendations from a collection of travel in the past. There are 4 stages of the process: Retrieve, Reuse, Revise, and Retain. In this study the main focus on the retrieve stage using the method hybrid method. The hybrid method of the mobile recommendation system is the combination of the Naive Bayes method, Bayes Theorem, and Dempster Shafer. Where Naive Bayes is used for calculating the probability of continuous criteria such as age and frequency of visits. The Bayes theorem is used for calculating the probability such as country, gender, and visiting purpose. To determine the mass value of the combination of evidence using the Dempster Shafer method. Based on system accuracy test, stated that the total system accuracy in giving recommendation is 95% consisting of 2 kinds of accuracy is 46% full accuracy and 49% of half accuracy. While the error rate of the system in providing tour package of 5%.</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="27958">
                <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="27959">
                <text>https://online-journals.org/index.php/i-jim/article/view/9483</text>
              </elementText>
              <elementText elementTextId="27960">
                <text>10.3991/ijim.v12i8.9483</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27961">
                <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="27962">
                <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="27963">
                <text>https://online-journals.org/index.php/i-jim/article/view/9483/5364</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27964">
                <text>Copyright (c) 2018 I Made Agus Wirawan, I Wayan Bayu Diarsa</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="27965">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 12 No. 8 (2018); pp. 64-84</text>
              </elementText>
              <elementText elementTextId="27966">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27967">
                <text>Tour package</text>
              </elementText>
              <elementText elementTextId="27968">
                <text>Recommendation system</text>
              </elementText>
              <elementText elementTextId="27969">
                <text>Case Based Reasoning</text>
              </elementText>
              <elementText elementTextId="27970">
                <text>Dempster Shafer Theory</text>
              </elementText>
              <elementText elementTextId="27971">
                <text>Naïve Bayes</text>
              </elementText>
              <elementText elementTextId="27972">
                <text>Bayes Theorem</text>
              </elementText>
              <elementText elementTextId="27973">
                <text>Web Responsive</text>
              </elementText>
              <elementText elementTextId="27974">
                <text>k-Fold Cross Validation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27975">
                <text>Mobile-based Recommendation System for the Tour Package Using the Hybrid Method</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27976">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="27977">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="27978">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1378" 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="27979">
                <text>ALFarsi, Ghalia Musallam</text>
              </elementText>
              <elementText elementTextId="27980">
                <text>Jabbar, Jasiya</text>
              </elementText>
              <elementText elementTextId="27981">
                <text>ALSinani, Maryam</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="27982">
                <text>2018-11-08</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27983">
                <text>Technology is developing and changing in every moment that all domains are patchy without it. Our research utilizes the current trends and technology to design and develop a mobile application for the all members of the college. The students are the fundamental members in the college and they are our targets. Mobile notification system is an emerging technology, which influence in solving various dimensions of life. The college announcements and events are disseminated to students and staff through circulars, notice boards, emails, etc. Our research was to employ mobile affinity of especially students who ignore the circulars and notifications in notice board. The tool may be installed from play store mobile. The tool supports the widely used mobile operating system like android and iphone. This tool helps and provides a flexible way for communication. It list all events and news at AlBuraimi University College (BUC) like announcement of training courses and scientific workshop or classes cancel and others events. It also helps in easy access of college portal for both students and staff. The evaluation held finds positive response towards the need of this mobile application. The result shows the interest and satisfaction of users with BUC NEWS mobile application tool</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="27984">
                <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="27985">
                <text>https://online-journals.org/index.php/i-jim/article/view/9484</text>
              </elementText>
              <elementText elementTextId="27986">
                <text>10.3991/ijim.v12i7.9484</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27987">
                <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="27988">
                <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="27989">
                <text>https://online-journals.org/index.php/i-jim/article/view/9484/5273</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27990">
                <text>Copyright (c) 2018 Ghalia Musallam ALFarsi</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="27991">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 12 No. 7 (2018); pp. 129-138</text>
              </elementText>
              <elementText elementTextId="27992">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27993">
                <text>Mobile application</text>
              </elementText>
              <elementText elementTextId="27994">
                <text>SQL</text>
              </elementText>
              <elementText elementTextId="27995">
                <text>java programming</text>
              </elementText>
              <elementText elementTextId="27996">
                <text>Android</text>
              </elementText>
              <elementText elementTextId="27997">
                <text>IOS</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27998">
                <text>Implementing a Mobile Application News Tool for Disseminating Messages and Events of AlBuraimi University College</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27999">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="28000">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="28001">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1379" 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="28002">
                <text>El Beqqal, Mohamed</text>
              </elementText>
              <elementText elementTextId="28003">
                <text>Azizi, Mostafa</text>
              </elementText>
              <elementText elementTextId="28004">
                <text>Lanet, Jean Louis</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="28005">
                <text>2018-10-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28006">
                <text>Increasingly, safety is present in everyday life, at work, at home, in recreational environments, and in all places where there is a flow of people who share a common space. Using biometric fingerprint technique for identity verification has become a primordial due � to the Reduced costs of implementation, � maturity of this � technology in the market � and the ease of use. Many implementations exist using this technique , however, these systems are hard coupled with the environment in which they were developed and the hardware used to capture biometric data. Consequently, � the interoperability issue is hard present in case of changing the environment or using new fingerprint reader. In this paper, we propose a new architecture to solve this problem by dividing the main biometric application to layers based on a flexible communication between components and supporting heterogeneous platforms and � biometric readers.</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="28007">
                <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="28008">
                <text>https://online-journals.org/index.php/i-jim/article/view/9528</text>
              </elementText>
              <elementText elementTextId="28009">
                <text>10.3991/ijim.v12i6.9528</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28010">
                <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="28011">
                <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="28012">
                <text>https://online-journals.org/index.php/i-jim/article/view/9528/5254</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28013">
                <text>Copyright (c) 2018 Mohamed EL BEQQAL, Mostafa Azizi, jean louis Lanet</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="28014">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 12 No. 6 (2018); pp. 124-132</text>
              </elementText>
              <elementText elementTextId="28015">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28016">
                <text>Fingerprint</text>
              </elementText>
              <elementText elementTextId="28017">
                <text>Authentication</text>
              </elementText>
              <elementText elementTextId="28018">
                <text>SDK</text>
              </elementText>
              <elementText elementTextId="28019">
                <text>Interoperability</text>
              </elementText>
              <elementText elementTextId="28020">
                <text>Biometrics.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28021">
                <text>A Novel Approach for an Interoperable Biometric Verification</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28022">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="28023">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="28024">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1380" 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="28025">
                <text>Yunita, Ariana</text>
              </elementText>
              <elementText elementTextId="28026">
                <text>Nursechafia, Nursechafia</text>
              </elementText>
              <elementText elementTextId="28027">
                <text>Setiawan, Erwin</text>
              </elementText>
              <elementText elementTextId="28028">
                <text>Nugroho, Herminarto</text>
              </elementText>
              <elementText elementTextId="28029">
                <text>Ramadhan, Hani</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="28030">
                <text>2018-12-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28031">
                <text>The use of mobile phone has been increasing nowadays in most part of the world and it has become the  phenomenon where people cannot live without. This study aims to reveal whether mobile phone use affects student’s academic achievement compared to other factors such as study program, student’s focus and gender. The frequent of mobile phone use and how excellence student’s academic performance will be analysed. A survey has been conducted to a large number of college students. A questionnaire was developed and delivered by online questionnaire to 513 students of Universitas Pertamina, Jakarta, Indonesia. Using Ordinary Least Square’s result statistical analysis, it can be concluded that gender and study program have significant effects to GPA, while the use of mobile phone and its effect of distracting student’s focus are not significant to GPA. Furthermore , female students significantly scored higher GPA result by 0.23 point than male students, cateris paribus. Then, students from social sciences have higher GPA results by 0.2 point than students from engineering sciences, cateris paribus. Generally, the results should be interesting for decision maker in academic field on how important to embrace mobile phone for learning style. </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="28032">
                <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="28033">
                <text>https://online-journals.org/index.php/i-jim/article/view/9530</text>
              </elementText>
              <elementText elementTextId="28034">
                <text>10.3991/ijim.v12i8.9530</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28035">
                <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="28036">
                <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="28037">
                <text>https://online-journals.org/index.php/i-jim/article/view/9530/5366</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28038">
                <text>Copyright (c) 2018 Ariana Yunita, Nursechafia Nursechafia, Erwin Setiawan, Herminarto Nugroho, Hani Ramadhan</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="28039">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 12 No. 8 (2018); pp. 96-103</text>
              </elementText>
              <elementText elementTextId="28040">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28041">
                <text>The Relationship between Mobile Phone Usage in Classroom and Academic Achievement in College Life</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28042">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="28043">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="28044">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1381" 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="28045">
                <text>Almeatani, Mashael</text>
              </elementText>
              <elementText elementTextId="28046">
                <text>Alotaibi, Haya</text>
              </elementText>
              <elementText elementTextId="28047">
                <text>Alasmari, Eman</text>
              </elementText>
              <elementText elementTextId="28048">
                <text>Meccawy, Maram</text>
              </elementText>
              <elementText elementTextId="28049">
                <text>Alghamdi, Banan</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="28050">
                <text>2019-06-20</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28051">
                <text>This paper investigates the problems facing masters’ students with their thesis writing phases and completion. This research seeks to provide a smart solution that is beneficial, both to the advisor and student(s). Survey and interviews were conducted among masters’ students to determine the challenges facing masters students in the course of their thesis writing phases and completion process. Based on the results of the survey and interviews, a concept model for thesis supervision system (TSS) was developed Providing an automated supervision system  might encourage  students and advisors to communicate in an efficient way resulting in more quality of thesis outcomes and reducing the delay in thesis process. Moreover, the user interface mimics the TSS process in an interactive way that illustrates how the application would be depicted when designed.</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="28052">
                <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="28053">
                <text>https://online-journals.org/index.php/i-jim/article/view/9533</text>
              </elementText>
              <elementText elementTextId="28054">
                <text>10.3991/ijim.v13i06.9533</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28055">
                <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="28056">
                <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="28057">
                <text>https://online-journals.org/index.php/i-jim/article/view/9533/5729</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28058">
                <text>Copyright (c) 2019 mashael mohammad almeatani</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="28059">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 06 (2019); pp. 4-14</text>
              </elementText>
              <elementText elementTextId="28060">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28061">
                <text>Thesis supervision system</text>
              </elementText>
              <elementText elementTextId="28062">
                <text>higher education</text>
              </elementText>
              <elementText elementTextId="28063">
                <text>mobile learning</text>
              </elementText>
              <elementText elementTextId="28064">
                <text>mobile application</text>
              </elementText>
              <elementText elementTextId="28065">
                <text>student-advisor communication</text>
              </elementText>
              <elementText elementTextId="28066">
                <text>peer collaboration.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28067">
                <text>Thesis Supervision Mobile System for Enhancing Student-supervisor Communication</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28068">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="28069">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="28070">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
