<?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://www.april16.vtlibraries.net/items/browse?output=omeka-xml&amp;page=47&amp;sort_field=added" accessDate="2026-04-08T08:44:24+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>47</pageNumber>
      <perPage>20</perPage>
      <totalResults>1884</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1007" public="1" featured="0">
    <fileContainer>
      <file fileId="510">
        <src>https://www.april16.vtlibraries.net/files/original/P1010020_e4aa483447.JPG</src>
        <authentication>null</authentication>
        <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="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14895">
                    <text>2007-08-12</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16015">
                    <text>2007-08-12 22:52:56</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2309">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4200">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6178">
                <text>2007-08-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8056">
                <text>View of the intermediate memorial in front of Burruss Hall. At the time of this photo, volunteers were cleaning up the site, moving some mementos to storage and others to the newly completed center of the memorial. Other parts of the memorial space were still under construction. Photo taken July 6, 2007.&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc-sa/3.0/"&gt;Creative Commons Attribution-NonCommercial-ShareAlike 3.0&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10027">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11933">
                <text>Creative Commons Attribution-NonCommercial-ShareAlike 3.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13428">
                <text>Transitional Memorial</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1341">
        <name> burruss</name>
      </tag>
      <tag tagId="1256">
        <name> construction</name>
      </tag>
      <tag tagId="1255">
        <name> drillfield</name>
      </tag>
      <tag tagId="664">
        <name>intermediate memorial</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="550" public="1" featured="0">
    <fileContainer>
      <file fileId="346">
        <src>https://www.april16.vtlibraries.net/files/original/P1000809_9ec2405879.JPG</src>
        <authentication>null</authentication>
        <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="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14739">
                    <text>2007-06-17</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15859">
                    <text>2007-06-17 20:18:41</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1879">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3770">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5748">
                <text>2007-06-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7626">
                <text>After April 16, plastic daisies have regularly been laid down at various places on the drillfield in the shape of the VT logo, near the temporary memorial in front of Burruss Hall. This photo was taken on Thursday, June 14.&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc-sa/3.0/"&gt;Creative Commons Attribution-NonCommercial-ShareAlike 3.0&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9597">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11585">
                <text>Creative Commons Attribution-NonCommercial-ShareAlike 3.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13041">
                <text>VT Daisies (Redux)</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="77">
        <name>burruss</name>
      </tag>
      <tag tagId="667">
        <name>daisies</name>
      </tag>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="31">
        <name>flowers</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1011" public="1" featured="0">
    <fileContainer>
      <file fileId="514">
        <src>https://www.april16.vtlibraries.net/files/original/P1010032_23e89e0f8b.JPG</src>
        <authentication>null</authentication>
        <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="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14899">
                    <text>2007-08-13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16019">
                    <text>2007-08-13 09:18:52</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2313">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4204">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6182">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8060">
                <text>Bags of plastic flowers sit on a walkway at the new intermediate memorial. Hokie stones for Nicole White, Daniel O&amp;#39;Neil, and Seung-Hui Cho (unmarked) are visible to the right. At the time of this this photo, staff members and volunteers were cleaning up the site, moving some mementos to storage and others to this area, the newly completed center of the memorial. Other parts of the intermediate memorial were still under construction. Photo taken July 6, 2007.&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc-sa/3.0/"&gt;Creative Commons Attribution-NonCommercial-ShareAlike 3.0&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10031">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11937">
                <text>Creative Commons Attribution-NonCommercial-ShareAlike 3.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13432">
                <text>Plastic Flowers and Hokie Stones</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1345">
        <name> cho</name>
      </tag>
      <tag tagId="1256">
        <name> construction</name>
      </tag>
      <tag tagId="1346">
        <name> flowers</name>
      </tag>
      <tag tagId="1347">
        <name> hokie stones</name>
      </tag>
      <tag tagId="1342">
        <name> intermediate memorial</name>
      </tag>
      <tag tagId="1344">
        <name> oneil</name>
      </tag>
      <tag tagId="108">
        <name>white</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1010" public="1" featured="0">
    <fileContainer>
      <file fileId="513">
        <src>https://www.april16.vtlibraries.net/files/original/P1010029_119f4e4138.JPG</src>
        <authentication>null</authentication>
        <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="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14898">
                    <text>2007-08-13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16018">
                    <text>2007-08-13 09:12:56</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2312">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4203">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6181">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8059">
                <text>A pile of mementos in front of construction fencing at the intermediate memorial site. At the time of this photo, staff members and volunteers were cleaning up the site, moving some items to storage and others to the newly completed center of the memorial. Photo taken July 6, 2007.&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc-sa/3.0/"&gt;Creative Commons Attribution-NonCommercial-ShareAlike 3.0&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10030">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11936">
                <text>Creative Commons Attribution-NonCommercial-ShareAlike 3.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13431">
                <text>Memorial Mementos</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1256">
        <name> construction</name>
      </tag>
      <tag tagId="1343">
        <name> mementos</name>
      </tag>
      <tag tagId="664">
        <name>intermediate memorial</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1009" public="1" featured="0">
    <fileContainer>
      <file fileId="512">
        <src>https://www.april16.vtlibraries.net/files/original/P1010026b_205060284f.jpg</src>
        <authentication>null</authentication>
        <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="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14897">
                    <text>2007-08-13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16017">
                    <text>2007-08-13 09:10:17</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2311">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4202">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6180">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8058">
                <text>View of the intermediate memorial in front of Burruss Hall. In the foreground lay a pile of memento items. At the time of this photo, staff and volunteers - including the student shown in this photo - were cleaning up the site, moving some items to storage and others to the new center of the memorial, shown in the middle of this photograph. Other parts of the memorial were still under construction. Photo taken July 6, 2007.&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc-sa/3.0/"&gt;Creative Commons Attribution-NonCommercial-ShareAlike 3.0&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10029">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11935">
                <text>Creative Commons Attribution-NonCommercial-ShareAlike 3.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13430">
                <text>Mementos and Memorial</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1256">
        <name> construction</name>
      </tag>
      <tag tagId="1342">
        <name> intermediate memorial</name>
      </tag>
      <tag tagId="1343">
        <name> mementos</name>
      </tag>
      <tag tagId="77">
        <name>burruss</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1008" public="1" featured="0">
    <fileContainer>
      <file fileId="511">
        <src>https://www.april16.vtlibraries.net/files/original/P1010021b_81ecd57c4b.jpg</src>
        <authentication>null</authentication>
        <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="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14896">
                    <text>2007-08-13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16016">
                    <text>2007-08-13 09:05:41</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2310">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4201">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6179">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8057">
                <text>Daisies and mementos lay on the ground near the intermediate memorial construction site, on the drillfield in front of Burruss Hall. At the time of this photo, volunteers and staff members  were cleaning up the area, moving some items to storage and other mementos to the newly finished center of the memorial. Photo taken July 6, 2007.&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc-sa/3.0/"&gt;Creative Commons Attribution-NonCommercial-ShareAlike 3.0&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10028">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11934">
                <text>Creative Commons Attribution-NonCommercial-ShareAlike 3.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13429">
                <text>Daisies and Mementos</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1256">
        <name> construction</name>
      </tag>
      <tag tagId="1255">
        <name> drillfield</name>
      </tag>
      <tag tagId="1342">
        <name> intermediate memorial</name>
      </tag>
      <tag tagId="1343">
        <name> mementos</name>
      </tag>
      <tag tagId="31">
        <name>flowers</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1012" public="1" featured="0">
    <fileContainer>
      <file fileId="515">
        <src>https://www.april16.vtlibraries.net/files/original/P1010038_e66a6b6f23.JPG</src>
        <authentication>null</authentication>
        <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="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14900">
                    <text>2007-08-13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16020">
                    <text>2007-08-13 09:26:45</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2314">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4205">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6183">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8061">
                <text>View of the newly finished center of the intermediate memorial, on the drillfield in front of Burruss Hall. Hokie stones - one for each victim - are arranged in an arc. At the time of this photo, volunteers and staff members  were cleaning up the area, moving some mementos to storage and other items to this area. Photo taken July 6, 2007.&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc-sa/3.0/"&gt;Creative Commons Attribution-NonCommercial-ShareAlike 3.0&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10032">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11938">
                <text>Creative Commons Attribution-NonCommercial-ShareAlike 3.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13433">
                <text>Intermediate Memorial In Transition</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1256">
        <name> construction</name>
      </tag>
      <tag tagId="1347">
        <name> hokie stones</name>
      </tag>
      <tag tagId="1343">
        <name> mementos</name>
      </tag>
      <tag tagId="664">
        <name>intermediate memorial</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1013" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2315">
                <text>Elva Orozco</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4206">
                <text>La Raza Newspaper</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6184">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8062">
                <text>Publicado por La Raza Newspaper&#13;
