<?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=54&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-03T03:06:13+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>54</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1526" 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="31375">
                <text>Puttinaovarat, Supattra</text>
              </elementText>
              <elementText elementTextId="31376">
                <text>Horkaew, Paramate</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="31377">
                <text>2019-11-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="31378">
                <text>Nowadays, natural disasters tend to increase and become more severe. They do affect life and belongings of great numbers of people. One kind of such disasters that hap-pen frequently almost every year is floods in all regions across the world. A prepara-tion measure to cope with upcoming floods is flood forecasting in each particular area in order to use acquired data for monitoring and warning to people and involved per-sons, resulting in the reduction of damage. With advanced computer technology and remote sensing technology, large amounts of applicable data from various sources are provided for flood forecasting. Current flood forecasting is done through computer processing by different techniques. The famous one is machine learning, of which the limitation is to acquire a large amount big data. The one currently used still requires manpower to download and record data, causing delays and failures in real-time flood forecasting. This research, therefore, proposed the development of an automatic big data downloading system from various sources through the development of applica-tion programming interface (API) for flood forecasting by machine learning. This research relied on 4 techniques, i.e., maximum likelihood classification (MLC), fuzzy logic, self-organization map (SOM), and artificial neural network with RBF Kernel. According to accuracy assessment of flood forecasting, the most accurate technique was MLC (99.2%), followed by fuzzy logic, SOM, and RBF (97.8%, 96.6%, and 83.3%), respectively.</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="31379">
                <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="31380">
                <text>https://online-journals.org/index.php/i-jim/article/view/11237</text>
              </elementText>
              <elementText elementTextId="31381">
                <text>10.3991/ijim.v13i11.11237</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="31382">
                <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="31383">
                <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="31384">
                <text>https://online-journals.org/index.php/i-jim/article/view/11237/6039</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="31385">
                <text>Copyright (c) 2019 Supattra Puttinaovarat, Paramate Horkaew</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="31386">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 11 (2019); pp. 137-156</text>
              </elementText>
              <elementText elementTextId="31387">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="31388">
                <text>Application Programming Interface</text>
              </elementText>
              <elementText elementTextId="31389">
                <text>Big Data</text>
              </elementText>
              <elementText elementTextId="31390">
                <text>Flood Forecasting</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="31391">
                <text>Application Programming Interface for Flood Forecasting from Geospatial Big Data and Crowdsourcing Data</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="31392">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="31393">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="31394">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2020" 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="42668">
                <text>Mahmood, Ibrahim Nasir</text>
              </elementText>
              <elementText elementTextId="42669">
                <text>Aliedane, Hussein Ali</text>
              </elementText>
              <elementText elementTextId="42670">
                <text>Abuzaraida, Mustafa Ali</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="42671">
                <text>2021-06-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="42672">
                <text>Due to the increased rate of fire accidents which cause many damages and losses to people souls, material, and property in Basra city. The necessity of analyzing and mining the data of the fire accidents became an urgent need to find a solution. The need increased for a solution that helps to mitigate and reduce the number of accidents. In this paper, data mining techniques and applications including data preprocessing, data cleaning, and data exploration have been applied. Data mining applications is performed to analyze and discover the hidden knowledge in ten years of data (fire accidents happened from 2010 – 2019) which is approximately 20k record of accidents. These data mining techniques along with the association rules algorithm is applied on the dataset. The applied approach and techniques resulted in discovering the patterns and the nature of the fire accidents in Basra city. It also helped to reach to recommendations and resolutions for mitigating the fire accidents and its occurrence rate.</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="42673">
                <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="42674">
                <text>https://online-journals.org/index.php/i-jim/article/view/22687</text>
              </elementText>
              <elementText elementTextId="42675">
                <text>10.3991/ijim.v15i12.22687</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="42676">
                <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="42677">
                <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="42678">
                <text>https://online-journals.org/index.php/i-jim/article/view/22687/9429</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="42679">
                <text>Copyright (c) 2021 Ibrahim Nasir Mahmood, Hussein Ali Aliedane, Mustafa Ali Abuzaraida</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="42680">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 15 No. 12 (2021); pp. 158-169</text>
              </elementText>
              <elementText elementTextId="42681">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="42682">
                <text>Data Mining</text>
              </elementText>
              <elementText elementTextId="42683">
                <text>Association Rules</text>
              </elementText>
              <elementText elementTextId="42684">
                <text>Fire Accidents Analysis</text>
              </elementText>
              <elementText elementTextId="42685">
                <text>Data Analysis</text>
              </elementText>
              <elementText elementTextId="42686">
                <text>Data Cleaning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="42687">
                <text>Applications of Data Mining in Mitigating Fire Accidents Based on Association Rules</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="42688">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="42689">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="42690">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2223" 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="47471">
                <text>Wu, Weishen</text>
              </elementText>
              <elementText elementTextId="47472">
                <text>Yu, Yi-Ting</text>
              </elementText>
              <elementText elementTextId="47473">
                <text>Ashar, Muhammad</text>
              </elementText>
              <elementText elementTextId="47474">
                <text>Kuncoroaji, Triyono Indrasiwi</text>
              </elementText>
              <elementText elementTextId="47475">
                <text>Darmawan, Vertic Eridani Budi</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="47476">
                <text>2022-03-08</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="47477">
                <text>In the regions of Chinese as the first language, children with backward Chinese characters ability are more likely to give up reading the subject content of long texts, which affects their learning in the long term. This study applies augmented reality (AR) to develop a remedial teaching model for Chinese radical recognition and assesses its effectiveness on underachieved students at an elementary school. Based on several Chinese characters that were easy for children to confuse radicals, an AR app for Android was developed and installed in tablet computers. The remedial teaching model involves students to use AR app to scan radical cards and trigger animations introducing the evolution of radicals. Students can practice Chinese character writing on the tablet computer's screen. With the multiple stimulus of AR, the teacher lead students collaboratively complete the worksheets. To assess students' learning outcomes, a quasi-experimental approach was administrated to 8 second grade students who had backward Chinese literacy, in which qualitative and quantitative data were collected. Results showed this remedial teaching model improved the disadvantaged students’ recognition accuracy on Chinese characters and flips their motivation toward Chinese characters learning. During the remedial teaching program, use of AR was effective to get students more attentions and impressions on Chinese radicals. Finally, Implications for Chinese characters teaching practices are discussed</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="47478">
                <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="47479">
                <text>https://online-journals.org/index.php/i-jim/article/view/28983</text>
              </elementText>
              <elementText elementTextId="47480">
                <text>10.3991/ijim.v16i05.28983</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="47481">
                <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="47482">
                <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="47483">
                <text>https://online-journals.org/index.php/i-jim/article/view/28983/10885</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="47484">
                <text>Copyright (c) 2022 Dr. Wu, Dr., Triyono, Vertic</text>
              </elementText>
              <elementText elementTextId="47485">
                <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="47486">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 16 No. 05 (2022); pp. 81-90</text>
              </elementText>
              <elementText elementTextId="47487">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="47488">
                <text>remedial teaching</text>
              </elementText>
              <elementText elementTextId="47489">
                <text>augmented reality</text>
              </elementText>
              <elementText elementTextId="47490">
                <text>Chinese radicals</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="47491">
                <text>Applying Augmented Reality to Chinese Radicals Learning: A Remedial Teaching Experiment in an Elementary School</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="47492">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="47493">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="47494">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1604" 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="33166">
                <text>Lai, Chien-Hung</text>
              </elementText>
              <elementText elementTextId="33167">
                <text>Jong, Bin-Shyan</text>
              </elementText>
              <elementText elementTextId="33168">
                <text>Hsia, Yen-Teh</text>
              </elementText>
              <elementText elementTextId="33169">
                <text>Lin, Tsong-Wuu</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="33170">
                <text>2020-04-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="33171">
                <text>There have been lots of studies using traditional concept assessment to measure student’s learning achievement. This study adding game elements in concept assessment try to measure student’s learning achievement, and compare this result with traditional concept assessment to see what’s the difference between traditional concept assessment and adding game element in concept assessment.     Traditional concept assessment using SPRT method in multiple-choice to measure student’s concept mastery, our study using the same method and present this method in concept game so that student won’t feel boring and tiring during this assessment. Our study observe each student’s feedback and their concept mastery by using game element to display concept assessment, and analyze is using concept game assessment can shorten student’s test time and improve student learning concept knowledge after assessment, the result shows that when student using concept game assessment they can know their concept mastery immediately by seeing process bar present as their life so the test time will be shorten, and student’s concept knowledge was improved after concept game assessment. Student’s feedback shows that they prefer concept game assessment because they can measure their concept mastery during the concept game assessment; this study shows that adding game element in concept assessment can improve student’s concept mastery and shorten the test time student took.</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="33172">
                <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="33173">
                <text>https://online-journals.org/index.php/i-jim/article/view/12057</text>
              </elementText>
              <elementText elementTextId="33174">
                <text>10.3991/ijim.v14i06.12057</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="33175">
                <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="33176">
                <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="33177">
                <text>https://online-journals.org/index.php/i-jim/article/view/12057/6873</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="33178">
                <text>Copyright (c) 2020 Chien-Hung Lai</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="33179">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 06 (2020); pp. 159-170</text>
              </elementText>
              <elementText elementTextId="33180">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="33181">
                <text>Concept assessment</text>
              </elementText>
              <elementText elementTextId="33182">
                <text>concept game assessment</text>
              </elementText>
              <elementText elementTextId="33183">
                <text>SPRT</text>
              </elementText>
              <elementText elementTextId="33184">
                <text>concept mastery.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="33185">
                <text>Applying Concept Map to Game-Base Concept Assessment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="33186">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="33187">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="33188">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1758" 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="36696">
                <text>Jurisch, Matthias Heinrich Friedrich</text>
              </elementText>
              <elementText elementTextId="36697">
                <text>Böhm, Stephan</text>
              </elementText>
              <elementText elementTextId="36698">
                <text>James-Schulz, Toby</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="36699">
                <text>2020-09-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36700">
                <text>Mobile enterprise applications (apps) are developed in dynamic and complex environments. Hardware characteristics, operating systems and development tools are constantly changing. In larger institutions, comprehensive corporate guidelines and requirements have to be followed. In addition, larger enterprises often develop numerous apps and lack an overview of development projects. Because of the size of such companies, a comprehensive direct information exchange between developers is often not practicable. In this situation, IT support is necessary, for example to prevent unnecessary duplication of work in the development of software artifacts such as user stories, app screen designs or code features within the company. One approach to overcome these challenges is to support reusing results from previous projects by building systems to organize and analyse the knowledge base of enterprise app development projects. For such systems an automatic categorization of artifacts is required. In this work we propose using a machine learning approach to categorize user stories. The approach is evaluated on a set of user stories from real-world mobile enterprise application development projects. The results are promising and suggest that machine learning approaches can be beneficially applied to user story classification in large companies.</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="36701">
                <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="36702">
                <text>https://online-journals.org/index.php/i-jim/article/view/15263</text>
              </elementText>
              <elementText elementTextId="36703">
                <text>10.3991/ijim.v14i15.15263</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36704">
                <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="36705">
                <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="36706">
                <text>https://online-journals.org/index.php/i-jim/article/view/15263/7759</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36707">
                <text>Copyright (c) 2020 Matthias Heinrich Friedrich Jurisch, Stephan Böhm, Toby James-Schulz</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="36708">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 15 (2020); pp. 81-94</text>
              </elementText>
              <elementText elementTextId="36709">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36710">
                <text>Mobile enterprise applications</text>
              </elementText>
              <elementText elementTextId="36711">
                <text>Text classification</text>
              </elementText>
              <elementText elementTextId="36712">
                <text>User stories</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36713">
                <text>Applying Machine Learning for Automatic User Story Categorization in Mobile Enterprises Application Development</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36714">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="36715">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="36716">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2037" 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="43072">
                <text>Ahmed, Shaymaa Taha</text>
              </elementText>
              <elementText elementTextId="43073">
                <text>Kadhim, Qusay Kanaan</text>
              </elementText>
              <elementText elementTextId="43074">
                <text>Alsultani, Hamid Sadeq Mahdi</text>
              </elementText>
              <elementText elementTextId="43075">
                <text>abd almahdy, Widyan Salman</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="43076">
                <text>2021-07-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="43077">
                <text> This paper researches the evolution process of what is called two-factor authentication technique and its adaptation related to the educational system through the Internet. This technique is a measure of security employed, particularly in scopes which have valuable information like bank services. It witnesses developments so far as today, in parallel with the developments occurring in technology. Since this technique consists of two phases, the security is going to be developed. Today, bank services, devices using the Internet of things, tickets of public transportation and lots of other scopes are utilized. In the information field, the researchers and scientists always update the techniques of two-factor authentication to resist the attacks related to security. Last years, the researchers studied novel technologies like behavioral biometric or biometrics. The training through the Internet may become much more useful than going to someplace to study a specific course. Mostly, the participants in the trainings through the Internet get many certificates for success, participation, etc. The principal problem is how to certify the truthiness of the participant who desires to get the certification. In this paper, and by researching the techniques of two-factor authentication, the Mimic Control Method with Sound Intensity (MCMSI) is proposed to be used for the training through the Internet.</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="43078">
                <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="43079">
                <text>https://online-journals.org/index.php/i-jim/article/view/23227</text>
              </elementText>
              <elementText elementTextId="43080">
                <text>10.3991/ijim.v15i13.23227</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="43081">
                <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="43082">
                <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="43083">
                <text>https://online-journals.org/index.php/i-jim/article/view/23227/9551</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="43084">
                <text>Copyright (c) 2021 qusay kadhim</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="43085">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 15 No. 13 (2021); pp. 162-171</text>
              </elementText>
              <elementText elementTextId="43086">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="43087">
                <text>Applying the MCMSI for Online Educational Systems Using the Two-Factor Authentication</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="43088">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="43089">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="43090">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="867" 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="16994">
                <text>Wong, Chui-Yin</text>
              </elementText>
              <elementText elementTextId="16995">
                <text>Khong, Chee Weng</text>
              </elementText>
              <elementText elementTextId="16996">
                <text>Thwaites, Harold</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="16997">
                <text>2008-09-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16998">
                <text>The advancement of mobile communication technologies has created a new form of social network for communities to communicate and share similar interests via the mobile platform. Given the fact that Malaysia is a fast-paced developing nation with a relatively low computer-Internet penetration, and high mobile network growth, there are desirable needs for disabled communities to leverage a mobile social network to enhance relationships for better communication in their daily lives. We designed DHearT, a mobile social network for hearing impaired users in Malaysia to bridge the communication gap between the deaf and hearing groups. This paper illustrates and discusses the user interface design process model with its design methods and human factors techniques for a mobile community project for the deaf, namely DHearT.</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="16999">
                <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="17000">
                <text>https://online-journals.org/index.php/i-jim/article/view/669</text>
              </elementText>
              <elementText elementTextId="17001">
                <text>10.3991/ijim.v2i4.669</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17002">
                <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="17003">
                <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="17004">
                <text>https://online-journals.org/index.php/i-jim/article/view/669/612</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17005">
                <text>Copyright (c) 2017 Chui-Yin Wong, Chee Weng Khong, Harold Thwaites</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="17006">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 2 No. 4 (2008); pp. 30-37</text>
              </elementText>
              <elementText elementTextId="17007">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17008">
                <text>online community</text>
              </elementText>
              <elementText elementTextId="17009">
                <text>mobile</text>
              </elementText>
              <elementText elementTextId="17010">
                <text>deaf</text>
              </elementText>
              <elementText elementTextId="17011">
                <text>design process model</text>
              </elementText>
              <elementText elementTextId="17012">
                <text>design methods</text>
              </elementText>
              <elementText elementTextId="17013">
                <text>human factors techniques</text>
              </elementText>
              <elementText elementTextId="17014">
                <text>interface design</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17015">
                <text>Applying User Interface Design Process Model for a Mobile Community Project for the Deaf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17016">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="17017">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="21" public="1" featured="0">
    <collection collectionId="5">
      <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="7">
                  <text>CLAWS Journal</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="45">
              <name>Publisher</name>
              <description>An entity responsible for making the resource available</description>
              <elementTextContainer>
                <elementText elementTextId="1982">
                  <text>Centre for Land Warfare Studies, New Delhi, India</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="44">
              <name>Language</name>
              <description>A language of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1983">
                  <text>English</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="379">
                <text>Singh, A.K.</text>
              </elementText>
              <elementText elementTextId="380">
                <text>Chandrashekhar, R.</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="381">
                <text>2020-06-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="382">
                <text>The announcement by the Prime Minister, Narendra Modi in his Independence Day address to the nation of Government's intent to appoint a Chief of Defence Staff (CDS) marked the gamechanger event that the country was to embark upon. The subsequent appointment, in December 2019,2 of General Bipin Rawat, to the newly created appointment as its first incumbent and the simultaneous creation of a Department of Military Affairs as a separate vertical within the Ministry of Defence with the CDS as its ex-officio Secretary are each and together tectonic shifts that have moved the balance in civil-military relations to a new normal. It has also disruptively altered the entire edifice of the structure of decision-making relating to matters of the military.</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="383">
                <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="384">
                <text>https://ojs.indrastra.com/index.php/clawsjournal/article/view/52</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="385">
                <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="386">
                <text>Centre For Land Warfare Studies (CLAWS), New Delhi, India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="387">
                <text>https://ojs.indrastra.com/index.php/clawsjournal/article/view/52/54</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="388">
                <text>Copyright (c) 2020 Center For Land Warfare Studies (CLAWS), New Delhi, India</text>
              </elementText>
              <elementText elementTextId="389">
                <text>https://ojs.indrastra.com/index.php/clawsjournal/copyright-transfer-form</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="390">
                <text>CLAWS Journal; Vol. 13 No. 1 (2020): Summer 2020; 1-18</text>
              </elementText>
              <elementText elementTextId="391">
                <text>2319-5177</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="392">
                <text>Military Affairs</text>
              </elementText>
              <elementText elementTextId="393">
                <text>India</text>
              </elementText>
              <elementText elementTextId="394">
                <text>South Asia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="395">
                <text>Appointment of Chief of Defence Staff and Creation of the Department of Military Affairs: A Gamechanger</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="396">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="397">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="398">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1271" 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="25587">
                <text>Rosas, João</text>
              </elementText>
              <elementText elementTextId="25588">
                <text>Brito, Vasco</text>
              </elementText>
              <elementText elementTextId="25589">
                <text>Palma, Luis Brito</text>
              </elementText>
              <elementText elementTextId="25590">
                <text>Barata, Jose</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="25591">
                <text>2017-07-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25592">
                <text>Enterprises are adopting the Internet of Things paradigm as a strategy to improve competitiveness. But enterprises also need to rely on their legacy systems, which are of vital importance to them and normally difficult to reconfigure or modify, their mere replacement being usually not affordable. These systems constitute, therefore, barriers to agility and competitiveness, raising the need to develop cost-effective ways for IoT adaptation. An approach for adapting legacy manufacturing systems into the IoT realm is proposed in this research. The methodology is twofold: an adaptation board is firstly designed to provide IoT connectivity, allowing to remotely invoke the “legacy” functionality as services. Then, the board itself can leverage the legacy system by developing additional functionalities inside it, as the update process is usually triggered by the need of new functionality from these systems. An experiment, which consists of adapting to IoT a small distribution line that is controlled by an aged Programmable Logic Controller, is developed to illustrate how straightforward, affordable and cost effective the adaptation approach is, allowing to holistically achieve a new system with more sophisticated functionality.</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="25593">
                <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="25594">
                <text>https://online-journals.org/index.php/i-jim/article/view/7073</text>
              </elementText>
              <elementText elementTextId="25595">
                <text>10.3991/ijim.v11i5.7073</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25596">
                <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="25597">
                <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="25598">
                <text>https://online-journals.org/index.php/i-jim/article/view/7073/4534</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25599">
                <text>Copyright (c) 2017 João Rosas, Vasco Brito, Luis Brito Palma, Jose Barata</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="25600">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 11 No. 5 (2017); pp. 91-104</text>
              </elementText>
              <elementText elementTextId="25601">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25602">
                <text>Internet of Things</text>
              </elementText>
              <elementText elementTextId="25603">
                <text>Legacy Systems</text>
              </elementText>
              <elementText elementTextId="25604">
                <text>Manufacturing Systems</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25605">
                <text>Approach to Adapt a Legacy Manufacturing System Into the IoT Paradigm</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25606">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="25607">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1706" 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="35522">
                <text>Kurni, Muralidhar</text>
              </elementText>
              <elementText elementTextId="35523">
                <text>K, Madhavi</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="35524">
                <text>2020-06-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35525">
                <text>Mobile Ad hoc Networks (MANETs) are getting essential to wireless communications because of the growing popularity of mobile devices. However, mobile devices face several challenges in their resources (eg., battery life, storage, and bandwidth) and communication (e.g., mobility and, security). Limited resources considerably impede the improvement of service qualities. MCC permits resources in cloud computing platforms to be used to overcome the dearth of native resources in mobile devices. However, this hinders a mobile user from taking part in a cloud computing service if a connection to the cloud computing platform is both unobtainable or too dear to afford. Therefore, an initial solution will be to use resources from nearby devices instantly. Such a paradigm is known as mobile ad hoc cloud computing where each mobile device can use the services and resources of its neighbor devices. This paper shortly explains the contributions done by us to overcome the three vital operational limitations of mobile devices namely connectivity, storage and, processing capability through the Mobile Ad Hoc Cloud Computing Paradigm. The potential promise of the proposed approaches is evaluated through simulations. Our proposals, taken together intend to increase the operational efficiency of MANETs.</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="35526">
                <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="35527">
                <text>https://online-journals.org/index.php/i-jim/article/view/14103</text>
              </elementText>
              <elementText elementTextId="35528">
                <text>10.3991/ijim.v14i09.14103</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35529">
                <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="35530">
                <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="35531">
                <text>https://online-journals.org/index.php/i-jim/article/view/14103/7179</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35532">
                <text>Copyright (c) 2020 Muralidhar Kurni, Madhavi K</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="35533">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 09 (2020); pp. 153-165</text>
              </elementText>
              <elementText elementTextId="35534">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35535">
                <text>MANETs</text>
              </elementText>
              <elementText elementTextId="35536">
                <text>Mobile Ad Hoc Cloud Computing</text>
              </elementText>
              <elementText elementTextId="35537">
                <text>DaaS</text>
              </elementText>
              <elementText elementTextId="35538">
                <text>ASaaS</text>
              </elementText>
              <elementText elementTextId="35539">
                <text>AhCaaS</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35540">
                <text>Approaches to Address the Operational Limitations of MANETs through Ad Hoc Mobile Cloud Computing Paradigm</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35541">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="35542">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="35543">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
