<?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=343&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-19T20:32:19+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>343</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="654" public="1" featured="0">
    <collection collectionId="29">
      <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="12879">
                  <text>Pitt Political Review </text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="13506">
                  <text>Political Science</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="13507">
                  <text>PPR has ceased publication with the ULS. Editions including and prior to the fall 2017 edition will remain archived with the ULS. For information concerning future issues including the submission of potential articles for new issues, please email pittpoliticalreview@gmail.com.</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="45">
              <name>Publisher</name>
              <description>An entity responsible for making the resource available</description>
              <elementTextContainer>
                <elementText elementTextId="13508">
                  <text>University Library System of the University of Pittsburgh</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="12976">
                <text>Myers, Daphne</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="12977">
                <text>2017-10-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12978">
                <text>The United States has seen presidential administrations with lofty goals for healthcare policy come and go time and again since its founding, but never an efficient healthcare system. The healthcare debate has been raging in America for years. Should healthcare be universal? Should it be publicly or privately funded, or both? Should all citizens have the right to healthcare? Should all citizens be required by law to have healthcare? The case for universal healthcare seems to be the strongest because it is the most cost-effective way for society to fulfill its humanitarian obligations.</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="12979">
                <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="12980">
                <text>https://ppr.pitt.edu/ojs/index.php/ppr/article/view/90</text>
              </elementText>
              <elementText elementTextId="12981">
                <text>10.5195/ppr.2017.90</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12982">
                <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="12983">
                <text>University Library System, University of Pittsburgh</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="12984">
                <text>https://ppr.pitt.edu/ojs/index.php/ppr/article/view/90/64</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12985">
                <text>Copyright (c) 2017 Daphne Myers</text>
              </elementText>
              <elementText elementTextId="12986">
                <text>https://creativecommons.org/licenses/by-nc-nd/3.0/us/</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="12987">
                <text>Pitt Political Review; vol 12, No 1 (2016-2017); 16-19</text>
              </elementText>
              <elementText elementTextId="12988">
                <text>2160-5807</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12989">
                <text>US Healthcare: A "Disaster" of a System</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12990">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="12991">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="906" 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="17811">
                <text>Mostakhdemin-Hosseini, Ali</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17812">
                <text>2009-07-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17813">
                <text>Abstract- Mobile usability is not one-dimensional property of user interface, it has many components and attributes [1]  The most attributes associated with the mobile usability are as following: Satisfaction, Efficiency, Learnability, Lack of Errors, and Memorability
