<?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=243&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-15T04:02:35+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>243</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="207" public="1" featured="0">
    <collection collectionId="26">
      <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="2304">
                  <text>Artha Journal of Social Sciences</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="4083">
                <text>M Jorum, Tasleema</text>
              </elementText>
              <elementText elementTextId="4084">
                <text>S Mali, Sujata</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="4085">
                <text>2021-11-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4086">
                <text>For the past three decades India's banking system has several outstanding achievements to its credit. The most striking is its extensive reach. It is no longer confined to only metropolitans or cosmopolitans in India. In fact, Indian banking system has reached even to the remote corners of the country. This is one of the main reasons for India's growth process. The government's regular policy for Indian banks since 1969 has paid rich dividends with the nationalization of 14 major private banks of India. Regional Rural Banks started their development process on 2 October 1975 with the formation of a single bank—Prathama Grameen Bank. The RRBs mobilize financial resources from rural/semi-urban areas and grant loans and advances mostly to small and marginal farmers, agricultural labourers and rural artisans. The area of operation of RRBs is limited to the area as notified by GoI covering one or more districts in the State. In this context, the present study is an attempt to examine the impact of amalgamation on physical performance of RRBs during post-amalgamation period.</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="4087">
                <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="4088">
                <text>https://journals.christuniversity.in/index.php/artha/article/view/733</text>
              </elementText>
              <elementText elementTextId="4089">
                <text>10.12724/ajss.22.1</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4090">
                <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="4091">
                <text>Centre for Publications, CHRIST (Deemed to be University), Bangalore</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="4092">
                <text>https://journals.christuniversity.in/index.php/artha/article/view/733/848</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4093">
                <text>Copyright (c) 2016 Artha - Journal of Social Sciences</text>
              </elementText>
              <elementText elementTextId="4094">
                <text>http://creativecommons.org/licenses/by-nc/4.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="4095">
                <text>Artha Journal of Social Sciences; Vol. 11 No. 3 (2012): Artha Journal of Social Sciences; 1-13</text>
              </elementText>
              <elementText elementTextId="4096">
                <text>0000-0000</text>
              </elementText>
              <elementText elementTextId="4097">
                <text>0975-329X</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4098">
                <text>Banking</text>
              </elementText>
              <elementText elementTextId="4099">
                <text>Regional rural banks</text>
              </elementText>
              <elementText elementTextId="4100">
                <text>Amalgamation</text>
              </elementText>
              <elementText elementTextId="4101">
                <text>profits and loss and economic development</text>
              </elementText>
              <elementText elementTextId="4102">
                <text>NPAs and deposits</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4103">
                <text>Performance of Regional Rural Banks after Amalgamation in India: Progress and Prospects</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4104">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="4105">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="4106">
                <text>Peer-reviewed Article</text>
              </elementText>
              <elementText elementTextId="4107">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3168" public="1" featured="0">
    <collection collectionId="47">
      <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="64218">
                  <text>Journal of Naval Architecture and Marine Engineering</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="64857">
                <text>Syed, Shafiuddin Amer</text>
              </elementText>
              <elementText elementTextId="64858">
                <text>Mani, JS</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="64859">
                <text>2009-02-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64860">
                <text>A floating system consisting of three pontoons equispaced, rigidly interconnected and taut moored to act as a single unit is analyzed. The theoretical formulation of the problem is based on the assumptions of irrotational fluid flow, an inviscid fluid, and small incident waves. The breakwater is assumed to be long and uniform in the direction parallel to the incident wave crests. The diffracted and the scattered potentials are obtained from the solution of boundary value problem using Green's identity method. The potentials and hence the free surface oscillations in between the spacing are also determined. The results of parametric study of varying space and drafts of the pontoons have been presented as a function of relative width of breakwater (Ratio of width of the breakwater to the wavelength) .It is evident from the results that the spaces between the pontoons have a definite effect on transmission and reflection characteristics of a floating breakwater system. As the draft of the floating breakwater increases the bandwidth of incident wave frequencies for which Kt (Ratio of transmitted wave height to incident wave height) is less than 0.2, also increases, thus ensuring a wider spectrum of operation. In addition the paper discusses on forces, oscillations in the interspaces and reflection coefficient. Keywords: breakwater, pontoon, taut moored, free surface oscillations.  doi: 10.3329/jname.v1i1.2031 Journal of Naval Architecture and Marine Engineering 1(2004) 3-17</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="64861">
                <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="64862">
                <text>https://www.banglajol.info/index.php/JNAME/article/view/2031</text>
              </elementText>
              <elementText elementTextId="64863">
                <text>10.3329/jname.v1i1.2031</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64864">
                <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="64865">
                <text>Association of Naval Architects and Marine Engineers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="64866">
                <text>https://www.banglajol.info/index.php/JNAME/article/view/2031/1891</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="64867">
                <text>Journal of Naval Architecture and Marine Engineering; Vol. 1 No. 1 (2004); 3-17</text>
              </elementText>
              <elementText elementTextId="64868">
                <text>2070-8998</text>
              </elementText>
              <elementText elementTextId="64869">
                <text>1813-8535</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64870">
                <text>breakwater</text>
              </elementText>
              <elementText elementTextId="64871">
                <text>pontoon</text>
              </elementText>
              <elementText elementTextId="64872">
                <text>taut moored</text>
              </elementText>
              <elementText elementTextId="64873">
                <text>free surface oscillations</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64874">
                <text>Performance of rigidly interconnected multiple floating pontoons</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64875">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="64876">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1955" 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="41184">
                <text>Chua, Nurul Ain</text>
              </elementText>
              <elementText elementTextId="41185">
                <text>Soon, Goh Ying</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="41186">
                <text>2021-03-16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="41187">
                <text>Students should be able to develop their communication abilities instead of just concentrating on translation methods. As a result, Communicative Teaching Language (CLT) had become the most favored approach to achieving the verbal goal as it was known as the most effective strategy to enhance learners' communicative competence. However, it was not a one-size-fits-all approach, and language instructors were advised to integrate educational technology to develop learning for students. Hence, CLT Mandarin mobile learning via personal action research was conducted to determine the extent of the approach on students' oral learning attainment, attitudes, and learners' recommendations during the learning process. The communicative task used in this study was Chatting to Mandarin Native Speakers programme. Pre- and post-oral assessments had been conducted in response to research inquiries. In verifying the reliability and validity of the study, data were triangulated through students' oral assessments, Students' Diaries, Self-Reflective Journals and Focus Group Interviews. The outcomes showed that students enjoyed the activity and improved their confidence and oral competence. Also, they suggested that there should be more language activities. The findings indicated that, when designing CLT technology-integrated projects, an instructor needed to consider students' learning preferences which make the project a success.</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="41188">
                <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="41189">
                <text>https://online-journals.org/index.php/i-jim/article/view/20899</text>
              </elementText>
              <elementText elementTextId="41190">
                <text>10.3991/ijim.v15i05.20899</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="41191">
                <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="41192">
                <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="41193">
                <text>https://online-journals.org/index.php/i-jim/article/view/20899/8835</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="41194">
                <text>Copyright (c) 2021 Nurul Ain Chua, Goh Ying Soon</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="41195">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 15 No. 05 (2021); pp. 87-99</text>
              </elementText>
              <elementText elementTextId="41196">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="41197">
                <text>Communicative Tasks</text>
              </elementText>
              <elementText elementTextId="41198">
                <text>Smartphone Applications</text>
              </elementText>
              <elementText elementTextId="41199">
                <text>Oral Competency</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="41200">
                <text>Performing Communicative Language Teaching in Mandarin Mobile Learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="41201">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="41202">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="41203">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1928" 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="40563">
                <text>Nik Ahmad, Nik Azlina</text>
              </elementText>
              <elementText elementTextId="40564">
                <text>Hamid, Nur Iman Mardhiah</text>
              </elementText>
              <elementText elementTextId="40565">
                <text>Mohd Lokman, Anitawati</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="40566">
                <text>2021-05-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="40567">
                <text>Usability evaluation is an essential activity to contribute to a higher standard of user experience. This study conducted a usability evaluation on multi-platform application according to usability attributes as defined in ISO 9241-11 standard which are efficiency, effectiveness, and satisfaction. The evaluation was conducted on both platforms; web and mobile application and involved 50 participants. The results discovered some points to usability issues. Therefore, to further enhance the users’ satisfaction, efficiency, and effectiveness, a set of improvement recommendations were proposed. Insights from this study provides a standard basis on the usability evaluation procedure which can serve as a guide for the usability evaluation of multi-platform applications.</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="40568">
                <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="40569">
                <text>https://online-journals.org/index.php/i-jim/article/view/20429</text>
              </elementText>
              <elementText elementTextId="40570">
                <text>10.3991/ijim.v15i10.20429</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="40571">
                <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="40572">
                <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="40573">
                <text>https://online-journals.org/index.php/i-jim/article/view/20429/9257</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="40574">
                <text>Copyright (c) 2021 Nik Azlina Nik Ahmad</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="40575">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 15 No. 10 (2021); pp. 103-117</text>
              </elementText>
              <elementText elementTextId="40576">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="40577">
                <text>ISO9241</text>
              </elementText>
              <elementText elementTextId="40578">
                <text>multi-platform</text>
              </elementText>
              <elementText elementTextId="40579">
                <text>usability attributes</text>
              </elementText>
              <elementText elementTextId="40580">
                <text>mobile usability</text>
              </elementText>
              <elementText elementTextId="40581">
                <text>usability evaluation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="40582">
                <text>Performing Usability Evaluation on Multi-Platform Based Application for Efficiency, Effectiveness, and Satisfaction Enhancement</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="40583">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="40584">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="40585">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3326" public="1" featured="0">
    <collection collectionId="47">
      <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="64218">
                  <text>Journal of Naval Architecture and Marine Engineering</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="68318">
                <text>Saravana, R.</text>
              </elementText>
              <elementText elementTextId="68319">
                <text>Sreenadh, S.</text>
              </elementText>
              <elementText elementTextId="68320">
                <text>Kumar, P. Rajesh</text>
              </elementText>
              <elementText elementTextId="68321">
                <text>Babu, V. Ramesh</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="68322">
                <text>2020-12-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68323">
                <text>The paper investigates the role of complete velocity slip on the axisymmetric peristaltic transport of Ellis fluid through a uniform flexible tube considering the long wavelength and tiny Reynolds number assumptions. The equations governing the axisymmetric flow are solved and provided the analytical expressions for axial velocity, stream function, pressure difference for shear thickening and shear thinning fluids and the effect of emerging parameters on the pressure rise with time averaged flux and stream line patterns have been discussed graphically. The trapping phenomenon results showed that the size of trapping bolus enhances with increasing values of first and second slip parameters.</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="68324">
                <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="68325">
                <text>https://www.banglajol.info/index.php/JNAME/article/view/49559</text>
              </elementText>
              <elementText elementTextId="68326">
                <text>10.3329/jname.v17i2.49559</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68327">
                <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="68328">
                <text>Association of Naval Architects and Marine Engineers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="68329">
                <text>https://www.banglajol.info/index.php/JNAME/article/view/49559/36215</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68330">
                <text>Copyright (c) 2020 Journal of Naval Architecture and Marine Engineering</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="68331">
                <text>Journal of Naval Architecture and Marine Engineering; Vol. 17 No. 2 (2020); 79-88</text>
              </elementText>
              <elementText elementTextId="68332">
                <text>2070-8998</text>
              </elementText>
              <elementText elementTextId="68333">
                <text>1813-8535</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68334">
                <text>Ellis fluid, complete slip, peristalsis, shear thickening behaviour, shear thinning behavior</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68335">
                <text>Peristaltic pumping of Ellis fluid through a flexible tube with complete slip effects</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68336">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="68337">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3106" public="1" featured="0">
    <collection collectionId="43">
      <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="63031">
                  <text>University of South Australia Law Review</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="63564">
                <text>Douglas, David M</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="63565">
                <text>2018-04-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="63566">
                <text>This commentary responds to the primary article by Åste Corbridge in this volume entitled ‘Responding to Doxing in Australia: Towards a Right to Informational Self-Determination?’. It discusses the way that concepts of ‘personal information’ and ‘identification information’ from the Privacy Act 1988 (Cth) correspond with the seven crucial types of identity knowledge identified by Gary T Marx and argues that these statutory definitions should be expanded to offer better protection to victims of doxing in Australia.</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="63567">
                <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="63568">
                <text>https://ojs.unisa.edu.au/index.php/uslr/article/view/1491</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="63569">
                <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="63570">
                <text>University of South Australia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="63571">
                <text>https://ojs.unisa.edu.au/index.php/uslr/article/view/1491/927</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="63572">
                <text>Copyright (c) 2018 UniSA Student Law Review</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="63573">
                <text>University of South Australia Law Review; Vol 3 (2017/2018): UniSA Student Law Review</text>
              </elementText>
              <elementText elementTextId="63574">
                <text>2206-1398</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="63575">
                <text>personal information</text>
              </elementText>
              <elementText elementTextId="63576">
                <text>identification information</text>
              </elementText>
              <elementText elementTextId="63577">
                <text>identity knowledge</text>
              </elementText>
              <elementText elementTextId="63578">
                <text>privacy act 1988 (Cth)</text>
              </elementText>
              <elementText elementTextId="63579">
                <text>protecting identity knowledge</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="63580">
                <text>Personal Information, Identification Information, and Identity Knowledge</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="63581">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="63582">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="864" 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="16933">
                <text>Petersen, Francoise</text>
              </elementText>
              <elementText elementTextId="16934">
                <text>Bartolomeo, Giovanni</text>
              </elementText>
              <elementText elementTextId="16935">
                <text>Pluke, Mike</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="16936">
                <text>2008-09-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16937">
                <text>Personalization and effective user profile management will be critical to meet the individual usersâ?? needs and for achieving e-Inclusion and e-Accessibility. This paper outlines means to achieve the goal of the new ICT era where services and devices can be personalized by the users in order to meet their needs and preferences, in various situations. Behind every instance of personalization is a profile that stores the user preferences, context of use and other information that can be used to deliver a user experience tailored to their individual needs and preferences. Next Generation Networks (NGN) and the convergence between telephony and Internet services offer a wide range of new terminal and service definition possibilities, and a much wider range of application in society. This paper describes the personalization and profile management activities at European Telecommunications Standards Institute (ETSI) Technical Committee Human Factors, together with relevant experimentations in recent European research projects.</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="16938">
                <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="16939">
                <text>https://online-journals.org/index.php/i-jim/article/view/666</text>
              </elementText>
              <elementText elementTextId="16940">
                <text>10.3991/ijim.v2i4.666</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16941">
                <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="16942">
                <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="16943">
                <text>https://online-journals.org/index.php/i-jim/article/view/666/611</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16944">
                <text>Copyright (c) 2017 Francoise Petersen, Giovanni Bartolomeo, Mike Pluke</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="16945">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 2 No. 4 (2008); pp. 25-29</text>
              </elementText>
              <elementText elementTextId="16946">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16947">
                <text>NGN</text>
              </elementText>
              <elementText elementTextId="16948">
                <text>Personalization</text>
              </elementText>
              <elementText elementTextId="16949">
                <text>Profile Management</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16950">
                <text>Personalization and User Profile Management</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16951">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="16952">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1481" 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="30340">
                <text>Mansor, Marzita</text>
              </elementText>
              <elementText elementTextId="30341">
                <text>Adnan, Wan Adilah Wan</text>
              </elementText>
              <elementText elementTextId="30342">
                <text>Abdullah, Natrah</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="30343">
                <text>2019-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30344">
                <text>Personalization is a good supplement for learning process. It has been claimed that personalization has a huge potential of providing solution to facilitate the learning path based on children ability and preferences. Diverse research on personalized learning for children have been conducted which, are commonly concerns on the development and implementation of personalized learning products and services. However these researches have little emphasized in exploring slow learner personalized learning process particularly on their reading ability. With that, this paper aims to highlight two key important processes of personalization for slow learner children which are construction of user profile and scenario. The scope of this study is on personalization of reading for slow learner children. There were 13 slow learner children with reading difficulties from primary school participated in this study. The key findings from this study are the construction of user profile and scenario that represent the personalization for reading. These user profile and scenario construction then provide guidelines for the development of personalized interface design for slow learner reading 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="30345">
                <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="30346">
                <text>https://online-journals.org/index.php/i-jim/article/view/10775</text>
              </elementText>
              <elementText elementTextId="30347">
                <text>10.3991/ijim.v13i07.10775</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30348">
                <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="30349">
                <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="30350">
                <text>https://online-journals.org/index.php/i-jim/article/view/10775/5779</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30351">
                <text>Copyright (c) 2019 Marzita Mansor</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="30352">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 07 (2019); pp. 103-116</text>
              </elementText>
              <elementText elementTextId="30353">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30354">
                <text>Keywords- Personalized Reading</text>
              </elementText>
              <elementText elementTextId="30355">
                <text>User Profile</text>
              </elementText>
              <elementText elementTextId="30356">
                <text>Scenario</text>
              </elementText>
              <elementText elementTextId="30357">
                <text>Slow Learner</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30358">
                <text>Personalized Reading: Developing User-Describing Profile for Slow Learner Children</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="30359">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="30360">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="30361">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1033" 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="20432">
                <text>Perttula, Arttu</text>
              </elementText>
              <elementText elementTextId="20433">
                <text>Multisilta, Jari</text>
              </elementText>
              <elementText elementTextId="20434">
                <text>Tuomi, Pauliina</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="20435">
                <text>2013-01-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20436">
                <text>This paper presents an idea on how to utilize mobile phones to support learning in the classroom. The paper also tries to initiate discussion on whether we can create new kinds of learning applications using mobile devices and whether this could be the way we should proceed in developing 21st century learning applications. In this study, a mobile phone is programmed to function as a collective sound sensor. To achieve an appropriate learning atmosphere, the designed system attempts to maintain the noise level at a comfortable tolerance level in the classroom. The main aim of the mobile application is to change student behaviour through persuasive visualizations. The prototype application was piloted during spring 2012 with a total of 72 students and two teachers. The results, based on observations and interviews, are promising and several subjects for future work arose during the pilot study.</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="20437">
                <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="20438">
                <text>https://online-journals.org/index.php/i-jim/article/view/2262</text>
              </elementText>
              <elementText elementTextId="20439">
                <text>10.3991/ijim.v7i1.2262</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20440">
                <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="20441">
                <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="20442">
                <text>https://online-journals.org/index.php/i-jim/article/view/2262/2448</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20443">
                <text>Copyright (c) 2017 Arttu Perttula, Jari Multisilta, Pauliina Tuomi</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="20444">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 7 No. 1 (2013); pp. 16-24</text>
              </elementText>
              <elementText elementTextId="20445">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20446">
                <text>classroom</text>
              </elementText>
              <elementText elementTextId="20447">
                <text>mobile</text>
              </elementText>
              <elementText elementTextId="20448">
                <text>learning</text>
              </elementText>
              <elementText elementTextId="20449">
                <text>persuasion</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20450">
                <text>Persuasive Mobile Device Sound Sensing in a Classroom Setting</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20451">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="20452">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="20453">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="879" 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="17246">
                <text>Pham, Cuong Ngyuen</text>
              </elementText>
              <elementText elementTextId="17247">
                <text>Garlatti, Serge</text>
              </elementText>
              <elementText elementTextId="17248">
                <text>Lau, Simon</text>
              </elementText>
              <elementText elementTextId="17249">
                <text>Barbry, Benjamin</text>
              </elementText>
              <elementText elementTextId="17250">
                <text>Vantroys, Thomas</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="17251">
                <text>2008-12-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17252">
                <text>We are interested in learning and working scenarios integrating web service retrieval and orchestration in pervasive TEL systems in a learning situation at workplace. This paper proposes a context-aware model of corporate learning and working scenarios in e-retail environment such as shops and hypermarkets. This scenario model enables us to select how to achieve activities according to the current situation. We outline the semantic description of web services to enable the selection, composition and execution of web services to achieve objectives specified by learning and working activities. We propose a context-aware and adaptive model for pervasive learning systems. This model enables the selection of the relevant methods or services to realize activities according to the current situation. Moreover, we also build and develop an Intelligent Selling Space (ISS) architecture that serves as an infrastructure for service management and execution in e-retail environment.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17253">
                <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="17254">
                <text>https://online-journals.org/index.php/i-jim/article/view/737</text>
              </elementText>
              <elementText elementTextId="17255">
                <text>10.3991/ijim.v3i2.737</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17256">
                <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="17257">
                <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="17258">
                <text>https://online-journals.org/index.php/i-jim/article/view/737/875</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17259">
                <text>Copyright (c) 2017 Cuong Ngyuen Pham, Serge Garlatti, Simon Lau, Benjamin Barbry, Thomas Vantroys</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="17260">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 3 No. 2 (2009); pp. 25-32</text>
              </elementText>
              <elementText elementTextId="17261">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17262">
                <text>Adaptation</text>
              </elementText>
              <elementText elementTextId="17263">
                <text>Context-aware</text>
              </elementText>
              <elementText elementTextId="17264">
                <text>Hierarchical task model</text>
              </elementText>
              <elementText elementTextId="17265">
                <text>Learning and working situation</text>
              </elementText>
              <elementText elementTextId="17266">
                <text>Pervasive learning</text>
              </elementText>
              <elementText elementTextId="17267">
                <text>Service description</text>
              </elementText>
              <elementText elementTextId="17268">
                <text>Service requirement</text>
              </elementText>
              <elementText elementTextId="17269">
                <text>Task/method paradigm.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17270">
                <text>Pervasive Learning System Based on a Scenario Model Integrating Web Service Retrieval and Orchestration</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17271">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="17272">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
