<?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=33&amp;sort_field=Dublin+Core%2CCreator" accessDate="2026-05-02T03:57:30+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>33</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1731" 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="36090">
                <text>El Mrabet, Hicham</text>
              </elementText>
              <elementText elementTextId="36091">
                <text>Ait Moussa, Abdelaziz</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="36092">
                <text>2020-08-28</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36093">
                <text>Nowadays, the world has known great changes which accelerated the mode of life. Students, on their part have become to expect a stimulating and simple learning experience which takes into consideration this quick pace and helps them solve the stereotypical problems of learning. The analyses conducted in this paper revealed that the recording of attendance in classrooms is done at the expense of the teaching- learning time. Therefore, the article at hand seeks to investigate an effective means to record attendance in a way which doesn’t hinder learning. Differently put, the educational and administrative staffs need to find an effective way to record students’ attendance at presential at the beginning of each learning session without affecting the time allotted to teaching and learning. This article presents and discusses the smart attendance monitoring system in smart classroom as a means to reduce the dropout rate, using connected objects and RFID technology. This system can facilitate the recording of students’ attendance via the Internet of things (IoT) at presential while transmitting attendance record to the administration. At the same time, parents can keep track of their children's attendance to classes through a notification they receive via Email or SMS. In addition, the system automatically sends missed lessons to absent students.</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="36094">
                <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="36095">
                <text>https://online-journals.org/index.php/i-jim/article/view/14625</text>
              </elementText>
              <elementText elementTextId="36096">
                <text>10.3991/ijim.v14i14.14625</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36097">
                <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="36098">
                <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="36099">
                <text>https://online-journals.org/index.php/i-jim/article/view/14625/7731</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36100">
                <text>Copyright (c) 2020 Hicham EL MRabet, Abdelaziz AIT MOUSSA</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="36101">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 14 (2020); pp. 95-108</text>
              </elementText>
              <elementText elementTextId="36102">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36103">
                <text>School attendance system</text>
              </elementText>
              <elementText elementTextId="36104">
                <text>Smart classroom</text>
              </elementText>
              <elementText elementTextId="36105">
                <text>Smart Education</text>
              </elementText>
              <elementText elementTextId="36106">
                <text>RFID Tags</text>
              </elementText>
              <elementText elementTextId="36107">
                <text>Internet of things</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36108">
                <text>IoT-School Attendance System Using RFID Technology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36109">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="36110">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="36111">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2633" public="1" featured="0">
    <collection collectionId="39">
      <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="56344">
                  <text>The University of Queensland Law Journal</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="56691">
                <text>Aitken, Lee</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="56692">
                <text>2020-05-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="56693">
                <text>This eponymous book on the general part of the law of contract will be the standard Australian work for some time to come. It aims to provide a guide to that legion of legal readers ‘who are searching for basic statements of contract law’.</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="56694">
                <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="56695">
                <text>https://journal.law.uq.edu.au/index.php/uqlj/article/view/3899</text>
              </elementText>
              <elementText elementTextId="56696">
                <text>10.38127/uqlj.v39i1.3899</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="56697">
                <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="56698">
                <text>The University of Queensland School of Law</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="56699">
                <text>https://journal.law.uq.edu.au/index.php/uqlj/article/view/3899/3399</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="56700">
                <text>Copyright (c) 2020 The University of Queensland Law Journal</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="56701">
                <text>The University of Queensland Law Journal; Vol. 39 No. 1 (2020): The University of Queensland Law Journal; 152-156</text>
              </elementText>
              <elementText elementTextId="56702">
                <text>1839-289X</text>
              </elementText>
              <elementText elementTextId="56703">
                <text>0083-4041</text>
              </elementText>
              <elementText elementTextId="56704">
                <text>10.38127/uqlj.v39i1</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="56705">
                <text>Heydon on Contract</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="56706">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="56707">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="56708">
                <text>Book review</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2662" public="1" featured="0">
    <collection collectionId="39">
      <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="56344">
                  <text>The University of Queensland Law Journal</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="57214">
                <text>Aitken, Lee</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="57215">
                <text>2021-08-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="57216">
                <text>To realise that there is no Court in Australia with unlimited jurisdiction is at one stroke to recognise the continuing importance of Justice Leeming’s standard work, and the relevance of this second edition. The ‘autochthonous expedient’, as Sir Owen Dixon named it, has much to answer for: it leads inexorably to a bifurcated system of state and federal courts, which has many toils and snares for the unwary. To compound the problem, the state courts enjoy a large amount of ‘invested’ federal jurisdiction, which means that on many occasions they exercise it without appreciating the fact that they have done so.</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="57217">
                <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="57218">
                <text>https://journal.law.uq.edu.au/index.php/uqlj/article/view/5777</text>
              </elementText>
              <elementText elementTextId="57219">
                <text>10.38127/uqlj.v40i2.5777</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="57220">
                <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="57221">
                <text>The University of Queensland School of Law</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="57222">
                <text>https://journal.law.uq.edu.au/index.php/uqlj/article/view/5777/4731</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="57223">
                <text>Copyright (c) 2021 The University of Queensland Law Journal</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="57224">
                <text>The University of Queensland Law Journal; Vol. 40 No. 2 (2021): The University of Queensland Law Journal; 306-309</text>
              </elementText>
              <elementText elementTextId="57225">
                <text>1839-289X</text>
              </elementText>
              <elementText elementTextId="57226">
                <text>0083-4041</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="57227">
                <text>Authority to Decide: The Law of Jurisdiction in Australia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="57228">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="57229">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="57230">
                <text>Book review</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1083" 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="21514">
                <text>Aitkenhead, Matt</text>
              </elementText>
              <elementText elementTextId="21515">
                <text>Donnelly, David</text>
              </elementText>
              <elementText elementTextId="21516">
                <text>Coull, Malcolm</text>
              </elementText>
              <elementText elementTextId="21517">
                <text>Hastings, Emily</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="21518">
                <text>2014-04-05</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21519">
                <text>In recent years, the use of mobile phones and tablets for personal communication has increased dramatically, with over 1 billion smartphones out of a total of 5 billion mobile phones worldwide.  The infrastructure and technology underlying these devices has improved to a level where it is now possible to integrate sensor technology directly and use them to acquire new data.  Given the available resources and the number of technical challenges that have already been overcome, it would seem a natural progression to use mobile communication technology for field-based environmental monitoring.  In this work, we review existing technology for acquiring, processing and reporting on environmental data in the field.  The objective is to demonstrate whether or not it is possible to use off-the-shelf technology for environmental monitoring.  We show several levels at which this challenge is being approached, and discuss examples of technology that have been produced.</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="21520">
                <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="21521">
                <text>https://online-journals.org/index.php/i-jim/article/view/3645</text>
              </elementText>
              <elementText elementTextId="21522">
                <text>10.3991/ijim.v8i2.3645</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21523">
                <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="21524">
                <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="21525">
                <text>https://online-journals.org/index.php/i-jim/article/view/3645/3118</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21526">
                <text>Copyright (c) 2017 Matt Aitkenhead, David Donnelly, Malcolm Coull, Emily Hastings</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="21527">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 8 No. 2 (2014); pp. 42-50</text>
              </elementText>
              <elementText elementTextId="21528">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21529">
                <text>Environmental monitoring</text>
              </elementText>
              <elementText elementTextId="21530">
                <text>mobile technology</text>
              </elementText>
              <elementText elementTextId="21531">
                <text>apps</text>
              </elementText>
              <elementText elementTextId="21532">
                <text>sensors</text>
              </elementText>
              <elementText elementTextId="21533">
                <text>mobile phones</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21534">
                <text>Innovations in Environmental Monitoring Using Mobile Phone Technology – A Review</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21535">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="21536">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="21537">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2346" 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="50367">
                <text>Daineko, Yevgeniya</text>
              </elementText>
              <elementText elementTextId="50368">
                <text>Tsoy, Dana</text>
              </elementText>
              <elementText elementTextId="50369">
                <text>Ipalakova, Madina</text>
              </elementText>
              <elementText elementTextId="50370">
                <text>Kozhakhmetova, Bagdat</text>
              </elementText>
              <elementText elementTextId="50371">
                <text>Aitmagambetov, Altay</text>
              </elementText>
              <elementText elementTextId="50372">
                <text>Kulakayeva, Aigul</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="50373">
                <text>2022-10-19</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50374">
                <text>Currently, we are witnessing the active introduction of modern digital technologies in the field of education. One of the main reasons for this was the transition to distance learning due to the global COVID-19 pandemic. More and more virtual labs, virtual textbooks, as well as educational platforms that allow students to acquire the necessary skills and abilities remotely using the Internet, are being used in the educational process.
