<?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=108&amp;sort_field=Dublin+Core%2CCreator" accessDate="2026-05-05T15:18:22+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>108</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1236" 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="24817">
                <text>bin Dollah, Hanafi</text>
              </elementText>
              <elementText elementTextId="24818">
                <text>Md Ghalib, Mohd Feham</text>
              </elementText>
              <elementText elementTextId="24819">
                <text>Sahrir, Muhammad Sabri bin</text>
              </elementText>
              <elementText elementTextId="24820">
                <text>Hassan, Rusni</text>
              </elementText>
              <elementText elementTextId="24821">
                <text>Zakaria, Abdul Wahab</text>
              </elementText>
              <elementText elementTextId="24822">
                <text>Omar, Zakaria</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="24823">
                <text>2017-04-27</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24824">
                <text>The existing use of mobile technology nowadays can be integrated with various forms of learning materials such as electronic books and digital references in a form of dictionary or encyclopaedia. The expansion of Islamic banking practices through various local financial institutions which received vast attention nowadays by educationists and learners for instance, leads to the need in understanding the terminologies used in the industry. In view of this scenario, the paper shed some light on using a workable model for developing a purposeful mobile Islamic banking terminology glossary application in a more convenient way via mobile devices such as iPhone, iPad or any Android-based smart gadgets. The mobile terminology glossary app was designed by using a developmental research design using via rapid prototype instructional design model. The process begun with a need analysis conducted among 225 respondents in International Islamic University Malaysia (IIUM) It further explored the prototype development and its implementations for mobile accessibility by providing multilingual glossary of Islamic banking and finance terminologies (Malay-Arabic-English). This paper reports the findings design and development prototype based on the need analysis stage, inclusive of mapping users’ device type, Internet accessibility, reasons for owning mobile devices, delivery and user interface, and preferred features to be embedded in the mobile app.</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="24825">
                <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="24826">
                <text>https://online-journals.org/index.php/i-jim/article/view/6620</text>
              </elementText>
              <elementText elementTextId="24827">
                <text>10.3991/ijim.v11i3.6620</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24828">
                <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="24829">
                <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="24830">
                <text>https://online-journals.org/index.php/i-jim/article/view/6620/4393</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24831">
                <text>Copyright (c) 2017 Hanafi bin Dollah, Mohd Feham Md Ghalib, Muhammad Sabri bin Sahrir, Rusni Hassan, Abdul Wahab Zakaria, Zakaria Omar</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="24832">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 11 No. 3 (2017); pp. 145-161</text>
              </elementText>
              <elementText elementTextId="24833">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24834">
                <text>Mobile app</text>
              </elementText>
              <elementText elementTextId="24835">
                <text>mobile learning</text>
              </elementText>
              <elementText elementTextId="24836">
                <text>Islamic Banking</text>
              </elementText>
              <elementText elementTextId="24837">
                <text>Islamic Finance</text>
              </elementText>
              <elementText elementTextId="24838">
                <text>instructional design model</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24839">
                <text>Prototype Development of Mobile App for Trilingual Islamic Banking and Finance Glossary of Terms via iOS and Android Based Devices</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24840">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="24841">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="24842">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1537" 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="31626">
                <text>Najwa Rusli, Farhatun</text>
              </elementText>
              <elementText elementTextId="31627">
                <text>Zulkifli, Abdul Nasir</text>
              </elementText>
              <elementText elementTextId="31628">
                <text>bin Saad, Mohd. Nizam</text>
              </elementText>
              <elementText elementTextId="31629">
                <text>Md.Yussop, Yussalita</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="31630">
                <text>2019-09-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="31631">
                <text>Welding is an introductory core subject that is taught in every mechanical engineering programs at all polytechnics in Malaysia. Normally students will learn the theoretical concepts of welding in the class followed by instruction based training in the workshop. �  However, students have difficulty to follow everything that has been taught in the class in a limited time. Welding is dangerous for beginners and the welding environments are harmful and injurious to the health. In this paper, we introduce Mobile Arc Welding Learning (MAWL) app, a new approach for learning arc welding that incorporates mobile technology and enhanced with augmented reality (AR). The aim of this app is to enhance the contents used in arc welding learning materials used in the conventional learning by visualizing the information through the use of text, images, videos and 3D models. The MAWL app covers topics related to safety in welding, components of welding and steps in welding. The students can use the app to learn about welding on their own anytime and anywhere. The potential of using the MAWL app for welding learning among the polytechnic students has been investigated, specifically focusing on ease of use, learnability, satisfaction, usefulness, motivation and engagement. The results of the evaluation indicate that the users strongly agreed on ease of use, learnability, satisfaction, usefulness and motivation, while they agreed on engagement. These prove that the MAWL app has the potential to contribute to students’ welding learning through interactive and accessible information that satisfies them.</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="31632">
                <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="31633">
                <text>https://online-journals.org/index.php/i-jim/article/view/11305</text>
              </elementText>
              <elementText elementTextId="31634">
                <text>10.3991/ijim.v13i10.11305</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="31635">
                <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="31636">
                <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="31637">
                <text>https://online-journals.org/index.php/i-jim/article/view/11305/5925</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="31638">
                <text>Copyright (c) 2019 Farhatun Najwa Rusli, Abdul Nasir Zulkifli, Mohd. Nizam bin Saad, Yussalita Md.Yussop</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="31639">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 10 (2019); pp. 89-105</text>
              </elementText>
              <elementText elementTextId="31640">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="31641">
                <text>Mobile Learning</text>
              </elementText>
              <elementText elementTextId="31642">
                <text>Augmented Reality</text>
              </elementText>
              <elementText elementTextId="31643">
                <text>Arc Welding Learning</text>
              </elementText>
              <elementText elementTextId="31644">
                <text>TVET</text>
              </elementText>
              <elementText elementTextId="31645">
                <text>User Evaluation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="31646">
                <text>A Study of Students’ Motivation in Using the Mobile Arc Welding Learning App</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="31647">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="31648">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="31649">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2420" 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="52124">
                <text>Gannapathy, Vigneswara Rao</text>
              </elementText>
              <elementText elementTextId="52125">
                <text>Narayanamurthy , Vigneswaran</text>
              </elementText>
              <elementText elementTextId="52126">
                <text>Subramaniam, Siva Kumar</text>
              </elementText>
              <elementText elementTextId="52127">
                <text>Bin Tuani Ibrahim , Ahamed Fayeez</text>
              </elementText>
              <elementText elementTextId="52128">
                <text>Md Isa, Ida Syafiza</text>
              </elementText>
              <elementText elementTextId="52129">
                <text>Rajkumar, Sujatha</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="52130">
                <text>2023-06-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="52131">
                <text>The&amp;nbsp;guard tour system&amp;nbsp;helps companies and organizations to monitor their security activities such as protecting people, buildings, assets, or equipment.&amp;nbsp;According to the existing system, the patrolling at each checkpoint is being executed by using RFID-based digital data loggers that records and save all patrolling entries internally. The data will be transferred manually by the guard once the patrolling is completed. In some cases, when there is a problem with the device, the system unable to retrieve the patrolling data that has been already stored in the device. In addition, the current system also not be able to track the guard’s movement, patrolling information, and incidents in real-time basis. The developed Security Guard Patrolling, Monitoring and Reporting (eSmartGuard) system is able incorporates many unique and intelligent technologies such as NFC, GPS and IoT to records and save the patrolling data automatically on the cloud/server in real-time basis. An important value-added feature of the system is real-time incidents notification that able to notify any risk of the guards instantly to the in-charged security officer. Furthermore, through the eSmartGuard, the patrolling information such as time, date, GPS coordinate, guard ID can be monitored and retrieved remotely via proposed Mobile Apps and Web at a convenient time. The eSmartGuard patrolling system is proposed to improve the safety of the people and assets by assisting the security guards to perform their patrolling duty efficiently.</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="52132">
                <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="52133">
                <text>https://online-journals.org/index.php/i-jim/article/view/35483</text>
              </elementText>
              <elementText elementTextId="52134">
                <text>10.3991/ijim.v17i11.35483</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="52135">
                <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="52136">
                <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="52137">
                <text>https://online-journals.org/index.php/i-jim/article/view/35483/13281</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="52138">
                <text>Copyright (c) 2023 Vigneswara Rao Gannapathy, Dr. Vigneswaran Narayanamurthy , Eur Ing Dr. Siva Kumar A/L Subramaniam, Dr. Ahamed Fayeez Bin Tuani Ibrahim , Dr. Ida Syafiza Md Isa, Sujatha Rajkumar</text>
              </elementText>
              <elementText elementTextId="52139">
                <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="52140">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 17 No. 11 (2023); pp. 4-14</text>
              </elementText>
              <elementText elementTextId="52141">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="52142">
                <text>guard patrolling, smartphones, Near Field Communication (NFC), Global Posi-tioning System (GPS), Internet-of-Things (IoT)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="52143">
                <text>A Mobile and Web-Based Security Guard Patrolling, Monitoring and Reporting System to Maintain Safe and Secure Environment at Premises</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="52144">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="52145">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="52146">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="597" 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="11983">
                <text>Bing, Jon</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="11984">
                <text>2013-12-18</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="11985">
                <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="11986">
                <text>https://ojs.law.cornell.edu/index.php/joal/article/view/23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11987">
                <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="11988">
                <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="11989">
                <text>https://ojs.law.cornell.edu/index.php/joal/article/view/23/27</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="11990">
                <text>Journal of Open Access to Law; Vol. 1 No. 1 (2013)</text>
              </elementText>
              <elementText elementTextId="11991">
                <text>2372-7152</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11992">
                <text>Celebrating Gnaeus Flavius and Open Access to Law</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11993">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="11994">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="602" 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="12071">
                <text>Binns, Reuben</text>
              </elementText>
              <elementText elementTextId="12072">
                <text>Millard, David</text>
              </elementText>
              <elementText elementTextId="12073">
                <text>Harris, Lisa</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="12074">
                <text>2015-03-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12075">
                <text>Data 	protection laws require organisations to be transparent about how 	they use personal data. This article explores the potential of 	machine-readable privacy notices to address this transparency 	challenge. We analyse a large source of open data comprised of 	semi-structured privacy notifications from hundreds of thousands of 	organisations in the UK, to investigate the reasons for data 	collection, the types of personal data collected and from whom, and 	the types of recipients who have access to the data. We analyse 	three specific sectors in detail; health, finance, and data 	brokerage. Finally, we draw recommendations for possible future 	applications of open data to privacy policies and transparency 	notices.</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="12076">
                <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="12077">
                <text>https://ojs.law.cornell.edu/index.php/joal/article/view/31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12078">
                <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="12079">
                <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="12080">
                <text>https://ojs.law.cornell.edu/index.php/joal/article/view/31/59</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="12081">
                <text>Journal of Open Access to Law; Vol. 3 No. 1 (2015)</text>
              </elementText>
              <elementText elementTextId="12082">
                <text>2372-7152</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12083">
                <text>open data</text>
              </elementText>
              <elementText elementTextId="12084">
                <text>transparency</text>
              </elementText>
              <elementText elementTextId="12085">
                <text>privacy</text>
              </elementText>
              <elementText elementTextId="12086">
                <text>semantic web</text>
              </elementText>
              <elementText elementTextId="12087">
                <text>Data Protection</text>
              </elementText>
              <elementText elementTextId="12088">
                <text>Privacy</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12089">
                <text>The Who, What, and Why: Data Transparency Notices in the UK</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12090">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="12091">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="12092">
                <text>Peer-reviewed article</text>
              </elementText>
              <elementText elementTextId="12093">
                <text>Empirical study</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2268" 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="48506">
                <text>Ehsan, Esra</text>
              </elementText>
              <elementText elementTextId="48507">
                <text>Ngah, Razali</text>
              </elementText>
              <elementText elementTextId="48508">
                <text>Binti Daud , Nurul Ashikin</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="48509">
                <text>2022-05-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="48510">
                <text>This document Designing system with Free-space optical (FSO) communication can supply high-speed digital data linkages to rural regions where geography, setup costs, and groundwork safety are major obstacles. Transmission impairments and space loss could be considered major challenges for handling the FSO system. This work has been designed and analyzed a system based on the combination of Dual Polarization Differential Quadrature Phase Shift Keying (DP-DQPSK) and Dense Wavelength Division Multiplexing (DWDM) using the Direct Detection (DD) technique. The proposed system has been utilized with a hybrid transmission medium of Single-Mode Fiber (SMF) with a fixed length of 60 km and FSO with varied lengths of (5, 7, and 9) km. The system was designed with Optisystem software 18 and consist of 64 channels and 14 Gbps of data rate per channel to make the system 5G communication compatible, 3.5 GHz RF electrical signals have been used to modulate the optical carrier. The channels 1,6,12, …,64 were selected as samples among all channels to be investigated and analyzed along with four different atmospheric weather conditions. Additionally, the proposed system is designed to investigate based on different weather attenuation that affected the parameters of Quality Factor (QF) and Bit Error Rate (BER). The significant advantage of the proposed system by using the DD technique, is no reference wave required. Hence, make the system become less complex and possible to be implemented and tested via different weather conditions. Results obtained indicate reverse relation between the QF and both the FSO distance and attenuation. While, BER based parameters showed a direct relation. For light air and haze, the results showed that the system have higher reliability for all the three investigated FSO distances.&amp;nbsp; For the medium haze, the system has shown capability to transfer as far as 7 km. And for the rain condition, the system capability was set to 5 km.</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="48511">
                <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="48512">
                <text>https://online-journals.org/index.php/i-jim/article/view/30127</text>
              </elementText>
              <elementText elementTextId="48513">
                <text>10.3991/ijim.v16i10.30127</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="48514">
                <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="48515">
                <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="48516">
                <text>https://online-journals.org/index.php/i-jim/article/view/30127/11367</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="48517">
                <text>Copyright (c) 2022 Haider Th.Salim Alrikabi; Esra  Ehsan, Razali  Ngah, Nurul Ashikin  Binti Daud</text>
              </elementText>
              <elementText elementTextId="48518">
                <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="48519">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 16 No. 10 (2022); pp. 223-243</text>
              </elementText>
              <elementText elementTextId="48520">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="48521">
                <text>FSO, SMF, Radio over Fiber, WDM, 5G.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="48522">
                <text>Design and Implementation of Hybrid Medium DP-DQPSK DWDM ROF Transmission System for Different Weather Conditions</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="48523">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="48524">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="48525">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="875" 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="17162">
                <text>Bischoff, Andreas</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="17163">
                <text>2008-11-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17164">
                <text>Mobile devices such as notebooks and PDAs are very interesting tools for web-based teaching and distant teaching today. We have adapted Web-based remote laboratory environments to mobile devices like PDAs and smartphones to remotely control a Pioneer 3 AT mobile robot.</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="17165">
                <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="17166">
                <text>https://online-journals.org/index.php/i-jim/article/view/703</text>
              </elementText>
              <elementText elementTextId="17167">
                <text>10.3991/ijim.v3i1.703</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17168">
                <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="17169">
                <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="17170">
                <text>https://online-journals.org/index.php/i-jim/article/view/703/771</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17171">
                <text>Copyright (c) 2017 Andreas Bischoff</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="17172">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 3 No. 1 (2009); pp. 49-52</text>
              </elementText>
              <elementText elementTextId="17173">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17174">
                <text>m-learning</text>
              </elementText>
              <elementText elementTextId="17175">
                <text>telerobotics</text>
              </elementText>
              <elementText elementTextId="17176">
                <text>distant learning</text>
              </elementText>
              <elementText elementTextId="17177">
                <text>speech recognition</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17178">
                <text>M-Learning, Mobile Experimentation and Telepresence with Cell Phones and PDAs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17179">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="17180">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="17181">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="190" 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="3696">
                <text>Ninan, Preethi Anne</text>
              </elementText>
              <elementText elementTextId="3697">
                <text>Biswas, Sudeshna</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="3698">
                <text>2022-01-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3699">
                <text>Borderline Personality Disorder (BPD) or Emotionally Unstable Personality Disorder (EUPD) clients are characterised by behavioural symptoms of acts of deliberate self-harm, difficulty controlling anger, and instability in relationships, besides others. While specific therapies address specific problem behaviours, an integrated or eclectic approach enables clinicians to adopt a comprehensive therapy plan (Livesley, 2008). Since the therapeutic relationship with BPD clients is characterised by frequent ruptures and fluctuations, it is necessary to understand how the eclectic stance approaches the therapeutic relationship with BPD clients. This study explores these questions through in-depth interviews with seven self-identified eclectic therapists who have worked with BPD clients. Using Thematic Network Analysis, it was found from the interviews that eclectic therapists choose the stance because of the flexibility it offers them, and because of definite client and setting factors. This stance, they suggested, helps in mutual decision-making and leads the therapist to make constant adjustments to the client‘s level. The process of rapport-building was seen to be an on-going process, where the therapist acts as a facilitator, and often works against resisting traits of the clients. Therapists also talked about ruptures in the relationship due to certain factors and identified means through which these can be repaired. Finally, they identified their reactions to BPD clients as consisting of both positive reactions, and negative and unconscious reactions, which require monitoring. The results of this study yield an understanding about the reasons behind the decision to take an eclectic stance, and how it affects the therapeutic relationship. Keywords: Borderline personality disorder, Eclectic therapy, Therapeutic alliance.</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="3700">
                <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="3701">
                <text>https://journals.christuniversity.in/index.php/artha/article/view/708</text>
              </elementText>
              <elementText elementTextId="3702">
                <text>10.12724/ajss.28.5</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3703">
                <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="3704">
                <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="3705">
                <text>https://journals.christuniversity.in/index.php/artha/article/view/708/527</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3706">
                <text>Copyright (c) 2016 Artha - Journal of Social Sciences</text>
              </elementText>
              <elementText elementTextId="3707">
                <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="3708">
                <text>Artha Journal of Social Sciences; Vol. 13 No. 1 (2014): Artha Journal of Social Sciences; 53-68</text>
              </elementText>
              <elementText elementTextId="3709">
                <text>0000-0000</text>
              </elementText>
              <elementText elementTextId="3710">
                <text>0975-329X</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3711">
                <text>Eclectic Therapeutic Relationship with BPD Clients: Examining the Eclectic Therapeutic Relationship with Clients with Borderline Personality Disorder</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3712">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="3713">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="3714">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2740" public="1" featured="0">
    <collection collectionId="41">
      <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="57791">
                  <text>Canadian Journal of European and Russian Studies</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="58402">
                <text>Black, Erin J.</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="58403">
                <text>2009-08-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58404">
                <text>This article follows the development of a European Union gender equality regime through three broad periods: equal treatment policies, positive action measures, and Gender Mainstreaming. The policy-making process entails conflict between competing policy frames; unequal resources behind each secures the dominance of an economic frame. Strategical framing practices have been employed by equality advocates to overcome this disadvantage. This article traces the gradual shifts in meaning within each period until equality goals are integrated into the dominant economic policy frame. It concludes that equality advocates need to engage in deeper analyses of power in order to sustain attention to equality goals over longer periods of time.
