<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01702nam a2200277Ia 4500</leader>
  <controlfield tag="003">MX-MdCICY</controlfield>
  <controlfield tag="005">20260521091647.0</controlfield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="c">CICY</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
    <subfield code="a">B-18980</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Governing beyond capacity: Engineering, banality, and the calibration of disaster in Mexico City</subfield>
  </datafield>
  <datafield tag="490" ind1="0" ind2=" ">
    <subfield code="v">American Ethnologist, 49(1), p.20-34, 2022</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">How are disasters made into routine, even banal parts of everyday life? In Mexico City the spatiality and temporality of disasters have become an object of dynamic governmental manipulation. The city's water engineers use a vast drainage tunnel system to strategically transform what would otherwise be catastrophic flooding of the city center into a slow-moving, spatially diffuse, and ultimately routine environmental problem for the poor on the urban periphery. Furthermore, to prevent unrest, the engineers deliberately modulate flooding within the thresholds of what populations can perceive and bear. This technopolitical work, which I call calibration, has emerged as a crucial means of governing beyond capacity, of maintaining social control even amid the unfolding of a disaster that has exceeded a government's capacity to prepare for or prevent.</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">DISASTER</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">GOVERNMENT</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">ENGINEERING</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">INFRASTRUCTURE</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">FLOODING</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">WATER</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">SPACE</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">TEMPORALITY</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">MEXICO</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Chahim, D.</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
    <subfield code="u">https://drive.google.com/file/d/1EQGfioYFISl953wMnjwJniNJ-muFrL4v/view?usp=drivesdk</subfield>
    <subfield code="z">Para ver el documento ingresa a Google con tu cuenta: @cicy.edu.mx</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">Loc</subfield>
    <subfield code="c">REF1</subfield>
  </datafield>
  <controlfield tag="008">250602s9999    xx |||||s2   |||| ||und|d</controlfield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">29061</subfield>
    <subfield code="d">29061</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">Loc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="8">F1</subfield>
    <subfield code="a">CICY</subfield>
    <subfield code="b">CICY</subfield>
    <subfield code="c">RE</subfield>
    <subfield code="d">2025-06-25</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">B-18980</subfield>
    <subfield code="r">2025-06-25 16:24:22</subfield>
    <subfield code="w">2025-06-25</subfield>
    <subfield code="y">REF1</subfield>
  </datafield>
</record>
