<?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://repository.horizon.ac.id/items/browse?collection=626&amp;output=omeka-xml" accessDate="2026-04-25T15:10:00+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>1</pageNumber>
      <perPage>10</perPage>
      <totalResults>13</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="8747" public="1" featured="1">
    <fileContainer>
      <file fileId="8771">
        <src>https://repository.horizon.ac.id/files/original/db91cc1b5fa964dfe902c47870facaa6.pdf</src>
        <authentication>513d6708e23fbceae1ec5b2472875e66</authentication>
      </file>
    </fileContainer>
    <collection collectionId="626">
      <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="93689">
                  <text>VOL 28 ISSUE 5 2023</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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93931">
                <text>Attitudinal and behavioral correlates of algorithmic&#13;
awareness among German and U.S. social media users</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93932">
                <text>algorithmic literacy, algorithmic awareness, algorithmic attitudes, algorithmic divide, social media algorithms</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93933">
                <text>With the increase in algorithms on social media, scholarship is increasingly focused on “algorithmic literacy,” or users’ understanding of&#13;
algorithms. Algorithmic literacy is multi-faceted (knowledge, attitudes, and behavior), and researchers are still uncovering how these facets are&#13;
connected. This article presents a preregistered survey of social media users from two western countries: the United States (n 1⁄4 990) and&#13;
Germany (n 1⁄4 1117). Results show key predictors of algorithmic awareness—age, education, frequency of social media use—are the same in&#13;
both countries. Nevertheless, U.S. social media users show higher algorithmic awareness and more positive attitudes toward algorithms than&#13;
German social media users, likely due to their higher overall social media usage. Results also indicate that algorithmic awareness predicts&#13;
attitudes about filtering algorithms depending on users’ defense motivations or accuracy motivations and behaviors to counteract filtering. These&#13;
patterns have implications for literacy interventions and for increasing algorithmic transparency.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93934">
                <text>Anne Oeldorf-Hirsch 1,*, German Neubaum</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="93935">
                <text>https://doi.org/10.1093/jcmc/zmad035</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="93936">
                <text>17 July 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93937">
                <text>PERI IRAWAN</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="93938">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93939">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93940">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8746" public="1" featured="1">
    <fileContainer>
      <file fileId="8770">
        <src>https://repository.horizon.ac.id/files/original/7f7c23a70b68c4bc8c2628baec7c8f3b.pdf</src>
        <authentication>f007dfb91c7a2ae9fbe64a4026c4674d</authentication>
      </file>
    </fileContainer>
    <collection collectionId="626">
      <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="93689">
                  <text>VOL 28 ISSUE 5 2023</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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93921">
                <text>No judgment: value optimization and the reinvention of&#13;
reviewing on YouTube</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93922">
                <text>creators, evaluation, platforms, platformized cultural production, optimization, reviews, values, YouTube</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93923">
                <text>Social media platforms employ algorithmic recommendations to optimize the user’s experience and incentivize particular forms of cultural pro-&#13;
duction. While prior research shows that creators respond to these incentives and seek to optimize their content in return, the normative implica-&#13;
tions of this process are ambiguous and contentious. To examine the values promoted by platforms, this study focuses on YouTube reviews, a&#13;
&#13;
popular genre that crosses communities and foregrounds values. Employing content and thematic analyses of 200 videos, I find that creators&#13;
communicate value consistently: good products are aesthetic, functional, distinctive, and either pleasurable or resonant, while good reviewers&#13;
are relatable above all else. I develop the concept of value optimization to refer to communicative strategies that appeal to the perceived values&#13;
of a platform and show how creators’ tendency to qualify their evaluations and avoid strong judgments transforms the historical function of&#13;
reviewing. Finally, I discuss implications for future research on the platformization of cultural production.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93924">
                <text>Blake Hallinan</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="93925">
                <text>https://doi.org/10.1093/jcmc/zmad034</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="93926">
                <text>22 June 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93927">
                <text>PERI IRAWAN</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="93928">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93929">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93930">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8744" public="1" featured="1">
    <fileContainer>
      <file fileId="8768">
        <src>https://repository.horizon.ac.id/files/original/9c1b7dd8a95e5fc13a902e3349601393.pdf</src>
        <authentication>b648b7321fd179882252ca245b531c36</authentication>
      </file>
    </fileContainer>
    <collection collectionId="626">
      <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="93689">
                  <text>VOL 28 ISSUE 5 2023</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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93898">
                <text>Sensors as media and sensor-mediated communication: an&#13;