&amp;nbsp;
Full text available at: https://doi.org/10.22215/rera.v5i1.201</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="58405">
                <text>https://ojs.library.carleton.ca/index.php/CJERS/article/view/2457</text>
              </elementText>
              <elementText elementTextId="58406">
                <text>10.22215/cjers.v5i1.2457</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="58407">
                <text>Centre for European Studies, Carleton University</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="58408">
                <text>Canadian Journal of European and Russian Studies; 2009: RERA V5:1 Fall 2009 (backfile abstracts)</text>
              </elementText>
              <elementText elementTextId="58409">
                <text>2562-8429</text>
              </elementText>
              <elementText elementTextId="58410">
                <text>10.22215/cjers.v5i1</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58411">
                <text>EU Equality Commitments and Shifting Meanings of Gender Equality</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58412">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="58413">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="58414">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2818" public="1" featured="0">
    <collection collectionId="41">
      <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="57791">
                  <text>Canadian Journal of European and Russian Studies</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="59617">
                <text>Blackburn, Matthew</text>
              </elementText>
              <elementText elementTextId="59618">
                <text>Hutcheson, Derek</text>
              </elementText>
              <elementText elementTextId="59619">
                <text>Tsumarova, Elena</text>
              </elementText>
              <elementText elementTextId="59620">
                <text>Petersson , Bo</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="59621">
                <text>2023-02-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="59622">
                <text>As was the case with other federal states, Russia’s response to the COVID-19 pandemic was decentralized and devolved responsibility to regional governors. Contrary to the common highly centralized governance in Russia, this approach is thought to have helped insulate the government from criticism. Using local research and analysis based on a national representative survey carried out at the height of the pandemic during the summer of 2021, the article charts the public response to the pandemic across Russia. It examines the regionalization of the response, with an in-depth focus on two of the Russian cities with the highest infection rates but differing responses to the pandemic: St. Petersburg and Petrozavodsk. There are two main findings: at one level, the diffusion of responsibility meant little distinction was made between the different levels of government by the population; at another level, approval of the pandemic measures was tied strongly to trust levels in central and regional government.</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="59623">
                <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="59624">
                <text>https://ojs.library.carleton.ca/index.php/CJERS/article/view/3955</text>
              </elementText>
              <elementText elementTextId="59625">
                <text>10.22215/cjers.v16i1.3955</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="59626">
                <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="59627">
                <text>Centre for European Studies, Carleton University</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="59628">
                <text>https://ojs.library.carleton.ca/index.php/CJERS/article/view/3955/3193</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="59629">
                <text>Copyright (c) 2023 Canadian Journal of European and Russian Studies</text>
              </elementText>
              <elementText elementTextId="59630">
                <text>https://creativecommons.org/licenses/by-nc-nd/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="59631">
                <text>Canadian Journal of European and Russian Studies; Vol. 16 No. 1 (2023): Responses to Covid-19 Pandemic Policies ; 29-54</text>
              </elementText>
              <elementText elementTextId="59632">
                <text>2562-8429</text>
              </elementText>
              <elementText elementTextId="59633">
                <text>10.22215/cjers.v16i1</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="59634">
                <text>COVID-19</text>
              </elementText>
              <elementText elementTextId="59635">
                <text>Russia</text>
              </elementText>
              <elementText elementTextId="59636">
                <text>Governance</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="59637">
                <text>Covid-19 and the Russian Regional Response: Blame Diffusion and Attitudes to Pandemic Governance</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="59638">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="59639">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="59640">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
