<?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;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-16T11:15:15+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>1</pageNumber>
      <perPage>10</perPage>
      <totalResults>15</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="8689" public="1" featured="1">
    <fileContainer>
      <file fileId="8713">
        <src>https://repository.horizon.ac.id/files/original/87f357c4ef85b6c7ff9a0269f94dd8a4.pdf</src>
        <authentication>56224b99dcde0002880a516335b1674c</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="93272">
                <text>Building relational confidence in remote and hybrid work&#13;
arrangements: novel ways to use digital technologies to&#13;
foster knowledge sharing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93273">
                <text>relational confidence, communication visibility, enterprise social media, knowledge sharing, anticipatory communication</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93274">
                <text>Remote and hybrid workers know fewer of their colleagues and have fewer strong workplace relationships. If strong relationships support&#13;
knowledge sharing, workers will have a harder time getting knowledge they need. Prior research shows that digital communication technologies&#13;
increase workers’ network-level knowledge of “who knows what” and “who knows who.” Yet, knowledge seekers may be hesitant to ask for&#13;
knowledge, particularly when they have concerns that their relationship with a knowledge source is too distant. We conduct a dyad-level study&#13;
&#13;
of 141 instances of knowledge seeking among employees of a South American telecommunications company employing a hybrid work arrange-&#13;
ment and using an enterprise social media called Chatter. We find that specific uses of the technology help develop what we call “relational con-&#13;
fidence,” or the confidence that one has a close enough relationship to a colleague to ask and get needed knowledge. With greater relational&#13;
&#13;
confidence, knowledge sharing is more successful.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93275">
                <text>Samantha M. Keppler1&#13;
&#13;
, Paul M. Leonardi2,*</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="93276">
                <text>https://doi.org/10.1093/jcmc/zmad020</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="93277">
                <text>14 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="93278">
                <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="93279">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93280">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93281">
                <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="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="8690" public="1" featured="1">
    <fileContainer>
      <file fileId="8714">
        <src>https://repository.horizon.ac.id/files/original/b59513b61ae602b4c5bc091ba3cad7b3.pdf</src>
        <authentication>e2e793a4d3bf1a3ed775a47d5f79e4da</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="93282">
                <text>Facts are hard to come by: discerning and sharing factual&#13;
information on social media</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93283">
                <text>Keywords: misinformation, epistemic vigilance, social endorsement, content–attitude congruity, reflective thinking</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93284">
                <text>How credulous are we when engaging information on social media? Addressing this question, this article aims to understand how individuals’ ep-&#13;
istemic vigilance, a set of cognitive mechanisms that comprise our system of precaution in social interactions, may operate and fall short.&#13;
&#13;
Reporting findings from two survey experiments (Study 1, N 1⁄4 413; Study 2, N 1⁄4 392), we show that participants tended to be skeptical toward&#13;
social media news, were reasonably successful in identifying true news, and reported a tendency to share true rather than false news. In one&#13;
study, social endorsement enticed a higher accuracy rating of news posts. In both studies, people judged attitudinally congruent news posts as&#13;
being more accurate and reported a higher likelihood to share them. Individuals’ propensity to reflective thinking measured by cognitive reflection&#13;
test potentially operated as a restraint on sharing inaccurate information and bolstered veracity anchoring in their information engagement.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93285">
                <text>Fangjing Tu 1,*, Zhongdang Pan1&#13;
&#13;
, Xinle Jia</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="93286">
                <text>https://doi.org/10.1093/jcmc/zmad021</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="93287">
                <text>1 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="93288">
                <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="93289">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93290">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93291">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8694" public="1" featured="1">
    <fileContainer>
      <file fileId="8718">
        <src>https://repository.horizon.ac.id/files/original/fd0b765b27039788ffeeb76b1d653ed0.pdf</src>
        <authentication>75f3a87639bb53b081642dc0f975b85c</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="93322">
                <text>Information sharing in a hybrid workplace: understanding&#13;
