<?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=193" accessDate="2026-05-14T06:41:27+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>193</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1656" 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="34360">
                <text>Mohd Zukhi, Mohd Zhafri</text>
              </elementText>
              <elementText elementTextId="34361">
                <text>Hussain, Azham</text>
              </elementText>
              <elementText elementTextId="34362">
                <text>Husni, Husniza</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="34363">
                <text>2020-04-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34364">
                <text>The usage of emoticon in computer-mediated communication has been growing rapidly among users, especially in social media. Emoticon has been used to express feelings, emotions, gestures, actions and places. Despite the growing number of emoticon users around the world, study on the cultural elements of the emoticon is still lacking. This research aims to propose a model for the development of Culturicon, which is Cultural-Based Emoticon. In doing so, a verification process must be done to the proposed model to ensure that the model is well verified. Expert review method was used for the verification method. Experts from the field of Human-Computer Interaction, User Experience and cultural study especially the academicians were chosen. In addition, application developer and graphic designer also were chosen as expert from the industry. The experts were approached by email and performed the verification by answering online questionnaire provided. The result obtained from these experts were analyzed and amendment were made based from the comments and suggestions. Results showed that 91% experts agreed the connections and flows of all components in the proposed model are logical and readable. Expert verification is important to ensure that the model is being develop correctly. By having this model, it can aid designer and developer in designing meaningful and effective Culturicon.</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="34365">
                <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="34366">
                <text>https://online-journals.org/index.php/i-jim/article/view/13313</text>
              </elementText>
              <elementText elementTextId="34367">
                <text>10.3991/ijim.v14i05.13313</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34368">
                <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="34369">
                <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="34370">
                <text>https://online-journals.org/index.php/i-jim/article/view/13313/6761</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34371">
                <text>Copyright (c) 2020 Mohd Zhafri Mohd Zukhi, Azham Hussain, Husniza Husni</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="34372">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 05 (2020); pp. 16-31</text>
              </elementText>
              <elementText elementTextId="34373">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34374">
                <text>emoticon</text>
              </elementText>
              <elementText elementTextId="34375">
                <text>culture</text>
              </elementText>
              <elementText elementTextId="34376">
                <text>expert review</text>
              </elementText>
              <elementText elementTextId="34377">
                <text>human-computer interaction</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34378">
                <text>Culturicon Design Model for Social Mobile Application</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34379">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34380">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34381">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1655" 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="34339">
                <text>Nordin, Noradila</text>
              </elementText>
              <elementText elementTextId="34340">
                <text>Mohd Fauzi, Nurul Husna</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="34341">
                <text>2020-04-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34342">
                <text>Attendance marking in a classroom is one of the methods used to track the student’s presence in the lecture. The conventional method that is being enforced has shown to be vulnerable, inaccurate and time-consuming especially in a large classroom. It is difficult to identify absentees and proxy attendees based on the conventional attendance marking method. In order to overcome the challenges faced in the conventional method, a web-based mobile attendance system with facial recognition feature is proposed. It incorporated the existing mobile devices with a camera and the face recognition system to allow the attendance system to be used in classrooms automatically and efficiently with minor implementation requirements. The system prototype received positive responses from the volunteers who tested the system to replace the conventional attendance marking.</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="34343">
                <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="34344">
                <text>https://online-journals.org/index.php/i-jim/article/view/13311</text>
              </elementText>
              <elementText elementTextId="34345">
                <text>10.3991/ijim.v14i05.13311</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34346">
                <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="34347">
                <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="34348">
                <text>https://online-journals.org/index.php/i-jim/article/view/13311/6775</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34349">
                <text>Copyright (c) 2020 Noradila Nordin, Nurul Husna Mohd Fauzi</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="34350">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 05 (2020); pp. 193-202</text>
              </elementText>
              <elementText elementTextId="34351">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34352">
                <text>mobile attendance</text>
              </elementText>
              <elementText elementTextId="34353">
                <text>facial recognition</text>
              </elementText>
              <elementText elementTextId="34354">
                <text>identification</text>
              </elementText>
              <elementText elementTextId="34355">
                <text>attendance management.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34356">
                <text>A Web-Based Mobile Attendance System with Facial Recognition Feature</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34357">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34358">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34359">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1654" 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="34317">
                <text>Habaebi, Mohamed Hadi</text>
              </elementText>
              <elementText elementTextId="34318">
                <text>Omar Khamis, Rashid</text>
              </elementText>
              <elementText elementTextId="34319">
                <text>Islam, Md Rafiqul</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="34320">
                <text>2020-04-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34321">
                <text>Radio Frequency Identification (RFID) is an information exchange technology based on RF communication. It provides solution to track and localize mobile objects in the indoor environment. Localization of mobile objects in an indoor environment garnered a significant attention due to the variety of applications needing higher degree of localization accuracy. RSS-based localization techniques are the major tools for tracking applications due to their simplicity. In this paper, a trilateration method for indoor localization is proposed. This method provides a solution for the drone tracking problem by collecting the RSS values between RFID tagged drone and reader, and estimate its location. The localization method is implemented in MATLAB by multiple readers; 4 RFID readers and 8 RFID readers. The performance of the localization method is also compared with other RFID localization previously reported in the literature. The simulation results in the case of 8 RFID readers demonstrate more accurate results than 4 RFID readers by minimizing the localization error from 0.84606 to 0.40079m. The results also indicate an improved localization performance of tracking a tagged drone in indoor environment by 42.8% when 8RFID readers are placed in the localization area.</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="34322">
                <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="34323">
                <text>https://online-journals.org/index.php/i-jim/article/view/13309</text>
              </elementText>
              <elementText elementTextId="34324">
                <text>10.3991/ijim.v14i05.13309</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34325">
                <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="34326">
                <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="34327">
                <text>https://online-journals.org/index.php/i-jim/article/view/13309/6757</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34328">
                <text>Copyright (c) 2020 Mohamed Hadi Habaebi, Rashid Khamis Omar, Md Rafiqul Islam</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="34329">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 05 (2020); pp. 4-15</text>
              </elementText>
              <elementText elementTextId="34330">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34331">
                <text>RFID</text>
              </elementText>
              <elementText elementTextId="34332">
                <text>Indoor Localization</text>
              </elementText>
              <elementText elementTextId="34333">
                <text>Trilateration</text>
              </elementText>
              <elementText elementTextId="34334">
                <text>Received Signal Strength.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34335">
                <text>Mobile Drone Localization in Indoor Environment Based on Passive RFID</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34336">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34337">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34338">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1653" 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="34295">
                <text>Emmanuel, Gahizi</text>
              </elementText>
              <elementText elementTextId="34296">
                <text>Emanuel, Andi Wahju Rahardjo</text>
              </elementText>
              <elementText elementTextId="34297">
                <text>Setyohadi, Djoko Budiyanto</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="34298">
                <text>2020-07-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34299">
                <text>Community health workers (CHWs) are the basis of public health services that aim to connect the gap between public health and the human service system. This gap can be completely bridged by navigating the health and human service systems and educating communities on disease prevention. Unfortunately, the way of sharing, accessing information, and delivering health services is still non-digitalized in Rwanda. Community Health workers use a manual system in their daily activities, which is prone to error and falsification. Moreover, these people selected to perform these activities often do not have adequate knowledge about diseases and health systems since they are not professional health workers. To address the above problem, we designed a prototype mobile application to enable these workers to automatically submit reports, transfer knowledge, share information, and receive training from professionals.  The design process followed a User-Centered Design approach to meet the users’ requirements. The evaluation of the design showed that 91.7% of the CHWs agreed with the designed application prototype.  This finding shows that CHWs has an interest in using the mobile application in their work. Using the mobile application will help CHWs to improve data collection, the reporting process, and ease of receiving training.</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="34300">
                <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="34301">
                <text>https://online-journals.org/index.php/i-jim/article/view/13307</text>
              </elementText>
              <elementText elementTextId="34302">
                <text>10.3991/ijim.v14i11.13307</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34303">
                <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="34304">
                <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="34305">
                <text>https://online-journals.org/index.php/i-jim/article/view/13307/7407</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34306">
                <text>Copyright (c) 2020 Gahizi Emmanuel, Andi Wahju Rahardjo Emanuel, Djoko Budiyanto Setyohadi</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="34307">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 11 (2020); pp. 271-279</text>
              </elementText>
              <elementText elementTextId="34308">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34309">
                <text>Health Systems</text>
              </elementText>
              <elementText elementTextId="34310">
                <text>Mobile application</text>
              </elementText>
              <elementText elementTextId="34311">
                <text>community health workers</text>
              </elementText>
              <elementText elementTextId="34312">
                <text>User-Centered Design</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34313">
                <text>Design of Mobile Application for Community Health Workers: A Case Study in Rwanda</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34314">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34315">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34316">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1652" 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="34272">
                <text>Alsaqqa, Samar</text>
              </elementText>
              <elementText elementTextId="34273">
                <text>Sawalha, Samer</text>
              </elementText>
              <elementText elementTextId="34274">
                <text>Abdel-Nabi, Heba</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="34275">
                <text>2020-07-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34276">
                <text>Software engineering is a discipline that undergone many improvements that aims to keep up with the new advancements in technologies and the modern business requirements through developing effective approaches to reach the final software product, agile software development is one of these successful approaches. Agile software development is a lightweight approach that was proposed to overcome the convolutional development methods’ limitations and to reduce the overhead and the cost while providing flexibility to adopt the changes in requirements at any stage, this is done by managing the tasks and their coordination through a certain set of values and principles.In this work, a comprehensive review that outlines the main agile values and principles, and states the key differences that distinguish agile methods over the traditional ones are presented. Then a discussion of the most popular agile methodologies; their life cycles, their roles, and their advantages and disadvantages are outlined. The recent state of art trends that adopts agile development especially in cloud computing, big data, and coordination are also explored. And finally, this work highlights how to choose the best suitable agile methodology that must be selected according to the task at hand, how sensitive the product is and the organization structure.</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="34277">
                <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="34278">
                <text>https://online-journals.org/index.php/i-jim/article/view/13269</text>
              </elementText>
              <elementText elementTextId="34279">
                <text>10.3991/ijim.v14i11.13269</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34280">
                <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="34281">
                <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="34282">
                <text>https://online-journals.org/index.php/i-jim/article/view/13269/7405</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34283">
                <text>Copyright (c) 2020 SAMAR ALSAQQA, Samer Sawalha, Heba Abdel-Nabi</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="34284">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 11 (2020); pp. 246-270</text>
              </elementText>
              <elementText elementTextId="34285">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34286">
                <text>Agile Development</text>
              </elementText>
              <elementText elementTextId="34287">
                <text>Agile Methods</text>
              </elementText>
              <elementText elementTextId="34288">
                <text>Big Data</text>
              </elementText>
              <elementText elementTextId="34289">
                <text>Coordination</text>
              </elementText>
              <elementText elementTextId="34290">
                <text>Cloud Computing.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34291">
                <text>Agile Software Development: Methodologies and Trends</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34292">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34293">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34294">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1651" public="1" featured="0">
    <collection collectionId="36">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34248">
                <text>Arif, Teuku Yuliar</text>
              </elementText>
              <elementText elementTextId="34249">
                <text>Munandar, Munandar</text>
              </elementText>
              <elementText elementTextId="34250">
                <text>Adriman, Ramzi</text>
              </elementText>
              <elementText elementTextId="34251">
                <text>Munadi, Rizal</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34252">
                <text>2020-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34253">
                <text>The wireless mesh network (WMN) is a future network technology that develops single-hop wireless local area networks (WLANs) into multi-hop wireless mesh networks, based on the IEEE 802.11s standard. However, this development still presents many challenges, such as determining the best route between sources and destinations, especially taking into account the use of the medium access control (MAC) and physical (PHY) layers of IEEE 802.11n/ac. Some papers have proposed rate adaptation algorithms particularly for single-hop networks; however, these only focused on mechanisms to find data rates suitable for channel conditions. In IEEE 802.11s WMNs, the design of the rate adaptation algorithm is more challenging. Besides considering the problem of channel quality and optimal throughput, it is necessary to also consider the problem of collision and the best route. It is important to take collision into account because the collision probability in multi-hop mesh networks is higher than that in single-hop networks and can lead to a lower throughput. Rate adaptation algorithms for IEEE 802.11s WMNs have been proposed in other papers, but they also do not consider the use of the MAC and PHY layers of IEEE 802.11n/ac. In this paper, we propose the collision-aware rate adaptation for optimal high-throughput (CARA-OHT) algorithm for WMN IEEE 802.11s. An evaluation through the extensive use of a network NS-3 simulator shows that the proposed algorithm exhibits a higher throughput than previously developed algorithms.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34254">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="34255">
                <text>https://online-journals.org/index.php/i-jim/article/view/13245</text>
              </elementText>
              <elementText elementTextId="34256">
                <text>10.3991/ijim.v14i13.13245</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34257">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="34258">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="34259">
                <text>https://online-journals.org/index.php/i-jim/article/view/13245/7677</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34260">
                <text>Copyright (c) 2020 Munandar Munandar, Teuku Yuliar Arif, Ramzi Adriman, Rizal Munadi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="34261">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 13 (2020); pp. 172-199</text>
              </elementText>
              <elementText elementTextId="34262">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34263">
                <text>CARA-OHT</text>
              </elementText>
              <elementText elementTextId="34264">
                <text>Rate Adaptation</text>
              </elementText>
              <elementText elementTextId="34265">
                <text>Collision-aware</text>
              </elementText>
              <elementText elementTextId="34266">
                <text>Optimal High Throughput</text>
              </elementText>
              <elementText elementTextId="34267">
                <text>802.11s WMN</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34268">
                <text>CARA-OHT: Collision-Aware Rate Adaptation for Optimal High-Throughput in IEEE 802.11s Wireless Mesh Networks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34269">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34270">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34271">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1650" 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="34224">
                <text>Mohammed, Bahaa Kareem</text>
              </elementText>
              <elementText elementTextId="34225">
                <text>alsaidi, Saif ali</text>
              </elementText>
              <elementText elementTextId="34226">
                <text>Chisab, Raad Farhood</text>
              </elementText>
              <elementText elementTextId="34227">
                <text>Alrikabi, Haider</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="34228">
                <text>2020-03-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34229">
                <text>It is a well-known fact that the forthcoming names are distinctively different: interference range, career sense, and transmission. The given paper reveals the underlying study of disengagement of a request to send (RTS)/ clear to send (CTS) dialog. It was basically adopted under the influence of both; the presence of distributed coordination function of IEEE 802.11 and a sub-layer protocol which is called media access control (MAC) protocol. The demonstration was seen when applying a type of traffic flows such as Constant Bit Rate (CBR), Transmission Control Protocol (TCP), and besides User Datagram Protocol (UDP). When these are applied the output performance in term of throughput shows a very linear topology configuration of the network. To sum up, a new RTS /CTS mechanism was proposed based on the results obtained from the above suggestions. The detailing for the new mechanism showed that a terminal node will be responsible for deciding if it is authorized to use an RTS/CTS protocol dialog to send one of its packets or not. Needless to say, this process will be dynamic in nature.</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="34230">
                <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="34231">
                <text>https://online-journals.org/index.php/i-jim/article/view/13243</text>
              </elementText>
              <elementText elementTextId="34232">
                <text>10.3991/ijim.v14i04.13243</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34233">
                <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="34234">
                <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="34235">
                <text>https://online-journals.org/index.php/i-jim/article/view/13243/6649</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34236">
                <text>Copyright (c) 2020 Bahaa Kareem Mohammed, Saif ali alsaidi, Raad Farhood Chisab, Haider Alrikabi</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="34237">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 04 (2020); pp. 204-211</text>
              </elementText>
              <elementText elementTextId="34238">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34239">
                <text>Wireless sensor network</text>
              </elementText>
              <elementText elementTextId="34240">
                <text>RTS</text>
              </elementText>
              <elementText elementTextId="34241">
                <text>CTS</text>
              </elementText>
              <elementText elementTextId="34242">
                <text>UDP</text>
              </elementText>
              <elementText elementTextId="34243">
                <text>TCP.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34244">
                <text>Efficient RTS and CTS Mechanism Which Save Time and System Resources</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34245">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34246">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34247">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1649" 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="34199">
                <text>Indrabayu, Indrabayu</text>
              </elementText>
              <elementText elementTextId="34200">
                <text>Nurtanio, Ingrid</text>
              </elementText>
              <elementText elementTextId="34201">
                <text>Areni, Intan Sari</text>
              </elementText>
              <elementText elementTextId="34202">
                <text>Bugiwati, Sri R.A</text>
              </elementText>
              <elementText elementTextId="34203">
                <text>Bustamin, Anugrayani</text>
              </elementText>
              <elementText elementTextId="34204">
                <text>Rahmatullah, Muhammad</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="34205">
                <text>2020-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34206">
                <text>This research focuses on developing an Android-based cattle identification system that is applicable and easy to use. This system uses a Scale Invariant Feature Transform (SIFT) algorithm to extract features from the muzzle images, and Random Sample Consensus (RANSAC) algorithm to eliminate features incompatibility. The system is experimented with four threshold values, i.e. 10, 15, 20, and 30 using a total data of 460 muzzle images.  In the first experiment, 3 images from each individual are used in the training stage and 2 images are used as the data test. In the second experiment, 5 images from each cattle are used in the training stage and 5 images are used as the data test. Data used in training stage are 244 images and in testing stage is 816 images. From the experiment, the highest accuracy rate is 98.1% with threshold values of 15 and 20. The execution time is also calculated to measure the processing time of the system. The average time taken to store an image to the database is 1.3 seconds. The main contribution of this research is technology implementation and more portable muzzle identification for local cattle in Makassar.</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="34207">
                <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="34208">
                <text>https://online-journals.org/index.php/i-jim/article/view/13237</text>
              </elementText>
              <elementText elementTextId="34209">
                <text>10.3991/ijim.v14i13.13237</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34210">
                <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="34211">
                <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="34212">
                <text>https://online-journals.org/index.php/i-jim/article/view/13237/7671</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34213">
                <text>Copyright (c) 2020 Indrabayu Indrabayu, Ingrid Nurtanio, Intan Sari Areni, Sri R.A Bugiwati, Anugrayani Bustamin, Muhammad Rahmatullah</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="34214">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 13 (2020); pp. 134-149</text>
              </elementText>
              <elementText elementTextId="34215">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34216">
                <text>cattle identification</text>
              </elementText>
              <elementText elementTextId="34217">
                <text>SIFT</text>
              </elementText>
              <elementText elementTextId="34218">
                <text>RANSAC</text>
              </elementText>
              <elementText elementTextId="34219">
                <text>muzzle pattern</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34220">
                <text>A Portable Cattle Tagging Based on Muzzle Pattern</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34221">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34222">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34223">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1648" 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="34174">
                <text>Mwandosya, Godfrey Isaac</text>
              </elementText>
              <elementText elementTextId="34175">
                <text>Suero Montero, Calkin</text>
              </elementText>
              <elementText elementTextId="34176">
                <text>Mbise, Esther Rossiner</text>
              </elementText>
              <elementText elementTextId="34177">
                <text>Oyelere, Solomon Sunday</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="34178">
                <text>2020-08-28</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34179">
                <text>This study reports the demonstration of the effectiveness of a mobile education tool (MET) that was co-designed and developed at the College of Business Education (CBE) in Tanzania by a team of teachers, researchers, and a developer using the Design Science Research (DSR) methodology. The demonstration of the CBEMET Prototype as an artifact was done to 30 teachers who had participated in the co-designing of the prototype phase, 3 members of CBE management team and 20 students in Bachelor II degree program as the observers and representative of those who will use the prototype at a later stage. Different sets of questionnaires were administered to the teachers, the members of the management team and the students. The demonstration confirmed that it is easy to access the prototype, share learning contents, and provide education through mobile devices. Nonetheless, teaching materials prepared for testing the prototype were insufficient and thus needed improvement. Furthermore, teachers and observers proposed for more options to the prototype such as the inclusion of timetables, alerts of events like examination dates, and news on innovation activities. The feedback from the participants has thus been considered to reduce errors in the usage of the prototype before its final deployment.</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="34180">
                <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="34181">
                <text>https://online-journals.org/index.php/i-jim/article/view/13195</text>
              </elementText>
              <elementText elementTextId="34182">
                <text>10.3991/ijim.v14i14.13195</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34183">
                <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="34184">
                <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="34185">
                <text>https://online-journals.org/index.php/i-jim/article/view/13195/7747</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34186">
                <text>Copyright (c) 2020 Godfrey Isaac Mwandosya, Calkin Suero Montero, Solomon Sunday Oyelere, Esther Rossiner Mbise</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="34187">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 14 (2020); pp. 31-51</text>
              </elementText>
              <elementText elementTextId="34188">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34189">
                <text>Mobile education tool</text>
              </elementText>
              <elementText elementTextId="34190">
                <text>demonstration</text>
              </elementText>
              <elementText elementTextId="34191">
                <text>evaluation</text>
              </elementText>
              <elementText elementTextId="34192">
                <text>Design science research</text>
              </elementText>
              <elementText elementTextId="34193">
                <text>CBE</text>
              </elementText>
              <elementText elementTextId="34194">
                <text>Tanzania</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34195">
                <text>Demonstration of a Mobile Education Artifact in a Tanzania’s Higher Education Institution</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34196">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34197">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34198">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1647" 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="34149">
                <text>M. Rafiq, Karmila Rafiqah</text>
              </elementText>
              <elementText elementTextId="34150">
                <text>Hashim, Harwati</text>
              </elementText>
              <elementText elementTextId="34151">
                <text>Md Yunus, Melor</text>
              </elementText>
              <elementText elementTextId="34152">
                <text>Norman, Helmi</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="34153">
                <text>2020-05-20</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34154">
                <text>Due to the rise of the digital era, various industries demand employees with a proficient communicative English skills, but many are still not up to par with the demands. One solution for this is to provide communicative English trainings for employees, especially support staffs, yet face-to-face trainings have many limitations, which can be overcome through mobile learning. Due to the fact that mobile learning can be accessed anytime and anywhere by anyone, the Massive Online Open Courses (MOOC) is one of the platforms that can be used to curb the issue. This paper aimed to identify the perceptions of support staffs towards using ‘ìSPEAK: English for the Workplace’ in MOOC. A total of 30 respondents were selected through purposive sampling and a survey through a 4-point Likert scale questionnaire was given out. The main findings showed that overall, the support staffs have a positive attitude towards using ìSPEAK. Nevertheless, half of them were unsure of the reliability of the sources available in the course. However, the findings of this study implied that ìSPEAK could be one of the training alternatives for support staffs to improve and increase their communicative ability. Future research can look into designing and developing various modules of communicative English in various mobile learning platforms, which could cater to different levels of proficiency of learners.</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="34155">
                <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="34156">
                <text>https://online-journals.org/index.php/i-jim/article/view/13185</text>
              </elementText>
              <elementText elementTextId="34157">
                <text>10.3991/ijim.v14i08.13185</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34158">
                <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="34159">
                <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="34160">
                <text>https://online-journals.org/index.php/i-jim/article/view/13185/7043</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34161">
                <text>Copyright (c) 2020 Karmila Rafiqah M. Rafiq, Harwati Hashim, Melor Md Yunus, Helmi Norman</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="34162">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 08 (2020); pp. 19-31</text>
              </elementText>
              <elementText elementTextId="34163">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34164">
                <text>Communicative English</text>
              </elementText>
              <elementText elementTextId="34165">
                <text>English for the Workplace</text>
              </elementText>
              <elementText elementTextId="34166">
                <text>MOOC</text>
              </elementText>
              <elementText elementTextId="34167">
                <text>self-paced learning</text>
              </elementText>
              <elementText elementTextId="34168">
                <text>support staffs</text>
              </elementText>
              <elementText elementTextId="34169">
                <text>technology-enhanced language learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34170">
                <text>ìSPEAK: Using Mobile-Based Online Learning Course to Learn ‘English for the Workplace’</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34171">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34172">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34173">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
