<?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=216" accessDate="2026-05-15T10:12:17+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>216</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <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="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="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="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="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="1421" 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="28950">
                <text>Saraubon, Kobkiat</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="28951">
                <text>2019-02-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28952">
                <text>This paper presents a learning media repository and delivery system (LMRD) for a smart classroom using IoT and mobile technologies. It was designed to support active learning pedagogy. Teachers are able to broadcast learning media or course materials directly to the student mobile devices, after that the students can interact to the media by drawing, editing, or adding comments using their mobile device then broadcast it back to present or reflect their thinking. The system includes 1) a server using a Raspberry Pi 3B+ and 2) mobile devices. The system supports full features involving two approaches in the form of an Internet model and a non-Internet model. The mobile applications were implemented using cross-platform approach to support major mobile platforms including iOS and Android. The evaluation had three dimensions in terms of usability, functionality and security. The results revealed that all dimensions were evaluated highly. The teacher and students were highly satisfied with the 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="28953">
                <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="28954">
                <text>https://online-journals.org/index.php/i-jim/article/view/9941</text>
              </elementText>
              <elementText elementTextId="28955">
                <text>10.3991/ijim.v13i02.9941</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28956">
                <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="28957">
                <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="28958">
                <text>https://online-journals.org/index.php/i-jim/article/view/9941/5481</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28959">
                <text>Copyright (c) 2019 Kobkiat Saraubon</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="28960">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 02 (2019); pp. 66-77</text>
              </elementText>
              <elementText elementTextId="28961">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28962">
                <text>Internet of Things (IoT)</text>
              </elementText>
              <elementText elementTextId="28963">
                <text>Smart classroom</text>
              </elementText>
              <elementText elementTextId="28964">
                <text>Raspberry Pi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28965">
                <text>Learning Media Repository and Delivery System for Smart Classroom using IoT and Mobile Technologies</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28966">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="28967">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="28968">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1420" 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="28927">
                <text>Kumar, Josh</text>
              </elementText>
              <elementText elementTextId="28928">
                <text>Kathirvel, A.</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="28929">
                <text>2019-04-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28930">
                <text>Mobile Ad hoc NETwork is a collection of mobile nodes connected with each other without any centralized infrastructure support. In MANET, every node acts as a router, thereby forwards the packet to other nodes through the best route possible. The cooperation of all other nodes is very essential for a node to transfer data to its desired destination. Throughput is a major factor that determines the health of any network including MANET and there can be many reasons that can disrupt the throughput. In this paper we deal with two prime reasons that may reduce the throughput in a MANET. The first reason is that, if a node behaves selfishly and utilizes the path only for forwarding its own packet, then the packets from other nodes will be dropped and the throughput will gradually get reduced. The second reason for reduction in throughput is the phenomenon called fading, which causes signal attenuation. This phenomenon creates path loss temporarily, during which the packet loss increases and the throughput takes a major hit. Removing such nodes from the network on the basis of doubt about its packet forwarding nature and ability will eventually weaken the network strength. Neglecting the original best route will also reduce the quality of the network. Both the cases of selfishness and fading can be normalized by switching over to an alternate path and coming back to the same route after a short period of time. Thereby the quality as well as the quantity of nodes involved in the network can be maintained. In this paper we have also introduced an innovation called helper nodes which will also help in the formation of alternate path and will very well neutralize the ill effects caused due to selfishness and fading.</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="28931">
                <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="28932">
                <text>https://online-journals.org/index.php/i-jim/article/view/9928</text>
              </elementText>
              <elementText elementTextId="28933">
                <text>10.3991/ijim.v13i04.9928</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28934">
                <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="28935">
                <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="28936">
                <text>https://online-journals.org/index.php/i-jim/article/view/9928/5597</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28937">
                <text>Copyright (c) 2019 Josh Kumar</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="28938">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 04 (2019); pp. 164-177</text>
              </elementText>
              <elementText elementTextId="28939">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28940">
                <text>MANET</text>
              </elementText>
              <elementText elementTextId="28941">
                <text>Selfish nodes</text>
              </elementText>
              <elementText elementTextId="28942">
                <text>Fading</text>
              </elementText>
              <elementText elementTextId="28943">
                <text>Throughput</text>
              </elementText>
              <elementText elementTextId="28944">
                <text>Alternate route</text>
              </elementText>
              <elementText elementTextId="28945">
                <text>Helper nodes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28946">
                <text>Analysis and Ideas for Improved Routing in MANET</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28947">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="28948">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="28949">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1419" 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="28906">
                <text>Raras, Merdu</text>
              </elementText>
              <elementText elementTextId="28907">
                <text>Kuswanto, Heru</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="28908">
                <text>2019-05-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28909">
                <text>­This study aimed to (1) develop a suitable learning device of Jemparingan Tradition-based (JEMASIK) Android-assisted (2) to know the effect of JEMASIK-based media to improve the representation ability of graphical and vector in sub-chapter of parabolic motion vector. The total sample on field test trial were 61 students, consisted of 29 control class students and 31 experimental class students. The research results showed that there were differences between experimental classes using JEMASIK and control classes using Power Point media. The difference was proved by multivariate test score of 0.000 less than 0.05. The effectiveness of JEMASIK media was viewed by the gain score of pretest and posttest. The gain score of control class was 0.54 in graphical representation and 0.49 in vector representation. Meanwhile, the gain score of experimental class was 0.75 in graphical representation and 0.60 in vector representation.</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="28910">
                <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="28911">
                <text>https://online-journals.org/index.php/i-jim/article/view/9926</text>
              </elementText>
              <elementText elementTextId="28912">
                <text>10.3991/ijim.v13i05.9926</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28913">
                <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="28914">
                <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="28915">
                <text>https://online-journals.org/index.php/i-jim/article/view/9926/5677</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28916">
                <text>Copyright (c) 2019 Merdu Raras, Heru Kuswanto</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="28917">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 05 (2019); pp. 58-74</text>
              </elementText>
              <elementText elementTextId="28918">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28919">
                <text>Android</text>
              </elementText>
              <elementText elementTextId="28920">
                <text>JEMASIK</text>
              </elementText>
              <elementText elementTextId="28921">
                <text>Graphic Representation</text>
              </elementText>
              <elementText elementTextId="28922">
                <text>Vector Representation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28923">
                <text>Developing Jemparingan Tradition-Based and Android-Assisted Learning Media for Improving the Graphic and Vector  Representation Ability</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28924">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="28925">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="28926">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1418" 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="28883">
                <text>El-Sofany, Hosam</text>
              </elementText>
              <elementText elementTextId="28884">
                <text>Abou El-Seoud, Samir</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="28885">
                <text>2019-01-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28886">
                <text>the increasing growth of mobile devices technology and Mobile-based systems with the emerging of cloud computing technology, created a Mobile Cloud Computing field to be the recent future technology for different wireless services. The development of Mobile-based system under cloud computing environment solve some performance and environment related issues include: bandwidth, storage capacity, availability, scalability and heterogeneity. The Mobile-based cloud computing apps are different comparing to mobile computing apps, since in the first model the devices run cloud based web applications not as mobile computing native apps. Services of Mobile-based systems via cloud are accessing and sharing through internet connection thus they are open for attacker to attack on its security. Distributed Denial of Service (DDoS) attacks can cause a big problem in mobile cloud computing security. The main objective of DDoS attacks is to infect wireless devises resources (e.g., software applications, wireless network, etc.) and make them unavailable to the authorized user. In DDoS, the attacker tries to overload the Mobile-based service with traffic. The main objective of this research paper is to introduce novel model for securing Mobile-based systems against DDoS attacks. Efficiency and performance analysis evaluations of the proposed model are presented.  The feedbacks of the experimental results were highly promising, for protecting mobile-based cloud computing systems against DDoS attacks.</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="28887">
                <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="28888">
                <text>https://online-journals.org/index.php/i-jim/article/view/9900</text>
              </elementText>
              <elementText elementTextId="28889">
                <text>10.3991/ijim.v13i01.9900</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28890">
                <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="28891">
                <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="28892">
                <text>https://online-journals.org/index.php/i-jim/article/view/9900/5439</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28893">
                <text>Copyright (c) 2019 Samir Abou El-Seoud, Hosam El-Sofany</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="28894">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 01 (2019); pp. 85-98</text>
              </elementText>
              <elementText elementTextId="28895">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28896">
                <text>mobile computing</text>
              </elementText>
              <elementText elementTextId="28897">
                <text>cloud computing</text>
              </elementText>
              <elementText elementTextId="28898">
                <text>mobile security</text>
              </elementText>
              <elementText elementTextId="28899">
                <text>mobile attacks</text>
              </elementText>
              <elementText elementTextId="28900">
                <text>denial of service attacks</text>
              </elementText>
              <elementText elementTextId="28901">
                <text>distributed denial-of-service attacks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28902">
                <text>A Novel Model for Securing Mobile-based Systems against DDoS Attacks in Cloud Computing Environment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28903">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="28904">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="28905">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1417" 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="28859">
                <text>Abou El-Seoud, Samir</text>
              </elementText>
              <elementText elementTextId="28860">
                <text>Taj-Eddin, Islam</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="28861">
                <text>2019-01-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28862">
                <text>this report will exhibit an outline of the basic features of Mobile Augmented Reality (MAR) and the key concepts of this technology in the Fashion Retail Industry. Several obstacles such as the necessity of putting on the garments to experience its actual view have been tackled by customers throughout the process of clothes shopping. The goal is to constringe these obstacles by creating an Augmented Reality based application that will directly solve these problems. The methodology was conducted by questioning shoppers about the different holdbacks faced during shopping. Solutions for the issues are expected to be achieved by developing an easily utilizable MAR application for targeted customers. The design of this paper involved the utilization of handed questionnaire and semi structured interviews with several store managers to gather sufficient about their sales strategy and proposing the solution of Augmented Reality utilization within the market. Augmented Reality Technology have a great potential to be utilized efficiently inside the fashion market as it will meritoriously improve the shopping experience of consumers across multiple fashion related industry channels.</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="28863">
                <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="28864">
                <text>https://online-journals.org/index.php/i-jim/article/view/9898</text>
              </elementText>
              <elementText elementTextId="28865">
                <text>10.3991/ijim.v13i01.9898</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28866">
                <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="28867">
                <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="28868">
                <text>https://online-journals.org/index.php/i-jim/article/view/9898/5412</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28869">
                <text>Copyright (c) 2019 Samir Abou El-Seoud</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="28870">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 01 (2019); pp. 4-19</text>
              </elementText>
              <elementText elementTextId="28871">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28872">
                <text>Fashion</text>
              </elementText>
              <elementText elementTextId="28873">
                <text>Augmented Reality</text>
              </elementText>
              <elementText elementTextId="28874">
                <text>Mobile Augmented Reality</text>
              </elementText>
              <elementText elementTextId="28875">
                <text>AR</text>
              </elementText>
              <elementText elementTextId="28876">
                <text>MAR</text>
              </elementText>
              <elementText elementTextId="28877">
                <text>Mobile Retailing</text>
              </elementText>
              <elementText elementTextId="28878">
                <text>Information Technology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28879">
                <text>An Android Augmented Reality Application  for Retail Fashion Shopping</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28880">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="28881">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="28882">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