introduction to the special issue</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93899">
                <text>sensors, media, sensor-mediated communication, technology adoption, ubiquitous computing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93900">
                <text>This special issue examines mediated communication through the rise of sensors. Sensors are increasingly in the phones we carry, in the cars&#13;
&#13;
we drive, and throughout the homes and communities in which we live. In this introduction to the special issue, we define sensor-mediated com-&#13;
munication (SMC) and argue the embedded, automatic, and datafied nature of sensors belie the glitches and biases in sensor mechanisms,&#13;
&#13;
networks, and infrastructure. The collection of articles in this issue explores SMC across a variety of contexts and cases, including municipal&#13;
infrastructure, community, health, industry, and the domestic. They represent studies of voice assistants, self-tracking apps, self-driving cars,&#13;
fitness games, home health care, as well as municipal sensor networks in urban, indigenous, and rural communities. Across them all we see the&#13;
different ways through which mediated communication is initiated, transformed, and maintained by sensing technologies. Together they&#13;
represent an important evolution in the study of computer-mediated communication.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93901">
                <text>Didem O ̈ zkul 1,*, Germaine R. Halegoua 2&#13;
&#13;
, Rowan Wilken 3&#13;
&#13;
, Lee Humphreys</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="93902">
                <text>https://doi.org/10.1093/jcmc/zmad033</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="93903">
                <text>Oxford University Press on behalf of International Communication Association.</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="93904">
                <text>18 July 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93905">
                <text>PERI IRAWAN</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="93906">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93907">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93908">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8742" public="1" featured="1">
    <fileContainer>
      <file fileId="8766">
        <src>https://repository.horizon.ac.id/files/original/ec63b2fbdb918012a5e77ec5637bbeef.pdf</src>
        <authentication>c62d06afee96b01980e06c0a353f72ef</authentication>
      </file>
    </fileContainer>
    <collection collectionId="626">
      <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="93689">
                  <text>VOL 28 ISSUE 5 2023</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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93877">
                <text>Digital parenting divides: the role of parental capital and&#13;
digital parenting readiness in parental digital mediation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93878">
                <text>digital divides, parental mediation, social media, personal capital, digital parenting</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93879">
                <text>This study investigates digital parenting divides, or how parents’ strategies for regulating their children’s online activities differ based on their&#13;
available resources and digital parenting readiness (i.e., digital parenting self-efficacy, attitudes, and knowledge). We conducted a survey of 530&#13;
&#13;
parents that reflected the composition of the U.S. population to explore how parents’ resources and digital parenting readiness predict their digi-&#13;
tal mediation strategies. The results indicate that parents’ economic, social, and cultural resources, as well as their digital parenting readiness,&#13;
&#13;
play a significant role in how they approach digital mediation. Furthermore, digital parenting readiness has emerged as an underlying mechanism&#13;
explaining the relationship between parental resources and parental mediation strategies. The presence of digital parenting divides highlights the&#13;
need for tailored interventions to support parents in effectively using digital mediation strategies based on their family’s circumstances.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93880">
                <text>Pengfei Zhao1,*, Natalie N. Bazarova1&#13;