06-14-2007 &#13;
&#13;
Washington, D.C. (EFE).â€” Un comitÃ© creado por el presidente de Estados Unidos, George W. Bush, para estudiar la matanza en la Universidad virginia tech recomendÃ³ ayer controlar mejor a las "personas peligrosas", pero no pidiÃ³ endurecer las leyes para restringir el acceso a las armas. &#13;
&#13;
El informe dice que todos los estados deberÃ­an enviar los datos de personas que no pueden poseer armas por problemas mentales a una lista nacional de la Oficina Federal de Investigaciones (FBI) denominada Sistema de ComprobaciÃ³n Inmediata de Antecedentes Penales (NICS). &#13;
&#13;
Actualmente, sÃ³lo 23 de los 50 estados del paÃ­s envÃ­an esa informaciÃ³n. &#13;
&#13;
El estado de Virginia no enviÃ³ al NICS los datos de Cho Seung-Hui, un estudiante coreano de 23 aÃ±os que habÃ­a sido sometido a tratamiento psiquiÃ¡trico. &#13;
&#13;
Sus problemas mentales deberÃ­an haberle impedido comprar las dos armas que usÃ³ para matar en abril a 32 estudiantes y profesores en la Universidad PolitÃ©cnica, pero Cho pudo adquirirlas legalmente porque su nombre no estaba en esa lista nacional. &#13;
&#13;
La CÃ¡mara de Representantes de EU aprobÃ³ ayer un proyecto de ley que obligarÃ­a a los estados a pasar al FBI de forma automÃ¡tica los nombres de personas como Cho. &#13;
&#13;
El informe, elaborado por los secretarios de Salud, Michael Leavitt, y EducaciÃ³n, Margaret Spellings, asÃ­ como el fiscal general, Alberto Gonzales, tambiÃ©n seÃ±ala que existe "confusiÃ³n sobre las leyes que regulan el intercambio de informaciÃ³n" respecto de personas que pueden ser un peligro. &#13;
&#13;
El comitÃ© concluye que profesores, administraciones e instituciones no tienen claro cuÃ¡ndo pueden o deben alertar a las autoridades sobre estas personas para impedir que tengan acceso a armas. &#13;
&#13;
"Este miedo y malos entendidos probablemente limitan la transferencia de informaciÃ³n", se explica en el documento. &#13;
&#13;
Asimismo, el comitÃ© recomienda poner en marcha programas para instruir a padres, alumnos y profesores sobre los signos de que una persona sufre desequilibrios mentales que le pueden llevar a la violencia. &#13;
&#13;
AdemÃ¡s, insta a mejorar los servicios mÃ©dicos para estudiantes que padecen enfermedades mentales. &#13;
&#13;
Por Ãºltimo, plantea que los planes para responder a emergencias a nivel local y estatal tengan en cuenta las necesidades de los centros educativos, y que los cuerpos de seguridad de las escuelas colaboren de forma mÃ¡s estrecha con la policÃ­a. &#13;
&#13;
El informe no habla en ningÃºn momento, sin embargo, de la necesidad de endurecer las leyes para restringir el acceso a las armas en general, en un paÃ­s donde sus ciudadanos poseen mÃ¡s de 200 millones de armas de fuego. &#13;
&#13;
En Virginia, por ejemplo, cualquier persona que no tenga un historial criminal puede comprar legalmente un arma por mes. &#13;
&#13;
Otras matanzas han sido cometidas por personas que no habÃ­an sido tratadas por problemas mentales, como por ejemplo la ocurrida en 1999 en la escuela secundaria de Columbine, en la que murieron 14 estudiantes y un profesor.&#13;
&#13;
--&#13;
Fuente Original: Diario La Raza - Chicago&#13;
&lt;a href="http://www.laraza.com/news.php?nid=44534&amp;clave=a%3A1%3A%7Bi%3A0%3Bs%3A13%3A%22virginia+tech%22%3B%7D"&gt;http://www.laraza.com/news.php?nid=44534&amp;clave=a%3A1%3A%7Bi%3A0%3Bs%3A13%3A%22virginia+tech%22%3B%7D&lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10033">
                <text>spa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11939">
                <text>Jorge Mederos&#13;
Executive Editor&#13;
La Raza Chicago Inc.&#13;
jorge.mederos@laraza.com&#13;
August, 13 2007</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13434">
                <text>Legisladores sÃ³lo piden mayor control sobre las â€˜personas peligrosasâ€™ en EE.UU.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="949">
        <name>armas</name>
      </tag>
      <tag tagId="891">
        <name>fbi</name>
      </tag>
      <tag tagId="628">
        <name>gonzales</name>
      </tag>
      <tag tagId="626">
        <name>leavitt</name>
      </tag>
      <tag tagId="1354">
        <name>nics</name>
      </tag>
      <tag tagId="1353">
        <name>problemas mentales</name>
      </tag>
      <tag tagId="627">
        <name>spellings</name>
      </tag>
      <tag tagId="234">
        <name>virginia</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1014" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2316">
                <text>Elva Orozco</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4207">
                <text>MarÃ­a Luisa Azpiazu</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6185">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8063">
                <text>Actividades en honor a los fallecidos marcan el regreso a virginia tech &#13;
&#13;
Publicado por MarÃ­a Luisa Azpiazu&#13;
EFE&#13;
04-24-2007 &#13;
&#13;
&#13;
Washington, D.C â€” Mucho dolor, impresionantes minutos de silencio y 32 campanadas en memoria de las vÃ­ctimas de la peor matanza de la historia estudiantil de E.U. marcaron ayer el regreso a clase de los alumnos de la Universidad PolitÃ©cnica de Virginia. &#13;
&#13;
Fueron miles los alumnos que regresaron ayer para rendir tributo a sus compaÃ±eros y profesores fallecidos. &#13;
&#13;
Justo una semana antes, Cho Seung-Hui, un estudiante coreano de 23 aÃ±os, decidiÃ³ cambiar el ritmo devida en esta Universidad del sur del estado de Virginia y matÃ³ a 32 personas. &#13;
&#13;
Las solemnes conmemoraciones comenzaron muy pronto. El primer minuto de silencio se guardÃ³ a las 7:10 de la maÃ±ana en el edificio en el que Cho cobrÃ³ sus dos primeras vÃ­ctimas. Algo mÃ¡s de dos horas despuÃ©s, la gran concentraciÃ³n se llevÃ³ a cabo en el campus central, donde los estudiantes colocaron miles de recuerdos, flores, velas y escritos en recuerdo de las vÃ­ctimas. &#13;
&#13;
Entre los objetos, alguien puso una bandera de PerÃº y otra de Israel en memoria de dos de las vÃ­ctimas, el estudiante peruano Daniel PÃ©rez Cuevas y el profesor Liviu Librescu, quien, segÃºn testigos, bloqueÃ³ con su cuerpo la entrada a su clase del agresor y salvÃ³ la vida de varios de sus alumnos, aunque perdiÃ³ la suya. &#13;
&#13;
La maÃ±ana fue brillante, soleada y cÃ¡lida, lo que contribuyÃ³ a que el acto fuera aÃºn mÃ¡s solemne. Los estudiantes portaron 33 banderas blancas que representaban tanto a las vÃ­ctimas como al agresor. &#13;
&#13;
Una pequeÃ±a banda de mÃºsica interpretÃ³ el himno "America the Beautiful" cerca del lugar donde se habÃ­a instalado un semicÃ­rculo con 33 piedras en recuerdo de los fallecidos. &#13;
&#13;
Junto a la piedra del agresor, alguien colocÃ³ una carta en la que se asegura que este joven "subestimÃ³ nuestra fuerza, coraje y compasiÃ³n" y en la que se asegura que "rompiste nuestros corazones pero no nuestros espÃ­ritus". &#13;
&#13;
Este es el resumen de un convencimiento que impera en esta Universidad, decidida a superar el gran trauma. &#13;
&#13;
"Tenemos que seguir adelante", aseguran desde las pÃ¡gina del "Collegiate Times", el periÃ³dico universitario. que ha jugado un papel fundamental tanto en la ayuda a los estudiantes como en la informaciÃ³n en los momentos posteriores de la tragedia. &#13;
&#13;
La consigna es clara- "Vamos HokiesÂ¡Â¡", que es el nombre con el que se denominan los estudiantes de esta Universidad. &#13;
&#13;
Alumnos, familiares y profesores, escucharon, en medio de un gran recogimiento, las 32 campanadas. Una por cada una de las vÃ­ctimas. Terminada la letanÃ­a, los estudiantes lanzaron 32 globos blancos al cielo seguidos de otros mil de colores naranja y marrÃ³n, la enseÃ±a de la Universidad. &#13;
&#13;
Muchos, todavÃ­a, no podÃ­an contener las lÃ¡grimas y, en declaraciones a medios locales, aseguran que aÃºn no saben si volverÃ¡n a la Universidad o darÃ¡n el curso por terminado ya, dos semanas antes de lo previsto. &#13;
&#13;
La Universidad permitirÃ¡ a todo aquel que no quiera volver a las clases repetir el semestre o quedarse con las notas que tenÃ­a hasta el momento.Para los que decidan volver, la Universidad tiene una baterÃ­a de psicÃ³logos que a ayudarÃ¡ a superar el trauma. &#13;
&#13;
Se estÃ¡n poniendo en marcha igualmente imaginativas terapias, como la que ha llevado a la Cruz Roja a llevar a este campus decenas de perros amaestrados para ser especialmente cariÃ±osos, que acompaÃ±arÃ¡n a los estudiantes. &#13;
&#13;
Se trata, en definitiva, de ofrecer calma y paz para evitar mÃ¡s episodios tristes como el vivido el fin de semana por la familia Soriano. &#13;
&#13;
Su hijo Jeff, un estudiante de Virginia Tech que habÃ­a sobrevivido a la tragedia, se matÃ³ en la carretera el viernes, poco antes de llegar a su casa, en Norfolk (Virginia). &#13;
&#13;
Su padre, Enrique Soriano, asegura que su hijo es "la vÃ­ctima nÃºmero 33" de la tragedia. EFE &#13;
&#13;
--&#13;
Fuente Original: Diario La Raza - Chicago&#13;
&lt;a href="http://www.laraza.com/news.php?nid=43429&amp;pag=0"&gt;http://www.laraza.com/news.php?nid=43429&amp;pag=0&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10034">
                <text>spa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11940">
                <text>Jorge Mederos&#13;
Executive Editor&#13;
La Raza Chicago Inc.&#13;
jorge.mederos@laraza.com&#13;
August, 13 2007</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13435">
                <text>Solemnes momentos de recordaciÃ³n</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1357">
        <name> vamos hokies</name>
      </tag>
      <tag tagId="441">
        <name>collegiate times</name>
      </tag>
      <tag tagId="435">
        <name>librescu</name>
      </tag>
      <tag tagId="105">
        <name>perez</name>
      </tag>
      <tag tagId="1356">
        <name>recuerdos</name>
      </tag>
      <tag tagId="1355">
        <name>regreso a clases</name>
      </tag>
      <tag tagId="1358">
        <name>soriano</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1015" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2317">
                <text>Elva Orozco</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4208">
                <text>JesÃºs DÃ¡vila</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6186">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8064">
                <text>Por JesÃºs DÃ¡vila&#13;
