<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://igi.indrastra.com/items?output=omeka-xml&amp;page=24&amp;sort_field=Dublin+Core%2CCreator" accessDate="2026-05-01T18:26:55+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>24</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1705" 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="35500">
                <text>Fuada, Syifaul</text>
              </elementText>
              <elementText elementTextId="35501">
                <text>Adiono, Trio</text>
              </elementText>
              <elementText elementTextId="35502">
                <text>Siregar, Lindawani</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="35503">
                <text>2020-09-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35504">
                <text>In this paper, we report a smart street lighting control system using the ESP8266 which is a low-cost Wi-Fi chip with full TCP/IP stack and microcontroller capability. Our system is equipped with a web server developed in HTML code. Hence, our smart street lighting system can be controlled wirelessly to turn ON or turn OFF, and it can be monitored its environmental condition (i.e., temperature and humidity around the system). All sensors used in this system are pure digitally-outputted sensor: DHT11 to monitor the ambient temperature and humidity and BH1750 to adjust the street light intensity automatically. The dimming technique was applied in the control system by using Pulse Width Modulation (PWM). The system was divided into two main parts: Gateway and Node in which these two parts employ the ESP8266. The Gateway as a coordinator will send a message to the node as an end device (in this work, the streetlight act as a Node). Later, the node will send the ACK to the Gateway. As results, each node can send a message to other nodes.</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="35505">
                <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="35506">
                <text>https://online-journals.org/index.php/i-jim/article/view/14081</text>
              </elementText>
              <elementText elementTextId="35507">
                <text>10.3991/ijim.v14i15.14081</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35508">
                <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="35509">
                <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="35510">
                <text>https://online-journals.org/index.php/i-jim/article/view/14081/7757</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35511">
                <text>Copyright (c) 2020 Syifaul Fuada, Trio Adiono, Lindawani Siregar</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="35512">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 15 (2020); pp. 68-80</text>
              </elementText>
              <elementText elementTextId="35513">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35514">
                <text>BH1750</text>
              </elementText>
              <elementText elementTextId="35515">
                <text>DHT11</text>
              </elementText>
              <elementText elementTextId="35516">
                <text>ESP8266</text>
              </elementText>
              <elementText elementTextId="35517">
                <text>Street lighting system</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35518">
                <text>Development of Wireless Control System for Smart Street Lighting using ESP8266</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35519">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="35520">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="35521">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1831" 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="38333">
                <text>Fuada, Syifaul</text>
              </elementText>
              <elementText elementTextId="38334">
                <text>Rabbani, Raihan Fakhri</text>
              </elementText>
              <elementText elementTextId="38335">
                <text>Majid, Nuur Wachid Abdul</text>
              </elementText>
              <elementText elementTextId="38336">
                <text>Prasetiyo, Prasetiyo</text>
              </elementText>
              <elementText elementTextId="38337">
                <text>Muttaqin, Rahmat</text>
              </elementText>
              <elementText elementTextId="38338">
                <text>Adiono, Trio</text>
              </elementText>
              <elementText elementTextId="38339">
                <text>Islam, Shorful</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="38340">
                <text>2021-04-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="38341">
                <text>In this short paper, we prove that smartphones connected to Wi-Fi can be detected (scanned) easily with a Raspberry Pi help. According to the observation, the smartphone eventually broadcasts some packets of data containing MAC layers data. The period of broadcasting data depends on the smartphone’s state (active scanning/sleep). Besides MAC layers data, we also detect/capture other parameters, i.e., wireless signature data transmitted by smartphone (RSSI) and Time-stamp. The RSSI value measured in this test has a range from –30 dBm to –80 dBm. The result proves that different smartphones give different RSSI values (each smartphone emits different power strength). The RSSI value has more significant changes in a short-range (in this test result, 1 to 10 meters) and less significant change in a long-distance (above 20 meters). MAC address, time-stamp, and RSSI scanned/captured successfully through Raspberry Pi from the smartphones can be used as a reference for various purposes/applications in future work, such as Wi-Fi scanning/tracking system.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="38342">
                <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="38343">
                <text>https://online-journals.org/index.php/i-jim/article/view/17169</text>
              </elementText>
              <elementText elementTextId="38344">
                <text>10.3991/ijim.v15i07.17169</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="38345">
                <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="38346">
                <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="38347">
                <text>https://online-journals.org/index.php/i-jim/article/view/17169/9075</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="38348">
                <text>Copyright (c) 2021 Syifaul Fuada, Raihan Fakhri Rabbani, Nuur Wachid Abdul Majid</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="38349">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 15 No. 07 (2021); pp. 176-184</text>
              </elementText>
              <elementText elementTextId="38350">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="38351">
                <text>MAC layer data</text>
              </elementText>
              <elementText elementTextId="38352">
                <text>Time-stamp</text>
              </elementText>
              <elementText elementTextId="38353">
                <text>RSSI</text>
              </elementText>
              <elementText elementTextId="38354">
                <text>Smartphone</text>
              </elementText>
              <elementText elementTextId="38355">
                <text>Wi-Fi tracking system</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="38356">
                <text>Your MAC Address Can be Detected Easily When Your Smartphone Connected to the Wi-Fi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="38357">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="38358">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="38359">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="773" public="1" featured="0">
    <collection collectionId="32">
      <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="14952">
                  <text>Internet of Things and Artificial Intelligence Journal</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="14996">
                <text>Aditya, Moch. Vicky</text>
              </elementText>
              <elementText elementTextId="14997">
                <text>Setiawan, Aries Boedi</text>
              </elementText>
              <elementText elementTextId="14998">
                <text>rabi, Abdur</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="14999">
                <text>2021-01-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15000">
                <text>a Speech Recognition is a system used to recognize word commands from human voices and then translated them into data that can be understood by a computer. The advantages of Speech Recognition include speed and ease of use. Merdeka Malang is a private university founded on January 29, 1964. The University of Merdeka Malang still doesn’t have a strategy in recommending new students based on historical data calculations in choosing faculties. and majors. In calculating the history, if you use a manual system, they will be constrained by the time and accuracy of the data, causing the data to be less valid.Therefore, there is a need for a system that can exchange data in real-time so that the data displayed is always up to date without manual data updating. This process is useful for monitoring and accelerating the process of calculating student interest data, which can later be recommended to future new students. Moreover, The speech technique used is using speech recognition which is used for processing speech data on smartphones while sending data using the XAMPP web server which is used to exchange data from smartphones to servers.