&#13;
, Natercia Valle2</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="93881">
                <text>https://doi.org/10.1093/jcmc/zmad032</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="93882">
                <text>Oxford University Press on behalf of International Communication Association.</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="93883">
                <text>30 May 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93884">
                <text>PERI IRAWAN</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="93885">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93886">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93887">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8740" public="1" featured="1">
    <fileContainer>
      <file fileId="8764">
        <src>https://repository.horizon.ac.id/files/original/d21107df722746ee3278c43ee133b661.pdf</src>
        <authentication>4a8c21abaea6fe9e7cd0fda0af1294d9</authentication>
      </file>
    </fileContainer>
    <collection collectionId="626">
      <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="93689">
                  <text>VOL 28 ISSUE 5 2023</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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93854">
                <text>Nalaquq (“it is found”): a knowledge co-production&#13;
framework for environmental sensing and communication&#13;
in Indigenous arctic communities</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93855">
                <text>sensors, citizen science, Yup’ik, climate change, Indigenous, communication</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93856">
                <text>In 2007, the Yup’ik village of Quinhagak contacted archaeologists after locals found precontact artifacts on a nearby beach. This collaboration led&#13;
to the subsequent excavation of Nunalleq, an important ancestral site threatened by climate change. Since then, an international research team&#13;
has partnered with Yup’ik leadership in Quinhagak to address the larger impact of climate change. In turn, this article introduces Nalaquq—our&#13;
framework for combining custom sensor networks with traditional knowledge to study ellavut (trans. “Our land and weather”). Doing so provides&#13;
a guide for communication scholars interested in working alongside Indigenous circumpolar communities to visualize and communicate climate&#13;
science.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93857">
                <text>Sean Gleason 1,2,*, Jonathan Lim 2,3, Lynn Marie Church2&#13;
&#13;
, Warren Jones4&#13;
&#13;
, Carl Nicolai5&#13;
,&#13;
&#13;
Joe Pleasant6&#13;
&#13;
, Willard Church6&#13;
&#13;
, Alice Watterson 7&#13;
&#13;
, Lonny Alaskuk Strunk8&#13;
&#13;
, Richard Knecht2,9&#13;
&#13;
Charlotta Hillerdal</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="93858">
                <text>https://doi.org/10.1093/jcmc/zmad030</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="93859">
                <text>Oxford University Press on behalf of International Communication Association.</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="93860">
                <text>23 May 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93861">
                <text>PERI IRAWAN</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="93862">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93863">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93864">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8738" public="1" featured="1">
    <fileContainer>
      <file fileId="8762">
        <src>https://repository.horizon.ac.id/files/original/6d08e49f4a4955aecddc4443bb7766a0.pdf</src>
        <authentication>fcd93482cf1471ce973f8c110c30f3e7</authentication>
      </file>
    </fileContainer>
    <collection collectionId="626">
      <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="93689">
                  <text>VOL 28 ISSUE 5 2023</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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93832">
                <text>To intervene or not to intervene: young adults’ views on&#13;
when and how to intervene in online harassment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93833">
                <text>social networking sites, online communities, qualitative methods, young adults, bystanders</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93834">
                <text>Incidents of online harassment are increasing and can have significant consequences for victims. Witnesses (“digital bystanders”) can be crucial&#13;
in identifying and challenging harassment. This study considered when and how young adults intervene online, with the aim of understanding&#13;
the applicability of existing theoretical models (i.e., Bystander Intervention Model; Response Decision-Making Framework). Thematic analysis of&#13;
eight focus groups (UK community sample, N 1⁄4 67, 18–25 years) resulted in five themes: Noticing and Interpreting the Harassment, Perceived&#13;
Responsibility for Helping, Consequences of Intervening, Perceived Ability to Make a Difference, and Deciding How to Help. The online context&#13;
&#13;
amplified offline preferences, such as greater preference for anonymity and perceived costs of intervention (e.g., social costs). Intervention strat-&#13;
egies varied in visibility and effort, preferring “indirect” micro-interventions focused on supporting victims. A new, merged model specific to digi-&#13;
tal bystanders is proposed, with implications for the design and messaging on social networking sites discussed.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93835">
                <text>Anna Davidovic1,*, Catherine Talbot 2&#13;