Corresponsal&#13;
Publicado el 04-23-2007 &#13;
&#13;
San Juan â€” El fÃ©retro con los restos del ingeniero Juan RamÃ³n Ortiz, muerto en la masacre de &lt;b&gt;virginia tech&lt;/b&gt; el pasado dÃ­a 16, fue transportado ayer sÃ¡bado a Puerto Rico, pero su viuda, Lizelle Vega, y demÃ¡s familiares pidieron a la prensa que les dejen en paz para poder comenzar el "proceso de sanaciÃ³n" luego de la tragedia. &#13;
&#13;
Vega hizo el llamado en una rueda de prensa en la que indicÃ³ que el velorio serÃ¡ en una funeraria de BayamÃ³n, ciudad natal de su esposo, y el entierro tendrÃ¡ lugar el martes en el cementerio catÃ³lico Porta Coeli, del mismo municipio. &#13;
&#13;
La tambiÃ©n ingeniero, quien junto a su esposo cursaba estudios avanzados en la universidad de Virginia, expresÃ³ agradecimiento para todos los que le han apoyado ante el dolor -tanto en Virginia como en Puerto Rico- ademÃ¡s de hacer reconocimiento de la labor que han realizado los medios noticiosos. &#13;
&#13;
Pero, pidiÃ³ que durante los prÃ³ximos dÃ­as se permita a la familia su espacio de intimidad y que no se hagan entrevistas en la funeraria o el cementerio. &#13;
&#13;
El pedido de Vega coincide con las instrucciones emitidas por la direcciÃ³n de &lt;b&gt;virginia tech&lt;/b&gt; de que a partir del lunes estarÃ¡ prohibido que los reporteros o fotÃ³grafos entren a los edificios universitarios ni camiones de transmisiÃ³n televisada podrÃ¡n estar en el campus para dar espacio a que comience "el proceso de sanaciÃ³n". &#13;
&#13;
Las instrucciones especifican ademÃ¡s que cualquier pedido de entrevistas a personas en el campus universitario respete los sentimientos de las personas. &#13;
&#13;
Vega dijo que no querÃ­a hacer declaraciones sobre lo que pasÃ³ y que sÃ³lo querÃ­a limitarse a recordar a su marido por su alegrÃ­a. Sobre su futuro, indicÃ³ que todavÃ­a no ha tomado una decisiÃ³n pero especificÃ³ claramente que no piensa demandar a la universidad, ni ahora, ni nunca. &#13;
&#13;
Entre las alternativas que ha ofrecido la universidad a los estudiantes afectados por la masacre estÃ¡ obtener la nota de fin de semestre con los trabajos realizados hasta el momento en los cursos. &#13;
&#13;
El dÃ­a de los hechos, Vega se encontraba en el edificio donde cursa estudios en geotecnia, mientras Ortiz asistÃ­a a clases de hidrologÃ­a avanzada en el edificio del frente, donde se produjo el segundo tiroteo. SegÃºn habÃ­a narrado previamente, no escuchÃ³ los disparos y sÃ³lo vio el movimiento de los policÃ­as, luego de lo cual se enterÃ³ que su esposo era una de las vÃ­ctimas fatales. Â© EDLP &#13;
&#13;
--&#13;
Fuente Original: Diario La Prensa - Chicago&#13;
&lt;a href="http://www.laraza.com/news.php?nid=43410&amp;clave=a%3A1%3A%7Bi%3A0%3Bs%3A13%3A%22virginia+tech%22%3B%7D"&gt;http://www.laraza.com/news.php?nid=43410&amp;clave=a%3A1%3A%7Bi%3A0%3Bs%3A13%3A%22virginia+tech%22%3B%7D&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10035">
                <text>spa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11941">
                <text>Jorge Mederos&#13;
Executive Editor&#13;
La Raza Chicago Inc.&#13;
jorge.mederos@laraza.com&#13;
August, 13 2007</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13436">
                <text>Viuda estudiante muerto pide paz</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1361">
        <name>bayamÃ³n</name>
      </tag>
      <tag tagId="1360">
        <name>lizelle vega</name>
      </tag>
      <tag tagId="896">
        <name>ortiz</name>
      </tag>
      <tag tagId="1362">
        <name>paz</name>
      </tag>
      <tag tagId="909">
        <name>puerto rico</name>
      </tag>
      <tag tagId="1359">
        <name>san juan</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1016" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2318">
                <text>Elva Orozco</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4209">
                <text>Servicios La OpiniÃ³n</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6187">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8065">
                <text>Las clases se reanudan hoy, aunque el edificio donde fueron asesinadas 30 personas permanecerÃ¡ cerrada el resto del semestre&#13;
&#13;
&#13;
Publicado por Servicios La OpiniÃ³n&#13;
04-23-2007&#13;
&#13;
&#13;
Blacksburg - La universidad de virginia tech, donde hace una semana un estudiante matÃ³ a 32 personas y se suicidÃ³, reanudarÃ¡ hoy sus actividades mientras prosiguen las investigaciones y debates en torno al incidente. &#13;
&#13;
Mientras, miles de estudiantes, profesores y demÃ¡s afectados por la tragedia, tratan de encontrar valor para regresar al campus y volver a la normalidad, acciÃ³n que fue impulsada ayer por el pastor de la Iglesia Bautista de Blacksburg, cuyo sermÃ³n estuvo centrado en la recuperaciÃ³n emocional de los sobrevivientes. &#13;
&#13;
La universidad espera el retorno de la mayorÃ­a de sus 26 mil estudiantes para la etapa final de los cursos de este aÃ±o., mientras se completan los funerales de las vÃ­ctimas del estudiante Seung Hui Cho. &#13;
&#13;
"Tenemos que seguir adelante. Haremos todo lo que podamos para reorganizar este sitio e impedir que algo como lo ocurrido vuelva a ocurrir", dijo el portavoz de la universidad, Larry Hincker. &#13;
&#13;
El edificio Norris, donde Cho dio muerte a 30 personas y luego se suicidÃ³, permanecerÃ¡ cerrado por el resto del semestre., y las autoridades han tomado medidas para aliviar la presencia de los medios de comunicaciÃ³n. &#13;
&#13;
Mientras, el pastor Tommy McDearis exhortÃ³ a los feligreses a regresar a sus actividades normales en la universidad de virginia tech luego de la matanza ocurrida en la instituciÃ³n. &#13;
&#13;
McDearis tuvo la penosa tarea de informar el pasado lunes a familiares de mÃ¡s de 20 vÃ­ctimas acerca de la matanza causada por el estudiante surcoreano Seung Hui Cho. &#13;
&#13;
El pastor dijo a la congregaciÃ³n que "si cedemos ante esta situaciÃ³n, y cesamos de hacer todas las cosas que realmente importan en la vida porque hemos sido visitados por la oscuridad, entonces, terminaremos rindiÃ©ndonos ante la oscuridad". &#13;
&#13;
El pastor pronunciÃ³ su sermÃ³n mientras los estudiantes que abandonaron virginia tech tras la matanza regresaban al campo universitario. &#13;
&#13;
El pastor contÃ³ la experiencia de un profesor que habÃ­a quedado muy afectado por la muerte de varios de sus estudiantes en Norris Hall. &#13;
&#13;
El profesor dijo que en principio no deseaba retornar. Pero que lo harÃ­a, para no traicionar los recuerdos, las esperanzas y los sueÃ±os de las vÃ­ctimas. &#13;
&#13;
Mientras se aprestaban a reanudar las clases, las autoridades universitarias invitaron a los centenares de periodistas que acamparon en predios de virginia tech, a irse del lugar a mÃ¡s tardar hoy. &#13;
&#13;
La vocera de la universidad, Liz Hart, dijo que las autoridades de virginia tech apreciaban lo que habÃ­an hecho los periodistas, pero era hora de ir hacia adelante. &#13;
&#13;
"La mejor manera de hacer eso es que la universidad retorne a la normalidad", seÃ±alÃ³ Hart. Â© Servicios&#13;
&#13;
&#13;
--&#13;
Fuente Original: Diario La Raza - Chicago&#13;
&lt;a href="http://www.laraza.com/news.php?nid=43402&amp;pag=0"&gt;http://www.laraza.com/news.php?nid=43402&amp;pag=0&lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10036">
                <text>spa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11942">
                <text>Jorge Mederos&#13;
Executive Editor&#13;
La Raza Chicago Inc.&#13;
jorge.mederos@laraza.com&#13;
August 13, 2007</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13437">
                <text>Intenta virginia tech volver a la normalidad</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1365">
        <name>hart</name>
      </tag>
      <tag tagId="1363">
        <name>hincker</name>
      </tag>
      <tag tagId="1364">
        <name>mcdearis</name>
      </tag>
      <tag tagId="49">
        <name>Norris</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1017" public="1" featured="0">
    <fileContainer>
      <file fileId="516">
        <src>https://www.april16.vtlibraries.net/files/original/Deb_2007_58c85ba8c9.pdf</src>
        <authentication>null</authentication>
        <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="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14901">
                    <text>2007-08-13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16021">
                    <text>2007-08-13 14:18:35</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2319">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4210">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6188">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8066">
                <text>(PDF, 36KB; full text copied below)&#13;