&amp;nbsp;</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="15001">
                <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="15002">
                <text>https://pubs.ascee.org/index.php/iota/article/view/355</text>
              </elementText>
              <elementText elementTextId="15003">
                <text>10.31763/iota.v1i1.355</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15004">
                <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="15005">
                <text>Association for Scientific Computing, Electronics, and Engineering (ASCEE)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="15006">
                <text>https://pubs.ascee.org/index.php/iota/article/view/355/95</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15007">
                <text>Copyright (c) 2021 IOTA (Internet of Things and Artificial Intelegence) Journal</text>
              </elementText>
              <elementText elementTextId="15008">
                <text>https://ascee.org/</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="15009">
                <text>Internet of Things and Artificial Intelligence Journal; Vol. 1 No. 1 (2021): Volume 1 Issue 1, 2021 [February]; 26-37</text>
              </elementText>
              <elementText elementTextId="15010">
                <text>2774-4353</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15011">
                <text>speech</text>
              </elementText>
              <elementText elementTextId="15012">
                <text>recognition</text>
              </elementText>
              <elementText elementTextId="15013">
                <text>realtime</text>
              </elementText>
              <elementText elementTextId="15014">
                <text>web</text>
              </elementText>
              <elementText elementTextId="15015">
                <text>server</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15016">
                <text>Implementation of The Speech Recognition System Using a real time web Server Based</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15017">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="15018">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3318" public="1" featured="0">
    <collection collectionId="47">
      <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="64218">
                  <text>Journal of Naval Architecture and Marine Engineering</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="68162">
                <text>Bouregba, F.</text>
              </elementText>
              <elementText elementTextId="68163">
                <text>Belkadi, M.</text>
              </elementText>
              <elementText elementTextId="68164">
                <text>Aounallah, M.</text>
              </elementText>
              <elementText elementTextId="68165">
                <text>Adjlout, L.</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="68166">
                <text>2020-12-26</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68167">
                <text>New contra-rotating four-bladed DTMB propeller configurations operating in open water are numerically studied to determine their hydrodynamic performances. The unsteady turbulent flow around propellers is modelled by RANS equations with Kω SST model then solved by a CFD code. The computational domain is divided in two blocks linked with a rotating interface. The obtained results show that thrust and efficiency of the contra-rotating (CRP) increase compared to the single propeller, leading to a significant reduction of the propeller diameter. The variation in axial spacing and angular displacement seems to have little effect on the CRP efficiency. The results also show that the thrust can be further improved by adopting a moderate negative twist angle of the rear propeller.
