<?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=254" accessDate="2026-06-11T06:12:58+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>254</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1046" 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="20705">
                <text>Abou El-Seoud, Samir</text>
              </elementText>
              <elementText elementTextId="20706">
                <text>Taj-Eddin, Islam</text>
              </elementText>
              <elementText elementTextId="20707">
                <text>Nosseir, Ann</text>
              </elementText>
              <elementText elementTextId="20708">
                <text>El-Sofany, Hosam</text>
              </elementText>
              <elementText elementTextId="20709">
                <text>Abu Rumman, Nadine</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="20710">
                <text>2013-01-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20711">
                <text>A handheld device system, such as cellular phone or a PDA, can be used in acquiring Sign Language (SL). The developed system uses graphic applications. The user uses the graphical system to view and to acquire knowledge about sign grammar and syntax based on the local vernacular particular to the country. This paper explores and exploits the possibility of the development of a mobile system to help the deaf and other people to communicate and learn using handheld devices. The pedagogical assessment of the prototype application that uses a recognition-based interface e.g., images and videos, gave evidence that the mobile application is memorable and learnable. Additionally, considering primary and recency effects in the interface design will improve memorability and learnability.</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="20712">
                <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="20713">
                <text>https://online-journals.org/index.php/i-jim/article/view/2387</text>
              </elementText>
              <elementText elementTextId="20714">
                <text>10.3991/ijim.v7i1.2387</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20715">
                <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="20716">
                <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="20717">
                <text>https://online-journals.org/index.php/i-jim/article/view/2387/2453</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20718">
                <text>Copyright (c) 2017 Samir Abou El-Seoud, Islam Taj-Eddin, Ann Nosseir, Hosam El-Sofany, Nadine Abu Rumman</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="20719">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 7 No. 1 (2013); pp. 46-55</text>
              </elementText>
              <elementText elementTextId="20720">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20721">
                <text>Sign Language</text>
              </elementText>
              <elementText elementTextId="20722">
                <text>Wireless J2ME</text>
              </elementText>
              <elementText elementTextId="20723">
                <text>Java Wireless Communication Technologies</text>
              </elementText>
              <elementText elementTextId="20724">
                <text>JSF</text>
              </elementText>
              <elementText elementTextId="20725">
                <text>JSP</text>
              </elementText>
              <elementText elementTextId="20726">
                <text>JMS</text>
              </elementText>
              <elementText elementTextId="20727">
                <text>SVG</text>
              </elementText>
              <elementText elementTextId="20728">
                <text>J2SE</text>
              </elementText>
              <elementText elementTextId="20729">
                <text>Client</text>
              </elementText>
              <elementText elementTextId="20730">
                <text>Server</text>
              </elementText>
              <elementText elementTextId="20731">
                <text>Handheld System</text>
              </elementText>
              <elementText elementTextId="20732">
                <text>Mobile System</text>
              </elementText>
              <elementText elementTextId="20733">
                <text>TCP/IP</text>
              </elementText>
              <elementText elementTextId="20734">
                <text>Video Streaming</text>
              </elementText>
              <elementText elementTextId="20735">
                <text>Adobe After Effects</text>
              </elementText>
              <elementText elementTextId="20736">
                <text>HTTP Connectivity</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20737">
                <text>A Proposed Pedagogical Mobile Application for Learning Sign Language</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20738">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="20739">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="20740">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1045" 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="20684">
                <text>Vihavainen, Sami</text>
              </elementText>
              <elementText elementTextId="20685">
                <text>Vä�¤nänen-Vainio-Mattila, Kaisa</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="20686">
                <text>2013-03-20</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20687">
                <text>Smartphones enable an always-on connection to Social Network Services (SNS). A typical way of interacting with SNSs is to access them when the user has a suitable situation to check the status of her social networks or to write an update. One way to enhance the usage of SNSs is to have the service automatically push notifications about events to the smartphone user interface. However, there is no research on how users experience such SNS notifications. We present an explorative field study with 11 participants to assess how users experience mobile notifications compared to reading SNS content manually, initiated by the user. The participants first used Facebook for a month without notifications and then for a month with an application called Socially that sends frequent notifications about Facebook events to the userâ??s smartphone desktop. The participants who kept the notification feature on reported increased reading of Facebook. However, after a while, many were unwilling to receive the notifications, mainly because of lack of control. We report the qualitative findings on user experience, which reveal for example, that the use of mobile notifications decreases interest in Facebook. Notifications limit user control, and using Facebook feels more meaningful when accessed manually. Implications for design are discussed.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20688">
                <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="20689">
                <text>https://online-journals.org/index.php/i-jim/article/view/2373</text>
              </elementText>
              <elementText elementTextId="20690">
                <text>10.3991/ijim.v7i2.2373</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20691">
                <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="20692">
                <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="20693">
                <text>https://online-journals.org/index.php/i-jim/article/view/2373/2561</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20694">
                <text>Copyright (c) 2017 Sami Vihavainen, Kaisa Vä�¤nänen-Vainio-Mattila</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="20695">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 7 No. 2 (2013); pp. 9-18</text>
              </elementText>
              <elementText elementTextId="20696">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20697">
                <text>Mobile notification</text>
              </elementText>
              <elementText elementTextId="20698">
                <text>Social Network Service (SNS)</text>
              </elementText>
              <elementText elementTextId="20699">
                <text>Field study</text>
              </elementText>
              <elementText elementTextId="20700">
                <text>User experience</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20701">
                <text>The Implications of Mobile Notifications for User Experience of a Social Network Service</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20702">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="20703">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="20704">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1044" 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="20662">
                <text>Otair, Mohammed</text>
              </elementText>
              <elementText elementTextId="20663">
                <text>Al-Refaei, Aiman</text>
              </elementText>
              <elementText elementTextId="20664">
                <text>Sarayreh, Bashar</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="20665">
                <text>2013-01-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20666">
                <text>This paper initiated to develop a WAP based ordering system. The paper extends the existing WEB enabled sales order capability to include a WAP service. Sales Representative Place the customer order during the customer visit to reduce time to order from second day to instant. Reduce paper work and costs associated with the recording of sales orders. In the Pharmacist Convenience to order, to check his /her account balance anytime anywhere, Get info on promotional items, and place orders.</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="20667">
                <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="20668">
                <text>https://online-journals.org/index.php/i-jim/article/view/2352</text>
              </elementText>
              <elementText elementTextId="20669">
                <text>10.3991/ijim.v7i1.2352</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20670">
                <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="20671">
                <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="20672">
                <text>https://online-journals.org/index.php/i-jim/article/view/2352/2901</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20673">
                <text>Copyright (c) 2017 Mohammed Otair, Aiman Al-Refaei, Bashar Sarayreh</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="20674">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 7 No. 1 (2013); pp. 41-45</text>
              </elementText>
              <elementText elementTextId="20675">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20676">
                <text>Mobile Portal</text>
              </elementText>
              <elementText elementTextId="20677">
                <text>WAP</text>
              </elementText>
              <elementText elementTextId="20678">
                <text>Pharmaceutical servies</text>
              </elementText>
              <elementText elementTextId="20679">
                <text>Smart-phones</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20680">
                <text>A Mobile Portal for Pharmaceutical Services</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20681">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="20682">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="20683">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1043" 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="20642">
                <text>Lezzar, Fouzi</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="20643">
                <text>2013-06-26</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20644">
                <text>In a health care environment, in which task planning process is fundamentally a collaborative task that requires the participation of many health care professionals with different skills working simultaneously on same cases. However, most recent healthcare research has focused on methods mainly based on communication, rather than collaboration supports. We followed then a CSCW-based planning approach which constitutes an evolution of planning environments toward new shared workspaces supporting collaboration. Our work led us first, to analyse the related tasks in an Algerian maternity ward in order to highlight the vital collaborative medical tasks that need to be modelled. The following sections outline basic design concepts of our mobile collaborative planning system, which is designed to provide a flexible group interaction support for care coordination and continuity.</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="20645">
                <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="20646">
                <text>https://online-journals.org/index.php/i-jim/article/view/2347</text>
              </elementText>
              <elementText elementTextId="20647">
                <text>10.3991/ijim.v7i3.2347</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20648">
                <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="20649">
                <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="20650">
                <text>https://online-journals.org/index.php/i-jim/article/view/2347/2713</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20651">
                <text>Copyright (c) 2017 Fouzi Lezzar</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="20652">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 7 No. 3 (2013); pp. 9-14</text>
              </elementText>
              <elementText elementTextId="20653">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20654">
                <text>Collaborative planning</text>
              </elementText>
              <elementText elementTextId="20655">
                <text>Healthcare task modelling</text>
              </elementText>
              <elementText elementTextId="20656">
                <text>Mobile application</text>
              </elementText>
              <elementText elementTextId="20657">
                <text>Synchronous/Asynchronous interaction</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20658">
                <text>A Mobile Shared Workspace Supporting Healthcare Task Cooperative Planning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20659">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="20660">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="20661">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1042" 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="20619">
                <text>Bhaskar, Nagella Uday</text>
              </elementText>
              <elementText elementTextId="20620">
                <text>Raju, Surya Narayana</text>
              </elementText>
              <elementText elementTextId="20621">
                <text>Paladugu, Govindarajulu</text>
              </elementText>
              <elementText elementTextId="20622">
                <text>Reddy, VenkataRamana</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="20623">
                <text>2013-03-20</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20624">
                <text>Mobile leaning application development has been influenced by the e-learning models, methods and a variation of these for the better understanding and accommodation of additional elements that prop up in m-learning scenarios and applications. Here uniquely designed models for various aspects of m-learning scenarios and situations by concentrating on Learner Styles or Contextual Features or Learning Content or Learner Behavior or Adaptation methods are proposed.</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="20625">
                <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="20626">
                <text>https://online-journals.org/index.php/i-jim/article/view/2338</text>
              </elementText>
              <elementText elementTextId="20627">
                <text>10.3991/ijim.v7i2.2338</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20628">
                <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="20629">
                <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="20630">
                <text>https://online-journals.org/index.php/i-jim/article/view/2338/2563</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20631">
                <text>Copyright (c) 2017 Nagella Uday Bhaskar, Surya Narayana Raju, Govindarajulu Paladugu, VenkataRamana Reddy</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="20632">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 7 No. 2 (2013); pp. 29-37</text>
              </elementText>
              <elementText elementTextId="20633">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20634">
                <text>Adaptation</text>
              </elementText>
              <elementText elementTextId="20635">
                <text>Content</text>
              </elementText>
              <elementText elementTextId="20636">
                <text>Context</text>
              </elementText>
              <elementText elementTextId="20637">
                <text>Mobile Learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20638">
                <text>Aspects of Content, Context and Adaptation Modeling in Mobile Learning Application Design</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20639">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="20640">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="20641">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1041" 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="20600">
                <text>Potgantwar, Amol Dnyaneshwar</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="20601">
                <text>2013-03-20</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20602">
                <text>NFC is a standards-based, short-range wireless
