<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="3967" public="1" featured="0" 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://www.socictopen.socict.org/items/show/3967?output=omeka-xml" accessDate="2026-04-19T03:07:02+00:00">
  <fileContainer>
    <file fileId="3967">
      <src>https://www.socictopen.socict.org/files/original/b28b5c040da698d41de0e76489349324.pdf</src>
      <authentication>a259d678ea49e8d4daf3875a73131635</authentication>
    </file>
  </fileContainer>
  <collection collectionId="1">
    <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="1">
                <text>Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2">
                <text>Dominio científico: Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="1">
    <name>Text</name>
    <description>A resource consisting primarily of words for reading. Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre Text.</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="36324">
              <text>Latent organizing for responding to emergencies: foundations for research</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="36325">
              <text>Paul C. van Fenema, A.  Georges L. Romme</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="36326">
              <text>Abstract Time and again, many organizations and their staff members must respond to unexpected catastrophes like hurricanes (e.g., Katrina), virus pandemics (e.g., COVID-19), or other major emergencies. As a result, some organizations allow their employees to respond to external emergencies by engaging in response actions for a limited time, like in the case of emergency response teams. The latter teams consist of employees that act as emergency response officers who can respond to floods, train crashes, or other emergencies. Emergency response teams constitute an example of so-called latent organizing (LO) in the preparation for and response to any (unpredictable) future emergency. While latent organizing is ubiquitous in a societal and professional sense, it has hardly been studied in the organization design literature. In this paper, we develop a research agenda for studying LO. LO serves to prepare for and respond to emergencies, but otherwise remains largely dormant and inactive. When it is inactive, host organizations use the LO’s human and other resources for their own gainful purposes. Resources for LO are thus organized in a quasi-permanent fashion, one that is rather latent until activated by an emergency. We further develop the construct of latency to explore how effective LO can be designed and facilitated. In addition, we develop a research agenda for future work in this area.</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="36327">
              <text>2020</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="36328">
              <text>routines, Capability, Resource Management, Organization Design, Emergency Response, Latent organizing</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="36329">
              <text>DOI: 10.1186/s41469-020-00074-z</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="36330">
              <text>Journal of Organization Design</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="36331">
              <text>SpringerOpen</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="36332">
              <text>Management. Industrial management</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