Keywords: CRP contra-rotating propeller, axial spacing, angular spacing, twist angle, CFD.</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="68168">
                <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="68169">
                <text>https://www.banglajol.info/index.php/JNAME/article/view/44950</text>
              </elementText>
              <elementText elementTextId="68170">
                <text>10.3329/jname.v17i2.44950</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68171">
                <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="68172">
                <text>Association of Naval Architects and Marine Engineers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="68173">
                <text>https://www.banglajol.info/index.php/JNAME/article/view/44950/36227</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68174">
                <text>Copyright (c) 2020 Journal of Naval Architecture and Marine Engineering</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="68175">
                <text>Journal of Naval Architecture and Marine Engineering; Vol. 17 No. 2 (2020); 129-141</text>
              </elementText>
              <elementText elementTextId="68176">
                <text>2070-8998</text>
              </elementText>
              <elementText elementTextId="68177">
                <text>1813-8535</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68178">
                <text>Effect of geometrical features on the contra-rotating propeller hydrodynamic performances</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68179">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="68180">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2061" 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="43617">
                <text>Wohllebe, Atilla</text>
              </elementText>
              <elementText elementTextId="43618">
                <text>Adler, Manuel Rolf</text>
              </elementText>
              <elementText elementTextId="43619">
                <text>Podruzsik, Szilárd</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="43620">
                <text>2021-08-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="43621">
                <text>With the increasing relevance of mobile apps for companies, push notifications to address app users are also becoming more important. While the acceptance factors of push notifications have already been extensively researched, the effect of the different design elements on user interaction by opening the mobile app is still completely unexplored. Based on existing scientific findings from related fields, especially banner advertising and e-mail marketing, the authors first develop hypotheses on the effect of title, button and image on user interaction with push notifications. In several experiments the hypotheses are tested using the example of a mobile shopping app. The results are evaluated using Chi-square test and Cramer's V. While the use of a title seems to have a positive effect on interaction rates, the hypotheses on the positive effect of buttons and images on interaction rates have to be rejected.</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="43622">
                <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="43623">
                <text>https://online-journals.org/index.php/i-jim/article/view/23897</text>
              </elementText>
              <elementText elementTextId="43624">
                <text>10.3991/ijim.v15i15.23897</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="43625">
                <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="43626">
                <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="43627">
                <text>https://online-journals.org/index.php/i-jim/article/view/23897/9657</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="43628">
                <text>Copyright (c) 2021 Atilla Wohllebe, Manuel Adler, Szilárd Podruzsik</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="43629">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 15 No. 15 (2021); pp. 35-46</text>
              </elementText>
              <elementText elementTextId="43630">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="43631">
                <text>Push Notifications</text>
              </elementText>
              <elementText elementTextId="43632">
                <text>Mobile Apps</text>
              </elementText>
              <elementText elementTextId="43633">
                <text>Mobile Push Notifications</text>
              </elementText>
              <elementText elementTextId="43634">
                <text>Design Elements</text>
              </elementText>
              <elementText elementTextId="43635">
                <text>Cramer’s V</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="43636">
                <text>Influence of Design Elements of Mobile Push Notifications on Mobile App User Interactions</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="43637">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="43638">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="43639">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2393" 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="51483">
                <text>Adnan Diwan, Sinan</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="51484">
                <text>2022-09-08</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51485">
                <text>Over seventy-one percent of the Earth's surface is covered by oceans, a vast body of water that is sometimes divided up into smaller bodies of water called seas. Research in this area is focusing on the significant advantages of an undersea or ocean-based environment, which is impacted by the ocean's temperature. Freshwater lakes and rivers cover less than 1% of the Earth's surface. So, ecosystems are damaged and modern technology must be developed so that climate and other elements may be regulated. The Internet of Underwater Things is cutting-edge technology in the ocean and underwater environments (IoUT). It's a network of underwater items that can be used to monitor large, undiscovered aquatic areas with a real-time Internet connection. There are several uses for IoUT, including in the military, strategic fields, climate research, and thermal pollution monitoring. With the use of the World Wide Web, Ocean of Things (OoT) devices may communicate in real-time using this technology. An IoUT is one of the most important IoT areas where a dynamic network is built and many advantages are reaped from the process. Using a multi-dimensional method for cumulative performance in the marine and undersea objects area, this research publication presents use examples for IoUT. Many significant applications and real-world domains are demonstrated to interface with crucial IoUT components. The proposed approach is making use of a multi-hop and metaheuristic-based approach for the effectiveness and overall performance of IoUT. As there are so many challenges in IoUT including frequent battery reduction and energy issues, there is a need to integrate the multi-layered approach. The presented approach is effective in terms of fewer packet losses, high throughput, and minimum energy consumption.</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="51486">
                <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="51487">
                <text>https://online-journals.org/index.php/i-jim/article/view/34405</text>
              </elementText>
              <elementText elementTextId="51488">
                <text>10.3991/ijim.v16i17.34405</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51489">
                <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="51490">
                <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="51491">
                <text>https://online-journals.org/index.php/i-jim/article/view/34405/11959</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51492">
                <text>Copyright (c) 2022 Haider Th.Salim Alrikabi; Sinan  Adnan Diwan</text>
              </elementText>
              <elementText elementTextId="51493">
                <text>https://creativecommons.org/licenses/by/4.0</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="51494">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 16 No. 17 (2022); pp. 88-100</text>
              </elementText>
              <elementText elementTextId="51495">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51496">
                <text>Internet of Underwater Things, Internet Connected Underwater Acoustic Net-works, IoUT, and Marine Applications, Ocean of Things</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51497">
                <text>A Multi-Layered Energy Efficient Approach for  Performance Aware Internet of Ocean Things</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51498">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="51499">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="51500">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="711" public="1" featured="0">
    <collection collectionId="30">
      <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="13509">
                  <text>AEGIS : Journal of International Relations</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="14704">
                  <text>School of International Relations, President University, Indonesia</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="13949">
                <text>Adriani, Isyana</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="13950">
                <text>2019-08-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13951">
                <text>Since President of China Xi Jinping introduced the mega infrastructure project Belt and Road Initiative (BRI) in late 2013, many have doubted the real objective of the president, particularly since world leadership position has been vacant because US President Donald Trump still has no clear foreign policy on Asia Pacific. BRI, which aims to connect China to all continents in the world, has already had negative and positive impacts. One of which is Africa, where China has been helping the Trans-African Highway project, a project that has been planned since 1971. However, BRI has caused African countries’ debts to China to multiply, and it is not impossible that they will experience what Sri Lanka has already experienced: Beijing taking over their Hambantota Port. In Indonesia itself, there have been several BRI projects, such as the 142-km fast train that connects Bandung, West Java, to Jakarta, and Morowali Industrial Park in Central Sulawesi. However, despite BRI’s help with infrastructure many people are suspicious that Indonesia will fall into a “debt trap” like Sri Lanka and African countries already did. They are also worried about the ever-increasing number of Chinese workers to Indonesia, which threaten the availability of jobs for locals. On the other hand, Indonesia’s involvement in BRI shows that Indonesia is an important country to China, and this can be seen through many things, one of which is the growing number of Chinese universities having Indonesian language and culture sub-majors in the past seven years. This essay focuses on how these Indonesian language and culture sub-majors contribute to the success of BRI in China.</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="13952">
                <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="13953">
                <text>http://e-journal.president.ac.id/presunivojs/index.php/AEGIS/article/view/730</text>
              </elementText>
              <elementText elementTextId="13954">
                <text>10.33021/aegis.v3i1.730</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13955">
                <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="13956">
                <text>President University</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="13957">
                <text>http://e-journal.president.ac.id/presunivojs/index.php/AEGIS/article/view/730/443</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13958">
                <text>Copyright (c) 2019 AEGIS : Journal of International Relations</text>
              </elementText>
              <elementText elementTextId="13959">
                <text>http://creativecommons.org/licenses/by-nc/4.0</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="13960">
                <text>AEGIS : Journal of International Relations; Vol 3, No 1 (2018): September 2018 - February 2019</text>
              </elementText>
              <elementText elementTextId="13961">
                <text>2548-4532</text>
              </elementText>
              <elementText elementTextId="13962">
                <text>2541-1373</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13963">
                <text>Indonesian Sub-Majors at Chinese Universities and Belt and Road Initiative (BRI)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13964">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="13965">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1651" 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="34248">
                <text>Arif, Teuku Yuliar</text>
              </elementText>
              <elementText elementTextId="34249">
                <text>Munandar, Munandar</text>
              </elementText>
              <elementText elementTextId="34250">
                <text>Adriman, Ramzi</text>
              </elementText>
              <elementText elementTextId="34251">
                <text>Munadi, Rizal</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="34252">
                <text>2020-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34253">
                <text>The wireless mesh network (WMN) is a future network technology that develops single-hop wireless local area networks (WLANs) into multi-hop wireless mesh networks, based on the IEEE 802.11s standard. However, this development still presents many challenges, such as determining the best route between sources and destinations, especially taking into account the use of the medium access control (MAC) and physical (PHY) layers of IEEE 802.11n/ac. Some papers have proposed rate adaptation algorithms particularly for single-hop networks; however, these only focused on mechanisms to find data rates suitable for channel conditions. In IEEE 802.11s WMNs, the design of the rate adaptation algorithm is more challenging. Besides considering the problem of channel quality and optimal throughput, it is necessary to also consider the problem of collision and the best route. It is important to take collision into account because the collision probability in multi-hop mesh networks is higher than that in single-hop networks and can lead to a lower throughput. Rate adaptation algorithms for IEEE 802.11s WMNs have been proposed in other papers, but they also do not consider the use of the MAC and PHY layers of IEEE 802.11n/ac. In this paper, we propose the collision-aware rate adaptation for optimal high-throughput (CARA-OHT) algorithm for WMN IEEE 802.11s. An evaluation through the extensive use of a network NS-3 simulator shows that the proposed algorithm exhibits a higher throughput than previously developed algorithms.</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="34254">
                <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="34255">
                <text>https://online-journals.org/index.php/i-jim/article/view/13245</text>
              </elementText>
              <elementText elementTextId="34256">
                <text>10.3991/ijim.v14i13.13245</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34257">
                <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="34258">
                <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="34259">
                <text>https://online-journals.org/index.php/i-jim/article/view/13245/7677</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34260">
                <text>Copyright (c) 2020 Munandar Munandar, Teuku Yuliar Arif, Ramzi Adriman, Rizal Munadi</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="34261">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 13 (2020); pp. 172-199</text>
              </elementText>
              <elementText elementTextId="34262">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34263">
                <text>CARA-OHT</text>
              </elementText>
              <elementText elementTextId="34264">
                <text>Rate Adaptation</text>
              </elementText>
              <elementText elementTextId="34265">
                <text>Collision-aware</text>
              </elementText>
              <elementText elementTextId="34266">
                <text>Optimal High Throughput</text>
              </elementText>
              <elementText elementTextId="34267">
                <text>802.11s WMN</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34268">
                <text>CARA-OHT: Collision-Aware Rate Adaptation for Optimal High-Throughput in IEEE 802.11s Wireless Mesh Networks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34269">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34270">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34271">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2695" public="1" featured="0">
    <collection collectionId="41">
      <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="57791">
                  <text>Canadian Journal of European and Russian Studies</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="57805">
                <text>Aervitz, Irina</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="57806">
                <text>2005-05-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="57807">
                <text>&amp;nbsp;
