<?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/browse?collection=3&amp;output=omeka-xml&amp;page=103" accessDate="2026-05-01T19:37:00+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>103</pageNumber>
      <perPage>10</perPage>
      <totalResults>1981</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1731" 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="36090">
                <text>El Mrabet, Hicham</text>
              </elementText>
              <elementText elementTextId="36091">
                <text>Ait Moussa, Abdelaziz</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="36092">
                <text>2020-08-28</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36093">
                <text>Nowadays, the world has known great changes which accelerated the mode of life. Students, on their part have become to expect a stimulating and simple learning experience which takes into consideration this quick pace and helps them solve the stereotypical problems of learning. The analyses conducted in this paper revealed that the recording of attendance in classrooms is done at the expense of the teaching- learning time. Therefore, the article at hand seeks to investigate an effective means to record attendance in a way which doesn’t hinder learning. Differently put, the educational and administrative staffs need to find an effective way to record students’ attendance at presential at the beginning of each learning session without affecting the time allotted to teaching and learning. This article presents and discusses the smart attendance monitoring system in smart classroom as a means to reduce the dropout rate, using connected objects and RFID technology. This system can facilitate the recording of students’ attendance via the Internet of things (IoT) at presential while transmitting attendance record to the administration. At the same time, parents can keep track of their children's attendance to classes through a notification they receive via Email or SMS. In addition, the system automatically sends missed lessons to absent students.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36094">
                <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="36095">
                <text>https://online-journals.org/index.php/i-jim/article/view/14625</text>
              </elementText>
              <elementText elementTextId="36096">
                <text>10.3991/ijim.v14i14.14625</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36097">
                <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="36098">
                <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="36099">
                <text>https://online-journals.org/index.php/i-jim/article/view/14625/7731</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36100">
                <text>Copyright (c) 2020 Hicham EL MRabet, Abdelaziz AIT MOUSSA</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="36101">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 14 (2020); pp. 95-108</text>
              </elementText>
              <elementText elementTextId="36102">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36103">
                <text>School attendance system</text>
              </elementText>
              <elementText elementTextId="36104">
                <text>Smart classroom</text>
              </elementText>
              <elementText elementTextId="36105">
                <text>Smart Education</text>
              </elementText>
              <elementText elementTextId="36106">
                <text>RFID Tags</text>
              </elementText>
              <elementText elementTextId="36107">
                <text>Internet of things</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36108">
                <text>IoT-School Attendance System Using RFID Technology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36109">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="36110">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="36111">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1730" 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="36067">
                <text>Hazim, Hussien Tuama</text>
              </elementText>
              <elementText elementTextId="36068">
                <text>Al-Behadili, Hasanain Abbas Hasan</text>
              </elementText>
              <elementText elementTextId="36069">
                <text>Kareem, Thaar A.</text>
              </elementText>
              <elementText elementTextId="36070">
                <text>Jabbar, Mays Kareem</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="36071">
                <text>2020-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36072">
                <text>Telecommunication technology serves several fields in the world. One of the most significant fields is the emergency services to provide a fast connection between the case, the vehicle and emergency treatment office. This paper is a part of a long-term project to design a reliable communication system service to be used for emergency services of a specific city. The hardware devices of this system are intended to work within an mm waves frequencies. In the current research, as a starting point, an exhaustive study accomplished to pave the way to the main goal of the project. The system uses OFDM technology to improve the performance of the system. Other requirements for error correction are also included in the model such as convolutional, hamming coding and interleaving. The system development is supported by a Matlab interface software to simulate the job of an IoT real-time network covering both vehicles and the control centres.</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="36073">
                <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="36074">
                <text>https://online-journals.org/index.php/i-jim/article/view/14623</text>
              </elementText>
              <elementText elementTextId="36075">
                <text>10.3991/ijim.v14i13.14623</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36076">
                <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="36077">
                <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="36078">
                <text>https://online-journals.org/index.php/i-jim/article/view/14623/7673</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36079">
                <text>Copyright (c) 2020 Hussien Tuma Hazim, Hasanain Abbas Hasan Al-Behadili, Thaar A. Kareem, Mays K. Jabbar</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="36080">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 13 (2020); pp. 238-247</text>
              </elementText>
              <elementText elementTextId="36081">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36082">
                <text>Internet of Things</text>
              </elementText>
              <elementText elementTextId="36083">
                <text>Codec</text>
              </elementText>
              <elementText elementTextId="36084">
                <text>Orthogonal Frequency Division Multiplexing</text>
              </elementText>
              <elementText elementTextId="36085">
                <text>Modelling.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36086">
                <text>Design of Mobile Communication System for Emergency Services</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36087">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="36088">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="36089">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1729" 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="36040">
                <text>Yashina, Marina V.</text>
              </elementText>
              <elementText elementTextId="36041">
                <text>Mokhov, Alexey I.</text>
              </elementText>
              <elementText elementTextId="36042">
                <text>Belova, Maria A.</text>
              </elementText>
              <elementText elementTextId="36043">
                <text>Kostsov, Alexey V.</text>
              </elementText>
              <elementText elementTextId="36044">
                <text>Pospelov, Pavel I.</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="36045">
                <text>2020-06-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36046">
                <text>Traffic flows are becoming more intense over time as a result of global automobilization. Road transport specialists are developing and analyzing different approaches to control traffic, to design and to build new highways. Decreasing total amount of accidents and congestion avoidance on a road are the main goals of this research. General traffic flow features and car localization are the most important types of data to be obtained, processed and analyzed in modern conditions as cars are highly maneuverable. Proper usage of this data allows building new high-quality traffic control systems taking in account all of its significant features. We have developed a system for video-processing from camera fixed on car torpedo.   Research presented in this paper suggests an algorithm of transverse safety clearance evaluation by analyzing a video from vehicle on-board camera.</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="36047">
                <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="36048">
                <text>https://online-journals.org/index.php/i-jim/article/view/14619</text>
              </elementText>
              <elementText elementTextId="36049">
                <text>10.3991/ijim.v14i10.14619</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36050">
                <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="36051">
                <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="36052">
                <text>https://online-journals.org/index.php/i-jim/article/view/14619/7367</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36053">
                <text>Copyright (c) 2020 Marina V. Yashina</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="36054">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 10 (2020); pp. 128-138</text>
              </elementText>
              <elementText elementTextId="36055">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36056">
                <text>computer vision</text>
              </elementText>
              <elementText elementTextId="36057">
                <text>traffic flow</text>
              </elementText>
              <elementText elementTextId="36058">
                <text>intensity</text>
              </elementText>
              <elementText elementTextId="36059">
                <text>congestion</text>
              </elementText>
              <elementText elementTextId="36060">
                <text>virtual detection method</text>
              </elementText>
              <elementText elementTextId="36061">
                <text>augmented reality (AR)</text>
              </elementText>
              <elementText elementTextId="36062">
                <text>video analysis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36063">
                <text>On-Board Video-Evaluation Algorithm of Transverse Safety Clearance for Ahead Road-Vehicle</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36064">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="36065">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="36066">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1728" 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="36015">
                <text>Gómez Prada, Urbano Eliécer</text>
              </elementText>
              <elementText elementTextId="36016">
                <text>Orellana Hernández, Martha Lucía</text>
              </elementText>
              <elementText elementTextId="36017">
                <text>Salinas Ibañez, Jesús Marí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="36018">
                <text>2020-09-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36019">
                <text>This document presents a Decision Support System (DSS) aimed at small livestock farmers who have not made use of Information Technologies (IT) in their production systems. The DSS was built based on the finite difference equations of a simulation model in System Dynamics in whose definition the beneficiaries participated and also served as a base for the development of a serious video game. The DSS and the Serious video game is supported in a Web and Mobile Architecture. The simulation model and the serious video game are used as support tools in the training given to users to learn how to use the DSS. These three tools are the result of a doctoral research project, which used two methodologies during its execution: Design and Development Research and the Case Studies methodology. The tools were applied in an appropriation strategy with livestock farmers of the department of Santander in Colombia, where resistance to change and cultural attachment causes a low adoption of technology. The inclusion of gamification elements helps the user to understand the connection of these elements and their processes in a real farm, know the large volume of data managed by the DSS, enhance the process by making it more fun, improve the learning curve and provide useful data for tracking the use of the DSS. 16 months after the end of the training, the DSS has more than 13000 reported records about the activities of the farmers in their farms.</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="36020">
                <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="36021">
                <text>https://online-journals.org/index.php/i-jim/article/view/14597</text>
              </elementText>
              <elementText elementTextId="36022">
                <text>10.3991/ijim.v14i15.14597</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36023">
                <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="36024">
                <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="36025">
                <text>https://online-journals.org/index.php/i-jim/article/view/14597/7753</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36026">
                <text>Copyright (c) 2020 Urbano Eliécer Gómez Prada, Martha Lucía Orellana Hernández, Jesús María Salinas Ibañez</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="36027">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 15 (2020); pp. 4-24</text>
              </elementText>
              <elementText elementTextId="36028">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36029">
                <text>Information Technologies</text>
              </elementText>
              <elementText elementTextId="36030">
                <text>Appropriation</text>
              </elementText>
              <elementText elementTextId="36031">
                <text>Information systems</text>
              </elementText>
              <elementText elementTextId="36032">
                <text>decision-making</text>
              </elementText>
              <elementText elementTextId="36033">
                <text>Bovine Production System</text>
              </elementText>
              <elementText elementTextId="36034">
                <text>System Dynamics</text>
              </elementText>
              <elementText elementTextId="36035">
                <text>Serious video game.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36036">
                <text>Systems Dynamics and Serious Video Games in an Appropriation Strategy of a Decision Support System for Small Livestock Farmers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36037">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="36038">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="36039">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1727" 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="35995">
                <text>Wohllebe, Atilla</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="35996">
                <text>2020-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35997">
                <text>Using push notifications, companies can address their smartphone app users with advertising messages. Each of these notifications can mean added value for smartphone users in terms of content, but also disruption and interruption. It is therefore important for advertisers to understand how the frequency of message delivery influences consumer acceptance. The systematic review is based on the PRISMA method and initially identifies a total of 18,725 potentially relevant scientific papers. The 17 research articles included in the qualitative synthesis show that push notifications are suitable for encouraging users to use an app and establish new habits. App usage increases with frequency, with particularly active users tolerating higher frequencies. At the same time it is also shown that too high a frequency can be perceived as disturbing and users should therefore be given the opportunity to determine the frequency with which they receive notifications. A gap in research has been identified in particular in studies that look at real observed behaviour of app users instead of behaviour reported via questionnaires and examine the interaction of frequency, content and presentation of notifications.</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="35998">
                <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="35999">
                <text>https://online-journals.org/index.php/i-jim/article/view/14563</text>
              </elementText>
              <elementText elementTextId="36000">
                <text>10.3991/ijim.v14i13.14563</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36001">
                <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="36002">
                <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="36003">
                <text>https://online-journals.org/index.php/i-jim/article/view/14563/7651</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36004">
                <text>Copyright (c) 2020 Atilla Wohllebe</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="36005">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 13 (2020); pp. 36-47</text>
              </elementText>
              <elementText elementTextId="36006">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36007">
                <text>Smartphone Apps</text>
              </elementText>
              <elementText elementTextId="36008">
                <text>Push Notifications</text>
              </elementText>
              <elementText elementTextId="36009">
                <text>Consumer Acceptance</text>
              </elementText>
              <elementText elementTextId="36010">
                <text>Frequency</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36011">
                <text>Consumer Acceptance of App Push Notifications: Systematic Review on the Influence of Frequency</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36012">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="36013">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="36014">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1726" 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="35974">
                <text>Chechina, Antonina Aleksandrovna</text>
              </elementText>
              <elementText elementTextId="35975">
                <text>Churbanova, Natalia Gennadievna</text>
              </elementText>
              <elementText elementTextId="35976">
                <text>Trapeznikova, Marina Aleksandrovna</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="35977">
                <text>2020-06-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35978">
                <text>The paper deals with traffic flow modelling and simulation on supercomputer systems. The created mathematical model is based on cellular automata (CA) approach and allows to depict multilane traffic on various complex road configurations. The numerical algorithms for the model are designed for supercomputer calculations.The main focus of this research is the validation of the created models and the comparison with results obtained by other researchers, as well as with experimental data. Several test problems were solved to carry out the comparison. The results obtained show that the model represents traffic flow characteristics efficiently and correctly and can be used for real-life traffic predictions.</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="35979">
                <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="35980">
                <text>https://online-journals.org/index.php/i-jim/article/view/14549</text>
              </elementText>
              <elementText elementTextId="35981">
                <text>10.3991/ijim.v14i10.14549</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35982">
                <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="35983">
                <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="35984">
                <text>https://online-journals.org/index.php/i-jim/article/view/14549/7361</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35985">
                <text>Copyright (c) 2020 Antonina Aleksandrovna Chechina, Natalia Gennadievna Churbanova, Marina Aleksandrovna Trapeznikova</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="35986">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 10 (2020); pp. 178-185</text>
              </elementText>
              <elementText elementTextId="35987">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35988">
                <text>traffic flow modelling</text>
              </elementText>
              <elementText elementTextId="35989">
                <text>cellular automata</text>
              </elementText>
              <elementText elementTextId="35990">
                <text>parallel computing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35991">
                <text>Modelling Traffic on Road Junctions on Parallel Computing Systems Using Cellular Automata Approach</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35992">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="35993">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="35994">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1725" 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="35949">
                <text>Houmer, Meriem</text>
              </elementText>
              <elementText elementTextId="35950">
                <text>Ouaissa, Mariya</text>
              </elementText>
              <elementText elementTextId="35951">
                <text>Ouaissa, Mariyam</text>
              </elementText>
              <elementText elementTextId="35952">
                <text>Hasnaoui, Moulay Lahcen</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="35953">
                <text>2020-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35954">
                <text>In Intelligent Transport Systems (ITS), Vehicular Ad-hoc Networks (VANET) play an essential role in improving road safety and traffic efficiency. Nevertheless, due to its special characteristics like high mobility, large size of the network and dynamic topology make routing of data in the vehicular ad hoc network more challenging. The problem in these networks is to determine the routing protocol best suited to this environment, and then secure it to provide optimal and secure routing for the data. Recently, position-based routing protocol has been developed by researchers to be a very interesting routing technique for communication between vehicles. In this paper, we propose an secured and enhanced version of the Greedy Perimeter Stateless Routing (GPSR) protocol. This protocol consists of two modules: (i) To implement an improvement of GPSR routing protocol which minimizes transfer delays and control messages. (ii) To deal with security issues, we have proposed a solution that combines between an improved Diffie-Hellman algorithm for reliable key exchange and the hash function based Message Authentication Code (MAC) for the verification of the authentication and integrity of GPSR packet. The proposed solution was checked by the security protocol verification tool, Automated Validation of Internet Security Protocols and Applications (AVISPA), which indicated that it is a very secure level. Simulation results showed that our proposed compared to the original GPSR offers better performances.</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="35955">
                <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="35956">
                <text>https://online-journals.org/index.php/i-jim/article/view/14537</text>
              </elementText>
              <elementText elementTextId="35957">
                <text>10.3991/ijim.v14i13.14537</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35958">
                <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="35959">
                <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="35960">
                <text>https://online-journals.org/index.php/i-jim/article/view/14537/7657</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35961">
                <text>Copyright (c) 2020 Meriem Houmer, Mariya Ouaissa, Mariyam Ouaissa, Moulay Lahcen Hasnaoui</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="35962">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 13 (2020); pp. 48-64</text>
              </elementText>
              <elementText elementTextId="35963">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35964">
                <text>VANET</text>
              </elementText>
              <elementText elementTextId="35965">
                <text>Position-based routing</text>
              </elementText>
              <elementText elementTextId="35966">
                <text>Security</text>
              </elementText>
              <elementText elementTextId="35967">
                <text>GPSR</text>
              </elementText>
              <elementText elementTextId="35968">
                <text>Diffie-Hellman</text>
              </elementText>
              <elementText elementTextId="35969">
                <text>H-MAC.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35970">
                <text>SE-GPSR: Secured and Enhanced Greedy Perimeter Stateless Routing Protocol for Vehicular Ad hoc Networks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35971">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="35972">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="35973">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1724" 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="35926">
                <text>Kharis, Kharis</text>
              </elementText>
              <elementText elementTextId="35927">
                <text>Dameria, Cut Nyak</text>
              </elementText>
              <elementText elementTextId="35928">
                <text>Ebner, Martin</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="35929">
                <text>2020-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35930">
                <text>This research is intended to answer the question, how are the students' perceptions of internet technology in learning and how is the acceptance of Padlet as a microblogging platform for writing skills in German language level A2-B1 CEFR standards for the student. In summary, 21 students within the range of 19-22 years participated, which consisted of 2 males and 19 females - data obtained through opened and closed questionnaires. The results of data analysis showed that students had positive perceptions using internet technology in learning. However, students cannot accept Padlet as a microblogging platform in learning German writing skills due to several factors that influence it. This research has an essential finding: before conducting online learning, lecturers have to consider internet availability and the adequacy of reviews to their smartphones as a learning infrastructure.</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="35931">
                <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="35932">
                <text>https://online-journals.org/index.php/i-jim/article/view/14493</text>
              </elementText>
              <elementText elementTextId="35933">
                <text>10.3991/ijim.v14i13.14493</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35934">
                <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="35935">
                <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="35936">
                <text>https://online-journals.org/index.php/i-jim/article/view/14493/7663</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35937">
                <text>Copyright (c) 2020 Kharis Kharis, Cut Nyak Dameria, Martin Ebner</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="35938">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 13 (2020); pp. 213-220</text>
              </elementText>
              <elementText elementTextId="35939">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35940">
                <text>Perception</text>
              </elementText>
              <elementText elementTextId="35941">
                <text>acceptance</text>
              </elementText>
              <elementText elementTextId="35942">
                <text>Padlet</text>
              </elementText>
              <elementText elementTextId="35943">
                <text>microblogging</text>
              </elementText>
              <elementText elementTextId="35944">
                <text>writing skills</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35945">
                <text>Perception and Acceptance of Padlet as  a Microblogging Platform for Writing Skills</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35946">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="35947">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="35948">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1723" 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="35903">
                <text>Chaeruman, Uwes Anis</text>
              </elementText>
              <elementText elementTextId="35904">
                <text>Wibawa, Basuki</text>
              </elementText>
              <elementText elementTextId="35905">
                <text>Syahrial, Zulfiati</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="35906">
                <text>2020-08-28</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35907">
                <text>Blended learning is not just merely blending face-to-face and online learning. The biggest challenge is making the right mix of relevant learning settings and teaching strategies to meet the learning outcomes. The latest study showed that research focusing on the instructional system design (ISD) model developments, especially related to blended learning approach, were still limited. This study aims to develop an ISD model that can provide a guideline for lecturers in creating a good course using a blended learning approach. This study applied a formative research method. A series of formative evaluation using several formative data collection techniques were used. They were expert review, one-to-one evaluations, and field tests. This study involved 242 respondents, consists of 7 instructional design and e-learning experts, and 235 lecturers. After conducted a series of formative evaluation stages, respondents able to create a good quality course using the ISD model developed.  Most of them get fair and low scores on the field test 1. The score increased significantly on the field test 2, where 33.6% get excellent scores, 48.2% get good scores, and 28.2% get fair scores. The score also increased significantly on field test 3 60.5% get excellent scores, 33.6% get good scores, and only 5.9% get poor scores. Hence, it can be concluded that the ISD model developed is feasible and usable. It can be used by higher education lecturers in Indonesia as a guideline in creating a course using blended learning approach.</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="35908">
                <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="35909">
                <text>https://online-journals.org/index.php/i-jim/article/view/14411</text>
              </elementText>
              <elementText elementTextId="35910">
                <text>10.3991/ijim.v14i14.14411</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35911">
                <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="35912">
                <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="35913">
                <text>https://online-journals.org/index.php/i-jim/article/view/14411/7745</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35914">
                <text>Copyright (c) 2020 Uwes Anis Chaeruman, Basuki Wibawa, Zulfiati Syahrial</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="35915">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 14 (2020); pp. 164-181</text>
              </elementText>
              <elementText elementTextId="35916">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35917">
                <text>asynchronous learning</text>
              </elementText>
              <elementText elementTextId="35918">
                <text>blended learning</text>
              </elementText>
              <elementText elementTextId="35919">
                <text>e-learning</text>
              </elementText>
              <elementText elementTextId="35920">
                <text>instructional sys-tem design</text>
              </elementText>
              <elementText elementTextId="35921">
                <text>synchronous learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35922">
                <text>Development of an Instructional System Design Model as a Guideline for Lecturers in Creating a Course Using Blended Learning Approach</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35923">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="35924">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="35925">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1722" 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="35880">
                <text>D, Uma Nandhini</text>
              </elementText>
              <elementText elementTextId="35881">
                <text>S, Udhayakumar</text>
              </elementText>
              <elementText elementTextId="35882">
                <text>Tamilselvan, Latha</text>
              </elementText>
              <elementText elementTextId="35883">
                <text>J, Silviya Nancy</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="35884">
                <text>2020-07-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35885">
                <text>Computing with mobile is still in its infancy due to its limitations of computational power, battery lifetime and storage capacity. These limitations hinder the growth of mobile computing, which in-turn affects the growth of computationally intensive applications developed for the mobile devices. So in-order to help execute complex applications within the mobile device, mobile cloud computing (MCC) emerged as a feasible solution. The job of offloading the task to the cloud data center for storage and execution from the mobile seems to gain popularity, however, issues related to network bandwidth, loss of mobile data connectivity, and connection setup does not augment well to extend the benefits offered by MCC. Cloudlet servers filled this gab by assisting the mobile cloud environment as an edge device, offering compute power to the connected devices with high speed wireless LAN connectivity. Implementation constraints of cloudlet faces severe challenges in-terms of its storage, network sharing, and VM provisioning. Moreover, the number of connected devices of the cloudlet and its load conditions vary drastically leading to unexpected bottleneck, in which case the availability to server becomes an issue. Therefore, a scalable cloudlet, Client Aware Scalable Cloudlet (CASC) is proposed with linear regression analysis, predicting the knowledge of expected load conditions for provisioning new virtual machines and to perform resource migration.</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="35886">
                <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="35887">
                <text>https://online-journals.org/index.php/i-jim/article/view/14407</text>
              </elementText>
              <elementText elementTextId="35888">
                <text>10.3991/ijim.v14i12.14407</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35889">
                <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="35890">
                <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="35891">
                <text>https://online-journals.org/index.php/i-jim/article/view/14407/7587</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35892">
                <text>Copyright (c) 2020 Udhayakumar S</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="35893">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 12 (2020); pp. 165-178</text>
              </elementText>
              <elementText elementTextId="35894">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35895">
                <text>client aware resource scalability cloudlet</text>
              </elementText>
              <elementText elementTextId="35896">
                <text>mobile cloud computing</text>
              </elementText>
              <elementText elementTextId="35897">
                <text>resource migration</text>
              </elementText>
              <elementText elementTextId="35898">
                <text>scalable cloudlet.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35899">
                <text>Client Aware Scalable Cloudlet to Augment Edge Computing with Mobile Cloud Migration Service</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35900">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="35901">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="35902">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
