<?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=618&amp;output=omeka-xml&amp;page=2" accessDate="2026-04-14T17:59:14+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>2</pageNumber>
      <perPage>10</perPage>
      <totalResults>15</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="8687" public="1" featured="1">
    <fileContainer>
      <file fileId="8711">
        <src>https://repository.horizon.ac.id/files/original/feccab1b45fe70e188cc09d3b9efa4a1.pdf</src>
        <authentication>c0831916f6584204f6b1a77147011c88</authentication>
      </file>
    </fileContainer>
    <collection collectionId="618">
      <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="93211">
                  <text>VOL 28 ISSUE 4 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="93252">
                <text>Differential perceptions of and reactions to incivil and&#13;
intolerant user comments</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93253">
                <text>incivility, intolerance, online discussions, user comments, social media, experimental research, multiverse analysis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93254">
                <text>Building on recent research that challenges the notion that norm violations in online discussions are inherently detrimental, this study relies on a&#13;
&#13;
distinction between incivil and intolerant user comments and investigates how online users perceive and react to these distinct forms of antinor-&#13;
mative discourse online. Conducting a preregistered factorial survey experiment with a nationally representative sample of n 1⁄4 964 German&#13;
&#13;
online users, we presented participants with manipulated user comments that included statements associated with incivil (profanity; attacks to-&#13;
ward arguments) and intolerant discourse (offensive stereotyping; violent threats). The results show that intolerant statements consistently lead&#13;
&#13;
to higher perceptions of offensiveness and harm to society as well as an increased intention to delete the comment containing the statement,&#13;
&#13;
whereas incivil statements do not. An exploratory multiverse analysis further suggests that these effects remain robust across a variety of analyt-&#13;
ical decisions.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93255">
                <text>Anna Sophie Ku ̈ mpel 1,*, Julian Unkel</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="93256">
                <text>https://doi.org/10.1093/jcmc/zmad018</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="93257">
                <text>28 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="93258">
                <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="93259">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93260">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93261">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8686" public="1" featured="1">
    <fileContainer>
      <file fileId="8710">
        <src>https://repository.horizon.ac.id/files/original/307dbc0fc02057795deb9a2715cfc78e.pdf</src>
        <authentication>53e008d5a8ed858f1999c814ea86eae4</authentication>
      </file>
    </fileContainer>
    <collection collectionId="618">
      <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="93211">
                  <text>VOL 28 ISSUE 4 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="93242">
                <text>Transparency, openness and privacy among software&#13;
professionals: discourses and practices surrounding use&#13;
of the digital calendar</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93243">
                <text>groupware calendar systems, workplace calendar use, transparency, privacy, digital calendar</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93244">
                <text>Research on the groupware calendar system (GCS) has sought to understand its situated use in workplace contexts, revealing insights around&#13;
design, culture, and self-understanding. A critical look at how knowledge workers use the GCS, and conceptualize of this use, reveals often&#13;
overlooked sociotechnical values that figure prominently in workers’ lives. At a time when the public–private entanglement has become top-of-mind,&#13;
this article adds to research on the GCS and professional subjectivity. It shows how organizational values circulate through use of the GCS and&#13;
explores how hierarchy is negotiated on it, in part through design. It finds that senior-level workers are afforded opportunities to make their calendars&#13;
private, while nonsenior workers are met with frustration when doing so. The article draws from a multi-sited ethnography, focusing on interviews&#13;
with software workers in Canada. Findings suggest that the logistical functions of the GCS shape the affective dimensions related to its use.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93245">
                <text>Vanessa Ciccone</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="93246">
                <text>https://doi.org/10.1093/jcmc/zmad015</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="93247">
                <text>3 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="93248">
                <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="93249">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93250">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93251">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8685" public="1" featured="1">
    <fileContainer>
      <file fileId="8709">
        <src>https://repository.horizon.ac.id/files/original/99393254eb842dddc8b2965128159252.pdf</src>
        <authentication>4ec44a32abc1d4b9fec81e268ce64371</authentication>
      </file>
    </fileContainer>
    <collection collectionId="618">
      <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="93211">
                  <text>VOL 28 ISSUE 4 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="93232">
                <text>Community health workers and the communicative&#13;
transformation of work-life interrelationships during&#13;
the COVID-19 pandemic</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93233">
                <text>Work-life, ICTs, in-depth interviews, community health workers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93234">
                <text>This study focuses on work-life interrelationships for community health workers (CHWs) during the COVID-19 pandemic. CHWs serve as liaisons&#13;