connectivity technology that enables simple and safe two-way
interactions between electronic devices. The concept is based
on combination of smartcard and contactless interconnection
technologies; NFC is compatible with todays field proven RFIDtechnology.
If this technology is used for identification of patient
in hospital, it will be very useful. Patients have different illness.
When doctors operate patients or exanimate patients, if the doctor
confuses the disease of patient, a fatal medical circumstance
may occur. If RFID and NFC technology is used for this case, we
can easily protect patients from fatal medical mistakes. It has the
potential to make almost all wireless technologies and also the
applications on these technologies easy enough so that everyone,
even the non-technical can use them.
Technological development and modern medicine practices are
amongst the outstanding factors triggering this shift. This trend is
resulting in a greater demand for health care-related services and
greater competition among health care providers. Achieving a
high operational efficiency in the health care sector is an essential
goal for organizational performance evaluation. Efficiency uses to
be considered as the primary indicator of hospital performance.
In order to bring down the cost and improve efficiency, intelligent
systems can play a significant role in providing intelligently
processed and personalized information about patients to doctors,
their health care staff (i.e. nurses) and health care administrators</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="20603">
                <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="20604">
                <text>https://online-journals.org/index.php/i-jim/article/view/2314</text>
              </elementText>
              <elementText elementTextId="20605">
                <text>10.3991/ijim.v7i2.2314</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20606">
                <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="20607">
                <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="20608">
                <text>https://online-journals.org/index.php/i-jim/article/view/2314/2568</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20609">
                <text>Copyright (c) 2017 Amol Dnyaneshwar Potgantwar</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="20610">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 7 No. 2 (2013); pp. 73-79</text>
              </elementText>
              <elementText elementTextId="20611">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20612">
                <text>NFC</text>
              </elementText>
              <elementText elementTextId="20613">
                <text>RFID</text>
              </elementText>
              <elementText elementTextId="20614">
                <text>MIFARE</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20615">
                <text>A Standalone RFID and NFC Based Healthcare</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20616">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="20617">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="20618">
                <text>Non-refereed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1040" 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="20577">
                <text>Daoud, Omar</text>
              </elementText>
              <elementText elementTextId="20578">
                <text>Hamarsheh, Qadri</text>
              </elementText>
              <elementText elementTextId="20579">
                <text>Al-Sawalmeh, Wael</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="20580">
                <text>2013-06-26</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20581">
                <text>This work proposes a new algorithm to enhance the performance of the speaker verification over the communication systems based Multiple-Input Multiple-Output (MIMO) - Orthogonal Frequency Division Multiplexing (OFDM) techniques.  The algorithm mainly tackles and overcomes the effect of the high Peak-to-Average Power Ratio problem that is found in OFDM systems, MIMO-OFDM combination has been developed to meet the rapidly increment in the users demand such as the ubiquitous transmission, imposing new multimedia applications and wireless services. In this algorithm, wavelets techniques have been used to denoise the affected OFDM symbol by high PAPR values. After that and based on adaptive threshold method the local maxima and minima will be determined and replaced by the average of them and their surrounding neighbors; Denoise OFDM and Replace PAPR (DORP).