&#13;
&lt;b&gt;EDITORIAL&#13;
&#13;
A Tribute to Professor G. V. Loganathan&lt;/b&gt;&#13;
&#13;
Arun K. Deb, Ph.D., P.E., F.ASCE &#13;
Vice President (Ret.), Weston Solutions, Inc. E-mail: arundeb@msn.com&#13;
&#13;
April 16, 2007 started like any other day on the Virginia Tech campus in Blacksburg, Virginia. Dr. G. V. Loganathan, a professor in the Civil and Environmental Engineering department at Virginia Tech left his home near the campus to teach a graduate class on Advanced Hydrology in room number 206 of Norris Hall. He never returned home. Loganathan, along with nine of his students, was killed by a gunman. It was the worst massacre on a university campus in the history of the United States. Very soon, the news started to flash on TV screens. I became concerned as I know quite a few faculty members at Virginia Tech, but never expected one of my dearest friends to be among the victims. I was stunned when I saw Prof. Loganathan&amp;#39;s name on TV as one of the victims. I barely got over the shock when I received a call from one of my friends confirming the news. I opened my e-mail to see several messages in this regard. That is one dreadful day I will never forget in my life.&#13;
&#13;
Dr. G. V. Loganathan was born in 1954, in the state of Tamil Nadu, India. He completed his Bachelor of Engineering at Madras University, India in 1976. He earned his Master of Technology at Indian Institute of Technology, Kanpur and received his PhD from Purdue University. In 1981, Dr. Loganathan joined Virginia Tech to conduct research and teach in the Civil and Environmental Engineering Department. He focused his research in the areas of hydrology and hydraulic networks. It was about 20 years ago while attending an ASCE Conference of the Water Resources Planning and Management Division, that I first met Loganathan in the Water Resources Systems Committee meeting. After the meeting, he came up to me and expressed his interest in water distribution system analysis. At the time, he was a young faculty member at Virginia Tech, full of energy and enthusiasm. He discussed with me his current projects on water distribution system research and his plans for the future. I impressed upon him the need to do some practical research for water utility personnel to help solve real water distribution system problems. He expressed his sincere interest to work with me on some future projects. We soon became friends and communicated frequently. He always informed me when he had new ideas or started to work on a challenging project. Quite often, we shared brainstorming sessions.  Soon, I became involved in conducting water distribution system research under the American Water Works Association Research Foundation  AwwaRF  grants.&#13;
&#13;
In 1997, I had an opportunity to get Loganathan involved in one of my proposals on "&lt;i&gt;Prioritizing Water Main Replacement and Rehabilitation&lt;/i&gt;" for AwwaRF. The success of that proposal was the beginning of a long working relationship with GV  as he preferred to be called . He quickly became a part of our team. It was a complex project that involved Newland Agbenowski, a PhD student from Ghana working under the guidance of Loganathan. I, along with our project team, spent many weekend hours with him brainstorming and formulating the concept of development of a computer model. With the help of Loganathan and Newland, we developed guidance and methodologies for the collection of on-site real-time water main break field data and a modeling system incorporating these data to predict and prioritize candidate mains for rehabilitation/replacement. This model helps water utility managers assess the condition of water mains and develop strategies for long-term rehabilitation plans for their distribution systems.&#13;
&#13;
In 1999, while working on the previous AwwaRF project, Loganathan and I prepared another successful proposal on "&lt;i&gt;Decision Support System for Distribution System Pipe Renewal&lt;/i&gt;." In this project Loganathan, with help from one of his graduate students, developed decision support system software to evaluate and identify suitable water main renewal technologies available to water utilities for renewal of a specific water main. Technologies considered include both open-cut and trenchless. A cost module was also developed for comparative cost analysis.  By this time, I had developed an excellent personal and working relationship with Loganathan. Also, I was fortunate to have his and Virginia Tech&amp;#39;s help in developing a prioritized water main replacement program for the Saint Louis County Water Company  now Missouri American Water Company . The Saint Louis County Water Company was experiencing a large number of cast-iron water main breaks. In this project Loganathan and his graduate student formulated a computer program to analyze a large amount of water main break data on a pipe-by-pipe basis.  An economic model was developed that predicted water main breaks, estimated costs of main break repair, and compared that with the cost of a replacement pipe to identify the optimum time to replace a pipe. Using this software, we developed an optimum water main replacement program for the Saint Louis County Water Company.&#13;
&#13;
In 2002, Loganathan and I had the opportunity to successfully submit another proposal on "&lt;i&gt;Criteria for Valve Location and System Reliability&lt;/i&gt;" for the AwwaRF Loganathan and his PhD student Hwandon Jun, developed a software for the analysis of water distribution networks and a strategic valve management model to assist water utilities in developing a rationale for the proper location of valves and optimum valve and system reliability.  This tool is suitable for water utilities to minimize impacts due to valve and pipe failures. A report on this project was published by AwwaRF in 2006. Loganathan prepared a paper entitled "Valve Distribution and Impact Analysis in Water Distribution Systems" which is included in this issue of the Journal. I am glad and proud to be associated with Loganathan&amp;#39;s paper as a coauthor.&#13;
&#13;
Loganathan&amp;#39;s work was recognized by ASCE with the Wesley W. Horner Award in 1996 for his paper, "&lt;i&gt;Sizing Stormwater Detention Basins for Pollutant Removal&lt;/i&gt;." He was an excellent teacher and earned the outstanding teaching award four times.  He also received the Faculty Achievement Award for Excellence in Civil Engineering Education. He was a very active member of ASCE and served as Associate Editor of the &lt;i&gt;Journal of Hydrologic Engineering&lt;/i&gt; specializing in the area of stochastic hydrology. He also served in the Water Resources Systems Committee, Trenchless Installation of Pipeline Committee, and acted as Vice Chair of the Operations Management Committee of ASCE.  He supervised more than 45 graduate students during his tenure at Virginia Tech. Students adored him. One student wrote in his memorial, "I regret not telling you that you are the best teacher I ever had." Another student wrote in his memorial posting, "Dr. Loganathan was an excellent teacher and mentor. I will always remember him for his kind heart and patience he displayed towards me and his other students." Jerry Snyder, a colleague of mine and a member of ASCE posted, "He was a dedicated professor and researcher and the most gentleman that I have ever known. I can only hope to live my life with purpose and humanity in the same manner as GV. It was a privilege to know him." Loganathan is survived by his wife, Usha and two daughters, Uma and Abhirami.&#13;
&#13;
The President of the ruling Congress Party of India, Mrs. Sonia Gandhi sent her heartfelt condolences to his wife Usha.&#13;
&#13;
During my long association with Loganathan, I found him a very polite, respectful, and humble man. In technical discussion, he respected opinions of all project team members, including his students. He always met deadlines, even if that meant working evenings and weekends. He was a complete gentleman. The last e-mail message I received from him was on April 9, 2007, exactly a week before his death. I will never forget him as long as I live.  I express my sincere condolences to his family. Virginia Tech University has established an annual graduate fellowship in the Civil and Environmental Engineering Department in memory of Loganathan. The best way to help continue his legacy is to contribute to this G. V. Loganathan Fellowship Fund by sending checks in favor of Virginia Tech Foundation with a memo to: G.V.  Loganathan Fellowship at 902 Prices Fork Road, Suite 4000, Blacksburg, VA 24061.&#13;
&#13;
I would like to thank Dr. Ray Ferrara for giving me the opportunity to write this editorial.&#13;
&#13;
--&#13;
&#13;
Archived with permission of the American Society of Civil Engineers (ASCE).&#13;
&#13;
Original Source: &lt;i&gt;Journal of Environmental Engineering&lt;/i&gt; Â© ASCE / August 2007</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10037">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11943">
                <text>Xi Van Fleet&#13;
Senior Manager, Information Services&#13;
Publication Division&#13;
American Society of Civil Engineers&#13;
1801 Alexander Bell Drive&#13;
Reston, VA  20191&#13;
(703) 295-6278-FAX&#13;
PERMISSIONS@asce.org</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13438">
                <text>A Tribute to Professor G. V. Loganathan (Editorial)</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1371">
        <name>asce</name>
      </tag>
      <tag tagId="1372">
        <name>civil engineering</name>
      </tag>
      <tag tagId="556">
        <name>editorial</name>
      </tag>
      <tag tagId="1366">
        <name>loganathan</name>
      </tag>
      <tag tagId="94">
        <name>tribute</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1018" public="1" featured="0">
    <fileContainer>
      <file fileId="517">
        <src>https://www.april16.vtlibraries.net/files/original/DSC00137_7c9029b7db.JPG</src>
        <authentication>null</authentication>
        <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="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14902">
                    <text>2007-08-13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16022">
                    <text>2007-08-13 19:22:02</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2320">
                <text>Na Mi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4211">
                <text>Jinfeng Jiao</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6189">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8067">
                <text>One week after the shooting,people set six flags on the lawn of the drillfield to mourn the victims.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10038">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13439">
                <text>Six flags of VT in drillfield</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1414">
        <name> flags</name>
      </tag>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="1109">
        <name>shooting</name>
      </tag>
      <tag tagId="1088">
        <name>victims</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1019" public="1" featured="0">
    <fileContainer>
      <file fileId="518">
        <src>https://www.april16.vtlibraries.net/files/original/DSC00138_4a2b683b90.JPG</src>
        <authentication>null</authentication>
        <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="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14903">
                    <text>2007-08-13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16023">
                    <text>2007-08-13 19:36:10</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2321">
                <text>Na Mi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4212">
                <text>Jinfeng Jiao</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6190">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8068">
                <text>After the vigil,people left candles and flowers on the drillfield to express their sadness and grief.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10039">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13440">
                <text>Candles on the drillfield</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="717">
        <name>grief</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1020" public="1" featured="0">
    <fileContainer>
      <file fileId="519">
        <src>https://www.april16.vtlibraries.net/files/original/DSC00139_13bfae2b7b.JPG</src>
        <authentication>null</authentication>
        <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="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14904">
                    <text>2007-08-13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16024">
                    <text>2007-08-13 19:41:41</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2322">
                <text>Na Mi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4213">
                <text>Na Mi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6191">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8069">
                <text>People volunteered to set up a stone marked with "VT" for other people to light candles.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10040">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13441">
                <text>Stone for candles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="450">
        <name>candles</name>
      </tag>
      <tag tagId="30">
        <name>vt</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1021" public="1" featured="0">
    <fileContainer>
      <file fileId="520">
        <src>https://www.april16.vtlibraries.net/files/original/DSC00140_c450cdd41e.JPG</src>
        <authentication>null</authentication>
        <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="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14905">
                    <text>2007-08-13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16025">
                    <text>2007-08-13 19:47:53</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2323">
                <text>Na Mi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4214">
                <text>Jinfeng Jiao</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6192">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8070">
                <text>Handmade memorials were placed on one of the corners of the drillfield.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10041">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13442">
                <text>Handmade memorials for the victims</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="173">
        <name>memorials</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1022" public="1" featured="0">
    <fileContainer>
      <file fileId="521">
        <src>https://www.april16.vtlibraries.net/files/original/DSC00143_676aa67fd0.JPG</src>
        <authentication>null</authentication>
        <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="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14906">
                    <text>2007-08-13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16026">
                    <text>2007-08-13 19:54:23</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2324">
                <text>Na Mi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4215">
                <text>Na Mi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6193">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8071">
                <text>In order to express the grief, Virginia Tech lowered down the national flag in front of the Burrus Hall for weeks after the shooting.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10042">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13443">
                <text>Lowering down the flag</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1415">
        <name>national flag</name>
      </tag>
      <tag tagId="1109">
        <name>shooting</name>
      </tag>
      <tag tagId="1416">
        <name>the burrus hall</name>
      </tag>
      <tag tagId="14">
        <name>virginia tech</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1023" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2325">
                <text>Adriana Seagle</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4216">
                <text>Paul Harris </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6194">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8072">
                <text>It was 7am on Monday. Another week was starting at Virginia Tech. Then the first shots rang out. Within hours, 32 people lay dead and America was left trying to make sense of the carnage. Paul Harris reports from Blacksburg. &#13;
