<?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=143&amp;sort_field=added" accessDate="2026-05-10T03:45:45+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>143</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1422" 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="28969">
                <text>Salmi, Khalid</text>
              </elementText>
              <elementText elementTextId="28970">
                <text>Magrez, Hamid</text>
              </elementText>
              <elementText elementTextId="28971">
                <text>Sefraoui, Hanane</text>
              </elementText>
              <elementText elementTextId="28972">
                <text>Ziyyat, Abdelhak</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="28973">
                <text>2019-02-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28974">
                <text>The teaching of transmission line theory in electrical engineering courses must be tailored to an audience which is increasingly reluctant to adhere to abstract disciplines. In our opinion, the best solution to make transmission line courses more attractive is to offer practical applications and intensively use of mathematical computer-aided teaching tools to overcome, at the beginning, the difficulties linked to the theory. Indeed, transmission line theory comes alive when the travelling waves are animated on a screen (smartphone, tablets, laptop, etc.). Fundamental concepts such as “progressive wave”, “reflected wave” and “load matching” could be easily demonstrated in the classroom or at home. Transmission line simulations are applied to problems using connections to shunt, open, matched and unmatched loads, and show how the signal waveforms arise from one end to another. The proposed Android-based animations are used with a sinusoidal generator to illustrate the evolution to the sinusoidal steady state and allow learners to easily handle the corresponding Smith chart. Students are encouraged to run those applications at home as a computational laboratory to verify their solutions to homework problems. This article introduces simple Android-based virtual tools for the investigation and visualization in real time of waves traveling along a terminated finite-length transmission line, without and with faults between the source and the load. The package can be used as an educational tool in various lectures or homework to aid teaching high frequency electronics and transmission lines theory.</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="28975">
                <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="28976">
                <text>https://online-journals.org/index.php/i-jim/article/view/10000</text>
              </elementText>
              <elementText elementTextId="28977">
                <text>10.3991/ijim.v13i02.10000</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28978">
                <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="28979">
                <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="28980">
                <text>https://online-journals.org/index.php/i-jim/article/view/10000/5482</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28981">
                <text>Copyright (c) 2019 Khalid Salmi, Hamid Magrez, Hanane Sefraoui, Abdelhak Ziyyat</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="28982">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 02 (2019); pp. 78-88</text>
              </elementText>
              <elementText elementTextId="28983">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28984">
                <text>m-learning</text>
              </elementText>
              <elementText elementTextId="28985">
                <text>transmission lines</text>
              </elementText>
              <elementText elementTextId="28986">
                <text>waves propagation</text>
              </elementText>
              <elementText elementTextId="28987">
                <text>high frequency electronics</text>
              </elementText>
              <elementText elementTextId="28988">
                <text>Smith chart</text>
              </elementText>
              <elementText elementTextId="28989">
                <text>FDTD method</text>
              </elementText>
              <elementText elementTextId="28990">
                <text>Android</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28991">
                <text>Development of a Mobile Application for Teaching Transmission Line Theory</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28992">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="28993">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="28994">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1423" 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="28995">
                <text>Jagdale, Balaso</text>
              </elementText>
              <elementText elementTextId="28996">
                <text>Bakal, Jagdish</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="28997">
                <text>2019-02-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28998">
                <text>Abstract—Due to complex monitoring systems in various business domains, secrecy and privacy has become critical issue for movable resources including human being. In a mobile object monitoring systems, balancing computing resources and quality of privacy is required.  Objects can be mobile devices or users or any other moving entity. This work is presented in wireless sensor network environment. Earlier work does not consider presence of mobile objects in 3D space. We can observe that objects also carry Z axis in city area where high rise buildings are present.  Earlier monitoring applications are mainly designed in two dimensional space to protect privacy. Our novelty is to suggest and design mechanism that reflect Z position (height) of mobile objects for protecting privacy. While calculating cloaking area and counting of objects, height is also considered as third dimension. This results in better location privacy as compared to the privacy delivered by the scheme that considers two dimensional space. We have presented performance, communications cost and privacy strength of modified 3D quality algorithm and 3D resource algorithm. Moreover, we present novel containment resolution algorithm that handles duplicate counting due to 3D presence of wireless system and mobile devices.</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="28999">
                <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="29000">
                <text>https://online-journals.org/index.php/i-jim/article/view/10023</text>
              </elementText>
              <elementText elementTextId="29001">
                <text>10.3991/ijim.v13i02.10023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29002">
                <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="29003">
                <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="29004">
                <text>https://online-journals.org/index.php/i-jim/article/view/10023/5486</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29005">
                <text>Copyright (c) 2019 Balaso Jagdale, Jagdish Bakal</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="29006">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 02 (2019); pp. 128-140</text>
              </elementText>
              <elementText elementTextId="29007">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29008">
                <text>3D Cloaking</text>
              </elementText>
              <elementText elementTextId="29009">
                <text>Location Privacy</text>
              </elementText>
              <elementText elementTextId="29010">
                <text>Mobile Sensor Networks</text>
              </elementText>
              <elementText elementTextId="29011">
                <text>Location monitoring sys-tems.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29012">
                <text>Privacy Aware Monitoring of Mobile Users in Sensor Networks Environment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29013">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29014">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29015">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1424" 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="29016">
                <text>Prasetyo, Novian Adi</text>
              </elementText>
              <elementText elementTextId="29017">
                <text>Prabawati, Andhika Galuh</text>
              </elementText>
              <elementText elementTextId="29018">
                <text>Suyoto, Suyoto</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="29019">
                <text>2019-03-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29020">
                <text>The development of the Internet of Things Industry in Indonesia is increasing rapidly from year to year. One of the uses in this industry is being able to carry out monitoring, control, and analysis. The smart home is one of the applications of IoT that is used in households to make it easier for humans to monitor and control all devices at home. Most homes in Indonesia have various commonly used resources, these are water, electricity, and gas. These resources will run out quickly if humans cannot use them properly. Therefore we need to monitor and control the resources we have at home. One of the resources that will be monitored and controlled in this study is electricity resources because it is more widely used in every corner of the house and almost all household devices use these electricity resources.This research proposes a way to do electricity use effectiveness with monitoring and power control using cloud-based IoT. The proposal discussed in the paper is expected to have other benefits besides saving electricity resources, but it is also expected to reduce the cost of energy use at home.</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="29021">
                <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="29022">
                <text>https://online-journals.org/index.php/i-jim/article/view/10070</text>
              </elementText>
              <elementText elementTextId="29023">
                <text>10.3991/ijim.v13i03.10070</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29024">
                <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="29025">
                <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="29026">
                <text>https://online-journals.org/index.php/i-jim/article/view/10070/5554</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29027">
                <text>Copyright (c) 2019 Novian Adi Prasetyo, Andhika Galuh Prabawati, Suyoto Suyoto</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="29028">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 03 (2019); pp. 143-151</text>
              </elementText>
              <elementText elementTextId="29029">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29030">
                <text>Monitoring and Controlling</text>
              </elementText>
              <elementText elementTextId="29031">
                <text>Power Electric System</text>
              </elementText>
              <elementText elementTextId="29032">
                <text>Smart Home</text>
              </elementText>
              <elementText elementTextId="29033">
                <text>IoT</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29034">
                <text>Smart Home: Power Electric Monitoring and Control in Indonesia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29035">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29036">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29037">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1425" 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="29038">
                <text>Ayo, Eliza Bundoc</text>
              </elementText>
              <elementText elementTextId="29039">
                <text>Anacio, Marcial Leyton</text>
              </elementText>
              <elementText elementTextId="29040">
                <text>Sakay, Lani Estrada</text>
              </elementText>
              <elementText elementTextId="29041">
                <text>Bustamante, Rosemarievic Abejero</text>
              </elementText>
              <elementText elementTextId="29042">
                <text>Mijares, Teresita Sacdalan</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="29043">
                <text>2019-08-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29044">
                <text>This study was undertaken to address the need to modernize the modes of teaching and learning pedagogy by taking advantage of the proliferation of electronic gadgets and mobile devices since, as counted there are more computers than the people in the world (Boren, 2014). This research found out how learning in the new platform could be adopted by teachers and students. In addition, it tested the different variables involved in the use of mobile in learning by faculty and students of Centro Escolar University (CEU) to determine factors that made implementing technology a success or a failure.To attain the set objectives, this study made use of descriptive and inferential method to the data gathered from respondents via stratified random sampling. Specifically, it employed frequency, mean, standard deviation, t-test, analysis of variance and multiple linear regressions for the treatment of data derived from the survey questionnaires. To complete the triangulation approach and for consistency of findings, observation and interview were also conducted.Subsequently, in order to determine adoption to mobile learning the modified Unified Theory of Acceptance and Use of Technology (UTAUT) model was employed. This model shows relationship of moderating variables which are age, gender, voluntariness of use and experience from independent variables like performance expectancy, effort expectancy, social influence, facilitating conditions, anxiety and self-efficacy. After all the statistical treatments were applied, Anxiety, Self-Efficacy, Effort Expectancy, Performance Expectancy and Facilitating Condition contribute to the success of the introduction of technology to the organization, while social influence was excluded as the reasons why users adopt it.</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="29045">
                <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="29046">
                <text>https://online-journals.org/index.php/i-jim/article/view/10083</text>
              </elementText>
              <elementText elementTextId="29047">
                <text>10.3991/ijim.v13i08.10083</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29048">
                <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="29049">
                <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="29050">
                <text>https://online-journals.org/index.php/i-jim/article/view/10083/5850</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29051">
                <text>Copyright (c) 2019 Eliza Bundoc Ayo, Marcial Leyton Anacio, Teresita Sacdalan Mijares, Rosemarievic Abejero Bustamante, Lani Estrada Sakay</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="29052">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 08 (2019); pp. 124-138</text>
              </elementText>
              <elementText elementTextId="29053">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29054">
                <text>mobile learning</text>
              </elementText>
              <elementText elementTextId="29055">
                <text>technology adoption</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29056">
                <text>Diagnosing Adoption to Mobile Learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29057">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29058">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29059">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1426" 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="29060">
                <text>Saeliw, Aekarat</text>
              </elementText>
              <elementText elementTextId="29061">
                <text>Hualkasin, Watcharasuda</text>
              </elementText>
              <elementText elementTextId="29062">
                <text>Puttinaovarat, Supattra</text>
              </elementText>
              <elementText elementTextId="29063">
                <text>Khaimook, Kanit</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="29064">
                <text>2019-05-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29065">
                <text>The common problem that is mostly found in urban area and the organizations service numbers of people such as government places, university, department store, and hospital, is the insufficient car parking. This problem is the result of the continuing increasing number of vehicle. Further, the car parking management is insufficient so the service users waste their time and fuel trying to look for the available parking. The objective of this research was to develop mobile application for smart car parking using Radio-Frequency Identification (RFID) and Internet of Thing (IoT) which can detect the available parking lot so it is time saving for people. Moreover, the parking area management is more efficient as it minimizes the limitation of traditional system which the users have to access web application which is unable to automatically alert when the parking lot status has changed. Further, the data can be applied to the management and planning such as analyzing numbers of vehicle daily to compare with the parking lot if it is sufficient or not in order to improve and provide more parking space appropriately.</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="29066">
                <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="29067">
                <text>https://online-journals.org/index.php/i-jim/article/view/10096</text>
              </elementText>
              <elementText elementTextId="29068">
                <text>10.3991/ijim.v13i05.10096</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29069">
                <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="29070">
                <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="29071">
                <text>https://online-journals.org/index.php/i-jim/article/view/10096/5673</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29072">
                <text>Copyright (c) 2019 Aekarat Saeliw, Watcharasuda Hualkasin, Supattra Puttinaovarat, Kanit Khaimook</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="29073">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 05 (2019); pp. 4-14</text>
              </elementText>
              <elementText elementTextId="29074">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29075">
                <text>Smart car parking</text>
              </elementText>
              <elementText elementTextId="29076">
                <text>Mobile Application</text>
              </elementText>
              <elementText elementTextId="29077">
                <text>IoT</text>
              </elementText>
              <elementText elementTextId="29078">
                <text>RFID</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29079">
                <text>Smart Car Parking Mobile Application based on RFID and IoT</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29080">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29081">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29082">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1427" 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="29083">
                <text>Al Hajri, Eid</text>
              </elementText>
              <elementText elementTextId="29084">
                <text>Hafeez, Farrukh</text>
              </elementText>
              <elementText elementTextId="29085">
                <text>N V, Ameer Azhar</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="29086">
                <text>2019-08-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29087">
                <text>This paper is based on study and implementation of the pilot project for customized, automated, highly secured class room management system known as JIC CMS (Jubail Industrial College Class room management System). In this research paper, the strategies, design, development and implementation of a pilot project for class room attendance management systems is explained in detail. As a pilot project, mobile app is built on Android platform using Xamarin programming. Prototype of proposed system provides high level of authentication by embedding face recognition and biometric verification together with RFID system.  Though given model features are specially designed for our college needs, but this model can be modified for general usage and can be applied for all academic levels i.e. school, college, universities. Among the other features of system, one important feature is selection of system to work in smart mode in which system closes after predefined time and uploaded automatically to the web server.</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="29088">
                <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="29089">
                <text>https://online-journals.org/index.php/i-jim/article/view/10100</text>
              </elementText>
              <elementText elementTextId="29090">
                <text>10.3991/ijim.v13i08.10100</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29091">
                <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="29092">
                <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="29093">
                <text>https://online-journals.org/index.php/i-jim/article/view/10100/5848</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29094">
                <text>Copyright (c) 2019 Farrukh Hafeez</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="29095">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 08 (2019); pp. 95-106</text>
              </elementText>
              <elementText elementTextId="29096">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29097">
                <text>Fully Automated Classroom Attendance System</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29098">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29099">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29100">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1428" 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="29101">
                <text>Seo, Younghoon</text>
              </elementText>
              <elementText elementTextId="29102">
                <text>Shin, DongRyeol</text>
              </elementText>
              <elementText elementTextId="29103">
                <text>Nam, Choonsung</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="29104">
                <text>2019-02-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29105">
                <text>Touch interface technologies for mobile devices are essentially in use. The purpose of such touch interfaces is to run an application by touching a screen with a user’s finger or to implement various functions on the device. When the user has an attempt to use the touch interface, users tend to grab the mobile device with one hand. Because of the existence of untouchable areas to which the user cannot reach with the user’s fingers, it is possible to occur for a case where the user is not able to touch a specific area on the screen accurately. This results in some issues that the mobile device does not carry out the user’s desired function and the execution time is delayed due to the wrong implementation. Therefore, there is a need to distinguish the area where the user can stably input the touch interface from the area where the users cannot and to overcome the problems of the unstable touch area. Furthermore, when the size of the screen increases, these issues will become more serious because of an increase in the unstable touch areas. Especially, an interface that receives position and force data like 3D-touch requires the stable area setting different from the conventional 2D-touch. In this paper, we search and analyze the stable touch areas on the large screen where the user can do 3D-touch inputs.</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="29106">
                <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="29107">
                <text>https://online-journals.org/index.php/i-jim/article/view/10153</text>
              </elementText>
              <elementText elementTextId="29108">
                <text>10.3991/ijim.v13i02.10153</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29109">
                <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="29110">
                <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="29111">
                <text>https://online-journals.org/index.php/i-jim/article/view/10153/5485</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29112">
                <text>Copyright (c) 2019 Younghoon Seo, DongRyeol Shin, Choonsung Nam</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="29113">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 02 (2019); pp. 115-127</text>
              </elementText>
              <elementText elementTextId="29114">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29115">
                <text>Touch screen interface</text>
              </elementText>
              <elementText elementTextId="29116">
                <text>2D-touch</text>
              </elementText>
              <elementText elementTextId="29117">
                <text>3D-touch</text>
              </elementText>
              <elementText elementTextId="29118">
                <text>Stable 3D-touch area</text>
              </elementText>
              <elementText elementTextId="29119">
                <text>Mo-bile device</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29120">
                <text>Defining Stable Touch Area Based on a Large-Screen Smart Device in 3D-Touch Interface</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29121">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29122">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29123">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1429" 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="29124">
                <text>Katuk, Norliza</text>
              </elementText>
              <elementText elementTextId="29125">
                <text>Zakaria, Nur Haryani</text>
              </elementText>
              <elementText elementTextId="29126">
                <text>Ku-Mahamud, Ku-Ruhana</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="29127">
                <text>2019-02-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29128">
                <text>Modern mobile phones or smartphones have multipurpose functions apart from being used as a device for voice and text communications. They are also embedded with many useful sensors, including camera, barometer, accelerometer, and digital compass. Unlike other types of sensor, the smartphone camera has been underutilized. This paper aims to fill the gap by analyzing and reviewing the hardware and software components of smartphones and highlighting the potential uses of the smartphone camera to support human daily life activities. A simple search of research papers indexed in Google Scholar was carried out using guided terms. The papers were filtered to match the research questions for this study. Only relevant papers were analyzed and reviewed. The results of the analysis suggested that the rapid development in the smartphone hardware has extended the use of the smartphone cameras beyond personal and social photography.  Consequently, applications (apps) based on smartphone cameras emerge, such as barcode readers, document digitizing tools, augmented reality, translation tools, and indoor positioning device. These apps benefit users and facilitate them in their daily life activities.</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="29129">
                <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="29130">
                <text>https://online-journals.org/index.php/i-jim/article/view/10166</text>
              </elementText>
              <elementText elementTextId="29131">
                <text>10.3991/ijim.v13i02.10166</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29132">
                <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="29133">
                <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="29134">
                <text>https://online-journals.org/index.php/i-jim/article/view/10166/5484</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29135">
                <text>Copyright (c) 2019 Norliza Katuk, Nur Haryani Zakaria, Ku-Ruhana Ku-Mahamud</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="29136">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 02 (2019); pp. 102-114</text>
              </elementText>
              <elementText elementTextId="29137">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29138">
                <text>mobile devices</text>
              </elementText>
              <elementText elementTextId="29139">
                <text>mobile phones</text>
              </elementText>
              <elementText elementTextId="29140">
                <text>mobile telecommunication systems</text>
              </elementText>
              <elementText elementTextId="29141">
                <text>sensors</text>
              </elementText>
              <elementText elementTextId="29142">
                <text>surveys</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29143">
                <text>Mobile Phone Sensing using the Built-in Camera</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29144">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29145">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29146">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1430" 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="29147">
                <text>Purnomo W.P., Yohanes Sigit</text>
              </elementText>
              <elementText elementTextId="29148">
                <text>Indriasari, Theresia Devi</text>
              </elementText>
              <elementText elementTextId="29149">
                <text>Anindito, Kusworo</text>
              </elementText>
              <elementText elementTextId="29150">
                <text>Andrean, Yoshua</text>
              </elementText>
              <elementText elementTextId="29151">
                <text>Prasetyo, Jaka Galih</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="29152">
                <text>2019-09-05</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29153">
                <text>The rate of crime incidence in Indonesia is quite high. Some efforts to prevent crime and to create community safety have been already conducted. However, the information technology has not been implemented yet. CrimeID could be a technology tool for both individual and collective crime prevention. The citizen could participate individually as a crowd to annotate the crime data from news article through the crowdsourcing platform using gamification concept. The collected data could be used to raise the awareness among community members of the crime that happens surrounding them by using the location-aware system.</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="29154">
                <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="29155">
                <text>https://online-journals.org/index.php/i-jim/article/view/10172</text>
              </elementText>
              <elementText elementTextId="29156">
                <text>10.3991/ijim.v13i09.10172</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29157">
                <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="29158">
                <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="29159">
                <text>https://online-journals.org/index.php/i-jim/article/view/10172/5891</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29160">
                <text>Copyright (c) 2019 Yohanes Sigit Purnomo WP, Th. Devi Indriasari, Kusworo Anindito, Yoshua Andrean, Jaka Galih Prasetyo</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="29161">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 09 (2019); pp. 52-65</text>
              </elementText>
              <elementText elementTextId="29162">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29163">
                <text>crime prevention</text>
              </elementText>
              <elementText elementTextId="29164">
                <text>community safety</text>
              </elementText>
              <elementText elementTextId="29165">
                <text>crowdsourcing</text>
              </elementText>
              <elementText elementTextId="29166">
                <text>gamification</text>
              </elementText>
              <elementText elementTextId="29167">
                <text>location-aware</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29168">
                <text>CrimeID: Towards Crime Prevention and Community Safety in Indonesia using Mobile and Web Technology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29169">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29170">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29171">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1431" 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="29172">
                <text>Chuchu, Tinashe</text>
              </elementText>
              <elementText elementTextId="29173">
                <text>Ndoro, Tinashe</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="29174">
                <text>2019-03-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29175">
                <text>The main purpose of the present study was to examine whether mobile applica-tions could be adopted as feasible tools for learning purposes at higher education institutions. Furthermore the study’s intention was to conduct an empirical inves-tigation into students’ perceptions towards mobile applications being introduced as learning aids. The researcher developed a conceptual model derived from the technology acceptance model in order to measure the constructs used in the study. Adopting a quantitative approach, the field study was conducted in South Africa at a selected higher education institution. Research data was collected from 380 registered students at the selected higher education institution who were older than 18 years. Using SPSS 23 and AMOS 23 software programs, Structural Equation Modeling (SEM) was performed to analyse the data set. The results re-vealed that perceived usefulness, perceived ease of use, attitudes towards a mo-bile application, intention to use a mobile application were all significant predic-tors for the actual use of mobile applications for learning. The findings of the study illuminate the importance of the determinants of the adoption of mobile ap-plications for learning in higher education.</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="29176">
                <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="29177">
                <text>https://online-journals.org/index.php/i-jim/article/view/10195</text>
              </elementText>
              <elementText elementTextId="29178">
                <text>10.3991/ijim.v13i03.10195</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29179">
                <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="29180">
                <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="29181">
                <text>https://online-journals.org/index.php/i-jim/article/view/10195/5548</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29182">
                <text>Copyright (c) 2019 Tinashe Chuchu, Tinashe Ndoro</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="29183">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 03 (2019); pp. 53-67</text>
              </elementText>
              <elementText elementTextId="29184">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29185">
                <text>An Examination of the Determinants of the Adoption of Mobile Applications as Learning Tools for Higher Education Students</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29186">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29187">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29188">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