the role of ease-of-use perceptions of communication&#13;
technologies in advice-seeking relationship maintenance</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93323">
                <text>Keywords: media multiplexity theory, relationship maintenance, advice networks, communication technology, hybrid work, SAOMs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93324">
                <text>Shifts to hybrid work prompted by the COVID-19 pandemic have the potential to substantially impact social relationships at work. Hybrid&#13;
employees rely heavily on digital collaboration technologies to communicate and share information. Therefore, employees’ perceptions of the&#13;
&#13;
technologies are critical in shaping organizational networks. However, the dyadic-level misalignment in these perceptions may lead to relation-&#13;
ship dissolution. To explore the social network consequences of hybrid work, we conducted a two-wave survey in a department of an industrial&#13;
&#13;
manufacturing firm (N 1⁄4 169). Our results show that advice seekers were less likely to maintain their advice-seeking ties when they had a&#13;
mismatch in ease-of-use perceptions of technology with their advisors. The effect was more substantial when advice seekers spent more&#13;
time working remotely. The study provides empirical insights into how congruence in employees’ perceptions of organizational communication&#13;
technologies affects how they maintain advice networks during hybrid work.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93325">
                <text>Y. Jasmine Wu 1,*, Brennan Antone 2,3, Leslie DeChurch 1&#13;
&#13;
, Noshir Contractor</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="93326">
                <text>https://doi.org/10.1093/jcmc/zmad025</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="93327">
                <text>11 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="93328">
                <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="93329">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93330">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93331">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8688" public="1" featured="1">
    <fileContainer>
      <file fileId="8712">
        <src>https://repository.horizon.ac.id/files/original/6a4d6727209b51c8e067f6837cace539.pdf</src>
        <authentication>226dc7ad9d485d691e571344927db65c</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="93262">
                <text>Managing collapsed boundaries in global work</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93263">
                <text>affordances, boundary management, communication technology, global work, remote work, office space</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93264">
                <text>Global workers have long contended with the challenges of working across geographical, temporal, and cultural boundaries enabled by communi-&#13;
cation technologies. However, the global work research has rarely intersected with the literature on work–home boundary management—which&#13;
&#13;
has been brought to the forefront due to the forced move to remote work during the Covid-19 pandemic. Drawing on a qualitative field study of&#13;
&#13;
55 in-depth interviews with global workers from a large organization headquartered in the Nordics, we found that global workers drew on socio-&#13;
material affordances to manage both global work and work–home boundaries through strategies of boundary support and boundary collapse.&#13;
&#13;
Although the shift to remote work created challenges due to boundary collapse, it presented new spatiotemporal affordances that led to unex-&#13;
pected benefits for both global work and work–life boundary management. The findings have implications for global work, remote work, and the&#13;
&#13;
future of work more broadly.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93265">
                <text>Anu Sivunen 1,*, Jennifer L. Gibbs 2&#13;
&#13;
, Jonna Leppa ̈ kumpu</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="93266">
                <text>https://doi.org/10.1093/jcmc/zmad019</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="93267">
                <text>11 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="93268">
                <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="93269">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93270">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93271">
                <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>
  <item itemId="8693" public="1" featured="1">
    <fileContainer>
      <file fileId="8717">
        <src>https://repository.horizon.ac.id/files/original/3fad50b75bb44c0cc4564c2f3287d23a.pdf</src>
        <authentication>ee1981e175634a34b6e16fb7f2d9d08b</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="93312">
                <text>Positioning in a collaboration network and performance in&#13;
competitions: a case study of Kaggle</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93313">
                <text>collaboration networks, virtual teams, online competition, data science, online communities</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93314">
                <text>Online innovation competitions are ecosystems where institutions source numerous solutions from knowledge workers through a platform&#13;