&#13;
&lt;b&gt;Sunday April 22, 2007&lt;/b&gt;&#13;
&lt;a href="http://www.observer.co.uk/"&gt;The Observer&lt;/a&gt; &#13;
&#13;
A group of Amish men, all in black, shuffled towards the chapel at one end of the enormous sports field that dominates the centre of Virginia Tech&amp;#39;s campus. They had come to pay their respects after a tragedy they knew all too well. It was only last year that a killer struck their community, shooting dead five young girls in a tiny Amish school. Now they had driven many long hours from their Pennsylvania farms to southern Virginia, to offer solace to another American community devastated by a mass killing.&#13;
&#13;
They spoke in hushed tones to the Reverend Kelly Sisson, one of the pastors of Glade Church in Blacksburg. Then they entered the comforting dark interior to pray and to mourn the dead of Virginia Tech. &amp;#39;They understand what has happened to us in a way few others do,&amp;#39; Sisson said.&#13;
&#13;
Everyone is trying to understand what happened at Blacksburg last week. Impromptu memorials have sprung up on the sports field, covering the grass in flickering candles, pictures of the dead, and flowers. Students, friends and family have written messages, sad, desperate, noble. They speak of loss and love. They vow to remember lives brutally cut short on what should have been just another Monday morning.&#13;
&#13;
But, although there was nothing ordinary about last Monday, there was a dreadful familiarity to it. Cho Seung-hui&amp;#39;s bloody rampage cost the lives of 32 of his fellow students and staff. It was the worst mass shooting in American history, but far from the only one.&#13;
&#13;
There is almost a ritual to such attacks: the fleeing students, the wailing sirens, the mourning survivors, the suicide of the gunman - Cho shot himself in the face. Columbine, the Amish school, Virginia Tech, all are now names that haunt the popular imagination. Yet no one pretends last week&amp;#39;s rite won&amp;#39;t happen again, somewhere else in America on some other seemingly ordinary day.&#13;
&#13;
For now it is Blacksburg&amp;#39;s tragedy that has the attention of the world. What Cho did last week is well known. In two separate attacks, he shot his victims methodically, without any outward show of emotion. It was an assault he had planned for weeks: buying guns, training physically and preparing a &amp;#39;manifesto&amp;#39; of his beliefs in writing, pictures and video. But the real question is not how Cho killed so many. It is why. And that is a much more difficult issue.&#13;
&#13;
What could have caused him to hate so much? If he was ill, should it have been spotted? Why did he pick the targets that he did? These questions could shake the strongest faith. Sisson shook her head at the thought of them: &amp;#39;I am determined to not give easy answers. Cliches are cheap and we are still waking up to this.&amp;#39; Then she thought of Cho. &amp;#39;He was in great pain. Great brokenness,&amp;#39; she said. A faint smile of incomprehension hovered around her lips. She was close to tears.&#13;
&#13;
The first sign something was wrong last Monday was a scream and &amp;#39;popping&amp;#39; sounds in the West Ambler Johnston dorm building. It was just after 7am: many students slept through the noise. Those who emerged bleary-eyed into the corridors found a dreadful scene. Two bodies lay near Room 4040, in the open space near the lifts. There was no sign of an attacker. The killer had disappeared, leaving a trail of bloody footprints down a hallway.&#13;
&#13;
By the time Cho claimed his first victim, he had already been planning his attack for weeks, possibly months. Not that anyone knew it. Cho was a solitary figure on campus, even among the five students with which he shared a &amp;#39;suite&amp;#39;, Room 2121. He spoke rarely and shunned human contact. His only visitors were his parents. &amp;#39;He never showed any interest in having conversations with anybody. He seemed like a shy person. He never spoke a word when he was around any of us in the suite,&amp;#39; said one room-mate, Karan Grewal.&#13;
&#13;
In the past few weeks, Cho&amp;#39;s routines seem to have shifted. He started going to the gym, beefing up his slight frame. He cut his hair short. He started waking up earlier, rising at 5.30am. He began taking night-time bike rides, disappearing for hours to roam the campus paths.&#13;
&#13;
These were the superficial changes. Unknown to anyone but himself, Cho was plotting mass murder. Nineteen days before he began shooting, he took a road-trip, renting a car and staying a night in a nearby hotel in Christiansburg. It was on this trip that he would film some of his rambling, hate-laden last testament. It is likely that he also used the privacy to take pictures of himself posing with his guns, a knife and a hammer. He also began drafting manuscripts blaming the outside world and decrying the lifestyles of his fellow students.&#13;
&#13;
Cho prepared in private. But police are checking to see if he had mentioned or hinted at his plans, whether by phone or email. He certainly had to buy his guns in public. Tragically, it is neither difficult nor unusual for a 23-year-old student legally to buy powerful weapons in Virginia. On 9 February, Cho purchased a Walther P22 pistol from a pawn shop on Main Street in Blacksburg. He then waited just over a month - in order to comply with Virginia state law - before buying a second weapon. On 16 March, he picked out a Glock semi-automatic from Roanoke Firearms, in a town about 30 miles away. With each purchase Cho filled out the correct forms and passed a background check. No one asked what a 23-year-old English student could possibly want with two powerful hand-guns.&#13;
&#13;
What the sellers did not know was that Cho had once spent a night in a mental hospital in 2005. Nor does Virginia law deem it necessary that anyone divulge such information. Yet it represented, perhaps, the biggest sign Cho was not an ordinary young man, but had at least once been through a very troubled passage in his life.&#13;
&#13;
There were other signs, albeit less definite. In two separate incidents, young women on campus had complained to police he was bothering them with unwanted advances, in person, on the phone or via text messaging. Last autumn, one of Cho&amp;#39;s teachers, poet Nikki Giovanni, had become so disturbed by the violent imagery in Cho&amp;#39;s work that she insisted he be removed from her class. &amp;#39;I am not allowed to say what he was writing,&amp;#39; she explained &amp;#39;But it was not bad poetry. It was intimidating. What I wanted was him out of my class.&amp;#39;&#13;
&#13;
He had also been taking pictures of his fellow students, many of whom had stopped attending class to avoid him. At the same time, Cho - in a rare remark to a dorm mate - said he might kill himself after the police spoke to him about pestering girls. The student reported the remark and Cho was sent for an overnight evaluation at the Carilion St Albans Psychiatric Hospital - the 2005 visit. &amp;#39;Affect is flat and mood is depressed,&amp;#39; a Carilion doctor wrote, but noted that Cho&amp;#39;s &amp;#39;insight and judgment are sound&amp;#39; and that he had denied suicidal intentions. The next day, a judge, following the doctor&amp;#39;s advice that Cho was mentally ill but posed no immediate danger, ordered him to take outpatient treatment.&#13;
&#13;
That was probably the greatest opportunity that presented itself to stop or help Cho. After that, he resumed his solitary existence, a phantom presence at Virginia Tech. Perhaps it was also the moment that Cho&amp;#39;s deep resentment came to fruition.&#13;
&#13;
His stalking - though disturbing - was at least an attempt to reach out to other human beings. That grasp for contact had ended with the police and a stay in a mental hospital. It is not too great a stretch to imagine Cho&amp;#39;s warped rage at such rejection. Perhaps, almost 17 months ago, the first thoughts of revenge began to take shape.&#13;
&#13;
At just after 5am on Monday, Karan Grewal bumped into his flatmate, Cho. Grewal had stayed up all night to finish an assignment and he had been to the bathroom before going, finally, to sleep. Cho looked normal, Grewal thought.&#13;
&#13;
Two hours later Cho killed Emily Hilscher, 18, and Ryan Clark, 23, at Ambler Johnston. Why he chose them - or that building - is not known. But investigators have strong suspicions that Cho may have had some form of contact with Hilscher, and have since been scouring her computer and phone looking for evidence.&#13;
&#13;
Cho&amp;#39;s whereabouts immediately after the attack are unknown. Perhaps he returned to his dorm room; perhaps not. What is certain is that he eventually walked across campus to the post office in Blacksburg, a 15-minute stroll away on Main Street. The post office was busy with people rushing to beat the national tax deadline and Cho did not stand out among the crowd.&#13;
&#13;
He was posting a package - wrongly addressed - to NBC News in New York. It contained his &amp;#39;manifesto&amp;#39;. He finally mailed his package at 9.01am, after a clerk noticed that he had put the wrong postal code on it. Then he made his way back to the campus.&#13;
&#13;
Cho - despite having murdered two fellow students - was still anonymous; the campus was still mostly normal. Unknown to Cho, police and university officials had gone down a disastrous blind alley in their reaction to the Ambler Johnston shootings.&#13;
&#13;
When police broke the news to one of Hilscher&amp;#39;s room-mates that her friend was dead, she told them that Hilscher&amp;#39;s new boyfriend, Karl Thornhill, loved guns and had recently taken them shooting. At 8.25am, university and police officials held a meeting and decided they faced a &amp;#39;domestic&amp;#39;. Thornhill was tracked down in his car and pulled off the road. It was decided not to lock down the campus. They believed the gunman had fled, or that they had already caught him.&#13;
&#13;
Some time before 9.40am, Cho walked into Norris Hall, on the other side of the sports field from Ambler Johnston. Once inside, he closed the doors with metal chains. He wandered the corridors, even poking his head into the German class in Room 207. Students inside assumed he was lost and late for a lecture. Cho shut the door and resumed his wandering. He may have been dealing with last-minute regrets, mulling whether it was too late to turn back. More likely he was selecting his first target.&#13;
&#13;
He choose Room 206, where Professor Give Loganathan was giving a hydrology class. Cho simply walked in and started shooting. Aiming his two guns methodically around the class, he shot people repeatedly, wordlessly and without any hurry. Only four people survived in Room 207, by playing dead or being shielded by the bodies of their dead friends. Then Cho walked out. Yesterday, Loganathan was buried.&#13;
&#13;
In other classes, the popping sounds were greeted with confusion and fear. Some appeared to know exactly what they were; others thought it was noise from a nearby construction site. Cho walked into Room 207. He fired a bullet into the head of the German teacher, James Bishop, a well-liked 35-year-old. Cho then stood at the front of the class, killing students in the first rows and then moving to the rear. He fired and reloaded, fired and reloaded. Students fell dead or wounded. Others cowered behind desks.&#13;
&#13;
He went next into the French class in Room 211. Alarmed by the initial bangs, the teacher, Jocelyne Couture-Nowak, had asked her class in disbelief: &amp;#39;That&amp;#39;s not what I think it is?&amp;#39; It was. She told her students to get to the back of the class and began putting desks against the door. It was heroism on her part. But it was not enough. Cho barged in, shot her dead and then worked his way through her class.&#13;
&#13;
Cho then returned to Room 207. By then, students had blocked the door. Cho tried to force and shoot his way through. But, fighting for their lives, the students - some gravely wounded - held him off this time.&#13;
&#13;
It was the same in a computer class. Those students also fought off Cho, even though he fired at the door. There were many acts of heroism. Some staunched their friends&amp;#39; wounds and tied tourniquets around shattered limbs. Many blockaded doors despite having been shot. By now students and staff were fleeing through windows. As Cho walked from room to room, trying to find more people to shoot, he killed Kevin Granata, a biomechanics teacher who had served in the US armed forces. Granata had rushed downstairs and confronted Cho. He shot him dead.&#13;
&#13;
Then Cho tried to get into Room 204, where Professor Liviu Librescu was giving an engineering class. Librescu, a 76-year-old Holocaust survivor, had been urging his students to flee out of the windows. Most of them did. As Cho tried to enter the room, the ageing teacher flung himself against the door, buying vital time for more students to leave. But Librescu could not hold him off forever. Cho murdered him and entered the room.&#13;
&#13;
By now, it was almost over. Cho had fired more than 200 rounds, reloading an estimated 15 times. The police arrived, eventually smashing open the chained doors. Bodies lay everywhere in slicks of blood. Cho had shot many of them repeatedly in his determination to kill. Armed police moved from room to room, ordering wounded survivors to hold up their hands to show they had no weapons. Cho knew the end was near. He put one of his guns to his head and pulled the trigger. The shot almost tore off his face. When police found him, his guns at his side, they knew he was dead. &amp;#39;Shooter down! Black tag!&amp;#39; they screamed. Cho&amp;#39;s killing spree was over. The story of the horror he left behind had barely begun.&#13;
&#13;
When Cho&amp;#39;s identity was first released, it came as no surprise to a few who had had contact with the loner. It confirmed their worst fears. But to most, the reaction was simply: who? Gradually, piece by piece, a picture of Cho&amp;#39;s life has emerged. It is a disturbing one. Just as his time on campus was marked by solitude and anger, so was his school and childhood. Cho seemed to have been born in a personal mental prison from which he either could not escape or chose not to. The one true surprise was that this perpetrator of such an American crime originally came from many thousands of miles away.&#13;
&#13;
Cho was born in South Korea. His parents ran a small, second-hand book store in Seoul, the capital, and lived in a cramped apartment. They had been a reluctant husband and wife. Cho&amp;#39;s father was from a poor southern family, while his mother&amp;#39;s kin were landowners from the north, dispossessed during the Korean War.&#13;
&#13;
The marriage was arranged against the wife-to-be&amp;#39;s wishes, but she had little choice. The family struggled to build a life and eventually moved to America at the invitation of relatives. They arrived in 1992, hoping for the best for their two children. They worked hard, in a laundry and a restaurant. And, like so many determined immigrants, they made it. They lived in a pleasant Washington DC suburb. Cho&amp;#39;s sister, Sun, went to Princeton.&#13;
&#13;
But there was one cloud on this heart-warming story of success: Cho himself. Back in South Korea, the family had noticed his deep, sullen silences as an infant. His grandfather worried he might be mute; his mother thought he was mentally ill. A committed Christian, she tried to involve her church in reaching out to the boy after his silences grew worse on the move to America. She prayed for him regularly. It did not make for a happy teenage existence.&#13;
&#13;
Clearly depressed and struggling with English, Cho became a target for bullies at Westfield High School in nearby Chantilly. Once, after refusing to read aloud in an English class, Cho was forced to speak. When he did, students laughed at his strange voice and told him to &amp;#39;go back to China&amp;#39;. He was teased as the &amp;#39;trombone kid&amp;#39; for his habit of walking to school alone carrying his musical instrument. He rarely spoke, playing solitary basketball in his home&amp;#39;s quiet cul-de-sac and ignoring the hellos of his neighbours.&#13;
&#13;
Things got worse in college. His fellow students remember reaching out to him at the start of class or when they moved into a dorm with him. He was invited to dine with them at local restaurants. But Cho showed little interest in talking. He would ignore them or answer in one-word replies. It was the same in class: Cho sat at the back, wearing dark glasses and a baseball cap.&#13;
&#13;
In one now notorious incident, when he filled out a sign-in sheet at the start of a literature class, he refused to write his name. Instead he put a question mark. In campus banter, Cho had turned from the &amp;#39;trombone kid&amp;#39; to the &amp;#39;question mark kid&amp;#39;. It became his totem. One of the girls he stalked awoke one morning to find a large question mark written on her room&amp;#39;s message board.&#13;
&#13;
Undoubtedly Cho&amp;#39;s stone-like facade hid a mind in deep distress. A few signs broke the surface. Once, at a party, Cho revealed to room-mates that he had a girlfriend, presumably imaginary. She was called Jelly, he said. She was a model and she called him Spanky. It was a brief and bizarre glimpse into Cho&amp;#39;s inner world. Another incident occurred after he had been reprimanded for bothering a girl student. In a quiet moment, he told one room-mate that he had wanted to look in her eyes and see if she was as &amp;#39;cool&amp;#39; as he thought. But he had been disappointed. He had gone to her dorm room and seen only &amp;#39;promiscuity&amp;#39;.&#13;
&#13;
Such insights were few and far between. Some students joked about him being a possible college shooter. One teacher had a codeword she could use when teaching him if she became fearful for herself. It sounds dramatic, but she never used it. Cho continued to keep to himself. He wore sunglasses in class. He had no friends. His room had no pictures or posters. He often just stared blankly at the walls or ceiling. He slept with the light on and never shut his door. He was a walking void.&#13;
&#13;
The silence Cho maintained in life was broken after his death. The package he sent to NBC contained 29 photographs, 27 short videos and an 1,800-word diatribe. In the clips, Cho is hard-eyed, his voice a tense, controlled staccato of rage. He speaks quickly but clearly. He is no longer silent. The pent-up emotions of his damaged psyche boil to the surface. Cho finally revealed himself.&#13;
&#13;
Cho was severely mentally ill: no sane person murders 32 people. But such sicknesses vary greatly. Cho was no serial killer. He was not a sociopath. In fact, experts say, Cho&amp;#39;s rampage was a form of suicide. He killed because he considered himself the victim; those he killed he saw as villains. &amp;#39;This was revenge. He wanted to kill himself, but first he was going to take others with him, people he saw as persecuting him,&amp;#39; said Professor Jack Levin, an expert on mass murderers at Northeastern University in Boston.&#13;
&#13;
Certainly that was what emerged from Cho&amp;#39;s own words. He felt himself utterly victimised. &amp;#39;You have vandalised my heart, raped my soul and torched my conscience. I die like Jesus Christ, to inspire generations of the weak and the defenceless people,&amp;#39; he said. &amp;#39;You&amp;#39; was the world as a whole, especially the students who he felt ignored him.&#13;
&#13;
He claimed he had not chosen to kill but had been forced into it. The coming massacre, he warned, was not his fault. &amp;#39;You had a hundred billion chances and ways to have avoided today, but you decided to spill my blood. You forced me into a corner and gave me only one option. The decision was yours. Now you have blood on your hands that will never wash off.&amp;#39; Such transference of blame is rare among serial killers, for whom blame or guilt are alien concepts. &amp;#39;It is a very elaborate blaming system. These people come from a sense of powerlessness,&amp;#39; said Gregg McCrary, a former FBI profiler.&#13;
&#13;
Cho also railed against what he saw as hedonism and materialism all around, perhaps revealing a deep resentment of his poorer background. &amp;#39;Your Mercedes wasn&amp;#39;t enough, you brats,&amp;#39; he cried &amp;#39;Your golden necklaces weren&amp;#39;t enough, you snobs. Your trust fund wasn&amp;#39;t enough. Your vodka and cognac weren&amp;#39;t enough. All your debaucheries weren&amp;#39;t enough. Those weren&amp;#39;t enough to fulfil your hedonistic needs.&amp;#39;&#13;
&#13;
It was the product of a diseased mind, but the words strike a tone horribly familiar to those who had shared creative writing classes with Cho. In poetry and drama classes, Cho had consistently produced work whose violence, sexual imagery and anger had upset classmates and teachers. One former student, Ian MacFarlane, had kept copies of Cho&amp;#39;s two plays and posted them on-line. They are deeply disturbing. One, Richard McBeef, deals with a young man confronting his step-father about murder and child abuse. The second - Mr Brownstone - has three students describing their desire to kill a sadistic teacher. Reading the plays is not easy. They are violent, profane and obsessed with scatological sex. They are not like reading the mind of a deranged 23-year-old: they are like reading the mind of a deranged 13-year-old. MacFarlane said he had thought of what he would do if Cho were ever to bring a gun to class. &amp;#39;I was that freaked about him,&amp;#39; he said.&#13;
&#13;
As people struggle to understand Cho, many experts think the specifics are not important. It is the tone of persecution and victimhood that matter. &amp;#39;He is clearly clinically depressed, probably delusional, and has been so for a very long period of time,&amp;#39; said Levin.&#13;
&#13;
There are other tantalising clues the meaning of which may never be known. Cho was found with the words &amp;#39;Ismail Ax&amp;#39; in red ink on his arm. The return address on the NBC package was &amp;#39;A. Ishmael&amp;#39;. It is impossible to know what that means, but suggestions have varied from the Bible to the Koran to Moby Dick to a Turkish hip hop artist. One literary reference Cho used was obvious. He quoted Romeo and Juliet. &amp;#39;My name, dear saint, is hateful to myself,&amp;#39; he wrote. Cho picked out the words about forbidden love and turned them against his own identity. It was morbidly fitting. He had denied his own name in class. His last act in life was to blast off his own face.&#13;
&#13;
Cho Seung-hui did not exist in a vacuum. His actions sprang from the gun-drenched culture of America where buying a rifle can be as easy as buying groceries. The shop where Cho bought his Glock is Roanoke Firearms, standing on a busy road about half an hour&amp;#39;s drive from Blacksburg. A bumper sticker on one wall declares, &amp;#39;Buy A Gun For America&amp;#39;.&#13;
&#13;
America is a highly armed society. Gun rights groups argue that citizens have to be able to defend themselves. Yet it is also easy for deranged people to obtain powerful firearms.&#13;
&#13;
The statistics speak for themselves. There are 200 million privately held guns in America. Each year, they cause roughly 30,000 deaths and 300,000 gun-related assaults.&#13;
&#13;
Cho&amp;#39;s massacre is just a drop in a very bloody pool. &amp;#39;It is long overdue for us to take some commonsense actions to prevent tragedies like this from continuing to occur,&amp;#39; said Paul Helmke, president of the Brady Campaign to Prevent Gun Violence.&#13;
&#13;
That such steps have not been taken yet is the result of the power of the National Rifle Association and the popular worship of gun use it encourages. The NRA is one of the most effective lobbying groups in American politics. It is motivated by a desire to protect the right of any American to own, carry and use firearms. It has an annual budget of $180m and 3.8 million members. The NRA also contributes about nine times more money to politicians&amp;#39; campaign coffers than gun control groups.&#13;
&#13;
Even now, even after Cho and his two hours of carnage, few politicians dare speak out against gun rights, despite the fact that Congress is now controlled by the Democrats. In fact, the one thing that seems certain in a post-Cho America is that another such massacre will happen again, and that it may possibly be even worse, as each perpetrator attempts to &amp;#39;beat&amp;#39; the last.&#13;
&#13;
Already a spate of copycat incidents have occurred across the country. In Houston, a man killed a hostage and himself at the Nasa space centre. In Florida, a teenager was arrested after threatening in an email to kill 100 people. Near Seattle, another high school student was arrested while in possession of three loaded guns. Classes in a Nevada university were cancelled after a man sent a text message saying: &amp;#39;The Korean is my hero.&amp;#39;&#13;
&#13;
The saturation media coverage, and especially the controversial broadcast of Cho&amp;#39;s videos, will provide an anti-hero for some disturbed youth. Somewhere in America, in some school or college, a future Cho may already be allowing themselves to think along the same lines: loneliness, victimhood, revenge and suicide - and all on a world stage. They will not find it hard to find guns with which to kill. &amp;#39;We are in trouble. This is not the end of it,&amp;#39; said Levin.&#13;
&#13;
But, just as Cho&amp;#39;s actions reveal the dark heart of an American society at home with firearms, it also reveals the other country, the emotional America, the America of positives. The America of his victims.&#13;
&#13;
The roll call of the dead speaks of a land of variety and opportunity. The dead should not be defined by dying at Cho&amp;#39;s hands, but by their own lives and deeds. They came from everywhere. There was Minal Panchal from Mumbai, a graduate student in architecture. There was Juan Ortiz Ortiz from Puerto Rico, who loved to dance salsa and played the timbales. There was Waleed Shaalan, 32, from Egypt, who leaves behind a widow and three fatherless children. Professor Librescu had escaped the Nazis and Romanian communism only to give up his life for his students.&#13;
&#13;
There were also young American women, full of hope and prospects - girls like Hilscher, whose small frame led her to name herself &amp;#39;Pixie&amp;#39;. Or Reema Samaha, 18, who loved dancing and planned to spend the summer in France, working at a children&amp;#39;s camp. Or Austin Cloyd, 18, the daughter of a Virginia Tech professor, who went on Christian mission trips in the Appalachian mountains, repairing the roofs and plumbing of the poorest of the poor. Or Erin Peterson, 18, a star basketball player who was as gentle off court as she was ferocious on it.&#13;
&#13;
They were also young men such as Jarrett Lan, 28, who was about to graduate in civil engineering and had been a four-sport athlete at his high school. Or Henry Lee, who had come to the US from China barely able to speak English. He belonged to an internet socialising group called &amp;#39;My name is Henry Lee&amp;#39; with other people sharing his name. In a recent online post, he had joked about having a convention. &amp;#39;We wouldn&amp;#39;t need name tags,&amp;#39; he wrote.&#13;
&#13;
Cho&amp;#39;s victims spanned a vast spectrum of life. They were young, middle-aged, elderly. They were students and professors. They were men and women. They were biologists, engineers and linguists. They were black, white, Middle Eastern, Jewish and Asian. They were Christian. Hindu, Jewish and Muslim. They were American and foreign-born. They had all started that terrible Monday in the expectation that their lives would continue. Cho cut them short, suddenly and inexplicably, leaving behind unimaginable grief for husbands, wives, mothers, fathers, children, colleagues and friends.&#13;
&#13;
But Cho also ensured they were honoured in their deaths. Their lives were celebrated by a mourning nation. Amid all the tributes springing up on campus, the tone is one of happy remembrance as well as grief. Perhaps one example among the thousands can stand for them all. It was written to Reema Samaha: &amp;#39;Reema, wherever you are, I know that your smile and your dancing is joyous.&amp;#39;&#13;
&#13;
Cho&amp;#39;s own family are in hiding under police protection. They are also shattered and despairing. Late last Friday, Cho&amp;#39;s sister, Sun, released a statement for the family as a whole. It mentioned each victim by name. &amp;#39;Each of these people had so much love, talent and gifts to offer, and their lives were cut short by a horrible and senseless act,&amp;#39; Sun said. &amp;#39;My brother was quiet and reserved, yet struggled to fit in. We never could have envisioned that he was capable of so much violence.&amp;#39;&#13;
&#13;
There is still a long way, a marathon, for this college, town and country to travel on the road to recovery. And incredibly many are determined to take Cho along with them. There is very little anger at Cho on campus, just disbelief and despair. He is not hated: he is pitied by many who wonder how someone can commit such evil, and slaughter 32 fellow human beings. Steven Dellinger, 20, stood on a rise in front of the main memorial. He thought about Cho all the time, he said. &amp;#39;I just wish someone had got to him. If only he had been able to have a friend who could have helped him out.&amp;#39;&#13;
&#13;
Behind Dellinger, a row of stone blocks - a memorial - has been laid out in a semi-circle, hugging a cluster of candles and messages. Each unmarked stone is topped with a flower and a Virginia Tech pennant. They represent the dead. There are 33 stones.&#13;
&#13;
Cho, whose lonely life turned his mind in ways one can hardly imagine, finally has company.&#13;
&#13;
&#13;
&lt;B&gt;On Guardian Unlimited&lt;/B&gt;&lt;BR&gt;&lt;A HREF="http://www.guardian.co.uk/usa/virginiashooting/"&gt;Full coverage of the Virginia Tech shootings&lt;/A&gt;&lt;BR&gt;&lt;A HREF="http://www.guardian.co.uk/usguns/0,,182056,00.html"&gt;Gun violence in the US&lt;/A&gt;&lt;BR&gt;&lt;A HREF="http://www.guardian.co.uk/gun/0,,178412,00.html"&gt;Gun violence in Britain&lt;/A&gt;&lt;BR&gt;&lt;A HREF="http://www.guardian.co.uk/usa/0,,759893,00.html"&gt;Full US coverage&lt;/A&gt;&lt;BR&gt;&lt;BR&gt;&lt;B&gt;Related articles&lt;/B&gt;&lt;BR&gt;&lt;A HREF="http://www.guardian.co.uk/usguns/Story/0,,2059217,00.html"&gt;Virginia massacre gunman named&lt;/A&gt;&lt;BR&gt;&lt;A HREF="http://www.guardian.co.uk/usa/story/0,,2059103,00.html"&gt;Unofficial list of shooting victims emerges&lt;/A&gt;&lt;BR&gt;&lt;A HREF="http://www.guardian.co.uk/usa/story/0,,2058887,00.html"&gt;Massacre on campus&lt;/A&gt;&lt;BR&gt;&lt;A HREF="http://www.guardian.co.uk/usa/story/0,,2059250,00.html"&gt;Q&amp;A: US gun laws&lt;/A&gt;&lt;BR&gt;&lt;BR&gt;&lt;B&gt;World news guide&lt;/B&gt;&lt;BR&gt;&lt;A HREF="http://www.guardian.co.uk/worldnewsguide/northamerica/0,,618255,00.html"&gt;North American Media&lt;/A&gt;&lt;BR&gt;&lt;BR&gt;&lt;B&gt;Media&lt;/B&gt;&lt;BR&gt;&lt;A HREF="http://edition.cnn.com/"&gt;CNN&lt;/A&gt;&lt;BR&gt;&lt;A HREF="http://www.nytimes.com/"&gt;New York Times&lt;/A&gt;&lt;BR&gt;&lt;A HREF="http://www.washingtonpost.com/"&gt;Washington Post&lt;/A&gt;&lt;BR&gt;&lt;BR&gt;&lt;B&gt;Government&lt;/B&gt;&lt;BR&gt;&lt;A HREF="http://www.state.va.us/cmsportal2/"&gt;Virginia state government portal&lt;/A&gt;&lt;BR&gt;&lt;A HREF="http://www.usa.gov/"&gt;US government portal&lt;/A&gt;&lt;BR&gt;&lt;A HREF="http://www.whitehouse.gov/"&gt;White House&lt;/A&gt;&lt;BR&gt;&lt;A HREF="http://www.senate.gov/"&gt;Senate&lt;/A&gt;&lt;BR&gt;&lt;A HREF="http://www.house.gov/"&gt;House of Representatives&lt;/A&gt;&#13;
&#13;
--&#13;
&#13;
Copyright Guardian News &amp; Media Ltd 2007.&#13;
&#13;
Original Source: Guardian Unlimited / EducationGuardian.co.uk&#13;
&lt;a href="http://education.guardian.co.uk/higher/news/story/0,,2063553,00.html"&gt;http://education.guardian.co.uk/higher/news/story/0,,2063553,00.html&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10043">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11944">
                <text>In consideration of the fee of GBP 0.00 ("the Fee") Guardian News &amp; Media Limited ("GNM") grants the Licensee the right to: publish on its website for 10 years.&#13;