A system performance investigation process will be accomplished based on both of numerical method and MATLAB simulation. Moreover, a comparison has been made to check the validity of our proposition either with our previously published work or with the literature. Although, the achieved results show that the proposed work has lower PAPR values; an additional complexity has been added to transceiverâ??s structure. Moreover, and as a result to the comparison with the conventional systems, the bit error rate (BER) performance has been improved for the same bandwidth occupancy.
As a validity process a comparison has been made with the current values found in the literature and we have achieved around 30% PAPR extra reduction. That is in addition to around 90% verification rate and noise immunity.</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="20582">
                <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="20583">
                <text>https://online-journals.org/index.php/i-jim/article/view/2302</text>
              </elementText>
              <elementText elementTextId="20584">
                <text>10.3991/ijim.v7i3.2302</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20585">
                <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="20586">
                <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="20587">
                <text>https://online-journals.org/index.php/i-jim/article/view/2302/2712</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20588">
                <text>Copyright (c) 2017 Omar Daoud, Qadri Hamarsheh, Wael Al-Sawalmeh</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="20589">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 7 No. 3 (2013); pp. 4-8</text>
              </elementText>
              <elementText elementTextId="20590">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20591">
                <text>MIMO</text>
              </elementText>
              <elementText elementTextId="20592">
                <text>OFDM</text>
              </elementText>
              <elementText elementTextId="20593">
                <text>Peak-to-Average Power Ratio</text>
              </elementText>
              <elementText elementTextId="20594">
                <text>wavelet</text>
              </elementText>
              <elementText elementTextId="20595">
                <text>Eigen vectors component.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20596">
                <text>MIMO-OFDM Systems Performance Enhancement Based Peaks Detection Algorithm</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20597">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="20598">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="20599">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1039" 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="20555">
                <text>Antic, Mladjan</text>
              </elementText>
              <elementText elementTextId="20556">
                <text>Jovanovic, Slobodan</text>
              </elementText>
              <elementText elementTextId="20557">
                <text>Cvetanovic, Svetlana</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="20558">
                <text>2013-01-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20559">
                <text>Abstractâ?? iOS is the Apple mobile operating system, for Apple mobile devices. Initially developed for iPhone, and later for iPod Touch, iPad, AppleTV.  The Metropolitan University has a Web application titled eStudent, which enables students by Web to get information about their marks for all subjects, their financies, exam scheduling, professors and assistents, and send exam registration and feedback about teaching,  etc. This paper explains the development of the mobile application eStudent on the iOS platform. This application enables students whenever they want, by using their iPhone mobile phone, to get access to the information from the eStudent Web application, and to present it on their iPhone User Interface (UI). This paper explains in details software requirements analysis, system architecture, system modelling, and UI of the eStudent  iOS mobile application.</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="20560">
                <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="20561">
                <text>https://online-journals.org/index.php/i-jim/article/view/2295</text>
              </elementText>
              <elementText elementTextId="20562">
                <text>10.3991/ijim.v7i1.2295</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20563">
                <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="20564">
                <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="20565">
                <text>https://online-journals.org/index.php/i-jim/article/view/2295/2451</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20566">
                <text>Copyright (c) 2017 Mladjan Antic, Slobodan Jovanovic, Svetlana Cvetanovic</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="20567">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 7 No. 1 (2013); pp. 35-40</text>
              </elementText>
              <elementText elementTextId="20568">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20569">
                <text>Apple</text>
              </elementText>
              <elementText elementTextId="20570">
                <text>API</text>
              </elementText>
              <elementText elementTextId="20571">
                <text>Ruby On Rails</text>
              </elementText>
              <elementText elementTextId="20572">
                <text>Objective C</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20573">
                <text>Development of eStudent iOS mobile application</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20574">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="20575">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="20576">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1038" 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="20529">
                <text>Saez de Arregui, Gastón</text>
              </elementText>
              <elementText elementTextId="20530">
                <text>Plano, Miguel</text>
              </elementText>
              <elementText elementTextId="20531">
                <text>Lerro, Federico</text>
              </elementText>
              <elementText elementTextId="20532">
                <text>Petrocelli, Lucía</text>
              </elementText>
              <elementText elementTextId="20533">
                <text>Marchisio, Susana</text>
              </elementText>
              <elementText elementTextId="20534">
                <text>Concari, Sonia</text>
              </elementText>
              <elementText elementTextId="20535">
                <text>Scotta, Virginia</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="20536">
                <text>2013-01-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20537">
                <text>In this paper we describe the design and development of interconnected devices which allow monitoring in situ the performance of solar boilers. This mobile remote lab system comprises two huge blocks of hardware: a mobile station located by the boiler, which is monitored and controlled in a remote way, and a fixed station, located in the Laboratory of Energy for the Sustained Development of the Universidad Nacional de Rosario. The communication between the fixed and mobile devices is controlled by microcontrollers included in both stations and programmed in C language. The project is being developed through three parallel lines of work: 1) Design and development of fixed and mobile hardware; 2) Development of firmware and software necessary to register and communicate data; 3) Design and development of learning activities. This mobile remote lab will be useful to test the behavior of solar boilers in the place and environmental conditions where they are placed so as to evaluate their performance and efficiency anywhere. This is also in order to contribute for the implementation of norms for the certification of solar boilers. On the other hand, the data and results obtained from the development will be used as supplies for the design of learning activities</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20538">
                <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="20539">
                <text>https://online-journals.org/index.php/i-jim/article/view/2292</text>
              </elementText>
              <elementText elementTextId="20540">
                <text>10.3991/ijim.v7i1.2292</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20541">
                <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="20542">
                <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="20543">
                <text>https://online-journals.org/index.php/i-jim/article/view/2292/2450</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20544">
                <text>Copyright (c) 2017 Gastón Saez de Arregui, Miguel Plano, Federico Lerro, Lucía Petrocelli, Susana Marchisio, Sonia Concari, Virginia Scotta</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="20545">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 7 No. 1 (2013); pp. 31-34</text>
              </elementText>
              <elementText elementTextId="20546">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20547">
                <text>remote lab</text>
              </elementText>
              <elementText elementTextId="20548">
                <text>remote control</text>
              </elementText>
              <elementText elementTextId="20549">
                <text>mobile technologies</text>
              </elementText>
              <elementText elementTextId="20550">
                <text>solar boilers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20551">
                <text>A Mobile Remote Lab System to Monitor in Situ Thermal Solar Installations</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20552">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="20553">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="20554">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1037" 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="20503">
                <text>El-Sofany, Hosam Farouk</text>
              </elementText>
              <elementText elementTextId="20504">
                <text>El-Seoud, Samir A.</text>
              </elementText>
              <elementText elementTextId="20505">
                <text>Al-Turki, Turky</text>
              </elementText>
              <elementText elementTextId="20506">
                <text>El-Howimel, Hasan</text>
              </elementText>
              <elementText elementTextId="20507">
                <text>Al-Sadoon, Amjad</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="20508">
                <text>2013-01-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20509">
                <text>The use of Computers, Networks, and Internet has successfully enabled educational institutions to provide their students and instructors with various online educational services. With the recent developments in M-learning and mobile technology, further possibilities are emerging to provide such services through mobile devices such as mobile phones and PDAs. By providing the educational services using wireless and mobile technologies, the educational institutions can potentially bring great convenience to those off-campus students who do not always have time to find Internet enabled computers to get the important educational information from their academic institutions. With the mobile or M-educational services, both the students and the instructors can access the services anytime and anywhere they want. This paper discusses those M-educational services that can be moved to the mobile platform and then presents the system prototype and architecture that integrate these services into the mobile technology platform. The paper will conclude with a description of the formative evaluation of the system prototype.</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="20510">
                <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="20511">
                <text>https://online-journals.org/index.php/i-jim/article/view/2287</text>
              </elementText>
              <elementText elementTextId="20512">
                <text>10.3991/ijim.v7i1.2287</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20513">
                <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="20514">
                <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="20515">
                <text>https://online-journals.org/index.php/i-jim/article/view/2287/2449</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20516">
                <text>Copyright (c) 2017 Hosam Farouk El-Sofany, Samir A. El-Seoud, Turky Al-Turki, Hasan El-Howimel, Amjad Al-Sadoon</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="20517">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 7 No. 1 (2013); pp. 25-30</text>
              </elementText>
              <elementText elementTextId="20518">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20519">
                <text>Mobile Applications and Services</text>
              </elementText>
              <elementText elementTextId="20520">
                <text>Computer Networks</text>
              </elementText>
              <elementText elementTextId="20521">
                <text>Mobile Telephony</text>
              </elementText>
              <elementText elementTextId="20522">
                <text>Educational Applications</text>
              </elementText>
              <elementText elementTextId="20523">
                <text>E-learning</text>
              </elementText>
              <elementText elementTextId="20524">
                <text>M-learning.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20525">
                <text>Improving Educational Outcomes by Providing Educational Services through Mobile Technology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20526">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="20527">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="20528">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