between marginalized communities and health and human service organizations to facilitate access to services. Required physical distancing&#13;
transformed their work from embodied, face-to-face interaction to almost wholly mediated by communication technologies. Interviews were&#13;
conducted with 52 participants to identify CHWs’ adaptive strategies for communication, consequences of their adaptations for their experience&#13;
of work and work-life interrelationships, and their communicative management of negative unintended consequences. Communicative practices&#13;
that were emergent from participant accounts are examined through the lenses of four mutually informing research frameworks: the impact of&#13;
technologically mediated remote work on work-life interrelationships, technological capital and differentiated digital inequalities, the text work/&#13;
&#13;
body work continuum, and gendered emotional work. Implications for the future of community-based care workers and for other workers with re-&#13;
spect to communication, technology, and managing work-life boundaries are examined.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93235">
                <text>Annis G. Golden1&#13;
&#13;
*, Jane Jorgenson2&#13;
&#13;
, Amy Williams1</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="93236">
                <text>https://doi.org/10.1093/jcmc/zmad009</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="93237">
                <text>6 March 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="93238">
                <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="93239">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93240">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93241">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8684" public="1" featured="1">
    <fileContainer>
      <file fileId="8708">
        <src>https://repository.horizon.ac.id/files/original/b901af65142d297e66c72565b20a7b32.pdf</src>
        <authentication>0575b1e234b2ee04ce823e28d807bf15</authentication>
      </file>
    </fileContainer>
    <collection collectionId="618">
      <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="93211">
                  <text>VOL 28 ISSUE 4 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="93222">
                <text>Surveillance and the future of work: exploring employees’&#13;
attitudes toward monitoring in a post-COVID workplace</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93223">
                <text>workplace surveillance, future of work, information and communication technologies, privacy, contextual integrity</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93224">
                <text>The future of work increasingly focuses on the collection and analysis of worker data to monitor communication, ensure productivity, reduce se-&#13;
curity threats, and assist in decision-making. The COVID-19 pandemic increased employer reliance on these technologies; however, the blurring&#13;
&#13;
of home and work boundaries meant these monitoring tools might also surveil private spaces. To explore workers’ attitudes toward increased&#13;
monitoring practices, we present findings from a factorial vignette survey of 645 U.S. adults who worked from home during the early months of&#13;
&#13;
the pandemic. Using the theory of privacy as contextual integrity to guide the survey design and analysis, we unpack the types of workplace sur-&#13;
veillance practices that violate privacy norms and consider attitudinal differences between male and female workers. Our findings highlight that&#13;
&#13;
the acceptability of workplace surveillance practices is highly contextual, and that reductions in privacy and autonomy at work may further exac-&#13;
erbate power imbalances, especially for vulnerable employees.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93225">
                <text>Jessica Vitak 1&#13;
&#13;
, Michael Zimmer</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="93226">
                <text>https://doi.org/10.1093/jcmc/zmad007</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="93227">
                <text>7 March 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="93228">
                <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="93229">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93230">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93231">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8683" public="1" featured="1">
    <fileContainer>
      <file fileId="8707">
        <src>https://repository.horizon.ac.id/files/original/3fae2501f401352dccd52c42e256991f.pdf</src>
        <authentication>f0127e788b5d5082d238bcba1f8bf8ab</authentication>
      </file>
    </fileContainer>
    <collection collectionId="618">
      <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="93211">
                  <text>VOL 28 ISSUE 4 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="93212">
                <text>Navigating the empty shell: the role of articulation&#13;
work in platform structures</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93213">
                <text>platform studies, articulation work, telehealth, mental and behavioral health, scale</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93214">
                <text>This article explores platform workers’ strategies for producing sustainable, quality services within platform structures that simultaneously over-&#13;
and under-determine their work. We present findings from interviews with U.S.-based mental health professionals (n 1⁄4 48) working on telether-&#13;
apy platforms. These therapists describe navigating both the presence of platformic controls and the absence of features supporting professional&#13;
&#13;
best practices and regulatory requirements. We describe this absence as the “empty shell” characteristic of platforms and argue that it is a cen-&#13;
tral technique through which platforms create scale. Our findings detail the communicative strategies therapists employ to navigate the empty&#13;
&#13;
shell and provide quality care to their clients. These strategies can be seen as a form of “articulation work,” a concept drawn from the sociology&#13;
of work. Attending to articulation work in an emerging platform labor context, such as teletherapy, contributes to our understanding of the politics&#13;
of platforms.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93215">
                <text>Linda Huber 1,*, Casey Pierce1</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="93216">
                <text>https://doi.org/10.1093/jcmc/zmad004</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="93217">
                <text>Accepted: 27 February 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="93218">
                <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="93219">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93220">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93221">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