The assessment and importance of the usability attributes varies based on the application and the type of the users. For the expert usersâ?? lack of errors, reliability and efficiency are important and for the novice users beside mentioned factors the adjustability, learnability and memorability are essentials factors.  This paper reveals different usability considerations for mobile learning system with approparte guidelines.</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="17814">
                <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="17815">
                <text>https://online-journals.org/index.php/i-jim/article/view/854</text>
              </elementText>
              <elementText elementTextId="17816">
                <text>10.3991/ijim.v3i0.854</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17817">
                <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="17818">
                <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="17819">
                <text>https://online-journals.org/index.php/i-jim/article/view/854/974</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17820">
                <text>Copyright (c) 2017 Ali Mostakhdemin-Hosseini</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="17821">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 3 (2009): Special Issue IMCL2009; pp. 29-31</text>
              </elementText>
              <elementText elementTextId="17822">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17823">
                <text>Usability</text>
              </elementText>
              <elementText elementTextId="17824">
                <text>Mobile Learning Content and Mobile Devices</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17825">
                <text>Usability Considerations of Mobile Learning Applications</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17826">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="17827">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1893" 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="39751">
                <text>Ghabban, Fahad Mahmoud</text>
              </elementText>
              <elementText elementTextId="39752">
                <text>Hajjar, Mohammed</text>
              </elementText>
              <elementText elementTextId="39753">
                <text>Alharbi, Saad</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="39754">
                <text>2021-04-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39755">
                <text>The evolution of mobile technologies in learning, has been increased the requirements for developing appropriate usability model to fall into the same line with mobile learning applications. Usability of mobile learning applications is a topic that is into research, this paper focuses a tailored designed model called (M-UTUAT) mobile usability model that combines People at the Centre of Mobile Application Development (PACMAD) and the unified theory of acceptance and use of technology (UTAUT) to form a more robust model. As an addition to the usability research, an application (ICT) was developed for children with speech delays and children diagnosed with autism spectrum. The application is a mobile/tablet-based application that developed according to mobile usability measures to get the maximum learning skills and abilities to help autistic children. It has been designed according to the needs of the children specific to their category and skills. The autism spectrum is a broad spectrum with high and low disabilities. The application consists of both visual and audio aids to help children feel comfortable and associate objects more easily with their original meaning and connections. (PECS) is one of the most common techniques that have been clinically proven to be effective in such cases. This application helped an individual with autism spectrum as well as children with speech delays or disabilities to communicate and correlate faster and easily. The application can help so many families by constructing a more communicative path for people with disabilities. The application is innovative that it developed in the Arabic language to serve Arabic learners as most of the autistic applications available serve English learners. Results gathered after questionnaire highlight the usability issues with the (ICT) application. We developed an app to overcome usability issues.</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="39756">
                <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="39757">
                <text>https://online-journals.org/index.php/i-jim/article/view/19881</text>
              </elementText>
              <elementText elementTextId="39758">
                <text>10.3991/ijim.v15i07.19881</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39759">
                <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="39760">
                <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="39761">
                <text>https://online-journals.org/index.php/i-jim/article/view/19881/9055</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39762">
                <text>Copyright (c) 2021 fahad mahmoud ghabban</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="39763">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 15 No. 07 (2021); pp. 30-46</text>
              </elementText>
              <elementText elementTextId="39764">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39765">
                <text>Usability Evaluation</text>
              </elementText>
              <elementText elementTextId="39766">
                <text>User Acceptance of Mobile Applications</text>
              </elementText>
              <elementText elementTextId="39767">
                <text>mobile use</text>
              </elementText>
              <elementText elementTextId="39768">
                <text>saudi arabia</text>
              </elementText>
              <elementText elementTextId="39769">
                <text>teaching</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39770">
                <text>Usability Evaluation and User Acceptance of Mobile Applications for Saudi Autistic Children</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39771">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="39772">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="39773">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1661" 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="34480">
                <text>Hussain, Azham</text>
              </elementText>
              <elementText elementTextId="34481">
                <text>Mohamed Omar, Ahlam</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="34482">
                <text>2020-04-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34483">
                <text>The usability of the mobile applications is the most important factor in developing, so the key to develop successful mobile applications is usability, especially for users have specific needs such as visually impaired. However, developers do not focus on visually impaired users. Moreover, there are limited studies and usability evaluation models for mobile applications for visually impaired so developers use just a modified usability evaluation methods which are not enough and useful to evaluate mobile applications for visually impaired, or they use general usability evaluation models. Therefore, using these methods or models is difficult for evaluator and not useful for visually impaired users. This study conducts Systematic Literature Review (SLR) to identify usability dimensions that help mobile applications developers and evaluators to evaluate mobile application for users which have moderate and severe visual impairment. The result shows that, six dimensions that have a significant impact on moderate and severe visually impaired users' satisfaction, who use mobile applications. These dimensions namely efficiency, effectiveness, satisfaction, errors, accessibility and understandability.</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="34484">
                <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="34485">
                <text>https://online-journals.org/index.php/i-jim/article/view/13349</text>
              </elementText>
              <elementText elementTextId="34486">
                <text>10.3991/ijim.v14i05.13349</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34487">
                <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="34488">
                <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="34489">
                <text>https://online-journals.org/index.php/i-jim/article/view/13349/6767</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34490">
                <text>Copyright (c) 2020 Azham Hussain, Ahlam Mohamed Omar</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="34491">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 05 (2020); pp. 95-107</text>
              </elementText>
              <elementText elementTextId="34492">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34493">
                <text>Visually impaired people</text>
              </elementText>
              <elementText elementTextId="34494">
                <text>Mobile application</text>
              </elementText>
              <elementText elementTextId="34495">
                <text>Usability dimensions</text>
              </elementText>
              <elementText elementTextId="34496">
                <text>Usability evaluation model.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34497">
                <text>Usability Evaluation Model for Mobile Visually Impaired Applications</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34498">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34499">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34500">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2335" 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="50105">
                <text>Dahri, Nisar Ahmed</text>
              </elementText>
              <elementText elementTextId="50106">
                <text>Muhammad Saleem Vighio</text>
              </elementText>
              <elementText elementTextId="50107">
                <text>Waleed Mugahed Al-Rahmi</text>
              </elementText>
              <elementText elementTextId="50108">
                <text>Omar A. Alismaiel</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="50109">
                <text>2022-08-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50110">
                <text>Teachers' professional development plays a significant role in the sustainability of quality education. However, providing sustainable professional development programs is difficult because of various challenges, such as insufficient government policies, a scarcity of qualified personnel and training opportunities, lack of access and resources, etc. The COVID-19 epidemic has further intensified the problem and adversely harmed schoolteachers’ interest, motivation, and involvement. In such situations, technology can play a positive role in carrying out sustainable educational activities. However, little focus has been paid to the use of technology for the sustainable professional development of teachers, particularly in the under developing countries. Due to its unique qualities, mobile learning is receiving much attention as an essential component to impart sustainable education to teaching professionals. It represents a paradigm shift in ongoing professional development, particularly for teachers who are constrained by time, resources, and travel requirements. Mobile learning is an alternate and complementary technique to enhance teachers' professional development, allowing them to work, learn, and attain their full potential.&amp;nbsp; To meet the sustainable development goal of teachers’ education, in [1] we have provided a framework for teachers' continuous professional development (CPD). Based on that, we have also developed a mobile App to provide training and ongoing support to teachers’ professionals. This study evaluates the usability of our mobile App for the sustainable development of teachers. Usability characteristics of usefulness, efficiency, and satisfaction are measured using a usability testing approach. 107 elementary school instructors took part in the study. Participants in the study performed eight usability tasks in the same room using the researcher's internet bandwidth. The participants' time and completion rate were recorded. A post-test questionnaire followed usability tasks. After the usability activities, participants completed a System Usability Scale questionnaire to assess overall satisfaction with the training app and gain a broad picture of the program. The application achieved a 100% completion rate for all tasks, indicating an extremely effective, efficient, and sustainable system. Moreover, the satisfaction percentage was also found to be 84.1 percent, which is considered highly satisfactory.</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="50111">
                <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="50112">
                <text>https://online-journals.org/index.php/i-jim/article/view/32015</text>
              </elementText>
              <elementText elementTextId="50113">
                <text>10.3991/ijim.v16i16.32015</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50114">
                <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="50115">
                <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="50116">
                <text>https://online-journals.org/index.php/i-jim/article/view/32015/11869</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50117">
                <text>Copyright (c) 2022 Nisar Ahmed Dahri, Muhammad Saleem Vighio , Waleed Mugahed Al-Rahmi , Omar A. Alismaiel</text>
              </elementText>
              <elementText elementTextId="50118">
                <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="50119">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 16 No. 16 (2022); pp. 4-30</text>
              </elementText>
              <elementText elementTextId="50120">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50121">
                <text>Sustainable CPD Model</text>
              </elementText>
              <elementText elementTextId="50122">
                <text>Teacher’s training</text>
              </elementText>
              <elementText elementTextId="50123">
                <text>Mobile-based training App</text>
              </elementText>
              <elementText elementTextId="50124">
                <text>Usability</text>
              </elementText>
              <elementText elementTextId="50125">
                <text>Effectiveness</text>
              </elementText>
              <elementText elementTextId="50126">
                <text>Efficiency</text>
              </elementText>
              <elementText elementTextId="50127">
                <text>digital learning use for education sustainability</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50128">
                <text>Usability Evaluation of Mobile App for the Sustainable Professional Development of Teachers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50129">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="50130">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="50131">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1567" 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="32307">
                <text>Samad Dahri, Abdul</text>
              </elementText>
              <elementText elementTextId="32308">
                <text>Al-Athwari, Ahmad</text>
              </elementText>
              <elementText elementTextId="32309">
                <text>Hussain, Azham</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="32310">
                <text>2019-11-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32311">
                <text>Purpose: This study endorses AI enabled Mobile Health application and investigates usability evaluation of the Mobile Health application by patients’ task performance evaluation and satisfaction.Materials and Methods: International Organization for Standards (ISO) 9241-11 standard metrics were used and 15 patients performed tasks on task success rate, errors, efficiency (time spent), satisfaction (SUS scale).Results: Getting registered was a top easy task while finding a relevant doctor was the most difficult task for users. The satisfaction scores by SUS suggest good rather excellent application user experience. Male were successful task achievers, while educational level and mobile know-how influence the usability scores in terms of time consumed, task errors occurred, and task completed.Conclusion: Methods used in this study suggest future research from different contexts. Using ISO 9241-11 usability standards, the SUS instrument for satisfaction, and measuring user characteristics influence performance and can provide considerable Mobile Health design.</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="32312">
                <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="32313">
                <text>https://online-journals.org/index.php/i-jim/article/view/11513</text>
              </elementText>
              <elementText elementTextId="32314">
                <text>10.3991/ijim.v13i11.11513</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32315">
                <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="32316">
                <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="32317">
                <text>https://online-journals.org/index.php/i-jim/article/view/11513/6031</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32318">
                <text>Copyright (c) 2019 Abdul Samad Dahri, Ahmaed Al-Athwari, Azham Hussain, Kamal Ab Hamid</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="32319">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 11 (2019); pp. 213-225</text>
              </elementText>
              <elementText elementTextId="32320">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32321">
                <text>Healthcare</text>
              </elementText>
              <elementText elementTextId="32322">
                <text>Mobile Health (mHealth)</text>
              </elementText>
              <elementText elementTextId="32323">
                <text>Usability</text>
              </elementText>
              <elementText elementTextId="32324">
                <text>Artificial Intelligence</text>
              </elementText>
              <elementText elementTextId="32325">
                <text>Developing countries.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32326">
                <text>Usability Evaluation of Mobile Health Application from AI Perspective in Rural Areas of Pakistan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32327">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="32328">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="32329">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1663" 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="34524">
                <text>Ali Saare, Murtaja</text>
              </elementText>
              <elementText elementTextId="34525">
                <text>Hussain, Azham Bin</text>
              </elementText>
              <elementText elementTextId="34526">
                <text>Jasim, Osamah Mohammed</text>
              </elementText>
              <elementText elementTextId="34527">
                <text>Mahdi, Alia Ahmed</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="34528">
                <text>2020-04-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34529">
                <text>In the recent years, mobile is found to be useful since they allow the user to perform more tasks in a mobile context. However, this usefulness come at the expense of the usability of these devices in some contexts. Thus, usability becomes an important factor in the adoption of mobile applications (such as mobile tracking applications, mobile health and mobile learning), which are often used by people who have problems when using mobile devices and who have a limited experience of technology. It’s critical in the Mobile domain to ensure the success of mobile applications. Despite some studies review usability evaluation, regrettably there are no systematic literature reviews focused on usability evaluation of mobile tracking applications. Consequently, in this study, the researchers strive to present the results of a systematic literature review (SLR) involving the use of usability evaluation techniques in Mobile tracking applications. Based on three research questions, the results indicated that, there are three kinds of the Mobile tracking applications namely: information tracking, location tracking and information and location tracking. In addition, and regard to the techniques used to evaluate the usability, the experimental study was the regularly used in the selected studies. Finally, the results shown that, for characteristics were frequently exploited to measure the usability of mobile tracking application are: Effectiveness, Efficiency, Usefulness and Accurate. This study is valuable for the researchers who need to evaluate the usability for any new mobile application through explored the appropriate methods used to evaluation the usability and indicators required for this purpose.</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="34530">
                <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="34531">
                <text>https://online-journals.org/index.php/i-jim/article/view/13353</text>
              </elementText>
              <elementText elementTextId="34532">
                <text>10.3991/ijim.v14i05.13353</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34533">
                <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="34534">
                <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="34535">
                <text>https://online-journals.org/index.php/i-jim/article/view/13353/6785</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34536">
                <text>Copyright (c) 2020 Murtaja Ali Saare, Azham Bin Hussain, Osamah Mohammed Jasim, Alia Ahmed Mahdi</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="34537">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 05 (2020); pp. 119-128</text>
              </elementText>
              <elementText elementTextId="34538">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34539">
                <text>Usability Evaluation</text>
              </elementText>
              <elementText elementTextId="34540">
                <text>Mobile Device</text>
              </elementText>
              <elementText elementTextId="34541">
                <text>Tracking Application</text>
              </elementText>
              <elementText elementTextId="34542">
                <text>Systematic Literature Review.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34543">
                <text>Usability Evaluation of Mobile Tracking Applications: A Systematic Review</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34544">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="34545">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="34546">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1498" 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="30731">
                <text>Maggay, Jake Guabes</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="30732">
                <text>2019-09-05</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30733">
                <text>The objective of the study is to evaluate the usability of SMS-Based Auto-Reply Inquiry System for Grades and Accounts. This descriptive study used a three-part questionnaire which was administered by the researcher. The usability questionnaire adapted from the USE Questionnaire used a 5-point scale composed of 30 statements. Convenience sampling was used choosing the respondents from the total population of 149 students of the CICS during the second semester of school year 2018-2019. A total of 45 questionnaires were retrieved and were used in the usability analysis. The usability evaluation results yielded a grand mean of 4.54 (Strongly Agree) showing that the SMS-based inquiry system is easy to learn, easy to use, useful, and satisfying. The results of this study show that pre-coded keywords are confusing for beginners but can be learned and familiarized by the users as they continue use the system. Further investigation should be conducted to prove that ease of use, ease of learning, and usefulness have direct impacts to user satisfaction.</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="30734">
                <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="30735">
                <text>https://online-journals.org/index.php/i-jim/article/view/10918</text>
              </elementText>
              <elementText elementTextId="30736">
                <text>10.3991/ijim.v13i09.10918</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30737">
                <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="30738">
                <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="30739">
                <text>https://online-journals.org/index.php/i-jim/article/view/10918/5894</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30740">
                <text>Copyright (c) 2019 Jake Guabes Maggay</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="30741">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 09 (2019); pp. 113-125</text>
              </elementText>
              <elementText elementTextId="30742">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30743">
                <text>auto-reply system</text>
              </elementText>
              <elementText elementTextId="30744">
                <text>SMS-based system</text>
              </elementText>
              <elementText elementTextId="30745">
                <text>system performance</text>
              </elementText>
              <elementText elementTextId="30746">
                <text>usability</text>
              </elementText>
              <elementText elementTextId="30747">
                <text>USE questionnaire</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30748">
                <text>Usability Evaluation of SMS-Based System: Basis for Systems Development</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30749">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="30750">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="30751">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1146" 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="22812">
                <text>Resch, Bernd</text>
              </elementText>
              <elementText elementTextId="22813">
                <text>Wichmann, Andreas</text>
              </elementText>
              <elementText elementTextId="22814">
                <text>Göll, Nicolas</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="22815">
                <text>2015-09-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22816">
                <text>Even though advantages of 3D visualisation of multi-temporal geo-data versus 2D approaches have been widely proven, the particular pertaining challenge of real-time visualisation of geo-data in mobile Digital Earth applications has not been thoroughly tackled so far. In the emerging field of Augmented Reality (AR), research needs comprise finding the optimal information density, the interplay between orientation data in the background and other information layers, using the appropriate graphical variables for display, or selecting real-time base data with adequate quality and suitable spatial accuracy. In this paper we present a concept for integrating real-time data into 4D (three spatial dimensions plus time) AR environments, i.e., data with “high” spatial and temporal variations. We focus on three research challenges: 1.) high-performance integration of real-time data into AR; 2.) usability design in terms of displaying spatio-temporal developments and the interaction with the application; and 3.) design considerations regarding reality vs. virtuality, visualisation complexity and information density. We validated our approach in a prototypical application and extracted several limitations and future research areas including natural feature recognition, the cross-connection of (oftentimes monolithic) AR interface developments and well-established cartographic principles, or fostering the understanding of the temporal context in dynamic 4D Augmented Reality environments.</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="22817">
                <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="22818">
                <text>https://online-journals.org/index.php/i-jim/article/view/4626</text>
              </elementText>
              <elementText elementTextId="22819">
                <text>10.3991/ijim.v9i4.4626</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22820">
                <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="22821">
                <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="22822">
                <text>https://online-journals.org/index.php/i-jim/article/view/4626/3609</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22823">
                <text>Copyright (c) 2017 Bernd Resch, Andreas Wichmann, Nicolas Göll</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="22824">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 9 No. 4 (2015); pp. 23-33</text>
              </elementText>
              <elementText elementTextId="22825">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22826">
                <text>real-time augmented reality</text>
              </elementText>
              <elementText elementTextId="22827">
                <text>4D augmented reality</text>
              </elementText>
              <elementText elementTextId="22828">
                <text>real-time mobile geo-app</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22829">
                <text>Usability in 4D AR: Visualising Multi-temporal Real-time Geo-data in Augmented Reality Environments</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22830">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="22831">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="22832">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="954" 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="18791">
                <text>Majumder, Moumita</text>
              </elementText>
              <elementText elementTextId="18792">
                <text>Basu, Pramatha Nath</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="18793">
                <text>2010-07-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18794">
                <text>In an effort to find out the best suitable application of mobile learning, several research works are undertaken till date. A review of related papers unveiled that mobile devices act better as a supporting media in teaching and learning scenario. The present worker has developed context specific learning modules i.e. personalized learning contents using an ontology based web service architecture and an experimantal exploration has been done with the target audience to justify the usability of such content in a real time environment. To ensure that the developed contents are acceptable and usable, usability aspects are carefully embedded during the analysis, design and development of the contents. In this paper, the steps to fulfill the usability aspects of the prepared contents are described, an architecture of the dissemination system has been designed and results of the study are presented.</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="18795">
                <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="18796">
                <text>https://online-journals.org/index.php/i-jim/article/view/1305</text>
              </elementText>
              <elementText elementTextId="18797">
                <text>10.3991/ijim.v4i3.1305</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18798">
                <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="18799">
                <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="18800">
                <text>https://online-journals.org/index.php/i-jim/article/view/1305/1420</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18801">
                <text>Copyright (c) 2017 Moumita Majumder, Pramatha Nath Basu</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="18802">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 4 No. 3 (2010); pp. 25-29</text>
              </elementText>
              <elementText elementTextId="18803">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18804">
                <text>Mobile Learning</text>
              </elementText>
              <elementText elementTextId="18805">
                <text>context specific</text>
              </elementText>
              <elementText elementTextId="18806">
                <text>learner centric</text>
              </elementText>
              <elementText elementTextId="18807">
                <text>ontology</text>
              </elementText>
              <elementText elementTextId="18808">
                <text>web service</text>
              </elementText>
              <elementText elementTextId="18809">
                <text>usability study.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18810">
                <text>Usability Study of Personalized Learning in Mobile Learning Environment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18811">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="18812">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="18813">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