This paper is an attempt to develop a critical reflection on the social, political, and economic transformation that Russia experienced in the last couple of decades. I argue that the continuity of elites in Russia is one of the major features of its transition. This paper attempts to illuminate the continuity of elites as a general trend by using the case study of the privatization process in Veliky Novgord, Russia. This project looks at privatization as an avenue or means of resource allocation by elites during the transition. The data were obtained from 16 structured and unstructured interviews conducted in Veliky Novgorod in the summer 2004 among the representatives of the business and political elites. This paper deals with one group of the nomenklatura elite – top enterprise managers.
Full text available at: https://doi.org/10.22215/rera.v1i1.158
&amp;nbsp;</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="57808">
                <text>https://ojs.library.carleton.ca/index.php/CJERS/article/view/2389</text>
              </elementText>
              <elementText elementTextId="57809">
                <text>10.22215/cjers.v1i1.2389</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="57810">
                <text>Centre for European Studies, Carleton University</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="57811">
                <text>Canadian Journal of European and Russian Studies; 2005: RERA V1:1  Inaugural Issue (backfile abstracts)</text>
              </elementText>
              <elementText elementTextId="57812">
                <text>2562-8429</text>
              </elementText>
              <elementText elementTextId="57813">
                <text>10.22215/cjers.v1i1</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="57814">
                <text>Elites in Transition: The Case of Privatization in Veliky Novgorod, Russia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="57815">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="57816">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="57817">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2402" 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="51697">
                <text>Febliza, Asyti</text>
              </elementText>
              <elementText elementTextId="51698">
                <text>Afdal, Zul</text>
              </elementText>
              <elementText elementTextId="51699">
                <text>Copriady, Jimmi</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="51700">
                <text>2023-02-06</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51701">
                <text>This study aims to analyze the comparison of students' critical thinking skills by using learning media based on phenomenon-based learning in a general chemistry course. The media were an interactive web module and an interactive video about the colloidal system. This research is comparative research with a quantitative approach. The sample comprised 68 students from the State Islamic University of Sultan Syarif Kasim Riau and The University of Riau from the chemistry education department. The research data were obtained from students' critical thinking ability test, which consisted of 10 questions and was analyzed using SPSS version 26 for windows. The data collected were analyzed using mean and standard deviation to notice the difference in students' achievement, while analysis of covariance (ANCOVA) was used to test hypotheses and the effect size contribution. The results showed there is a significant difference in students' critical thinking skills between classes that use interactive web modules and classes that use interactive video. Both PhenoBL learning media can improve students' critical thinking skills where the effect size reaches one-third of the percentage. Therefore, educators can consider these learning media to facilitate students in improving critical thinking skills.</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="51702">
                <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="51703">
                <text>https://online-journals.org/index.php/i-jim/article/view/34699</text>
              </elementText>
              <elementText elementTextId="51704">
                <text>10.3991/ijim.v17i03.34699</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51705">
                <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="51706">
                <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="51707">
                <text>https://online-journals.org/index.php/i-jim/article/view/34699/12637</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51708">
                <text>Copyright (c) 2023 Asyti Febliza, Dr. Zul Afdal, M.Pd, Prof. Dr. Jimmi Copriady, M.Si</text>
              </elementText>
              <elementText elementTextId="51709">
                <text>https://creativecommons.org/licenses/by/4.0</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="51710">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 17 No. 03 (2023); pp. 70-86</text>
              </elementText>
              <elementText elementTextId="51711">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51712">
                <text>phenomenon-based Learning</text>
              </elementText>
              <elementText elementTextId="51713">
                <text>interactive video</text>
              </elementText>
              <elementText elementTextId="51714">
                <text>interactive web module</text>
              </elementText>
              <elementText elementTextId="51715">
                <text>critical thinking skills</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51716">
                <text>Improving Students' Critical Thinking Skills: Is Interactive Video and Interactive Web Module Beneficial?</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51717">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="51718">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="51719">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