intermediary. By considering how an individual competitor’s performance varies based on their social positioning in a competition ecosystem’s&#13;
collaboration network, we illustrate the value of social networks for individual outcomes in online competitions. The study reports results from&#13;
Kaggle, a popular online competition platform for data science, where a sample of 350,956 users participated in 2,789 competitions over 4 years.&#13;
We investigate how the number of collaborations, membership in the largest connected component in the network, and diversity of collaboration&#13;
experiences impact the points and medals earned and how quickly competitors earn their first medal. Results show that positioning has a&#13;
positive relationship with performance in competitive ecosystems. Relevant to the future of work, the study considers how knowledge workers&#13;
in future workplaces should manage their online collaborations.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93315">
                <text>Marlon Twyman 1,*, Goran Muric2&#13;
&#13;
, Weiwei Zheng3</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="93316">
                <text>https://doi.org/10.1093/jcmc/zmad024</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="93317">
                <text>9 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="93318">
                <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="93319">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93320">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93321">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8696" public="1" featured="1">
    <fileContainer>
      <file fileId="8720">
        <src>https://repository.horizon.ac.id/files/original/495ad75deebbf32cff01228ab387a13e.pdf</src>
        <authentication>6620751fab7c8507f174b55cb7316857</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="93342">
                <text>Pre-framing an emerging technology before it is deployed&#13;
at work: the case of artificial intelligence and radiology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93343">
                <text>artificial intelligence, frame, framing, future of work, technological promises</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93344">
                <text>Various occupations are increasingly confronted with promises that new technologies will transform their work long before these technologies&#13;
&#13;
are deployed in their workplace. Although we know how new technologies are framed when they are introduced to work, we have limited under-&#13;
standing of how practitioners frame an emerging technology before it is deployed. Building on frame literature and examining the case of artificial&#13;
&#13;
intelligence (AI) in diagnostic radiology, I show how radiologists go beyond technological promises by engaging in constructing multiple frames&#13;
ex ante (pre-frames). These pre-frames are neither technology-centric nor work-centric, but rather are dialectic technology–work frames, through&#13;
which their accounts of both technology and work are simultaneously (re)constructed. They not only help radiologists settle around certain ways&#13;
&#13;
of relating AI to their work, but also unsettle their accounts by unearthing unresolved debates, raising new questions, and impelling them to con-&#13;
sider divergent reaction strategies.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93345">
                <text>Mohammad Hosein Rezazade Mehrizi</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="93346">
                <text>https://doi.org/10.1093/jcmc/zmad029</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="93347">
                <text>22 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="93348">
                <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="93349">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93350">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93351">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8692" public="1" featured="1">
    <fileContainer>
      <file fileId="8716">
        <src>https://repository.horizon.ac.id/files/original/0a08b52d63fd76395eb2bbe5e3e72ae4.pdf</src>
        <authentication>ec29563d894e339d7597c4d5a6155751</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="93302">
                <text>Signaling and meaning in organizational analytics: coping&#13;
with Goodhart’s Law in an era of digitization and&#13;
datafication</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93303">
                <text>analytics, data, signaling, metrics, measurement, commensuration</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93304">
                <text>The future of work will be measured. The increasing and widespread adoption of analytics, the use of digital inputs and outputs to inform organi-&#13;
zational decision making, makes the communication of data central to organizing. This article applies and extends signaling theory to provide a&#13;
&#13;
framework for the study of analytics as communication. We report three cases that offer examples of dubious, selective, and ambiguous signal-&#13;
ing in the activities of workers seeking to shape the meaning of data within the practice of analytics. The analysis casts the future of work as a&#13;
&#13;
game of strategic moves between organizations, seeking to measure behaviors and quantify the performance of work, and workers, altering their&#13;
&#13;
behavioral signaling to meet situated goals. The framework developed offers a guide for future examinations of the asymmetric relationship be-&#13;
tween management and workers as organizations adopt metrics to monitor and evaluate work.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93305">
                <text>Jeffrey W. Treem 1,*, William C. Barley 2&#13;
&#13;
, Matthew S. Weber3&#13;
&#13;
, Joshua B. Barbour</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="93306">
                <text>https://doi.org/10.1093/jcmc/zmad023</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="93307">
                <text>11 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="93308">
                <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="93309">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93310">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93311">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