&#13;
, Catherine Hamilton-Giachritsis3&#13;
&#13;
, Adam Joinson1</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="93836">
                <text>https://doi.org/10.1093/jcmc/zmad027</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="93837">
                <text>17 May 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93838">
                <text>PERI IRAWAN</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="93839">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93840">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93841">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8737" public="1" featured="1">
    <fileContainer>
      <file fileId="8761">
        <src>https://repository.horizon.ac.id/files/original/68156b4c8a589300b5ebaaceb7d05c96.pdf</src>
        <authentication>81f4241f2b667bcc62b3ee9e9fd092f8</authentication>
      </file>
    </fileContainer>
    <collection collectionId="626">
      <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="93689">
                  <text>VOL 28 ISSUE 5 2023</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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93822">
                <text>Sensing technologies, digital inclusion, and disability&#13;
diversity</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93823">
                <text>sensory technologies, disability, cultural diversity, intersectionality, critical disability study</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93824">
                <text>This article focuses on uses and experiences of everyday sensory technologies by racially and ethnically diverse persons with disabilites, bringing&#13;
our research to the junction of critical technology studies, migration studies, and critical disability studies. We draw on a large-scale qualitative&#13;
project that involves new and second-generation migrants with disabilities from a socio-economically disadvantaged area in Sydney, Australia.&#13;
&#13;
Findings show the negotiated exchanges of inclusion and exclusion that disabled people from diverse racial and ethnic minority backgrounds en-&#13;
counter with sensory and other technologies. While such technologies have rightfully been criticized for their roles in the surveillance, regulation,&#13;
&#13;
exclusion, and financialization of disability and ethnically diverse groups, these negotiations show how processes of agency, awareness, and&#13;
peer support produce and in turn benefit from encounters with technology in complex ways. We argue the continued emergence of automation&#13;
warrants both critique and cautious ongoing experimentation.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93825">
                <text>Sarah Nectoux1,*, Liam Magee1&#13;
&#13;
, Karen Soldatic1</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="93826">
                <text>https://doi.org/10.1093/jcmc/zmad026</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="93827">
                <text>21 April 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93828">
                <text>PERI IRAWAN</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="93829">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93830">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93831">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8733" public="1" featured="1">
    <fileContainer>
      <file fileId="8757">
        <src>https://repository.horizon.ac.id/files/original/616390d7635cdf6f961889ef37baf51f.pdf</src>
        <authentication>7f89554383b3d354b4819e78a58dc4c7</authentication>
      </file>
    </fileContainer>
    <collection collectionId="626">
      <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="93689">
                  <text>VOL 28 ISSUE 5 2023</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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93780">
                <text>“Sensing” productivity at home: self-tracking&#13;
technologies, gender, and labor in Turkey</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93781">
                <text>self-tracking, sensors, domestic labor, productivity, home–workplace separation, neoliberal/digital capitalism, gender</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93782">
                <text>This article explores how women in Turkey use sensing technologies to render visible their productivity at home in ways that contest home–&#13;