&#13;
Contact info: Eve Thompson; permissions.syndication@guardian.co.uk&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13444">
                <text>The killer of room 2121</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1418">
        <name>amish</name>
      </tag>
      <tag tagId="323">
        <name>cho</name>
      </tag>
      <tag tagId="1420">
        <name>essay</name>
      </tag>
      <tag tagId="1419">
        <name>room 2121</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1025" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2326">
                <text>Sara  Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4217">
                <text>Lisa Davis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6195">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8073">
                <text>&lt;b&gt;Emergency notification system a main goal&lt;/b&gt;&#13;
&#13;
By: Lisa Davis&#13;
Posted: 5/2/07&#13;
&#13;
After Boston University felt the impact of several tragedies that brought into question the level of campus safety, officials say they will continue to review their safety policies and procedures, including ways to better reach the community in case of an emergency.&#13;
&#13;
"These events are starting to highlight, not only on our campus, but on other campuses, this issue of personal safety and risky behavior in a broader context than people have thought about it before," said President Robert Brown in an April 27 interview.&#13;
&#13;
Methods the BU Police Department uses to communicate emergency information to the community are important, said BUPD Chief Thomas Robbins, who added his department often reviews its procedures when a problem arises.&#13;
&#13;
"How you communicate in different emergencies is different," Brown said. "There is not one size that fits all."&#13;
&#13;
Robbins, who attended a Coffee and Conversation with the dean of students after the April 16 Virginia Tech shootings, said BUPD plans to add safety information for students to its website, similar to how BU launched a fire-safety website after the two deadly fires that killed three students Feb. 24 and March 16.&#13;
&#13;
The day after the Virginia Tech shootings, in which senior Cho Seung-Hui killed 32 people before killing himself, BU formed a committee headed by Administration Vice President Peter Fiedler to review emergency and communication policies, Brown said.&#13;
&#13;
"One of the things we put on the table was a blast communication system, which we do not have," he said. "People think that you can send 20,000 emails instantly. The fact is: It takes about 30 minutes to an hour, depending on the technology you&amp;#39;re using and how you do it."&#13;
&#13;
In a town hall meeting last week, Robbins said he is considering the use of email and text messaging to contact the community in an emergency.&#13;
&#13;
It is currently impossible to reach every community member at once because the BU registry does not require telephone numbers and email addresses, Brown said, adding the committee is considering a change to his policy changing this policy.&#13;
&#13;
"The reasons you would like an emergency communication system are varied, and I don&amp;#39;t think I would couple it just directly with the Virginia Tech shooter incident," he said.&#13;
&#13;
After the two off-campus fires, inspectors visited residence halls and reviewed their fire-alarm procedures.&#13;
&#13;
Brown said although it is important for BUPD to treat BU as a community, police must be trained to "deal with violent or disruptive acts that you&amp;#39;d find in any urban environment."&#13;
&#13;
"I think the most important thing for us, which I&amp;#39;ve said many times, is that we have a truly professionally trained police force," Brown said.&#13;
&#13;
BUPD trains with the Boston Police Department, and BUPD officers are official Boston police officers, Robbins said.&#13;
&#13;
"One of the things we train on is how to deal with Columbine or Virginia Tech [incidents]," Robbins said. "I&amp;#39;m comfortable of our response we have."&#13;
&#13;
BUPD works toward having its policies and standards match those of police and fire departments across the country through state and national accreditation, said BUPD spokesman Sgt. Jack St. Hilaire.&#13;
&#13;
"We&amp;#39;ve always had a good relationship [with BU], and nothing has happened to change that," said BFD spokesman Steve MacDonald. "We&amp;#39;re responsive when they bring things to our attention."&#13;
&#13;
Boston Emergency Medical Response Chief Richard Serino said EMS has regular exercises in which Boston officials meet to discuss their responses to certain issues and to become familiar with each other. EMS held a meeting last week to address the best ways to respond to shootings, Serino said.&#13;
&#13;
"I think that most colleges in Boston have well-trained, well-equipped public safety staff," Serino said. "We are on a lot of college campuses on a regular basis."&#13;
&#13;
MacDonald said it is easier to deal with fires on campus than in off-campus apartment buildings because BU works closely with BFD.&#13;
&#13;
"Usually, it works smoother from our end, dealing with the colleges and universities, because they have full-time staff who work 24 hours a day," he said.&#13;
&#13;
BUPD, which announced last month it will revamp its methods, for analyzing a revamp in its methods for analyzing "hot spot" crime locations and how the officer force is divided into sections, will respond to any location on the Charles River and Medical campuses in two minutes or less, Robbins said.&#13;
&#13;
"We have authority to stop all traffic, including trains," said Robbins, who served as the Massachusetts State Police superintendent before coming to BU in June 2006.&#13;
&#13;
Although most parents are concerned about their child&amp;#39;s safety, it is difficult for BU to hold students&amp;#39; attention about safety resources, Brown said.&#13;
&#13;
"We will have changes in orientation next summer that are not reactionary," he said, "[but] that are trying to change behavior of students as they come into our community, and to make them aware of risks and choices they make."&#13;
&#13;
The Charles River campus, which is situated along the traffic-heavy Commonwealth Avenue, can be a safety hazard to students who are not responsible pedestrians, Brown said.&#13;
&#13;
"We should not have to instruct people on how to cross the street safely at the age of 18," he said.&#13;
&#13;
There are no plans to change academic curricula to incorporate safety information, Brown said.&#13;
&#13;
"The question is: What is the balance between personal responsibility and the university&amp;#39;s responsibility?" Brown said.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailyfreepress.com/media/storage/paper87/news/2007/05/02/News/Final.Week.Bu.To.Review.Policies.For.Campus.Security-2891718.shtml&gt;The Daily Free Press - May 2, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10044">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11945">
                <text>Matt Negrin &lt;editor@dailyfreepress.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13445">
                <text>Final Week: BU to review policies for campus security</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1423">
        <name> campus response</name>
      </tag>
      <tag tagId="1421">
        <name> safety</name>
      </tag>
      <tag tagId="1422">
        <name> university policy</name>
      </tag>
      <tag tagId="895">
        <name>boston university</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1026" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  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="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2327">
                <text>Sara  Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4218">
                <text>Don Lucas</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6196">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8074">
                <text>By: Don Lucas&#13;