The most promising educational platform is an interactive mobile learning platform. It has several advantages, among which one can especially single out the convenience of learning due to its interactivity and organization of the studied material. The application of augmented and virtual reality allows for increasing the effectiveness of classes. These technologies provide another level of interaction and material perception by students. However, VR and its high level of immersion require special equipment and more actions from the user while AR is cheaper and more affordable, but still interactive and has great visual aids. The aim of the paper is to demonstrate how augmented reality can be used for radio engineering disciplines on the example of an interactive mobile platform.  
This article discusses the process of developing a mobile platform that allows studying the material of radio engineering courses using augmented reality technology. The work also contains the results of a survey conducted among the students who used it as a part of their class activities. In addition, sections of the article contain a description of the project development process, its structure, international experience, and the conclusions.</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="50375">
                <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="50376">
                <text>https://online-journals.org/index.php/i-jim/article/view/32373</text>
              </elementText>
              <elementText elementTextId="50377">
                <text>10.3991/ijim.v16i19.32373</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50378">
                <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="50379">
                <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="50380">
                <text>https://online-journals.org/index.php/i-jim/article/view/32373/12113</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50381">
                <text>Copyright (c) 2022 Dana Tsoy, Yevgeniya Daineko, Madina Ipalakova, Bagdat Kozhakhmetova, Altay Aitmagambetov, Aigul Kulakayeva</text>
              </elementText>
              <elementText elementTextId="50382">
                <text>https://creativecommons.org/licenses/by/4.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="50383">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 16 No. 19 (2022); pp. 147-162</text>
              </elementText>
              <elementText elementTextId="50384">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50385">
                <text>mobile interactive platform</text>
              </elementText>
              <elementText elementTextId="50386">
                <text>mobile application</text>
              </elementText>
              <elementText elementTextId="50387">
                <text>augmented reality</text>
              </elementText>
              <elementText elementTextId="50388">
                <text>Unity3D</text>
              </elementText>
              <elementText elementTextId="50389">
                <text>physics</text>
              </elementText>
              <elementText elementTextId="50390">
                <text>radio engineering disciplines</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50391">
                <text>Development of an Interactive Mobile Platform for Studying Radio Engineering Disciplines Using Augmented Reality Technology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50392">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="50393">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="50394">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2364" 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="50794">
                <text>Ajallouda, Lahbib</text>
              </elementText>
              <elementText elementTextId="50795">
                <text>Fagroud, Fatima Zahra</text>
              </elementText>
              <elementText elementTextId="50796">
                <text>Zellou, Ahmed</text>
              </elementText>
              <elementText elementTextId="50797">
                <text>Benlahmar, El habib</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="50798">
                <text>2022-08-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50799">
                <text>The keyphrases of a document are the textual units that characterize its content such as the topics it addresses, its ideas, their field, etc. Thousands of books, articles and web pages are published every day. Manually extracting keyphrases is a tedious task and takes a lot of time. Automatic keyphrases extraction is an area of text mining that aims to identify the most useful and important phrases that give meaning to the content of a document. Keyphrases can be used in many Natural Language Processing (NLP) applications, such as text summarization, text clustering and text classification. This article provides a Systematic Literature Review (SLR) to investigate, analyze, and discuss existing relevant contributions and efforts that use new concepts and tools to improve keyphrase extraction. We have studied the supervised and unsupervised approaches to extracting keyphrases published in the period 2015-2022. We have also identified the steps most commonly used by the different approaches. Additionally, we looked at the criteria that should be evaluated to improve the accuracy of keyphrases extraction. Each selected approach was evaluated for its ability to extract keyphrases. Our findings highlight the importance of keyphrase extraction, and provide researchers and practitioners with information about proposed solutions and their limitations, which contributes to extract keyphrases in a powerful and meaningful way effective.</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="50800">
                <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="50801">
                <text>https://online-journals.org/index.php/i-jim/article/view/33081</text>
              </elementText>
              <elementText elementTextId="50802">
                <text>10.3991/ijim.v16i16.33081</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50803">
                <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="50804">
                <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="50805">
                <text>https://online-journals.org/index.php/i-jim/article/view/33081/11871</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50806">
                <text>Copyright (c) 2022 Lahbib AJALLOUDA, Phd Student Fatima Zahra Fagroud, Dr. Ahmed Zellou, Dr. El habib  Benlahmar</text>
              </elementText>
              <elementText elementTextId="50807">
                <text>https://creativecommons.org/licenses/by/4.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="50808">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 16 No. 16 (2022); pp. 31-58</text>
              </elementText>
              <elementText elementTextId="50809">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50810">
                <text>Keyphrases extraction</text>
              </elementText>
              <elementText elementTextId="50811">
                <text>Systematic literature review</text>
              </elementText>
              <elementText elementTextId="50812">
                <text>Text mining</text>
              </elementText>
              <elementText elementTextId="50813">
                <text>Natural language processing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50814">
                <text>A Systematic Literature Review of Keyphrases Extraction Approaches</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50815">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="50816">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="50817">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="605" public="1" featured="0">
    <collection collectionId="28">
      <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="11779">
                  <text>Journal of Open Access to Law</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="45">
              <name>Publisher</name>
              <description>An entity responsible for making the resource available</description>
              <elementTextContainer>
                <elementText elementTextId="12877">
                  <text>Cornell University</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="12147">
                <text>Ajayi, Efg</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="12148">
                <text>2015-03-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12149">
                <text>The mobile telephone alternatively referred to as mobile handset, has immense advantages over the traditional land line telephone in that it enables the user to traverse wherever he desires, and yet able to communicate with others either for purposes of transacting businesses or as a means of effecting social interactions, but notwithstanding the apparent advantages of mobile phones, like every coin having two sides, its use has demerits which as a matter of necessity, calls for regulatory measures to protect the subscribers; unfortunately, this is not the case in most African countries, for example, Nigeria reputed for the highest population in Africa ditto the highest number of mobile telephone subscribers in addition to being the biggest economy in the continent, does not have in place, law and policy specifically aimed at protecting or promoting the interest of its subscribers. The usage of mobile phones has assumed phenomenal increase recently; it is the norm rather than the exception in Africa but with the unfortunate trend of dearth of legal and regulatory measures. This Article deals with the legal and regulatory framework pertaining to mobile phones and examines issues relating to or consequences generated thereof. The paper argues that the extant legal and regulatory framework in Africa is not in the best interest of subscribers,’ and calls for a paradigm shift towards taking into cognizance the said interest of subscribers’ by governments’ with the view to putting in place, legal and regulatory precepts simply because the manufacturers of mobile phones and telephony companies, wherever they are situate or operate from, need and rely on the profits generated from African countries. Keywords: Telecommunications law and policy, mobile phone, consumer protection, Africa</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="12150">
                <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="12151">
                <text>https://ojs.law.cornell.edu/index.php/joal/article/view/37</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12152">
                <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="12153">
                <text>Journal of Open Access to Law</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="12154">
                <text>https://ojs.law.cornell.edu/index.php/joal/article/view/37/55</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="12155">
                <text>Journal of Open Access to Law; Vol. 3 No. 1 (2015)</text>
              </elementText>
              <elementText elementTextId="12156">
                <text>2372-7152</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12157">
                <text>Telecommunications law and policy to protect subscribers’ of mobile phones in Africa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12158">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="12159">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="12160">
                <text>Peer-reviewed article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="850" 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="16638">
                <text>Daoudi, Najima</text>
              </elementText>
              <elementText elementTextId="16639">
                <text>Ajhoun, Rachida</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="16640">
                <text>2008-05-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16641">
                <text>The exploitation of technological advances in learning has result in an exponential progress in this field through e-learning applications in the last decade, and currently through the emergence of a new concept called m-learning. M-learning is defined as the use of mobile technologies for learning; m-learning must benefit from e-learning technological advances in order to avoid reinventing the wheel. Nevertheless, m-learning, which is characterized by the use of mobile devices, permits, for example, the learners' mobility during their learning, and, as opposed to e-learning, allows a continuous change of the context. Moreover, m-learning faces some constraints caused by the use of its mobile technologies such as the limited screen size, reduced energy, resolution capacity and location change during an activity. Yet, there is an agreement among most research laboratories interested in e- and m- learning on the parallel use of these two learning environments. Therefore, it would be more sensible to allow communication and exchanges, to facilitate the sharing of learning subject matters and data between the two environments, and thereby to avoid the reproduction of contents that already exist. In other words, an educational heritage which is exploitable independently of the environment of its development must be created. The utilization of standards can offer pedagogical contents some structures which facilitate the interchangeability between e- and m- learning. In order to ensure the interoperability between e- and â??m learning platforms and to take into account the specificities of m-learning, we have adopted the already existing standard LOM and the specification IMS LD.</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="16642">
                <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="16643">
                <text>https://online-journals.org/index.php/i-jim/article/view/286</text>
              </elementText>
              <elementText elementTextId="16644">
                <text>10.3991/ijim.v2i3.286</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16645">
                <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="16646">
                <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="16647">
                <text>https://online-journals.org/index.php/i-jim/article/view/286/472</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16648">
                <text>Copyright (c) 2017 Najima Daoudi, Rachida Ajhoun</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="16649">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 2 No. 3 (2008); pp. 11-16</text>
              </elementText>
              <elementText elementTextId="16650">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16651">
                <text>e-learning</text>
              </elementText>
              <elementText elementTextId="16652">
                <text>interoperability</text>
              </elementText>
              <elementText elementTextId="16653">
                <text>m-learning</text>
              </elementText>
              <elementText elementTextId="16654">
                <text>LOM</text>
              </elementText>
              <elementText elementTextId="16655">
                <text>IMS LD</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16656">
                <text>An Adaptation of E-learning Standards to M-learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16657">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="16658">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2343" 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="50295">
                <text>Sandoussi, Rima</text>
              </elementText>
              <elementText elementTextId="50296">
                <text>Hnida, Meriem</text>
              </elementText>
              <elementText elementTextId="50297">
                <text>Daoudi, Najima</text>
              </elementText>
              <elementText elementTextId="50298">
                <text>Ajhoun, Rachida</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="50299">
                <text>2022-10-03</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50300">
                <text>background: In recent years, recommender systems (RS) have grown in popularity among learning and education stakeholders, while open educational resources (OER) have begun to be deployed to improve the education field. The selection of OERs should not be haphazard; rather, it should be based on the learning objectives and (RS) commonly utilized to overcome the abundance of OER. Objective: The aim of this paper is to examine the current advances in OER recommenders and the different commonly used recommendation approaches and technical features, to position our future research alongside the existing. Method: A systematic literature review with a deductive approach using the grounded theory technique, combining quantitative and qualitative analysis by adopting open coding (inductive and deductive) for content analysis. Databases: we employed Google Scholar as a search engine to crawl data. Results: The findings are presented according to the (Bernard, H. Russell .2000) process. We present the results of the analysis using quotes from interviews that illuminate the theory (exemplars). Conclusion: The review reveals an emerging interest in the area; nevertheless, hybrid interactive systems; chatbot-based, dedicated to course creators are lacking. Further and future research is needed</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="50301">
                <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="50302">
                <text>https://online-journals.org/index.php/i-jim/article/view/32197</text>
              </elementText>
              <elementText elementTextId="50303">
                <text>10.3991/ijim.v16i18.32197</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50304">
                <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="50305">
                <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="50306">
                <text>https://online-journals.org/index.php/i-jim/article/view/32197/12023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50307">
                <text>Copyright (c) 2022 rima sandoussi</text>
              </elementText>
              <elementText elementTextId="50308">
                <text>https://creativecommons.org/licenses/by/4.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="50309">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 16 No. 18 (2022); pp. 44-77</text>
              </elementText>
              <elementText elementTextId="50310">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50311">
                <text>Recommender Systems</text>
              </elementText>
              <elementText elementTextId="50312">
                <text>Open Educational Resources</text>
              </elementText>
              <elementText elementTextId="50313">
                <text>Systematic literature review</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50314">
                <text>Systematic Literature Review on Open Educational Resources Recommender Systems</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="50315">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="50316">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="50317">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1683" 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="34983">
                <text>Hussien, Naseer Ali</text>
              </elementText>
              <elementText elementTextId="34984">
                <text>alsaidi, Saif abd alradha</text>
              </elementText>
              <elementText elementTextId="34985">
                <text>Ajlan, Iman Kadhim</text>
              </elementText>
              <elementText elementTextId="34986">
                <text>Mohamed Firdhous, Mohamed Fazil</text>
              </elementText>
              <elementText elementTextId="34987">
                <text>Alrikabi, Haider TH. Salim</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="34988">
                <text>2020-03-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34989">
                <text>The Internet of Things (IoT) incorporates most extensive number of innovations and imagines a mixture of things or questions around us that, through one of a kind tending to plans and standard correspondence conventions, consume the ability to connect through one another's also collaborate by their neighbors in the direction of attain regular purposes. The misuse of such a standard has been broadly explored in Internet-related investigates. As a result, a few plans have been suggested that utilization informal organizations to hunt Internet assets, to course activity, or to choose powerful strategies for substance dissemination. The essential understood this knowledge remains persistent locality everywhere us as a diverse carrier of things or articles – i.e. Radio-Frequency identification (RFID) sensors, labels, cellular telephones, actuators, and more – that finished novel inclining to ideas, consume the ability to subordinate through one another besides chip in through their neighbors to realize normal objectives of shopping situation in business sector. Web of Things (IoT) overpowered standard imperfection for structure code, which backing to shopping in business sector or undertaking gathering of most prominent concern and examinant. </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="34990">
                <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="34991">
                <text>https://online-journals.org/index.php/i-jim/article/view/13511</text>
              </elementText>
              <elementText elementTextId="34992">
                <text>10.3991/ijim.v14i04.13511</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34993">
                <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="34994">
                <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="34995">
                <text>https://online-journals.org/index.php/i-jim/article/view/13511/6623</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34996">
                <text>Copyright (c) 2020 Naseer Ali Hussien, Iman Kadhim Ajlan, Saif abd alradha alsaidi, Haider Alrikabi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="34997">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 04 (2020); pp. 17-29</text>
              </elementText>
              <elementText elementTextId="34998">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34999">
                <text>RFID Innovation</text>
              </elementText>
              <elementText elementTextId="35000">
                <text>Internet of Things</text>
              </elementText>
              <elementText elementTextId="35001">
                <text>Future Application</text>
              </elementText>
              <elementText elementTextId="35002">
                <text>Shopping</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35003">
                <text>Smart Shopping System with RFID Technology Based on Internet of Things</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35004">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="35005">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="35006">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