workplace boundary under neoliberal, digital capitalism. It does so by focusing on a group of lower- and middle-class women, who work from&#13;
&#13;
home as both paid laborers and unpaid caregivers. Although neoliberalism makes it harder to distinguish home and workplace, my digital ethnog-&#13;
raphy highlights that women working from home feel a home–workplace separation that renders invisible their productivity. By translating em-&#13;
bodied knowledge into quantified data, smartwatches provide women with new information that I call revelations. Women share these revela-&#13;
tions on digital platforms to render visible their productivity at home in ways that transgress the home–workplace boundary. By exploring these&#13;
&#13;
revelations as moments of “otherwise,” this article highlights both when smartwatches reproduce neoliberal mentality and become tools for&#13;
others in the public to register its exploitative consequences.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93783">
                <text>Nazlı O ̈ zkan1,*</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="93784">
                <text>https://doi.org/10.1093/jcmc/zmad017</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="93785">
                <text>20 April 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93786">
                <text>PERI IRAWAN</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="93787">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93788">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93789">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8732" public="1" featured="1">
    <fileContainer>
      <file fileId="8756">
        <src>https://repository.horizon.ac.id/files/original/454ca68017cc470489f050d5e0b53c65.pdf</src>
        <authentication>e6d612050a62be13795b14ba945150bf</authentication>
      </file>
    </fileContainer>
    <collection collectionId="626">
      <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="93689">
                  <text>VOL 28 ISSUE 5 2023</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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93769">
                <text>Digital governance with smart sensors: exploring grid&#13;
administration in Zhejiang’s “Future Community”</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93770">
                <text>China, smart sensors, digital governance, e-government in everyday practice, grid members</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93771">
                <text>This study explored sensor-based e-government practices in eight pilot “Future Communities” in Zhejiang Province, China. Adopting the ap-&#13;
proach of “e-government in everyday practice,” it examines how grid members at the grassroots level make sense of smart sensors and their&#13;
&#13;
mediated governance through the parameters of passive response, collaborative human and nonhuman networks, and calculability. In an emerg-&#13;
ing sensing environment, grid members are exposed to contradictory governance regimes, experimenting with and performing competing sets&#13;
&#13;
of discourses and actions that are either efficient or inefficient, manual or automatic, and progressive or regressive. Neither facilitated nor emp-&#13;
tied by sensor-enabled Weberian functions, they actively improvise along with the dynamism of specific local interactions and situations.&#13;
&#13;
However, currently sensors and attendant technologies merely leave space for them to engage in ambiguities and negotiations concerning the&#13;
extent and boundaries of technical solutionism rather than opening up possibilities for empowerment to refine the forms of governance.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93772">
                <text>Yuchao Zhao</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="93773">
                <text>https://doi.org/10.1093/jcmc/zmad016</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="93774">
                <text>20 April 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93775">
                <text>PERI IRAWAN</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="93776">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93777">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93778">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8730" public="1" featured="1">
    <fileContainer>
      <file fileId="8754">
        <src>https://repository.horizon.ac.id/files/original/f903984c226604e5e5360f646472eb39.pdf</src>
        <authentication>f6be132bdfce1f00ad06918050a77bff</authentication>
      </file>
    </fileContainer>
    <collection collectionId="626">
      <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="93689">
                  <text>VOL 28 ISSUE 5 2023</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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93746">
                <text>Sensor work: enabling the interoperation of&#13;
autonomous vehicles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93747">
                <text>sensing, autonomous driving, interoperability, sensor work, machine vision, AI</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93748">
                <text>This article examines the “sensor work” carried out in the development of autonomous vehicles which, without sensor data, would not and&#13;
arguably still do not, have the capacity to decide on where, and how, to drive. I begin by discussing three aspects of sensor technologies&#13;
considered to be the foundation for sensor work being carried out in autonomous vehicle settings, namely the distribution, processing, and&#13;
sourcing of sensor technologies and sensor data. The article considers how that much of this sensor work aids not only the operation of&#13;
autonomous vehicles but also their necessary “interoperation.” In studying four specific sensing methods from an operational perspective,&#13;
I consider how the interoperation between sensing devices and subsequent algorithmic, object-recognition, and motion planning procedures is&#13;
fundamental to the development of autonomous vehicles.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93749">
                <text>Sam Hind</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="93750">
                <text>https://doi.org/10.1093/jcmc/zmad014</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="93751">
                <text>Oxford University Press on behalf of International Communication Association.</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="93752">
                <text>5 April 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93753">
                <text>PERI IRAWAN</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="93754">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93755">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93756">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