Posted: 4/30/07&#13;
&#13;
Two weeks ago, I was shocked once again when a maniac took so many innocent lives at Virginia Tech. I focused on the many news events that followed this tragedy in my home state.&#13;
&#13;
I reflected on the campus, wrapped in such scenic beauty, where my many of my friends attended and later taught. Virginia Tech is a university in which many of my former students attended. It is also a university where my former students and I visited while teaching and performing music.&#13;
&#13;
As I continued to watch the television coverage throughout the week, I had many reflections and feelings, including shock, outrage and compassion.&#13;
Late last week, officials posted a letter written by the sister of the murderer. Her words touched me very much. I felt her pain and hurt for those who suffered at the hands of her brother. I perceived her words to be most sincere and heartfelt. In a week of such tragedy, this is the moment that produced my tears. I couldn&amp;#39;t help but think she didn&amp;#39;t have to write that letter. But she did.&#13;
&#13;
In the last ten years, I have had the opportunity to teach and perform music in South Korea on four occasions, most recently at Yonsei University in Seoul. During my first trip, I remember an older man looking me straight in the eyes and thanking me for the United States&amp;#39; intervention in his country years ago.&#13;
&#13;
I am very proud of the United States&amp;#39; involvement in the Korean War. South Korea is a beautiful country, a beautiful culture and a beautiful people. The Daily Free Press&amp;#39;s article ("After VT, Koreans prepare for backlash," April 25, p. 1) quite, and cited the Korean values of community support. I would like to add the values of courtesy and a great work ethic. At the end of the Korean War, South Korea was one of the poorest countries in the world. Today, South Korea has the eighth-highest gross national product wordwide.&#13;
&#13;
I read in a recent book by Lee Iacocca that of all international students recently rated in math and science, Korean students scored the highest.&#13;
&#13;
The Virginia Tech killer did not reflect Korean values. But his sister did.&#13;
&#13;
I also have been reflecting on many of the Korean students at Boston University whom I interact with on our campus. These students continually demonstrate an excellence with dignity and class.&#13;
&#13;
I was so pleased to see written in the article that there have been no backlash incidents reported among the BU community. I am proud of our BU community in this regard.&#13;
&#13;
It is understandable to regret when a tragedy has happened by persons from one&amp;#39;s own culture. I have felt this many times as a U.S. citizen. I have also felt pride in the United States. But I hope the readers of the Free Press will join me in answering Clara Pyo and all the students of the Korean Student Association.&#13;
&#13;
Yes, Pyo should celebrate, because her heritage, the heritage of South Korea, is still a proud heritage.&#13;
&#13;
Don Lucas&#13;
Associate Professor of Music and Chairman, Brass, Woodwind, Percussion&#13;
&#13;
College of Fine Arts</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10045">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="11153">
                <text>The Daily Free Press</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11946">
                <text>Matt Negrin &lt;editor@dailyfreepress.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13446">
                <text>LETTER: Shooter didn&amp;#39;t represent Korea</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1230">
        <name> blame</name>
      </tag>
      <tag tagId="1424">
        <name> korean identity</name>
      </tag>
      <tag tagId="1425">
        <name> representation</name>
      </tag>
      <tag tagId="895">
        <name>boston university</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
