<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://igi.indrastra.com/items?output=omeka-xml&amp;page=216&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-13T20:10:47+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>216</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="945" 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="18604">
                <text>Ramli, Aznarahayu</text>
              </elementText>
              <elementText elementTextId="18605">
                <text>Ismail, Issham</text>
              </elementText>
              <elementText elementTextId="18606">
                <text>MD. Idrus, Rozhan</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="18607">
                <text>2010-07-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18608">
                <text>The purpose of this study is to determine whether learners are willing to transfer learning in this mobile learning environment via SMS.  The reason for this is to measure the effectiveness of the new method used in learning and education especially in distance education field.  For this reason, studentsâ?? responses are gathered which looked at three factors namely learner characteristic, learning design and learning environment. The data are gathered through a survey research design with questionnaires using five-point likert scale. The questionnaires was administered for 105 distance education students from four courses including Bachelor of Science, Bachelor of Arts, Bachelor of Social Science and Bachelor of Management. The Rasch Model Analysis was used to measure these dimensions. Rasch Model is a one-parameter logistic model within item response theory (IRT) whereby the amount of a given latent trait in a person and the amount of that same latent trait reflected in various items can be estimated independently yet still compared explicitly to one another.  The result of the study showed that learning transfer occurred and being influenced most by learnerâ??s characteristics especially in term of their motivation as well as their perceive utility/value of the SMS learning to their job and academic performances.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18609">
                <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="18610">
                <text>https://online-journals.org/index.php/i-jim/article/view/1180</text>
              </elementText>
              <elementText elementTextId="18611">
                <text>10.3991/ijim.v4i3.1180</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18612">
                <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="18613">
                <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="18614">
                <text>https://online-journals.org/index.php/i-jim/article/view/1180/1421</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18615">
                <text>Copyright (c) 2017 Aznarahayu Ramli, Issham Ismail, Rozhan MD. Idrus</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="18616">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 4 No. 3 (2010); pp. 30-35</text>
              </elementText>
              <elementText elementTextId="18617">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18618">
                <text>Mobile Learning</text>
              </elementText>
              <elementText elementTextId="18619">
                <text>SMS</text>
              </elementText>
              <elementText elementTextId="18620">
                <text>Distance Education</text>
              </elementText>
              <elementText elementTextId="18621">
                <text>Learning Transfer</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18622">
                <text>Mobile Learning Via SMS Among Distance Learners:  Does Learning Transfer Occur?</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18623">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="18624">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="18625">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1005" 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="19844">
                <text>Scolari, Carlos Alberto</text>
              </elementText>
              <elementText elementTextId="19845">
                <text>Aguado, Juan Miguel</text>
              </elementText>
              <elementText elementTextId="19846">
                <text>Feij, Claudio</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="19847">
                <text>2012-04-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19848">
                <text>The paper is grounded in the idea that a theory of mobile media, like that of any other scientific discourse, must be built on solid conceptual and taxonomical bases. Within this context the paper brings together previous fragmented approaches to studying mobile media, analyses them, and develops a set of definitions and classifications of contents and applications in order to consolidate the construction of a robust mobile media theory. The paper finishes with a reflection on the ongoing mutations of this field and their implications, suggesting that scholars need to rethink the basic concepts behind their theories.</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="19849">
                <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="19850">
                <text>https://online-journals.org/index.php/i-jim/article/view/1880</text>
              </elementText>
              <elementText elementTextId="19851">
                <text>10.3991/ijim.v6i2.1880</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19852">
                <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="19853">
                <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="19854">
                <text>https://online-journals.org/index.php/i-jim/article/view/1880/2179</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19855">
                <text>Copyright (c) 2017 Carlos Alberto Scolari, Juan Miguel Aguado, Claudio Feij</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="19856">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 6 No. 2 (2012); pp. 29-38</text>
              </elementText>
              <elementText elementTextId="19857">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19858">
                <text>mobile media</text>
              </elementText>
              <elementText elementTextId="19859">
                <text>mobile content</text>
              </elementText>
              <elementText elementTextId="19860">
                <text>mobile applications</text>
              </elementText>
              <elementText elementTextId="19861">
                <text>mobile news</text>
              </elementText>
              <elementText elementTextId="19862">
                <text>mobile advertising</text>
              </elementText>
              <elementText elementTextId="19863">
                <text>mobile books</text>
              </elementText>
              <elementText elementTextId="19864">
                <text>mobile music</text>
              </elementText>
              <elementText elementTextId="19865">
                <text>mobile television</text>
              </elementText>
              <elementText elementTextId="19866">
                <text>mobile games</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19867">
                <text>Mobile Media: Towards a Definition and Taxonomy of Contents and Applications</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19868">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="19869">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="19870">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="868" 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="17018">
                <text>Nyberg, Marcus</text>
              </elementText>
              <elementText elementTextId="17019">
                <text>Chincholle, Didier</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="17020">
                <text>2008-09-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17021">
                <text>In order to understand how mobile instant messaging services can fit into the usersâ?? current communication behavior, Ericsson Research performed a qualitative user study in Sweden in May 2007. The results showed that the respondents were positive towards (free of charge) mobile MSN Messenger and perceived it as an ex¬tension of the computer-based version that could be used anywhere. However, although MSN Messenger on the com¬puter definitely was considered as a â??must-haveâ?? application, the mobile version was only perceived as a â??nice-to-haveâ?? application and a complement to text mes¬saging (SMS). Almost one year later, in April 2008, Ericsson Research performed a short qualita¬tive follow-up study with the same set of respondents to un¬derstand if and how the mobile MSN Messenger usage had changed. The results actually revealed that none of the re¬spondents used mobile MSN Messenger anymore as the application no longer was free of charge. On a general level, the study highlights important considera¬tions when intro¬ducing computer-based concepts and Internet services in a mo¬bile environment.</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="17022">
                <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="17023">
                <text>https://online-journals.org/index.php/i-jim/article/view/670</text>
              </elementText>
              <elementText elementTextId="17024">
                <text>10.3991/ijim.v2i4.670</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17025">
                <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="17026">
                <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="17027">
                <text>https://online-journals.org/index.php/i-jim/article/view/670/610</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17028">
                <text>Copyright (c) 2017 Marcus Nyberg, Didier Chincholle</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="17029">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 2 No. 4 (2008); pp. 18-24</text>
              </elementText>
              <elementText elementTextId="17030">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17031">
                <text>User experience</text>
              </elementText>
              <elementText elementTextId="17032">
                <text>mobile phones</text>
              </elementText>
              <elementText elementTextId="17033">
                <text>IM</text>
              </elementText>
              <elementText elementTextId="17034">
                <text>chat</text>
              </elementText>
              <elementText elementTextId="17035">
                <text>text messaging</text>
              </elementText>
              <elementText elementTextId="17036">
                <text>multi-device services</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17037">
                <text>Mobile MSN Messenger: Still a Complement?</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17038">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="17039">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1372" 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="27837">
                <text>Sutopo, Hadi</text>
              </elementText>
              <elementText elementTextId="27838">
                <text>Samosir, Ridha Sefina</text>
              </elementText>
              <elementText elementTextId="27839">
                <text>Gatc, Jullend</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="27840">
                <text>2019-05-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27841">
                <text>This research is intended to evaluate the development of mobile multimedia based stop drug tutorial.  This tutorial as a campaign to stop drugs, that should encourage people’s ability to integrate all information on mobile application. The tutorial focuses on how people understand about drugs and what to do if someone is drugs addicted.  Stopping drug tutorial is created using ADDIE instructional development method, and during the developing stage, it is done using Multimedia Development Life Cycle according to Luther. Subjects of the research are experts in education, visual communication and information technology in the preliminary testing. Evaluation was conducted using the analytic descriptive method on mobile multimedia evaluation method, and interpreted in a narrative way based on the research findings. The evaluation of mobile multimedia application uses combination of multimedia evaluation that is used by educationalist with ISO 9126 that was used by software developer. The research findings show that mobile multimedia stop drugs application can be used with minor revision.</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="27842">
                <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="27843">
                <text>https://online-journals.org/index.php/i-jim/article/view/9436</text>
              </elementText>
              <elementText elementTextId="27844">
                <text>10.3991/ijim.v13i05.9436</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27845">
                <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="27846">
                <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="27847">
                <text>https://online-journals.org/index.php/i-jim/article/view/9436/5680</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27848">
                <text>Copyright (c) 2019 Hadi Sutopo, Ridha Sefina Samosir, Jullend Gatc</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="27849">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 05 (2019); pp. 124-136</text>
              </elementText>
              <elementText elementTextId="27850">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27851">
                <text>drugs</text>
              </elementText>
              <elementText elementTextId="27852">
                <text>evaluation</text>
              </elementText>
              <elementText elementTextId="27853">
                <text>instruction</text>
              </elementText>
              <elementText elementTextId="27854">
                <text>mobile multimedia</text>
              </elementText>
              <elementText elementTextId="27855">
                <text>tutorial</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27856">
                <text>Mobile Multimedia Evaluation: Development of Stop Drugs Tutorial</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27857">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="27858">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="27859">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2160" 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="45988">
                <text>Yafie, Evania</text>
              </elementText>
              <elementText elementTextId="45989">
                <text>Ashari, Zakiah Mohamad</text>
              </elementText>
              <elementText elementTextId="45990">
                <text>Samah, Norazrena Abu</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="45991">
                <text>2022-01-28</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45992">
                <text>The lack of knowledge about parenting has led to several cases of violence against children. Providing training on parenting skills is a possible solution. This study was presented with the aim of knowing the effectiveness of a mobile parenting training program based on ubiquitous learning to improve parenting skills moderated by parental locus of control. This study used a quasi-experimental design with control and experimental groups. Sampling in this study used purposive sampling with the following criteria for parents: 1) Having children aged 3-6 years, 2) Parents experiencing parenting problems, 3) Children experiencing developmental delays, 4) Willing to participate in the training program to completion. The tests used in this study include testing the validity and reliability of the instrument, classical assumption test, homogeneity test, and hypothesis testing using Two Way Anova parametric statistics. The results of this study can be concluded that a mobile parenting training program based on unbiquitous learning moderated by a good parental locus of control can improve parenting skills in parents.</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="45993">
                <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="45994">
                <text>https://online-journals.org/index.php/i-jim/article/view/27301</text>
              </elementText>
              <elementText elementTextId="45995">
                <text>10.3991/ijim.v16i02.27301</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45996">
                <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="45997">
                <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="45998">
                <text>https://online-journals.org/index.php/i-jim/article/view/27301/10633</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45999">
                <text>Copyright (c) 2021 Evania Yafie, Zakiah Mohamad Ashari, Norazrena Abu Samah</text>
              </elementText>
              <elementText elementTextId="46000">
                <text>https://creativecommons.org/licenses/by/4.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="46001">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 16 No. 02 (2022); pp. 42-58</text>
              </elementText>
              <elementText elementTextId="46002">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46003">
                <text>mobile parenting training program</text>
              </elementText>
              <elementText elementTextId="46004">
                <text>ubiquitous learning</text>
              </elementText>
              <elementText elementTextId="46005">
                <text>parenting skills</text>
              </elementText>
              <elementText elementTextId="46006">
                <text>parental locus of control</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46007">
                <text>Mobile Parenting Training Program Based on a Ubiquitous Learning Context to Improve Parenting Skill: The Moderating Role Parental Locus of Control</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46008">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="46009">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="46010">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1027" 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="20299">
                <text>Husni, Emir Mauludi</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="20300">
                <text>2012-10-05</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20301">
                <text>Communication between the near field communication (NFC) devices occurs in a very close distance of less than 10 cm. In the NFC-based payment system, close proximity between devices will increase the security of transactions. The disadvantage is the interaction between devices requires more physical activity of device owners because the device must be brought near to other devices some times. Besides requiring more physical activity, NFC-based interaction also takes a longer time because the device needs to be moved from one position to another. This paper proposed secure and efficient protocol that will reduce the physical activity of the device owners and reducing transaction time. The data exchange between merchant and payer will be executed without waiting for each other and one transaction will require two data transmissions are performed by the merchant and payer. Transactions are secured by the use of encryption on each data which sent by the merchant and payer. In addition, the protocol also guarantees the security of offline micro transactions and online macros transactions.</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="20302">
                <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="20303">
                <text>https://online-journals.org/index.php/i-jim/article/view/2166</text>
              </elementText>
              <elementText elementTextId="20304">
                <text>10.3991/ijim.v6i4.2166</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20305">
                <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="20306">
                <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="20307">
                <text>https://online-journals.org/index.php/i-jim/article/view/2166/2336</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20308">
                <text>Copyright (c) 2017 Emir Mauludi 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="20309">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 6 No. 4 (2012); pp. 34-38</text>
              </elementText>
              <elementText elementTextId="20310">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20311">
                <text>NFC-based payment</text>
              </elementText>
              <elementText elementTextId="20312">
                <text>transaction protocol</text>
              </elementText>
              <elementText elementTextId="20313">
                <text>mobile payment</text>
              </elementText>
              <elementText elementTextId="20314">
                <text>secure protocol</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20315">
                <text>Mobile Payment Protocol for Tag-to-Tag Near Field Communication (NFC)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20316">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="20317">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="20318">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2301" 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="49288">
                <text>Muhammad Hassan</text>
              </elementText>
              <elementText elementTextId="49289">
                <text>Siti Falindah Padlee</text>
              </elementText>
              <elementText elementTextId="49290">
                <text>Sheikh Muhammad Zahid</text>
              </elementText>
              <elementText elementTextId="49291">
                <text>Muhammad Ali</text>
              </elementText>
              <elementText elementTextId="49292">
                <text>Shahid Ali Khawaj</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="49293">
                <text>2022-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="49294">
                <text>Today’s world is technology-oriented, and the use of mobile devices is imperative for individuals to keep pace with the modern lifestyle. This paper aims to determine the causes that formulate a consumer’s choice to adopt mobile payment technology in an underdeveloped economy. Data is collected through an online questionnaire from a sample drawn from a population determined through a statistical database. Structural Equation Modeling (SEM) was employed to test the conceptual framework with the assessment of measurement and structural model. The software used is SmartPLS version 3.0. The results of data analysis show that even in the presence of perceived security risk, customers show a tendency to engage in mobile payment systems based on strong relationships among perceived ease of use and perceived usefulness with attitude towards the use of MPS. The results point out a strong affinity for mobility, compatibility, and subjective norms in mobile technology acceptance.</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="49295">
                <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="49296">
                <text>https://online-journals.org/index.php/i-jim/article/view/30615</text>
              </elementText>
              <elementText elementTextId="49297">
                <text>10.3991/ijim.v16i13.30615</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="49298">
                <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="49299">
                <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="49300">
                <text>https://online-journals.org/index.php/i-jim/article/view/30615/11595</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="49301">
                <text>Copyright (c) 2022 Muhammad Hassan , Siti Falindah Padlee, Sheikh Muhammad Zahid , Muhammad Ali , Shahid Ali Khawaj</text>
              </elementText>
              <elementText elementTextId="49302">
                <text>https://creativecommons.org/licenses/by/4.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="49303">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 16 No. 13 (2022); pp. 95-106</text>
              </elementText>
              <elementText elementTextId="49304">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="49305">
                <text>mobile payment system (MPS)</text>
              </elementText>
              <elementText elementTextId="49306">
                <text>attitude, subjective norms</text>
              </elementText>
              <elementText elementTextId="49307">
                <text>intention, perceived usefulness</text>
              </elementText>
              <elementText elementTextId="49308">
                <text>perceived ease of use</text>
              </elementText>
              <elementText elementTextId="49309">
                <text>perceived security</text>
              </elementText>
              <elementText elementTextId="49310">
                <text>individual mobility</text>
              </elementText>
              <elementText elementTextId="49311">
                <text>compatibility</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="49312">
                <text>Mobile Payment Services (MPS) Acceptance by Consumers in Developing Economy: An Empirical Analysis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="49313">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="49314">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="49315">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1485" 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="30437">
                <text>Kadhim, Huda Yousif</text>
              </elementText>
              <elementText elementTextId="30438">
                <text>Al-saedi, Karim Hashim</text>
              </elementText>
              <elementText elementTextId="30439">
                <text>Al-Hassani, Mustafa Dhiaa</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="30440">
                <text>2019-09-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30441">
                <text>Abstract— The widespread use of smart phones nowadays makes them vulnerable to phishing. Phishing is the process of trying to steal user information over the Internet by claiming they are a trusted entity and thus access and steal the victim's data(user name, password and credit card details). Consequently, the need for mobile phishing detection system has become an urgent need. And this is what we are attempting to introduce in this paper, where we introduce a system to detect phishing websites on Android phones. That predicts and prevents phishing websites from deceiving users, utilizing data mining techniques to predict whether a website is phishing or not, relying on a set of factors (URL based features, HTML based features and Domain based features). The results shows system effectiveness in predicting phishing websites with 97% as prediction accuracy.</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="30442">
                <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="30443">
                <text>https://online-journals.org/index.php/i-jim/article/view/10797</text>
              </elementText>
              <elementText elementTextId="30444">
                <text>10.3991/ijim.v13i10.10797</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30445">
                <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="30446">
                <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="30447">
                <text>https://online-journals.org/index.php/i-jim/article/view/10797/5934</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30448">
                <text>Copyright (c) 2019 Huda Yousif Kadhim</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="30449">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 10 (2019); pp. 205-213</text>
              </elementText>
              <elementText elementTextId="30450">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30451">
                <text>mobile Phishing attacks</text>
              </elementText>
              <elementText elementTextId="30452">
                <text>Phishing</text>
              </elementText>
              <elementText elementTextId="30453">
                <text>Data Mining</text>
              </elementText>
              <elementText elementTextId="30454">
                <text>Web-based Phishing attack</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30455">
                <text>Mobile Phishing Websites Detection and Prevention Using Data Mining Techniques</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30456">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="30457">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="30458">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1845" 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="38652">
                <text>Akrim, A.</text>
              </elementText>
              <elementText elementTextId="38653">
                <text>Dalle, Juhriyansyah</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="38654">
                <text>2021-11-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="38655">
                <text>Mobile phone communication has established itself as an essential element of people's personal and working lives medium of connection in daily interactions and relationships. It has thus become significant for the most intimate form of interpersonal relations, including marital relationships. This small-scale research seeks to find the importance of mobile phone communication in marriage and its influence on family happiness. The study unearths the patterns of mobile phone communication among married partners, by outlining the most common reasons for communicating with the spouse on a mobile phone. In this research, a survey was conducted using a questionnaire to collect data from 30 respondents who were married partners, staff, or students in one of the state-owned universities in South Kalimantan. Each of the respondents possessed a mobile phone. The Mann-Whitney test indicates that the males profoundly believed that mobile phone communication was more important to their marriage than females to strengthen their relationship. Also, the males reported a higher frequency of sending messages and calling their spouses. By and large, the study results describe the most common reasons for communicating with the spouse. The outstanding reason is maintaining a strong intimate relationship by keeping in touch, sharing updates, emotions, feelings, knowing about children, and ensuring the safety of each other through checking on one another using a mobile phone. The findings have significance in showing the need for continued communication in a marital relationship, especially by using the fastest and most comfortable means of mobile phone. Given the synchronous nature of mobile phone communication, the results indicate that married spouses cannot do without it, especially in this Information Society, where we need updates from our spouses, children, friends, and the situation at large.</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="38656">
                <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="38657">
                <text>https://online-journals.org/index.php/i-jim/article/view/17811</text>
              </elementText>
              <elementText elementTextId="38658">
                <text>10.3991/ijim.v15i21.17811</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="38659">
                <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="38660">
                <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="38661">
                <text>https://online-journals.org/index.php/i-jim/article/view/17811/10179</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="38662">
                <text>Copyright (c) 2021 A. Akrim, Juhriyansyah Dalle</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="38663">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 15 No. 21 (2021); pp. 107-118</text>
              </elementText>
              <elementText elementTextId="38664">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="38665">
                <text>Mobile phone</text>
              </elementText>
              <elementText elementTextId="38666">
                <text>marital communication</text>
              </elementText>
              <elementText elementTextId="38667">
                <text>interpersonal relationships</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="38668">
                <text>Mobile Phone and Family Happiness, Mediating Role of Marital Communication: An Attachment Theory Perspective</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="38669">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="38670">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="38671">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1429" 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="29124">
                <text>Katuk, Norliza</text>
              </elementText>
              <elementText elementTextId="29125">
                <text>Zakaria, Nur Haryani</text>
              </elementText>
              <elementText elementTextId="29126">
                <text>Ku-Mahamud, Ku-Ruhana</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="29127">
                <text>2019-02-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29128">
                <text>Modern mobile phones or smartphones have multipurpose functions apart from being used as a device for voice and text communications. They are also embedded with many useful sensors, including camera, barometer, accelerometer, and digital compass. Unlike other types of sensor, the smartphone camera has been underutilized. This paper aims to fill the gap by analyzing and reviewing the hardware and software components of smartphones and highlighting the potential uses of the smartphone camera to support human daily life activities. A simple search of research papers indexed in Google Scholar was carried out using guided terms. The papers were filtered to match the research questions for this study. Only relevant papers were analyzed and reviewed. The results of the analysis suggested that the rapid development in the smartphone hardware has extended the use of the smartphone cameras beyond personal and social photography.  Consequently, applications (apps) based on smartphone cameras emerge, such as barcode readers, document digitizing tools, augmented reality, translation tools, and indoor positioning device. These apps benefit users and facilitate them in their daily life activities.</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="29129">
                <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="29130">
                <text>https://online-journals.org/index.php/i-jim/article/view/10166</text>
              </elementText>
              <elementText elementTextId="29131">
                <text>10.3991/ijim.v13i02.10166</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29132">
                <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="29133">
                <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="29134">
                <text>https://online-journals.org/index.php/i-jim/article/view/10166/5484</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29135">
                <text>Copyright (c) 2019 Norliza Katuk, Nur Haryani Zakaria, Ku-Ruhana Ku-Mahamud</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="29136">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 02 (2019); pp. 102-114</text>
              </elementText>
              <elementText elementTextId="29137">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29138">
                <text>mobile devices</text>
              </elementText>
              <elementText elementTextId="29139">
                <text>mobile phones</text>
              </elementText>
              <elementText elementTextId="29140">
                <text>mobile telecommunication systems</text>
              </elementText>
              <elementText elementTextId="29141">
                <text>sensors</text>
              </elementText>
              <elementText elementTextId="29142">
                <text>surveys</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29143">
                <text>Mobile Phone Sensing using the Built-in Camera</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29144">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29145">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29146">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
