<?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?output=omeka-xml&amp;page=67&amp;sort_field=Dublin+Core%2CCreator" accessDate="2026-04-13T06:33:47+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>67</pageNumber>
      <perPage>20</perPage>
      <totalResults>1884</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="245" public="1" featured="0">
    <fileContainer>
      <file fileId="161">
        <src>https://www.april16.vtlibraries.net/files/original/We Are Virginia Tech_5c0d81c866.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="14559">
                    <text>2007-05-25</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="15679">
                    <text>2007-05-25 10:57:57</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="1599">
                <text>Chad Newswander</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3490">
                <text>Max Power</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="5468">
                <text>2007-05-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7347">
                <text>The memorial at the Drill Field near Burress Hall and Norris Hall. &#13;
&#13;
Original source: &lt;a href=" http://www.flickr.com/photos/maxpower/468742227/"&gt; http://www.flickr.com/photos/maxpower/468742227/&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href=" http://creativecommons.org/licenses/by-sa/2.0/"&gt;Creative Commons Attribution-ShareAlike 2.0&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9317">
                <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="11327">
                <text>Permission&#13;
Contact: Max Power&#13;
(http://www.flickr.com/photos/maxpower/468742227/)&#13;
Creative Commons Attribution-ShareAlike 2.0&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12794">
                <text>We Are Virginia Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="342">
        <name>drill field</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="343">
        <name>we are virginia tech</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2804" public="1" featured="0">
    <fileContainer>
      <file fileId="1311">
        <src>https://www.april16.vtlibraries.net/files/original/drillfieldtentsunjpg_72fdd784aa.jpg</src>
        <authentication>918026c95741753c847d45bd3ef87f46</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="75">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17912">
                    <text>1280</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="76">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17930">
                    <text>960</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="77">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17948">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="78">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17966">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="82">
                <name>IPTC Array</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="18018">
                    <text>a:0:{}</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="8">
        <name>Contribution Form</name>
        <description>The set of elements containing metadata from the Contribution form.</description>
        <elementContainer>
          <element elementId="39">
            <name>Submission Consent</name>
            <description>Indicates whether or not the contributor of this Item has given permission to submit this to the archive. (Yes/No)</description>
            <elementTextContainer>
              <elementText elementTextId="1095">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Posting Consent</name>
            <description>Indicates whether or not the contributor of this Item has given permission to post this to the archive. (Yes/No)</description>
            <elementTextContainer>
              <elementText elementTextId="1096">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Online Submission</name>
            <description>Indicates whether or not this Item has been contributed from a front-end contribution form.</description>
            <elementTextContainer>
              <elementText elementTextId="1097">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="89">
            <name>Contributor is Creator</name>
            <description>Indicates whether or not the contributor of the Item is responsible for its creation.</description>
            <elementTextContainer>
              <elementText elementTextId="18030">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
      <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="3263">
                <text>Megan  Minter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5241">
                <text>Megan  Minter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9093">
                <text>The sun shining over the tent full of memorials on the Drillfield one evening</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12572">
                <text>	You are contributing your stories and/or files to The April 16 Archive, which is developing a permanent digital record of the events surrounding the tragedy on the Virginia Tech campus on April 16, 2007. Your participation in this project will allow future researchers, and people such as yourself, to gain a greater understanding of these events and the responses to them.&#13;
		&#13;
	You must be 13 years of age or older to submit material to us. Your submission of material constitutes your permission for, and consent to, its dissemination and use in connection with The April 16 Archive in all media in perpetuity. If you have so indicated on the form, your material will be published on The April 16 Archive web site (with or without your name, depending on what you have indicated). Otherwise, your submitted materials will only be available to approved researchers using The April 16 Archive. The material you submit must have been created by you, wholly original, and shall not be copied from or based, in whole or in part, upon any other photographic, literary, or other material, except to the extent that such material is in the public domain. Further, submitted material must not violate any confidentiality, privacy, security or other laws.&#13;
&#13;
	By submitting material to The April 16 Archive you release, discharge, and agree to hold harmless The April 16 Archive and persons acting under its permission or authority, including a public library or archive to which the collection might be donated for purposes of long-term preservation, from any claims or liability arising out the The April 16 Archive's use of the material, including, without limitation, claims for violation of privacy, defamation, or misrepresentation.&#13;
&#13;
	The April 16 Archive has no obligation to use your material.&#13;
&#13;
	You will be sent via email a confirmation of your contribution to The April 16 Archive. We cannot return any material you submit to us so be sure to keep a copy. The April 16 Archive will not share your email address or any other information with commercial vendors.&#13;
	</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14400">
                <text>Drillfield tent</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2805" public="1" featured="0">
    <fileContainer>
      <file fileId="1312">
        <src>https://www.april16.vtlibraries.net/files/original/bearhugs_2b5e9bae36.jpg</src>
        <authentication>6356b458524b4314c540a3559a85c5a1</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="75">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17913">
                    <text>534</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="76">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17931">
                    <text>458</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="77">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17949">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="78">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17967">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="82">
                <name>IPTC Array</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="18019">
                    <text>a:0:{}</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="8">
        <name>Contribution Form</name>
        <description>The set of elements containing metadata from the Contribution form.</description>
        <elementContainer>
          <element elementId="39">
            <name>Submission Consent</name>
            <description>Indicates whether or not the contributor of this Item has given permission to submit this to the archive. (Yes/No)</description>
            <elementTextContainer>
              <elementText elementTextId="1098">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Posting Consent</name>
            <description>Indicates whether or not the contributor of this Item has given permission to post this to the archive. (Yes/No)</description>
            <elementTextContainer>
              <elementText elementTextId="1099">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Online Submission</name>
            <description>Indicates whether or not this Item has been contributed from a front-end contribution form.</description>
            <elementTextContainer>
              <elementText elementTextId="1100">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="89">
            <name>Contributor is Creator</name>
            <description>Indicates whether or not the contributor of the Item is responsible for its creation.</description>
            <elementTextContainer>
              <elementText elementTextId="18031">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
      <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="3264">
                <text>Megan  Minter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5242">
                <text>Megan  Minter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9094">
                <text>Free bear hugs set up in the Cheatham Hall student lounge shortly after Apr 16 2007</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12573">
                <text>	You are contributing your stories and/or files to The April 16 Archive, which is developing a permanent digital record of the events surrounding the tragedy on the Virginia Tech campus on April 16, 2007. Your participation in this project will allow future researchers, and people such as yourself, to gain a greater understanding of these events and the responses to them.&#13;
		&#13;
	You must be 13 years of age or older to submit material to us. Your submission of material constitutes your permission for, and consent to, its dissemination and use in connection with The April 16 Archive in all media in perpetuity. If you have so indicated on the form, your material will be published on The April 16 Archive web site (with or without your name, depending on what you have indicated). Otherwise, your submitted materials will only be available to approved researchers using The April 16 Archive. The material you submit must have been created by you, wholly original, and shall not be copied from or based, in whole or in part, upon any other photographic, literary, or other material, except to the extent that such material is in the public domain. Further, submitted material must not violate any confidentiality, privacy, security or other laws.&#13;
&#13;
	By submitting material to The April 16 Archive you release, discharge, and agree to hold harmless The April 16 Archive and persons acting under its permission or authority, including a public library or archive to which the collection might be donated for purposes of long-term preservation, from any claims or liability arising out the The April 16 Archive's use of the material, including, without limitation, claims for violation of privacy, defamation, or misrepresentation.&#13;
&#13;
	The April 16 Archive has no obligation to use your material.&#13;
&#13;
	You will be sent via email a confirmation of your contribution to The April 16 Archive. We cannot return any material you submit to us so be sure to keep a copy. The April 16 Archive will not share your email address or any other information with commercial vendors.&#13;
	</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14401">
                <text>Bear Hugs</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="2550">
        <name>bear</name>
      </tag>
      <tag tagId="2548">
        <name>Cheatham</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2806" public="1" featured="0">
    <fileContainer>
      <file fileId="1313">
        <src>https://www.april16.vtlibraries.net/files/original/welcometo_cheatham_bb343ee691.jpg</src>
        <authentication>7be70f81c38841f382c120c22df63caf</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="75">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17914">
                    <text>529</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="76">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17932">
                    <text>592</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="77">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17950">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="78">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17968">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="82">
                <name>IPTC Array</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="18020">
                    <text>a:0:{}</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="8">
        <name>Contribution Form</name>
        <description>The set of elements containing metadata from the Contribution form.</description>
        <elementContainer>
          <element elementId="39">
            <name>Submission Consent</name>
            <description>Indicates whether or not the contributor of this Item has given permission to submit this to the archive. (Yes/No)</description>
            <elementTextContainer>
              <elementText elementTextId="1101">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Posting Consent</name>
            <description>Indicates whether or not the contributor of this Item has given permission to post this to the archive. (Yes/No)</description>
            <elementTextContainer>
              <elementText elementTextId="1102">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Online Submission</name>
            <description>Indicates whether or not this Item has been contributed from a front-end contribution form.</description>
            <elementTextContainer>
              <elementText elementTextId="1103">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="89">
            <name>Contributor is Creator</name>
            <description>Indicates whether or not the contributor of the Item is responsible for its creation.</description>
            <elementTextContainer>
              <elementText elementTextId="18032">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
      <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="3265">
                <text>Megan  Minter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5243">
                <text>Megan  Minter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9095">
                <text>A sign posted on a door to Cheatham Hall directing students from Norris to their new classrooms in the aftermath</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12574">
                <text>	You are contributing your stories and/or files to The April 16 Archive, which is developing a permanent digital record of the events surrounding the tragedy on the Virginia Tech campus on April 16, 2007. Your participation in this project will allow future researchers, and people such as yourself, to gain a greater understanding of these events and the responses to them.&#13;
		&#13;
	You must be 13 years of age or older to submit material to us. Your submission of material constitutes your permission for, and consent to, its dissemination and use in connection with The April 16 Archive in all media in perpetuity. If you have so indicated on the form, your material will be published on The April 16 Archive web site (with or without your name, depending on what you have indicated). Otherwise, your submitted materials will only be available to approved researchers using The April 16 Archive. The material you submit must have been created by you, wholly original, and shall not be copied from or based, in whole or in part, upon any other photographic, literary, or other material, except to the extent that such material is in the public domain. Further, submitted material must not violate any confidentiality, privacy, security or other laws.&#13;
&#13;
	By submitting material to The April 16 Archive you release, discharge, and agree to hold harmless The April 16 Archive and persons acting under its permission or authority, including a public library or archive to which the collection might be donated for purposes of long-term preservation, from any claims or liability arising out the The April 16 Archive's use of the material, including, without limitation, claims for violation of privacy, defamation, or misrepresentation.&#13;
&#13;
	The April 16 Archive has no obligation to use your material.&#13;
&#13;
	You will be sent via email a confirmation of your contribution to The April 16 Archive. We cannot return any material you submit to us so be sure to keep a copy. The April 16 Archive will not share your email address or any other information with commercial vendors.&#13;
	</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14402">
                <text>Norris classes moved</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="2549">
        <name>aftermath</name>
      </tag>
      <tag tagId="2548">
        <name>Cheatham</name>
      </tag>
      <tag tagId="49">
        <name>Norris</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2807" public="1" featured="0">
    <fileContainer>
      <file fileId="1314">
        <src>https://www.april16.vtlibraries.net/files/original/dsc01015_6ca8c7488c.jpg</src>
        <authentication>83bbde9f0c2ebf9e72c7b6f5a870d9f2</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="75">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17915">
                    <text>2592</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="76">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17933">
                    <text>1944</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="77">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17951">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="78">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17969">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="82">
                <name>IPTC Array</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="18021">
                    <text>a:0:{}</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="8">
        <name>Contribution Form</name>
        <description>The set of elements containing metadata from the Contribution form.</description>
        <elementContainer>
          <element elementId="39">
            <name>Submission Consent</name>
            <description>Indicates whether or not the contributor of this Item has given permission to submit this to the archive. (Yes/No)</description>
            <elementTextContainer>
              <elementText elementTextId="1104">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Posting Consent</name>
            <description>Indicates whether or not the contributor of this Item has given permission to post this to the archive. (Yes/No)</description>
            <elementTextContainer>
              <elementText elementTextId="1105">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Online Submission</name>
            <description>Indicates whether or not this Item has been contributed from a front-end contribution form.</description>
            <elementTextContainer>
              <elementText elementTextId="1106">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="89">
            <name>Contributor is Creator</name>
            <description>Indicates whether or not the contributor of the Item is responsible for its creation.</description>
            <elementTextContainer>
              <elementText elementTextId="18033">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
      <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="3266">
                <text>Megan  Minter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5244">
                <text>Megan  Minter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9096">
                <text>The Hokie stones on the drillfield before the permanent memorial was built</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12575">
                <text>	You are contributing your stories and/or files to The April 16 Archive, which is developing a permanent digital record of the events surrounding the tragedy on the Virginia Tech campus on April 16, 2007. Your participation in this project will allow future researchers, and people such as yourself, to gain a greater understanding of these events and the responses to them.&#13;
		&#13;
	You must be 13 years of age or older to submit material to us. Your submission of material constitutes your permission for, and consent to, its dissemination and use in connection with The April 16 Archive in all media in perpetuity. If you have so indicated on the form, your material will be published on The April 16 Archive web site (with or without your name, depending on what you have indicated). Otherwise, your submitted materials will only be available to approved researchers using The April 16 Archive. The material you submit must have been created by you, wholly original, and shall not be copied from or based, in whole or in part, upon any other photographic, literary, or other material, except to the extent that such material is in the public domain. Further, submitted material must not violate any confidentiality, privacy, security or other laws.&#13;
&#13;
	By submitting material to The April 16 Archive you release, discharge, and agree to hold harmless The April 16 Archive and persons acting under its permission or authority, including a public library or archive to which the collection might be donated for purposes of long-term preservation, from any claims or liability arising out the The April 16 Archive's use of the material, including, without limitation, claims for violation of privacy, defamation, or misrepresentation.&#13;
&#13;
	The April 16 Archive has no obligation to use your material.&#13;
&#13;
	You will be sent via email a confirmation of your contribution to The April 16 Archive. We cannot return any material you submit to us so be sure to keep a copy. The April 16 Archive will not share your email address or any other information with commercial vendors.&#13;
	</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14403">
                <text>Before the permanent memorial</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="372">
        <name>Hokie stone</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="946" 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="2249">
                <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="4140">
                <text>Megan Cox</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="6118">
                <text>2007-08-08</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7996">
                <text>&lt;b&gt;In wake of tragedy, nation is encouraged to focus on heroic victims of school shooting&lt;/b&gt;&#13;
&#13;
By: Megan Cox&#13;
Posted: 4/20/07&#13;
&#13;
A great atrocity occurred in Blacksburg on the morning of April 16. Cho Seung-Hui, a Korean-born English major at Virginia Tech, shot 62 students and teachers, killing 32 people, wounding 29 and leaving an entire nation in shock and mourning.&#13;
&#13;
Many people question how and why a single deranged individual could so proficiently commit "the deadliest rampage in American history." Did the university perform all of its duties to secure the safety of its students? Could a better response have saved any lives? How is the media handling this tragedy? What actions is the president taking? Could gun control laws have prevented this tragedy? Who was Cho Seung-Hui, and why did he commit these murders?&#13;
&#13;
Details are now trickling in about the young murderer. In an English class, he wrote plays full of grotesque violence. The playwriting professor and the English department had sought help for the young man. He was detached and troubled. He was admitted to a mental institution in late 2005. Possibly the most disturbing piece of the twisted psychological puzzle is that Seung-Hui sent a multimedia package to NBC News between the killings in the dorm and the massacre in the classrooms.&#13;
&#13;
It is too soon, both temporally and emotionally, to delve into all of the issues this tragedy presents. Of course, that a man like Seung-Hui should have such ready access to firearms is disturbing, and that the media is turning a profit by running such intense coverage of the tragedy is indeed unnerving. However, all these questions will pale in comparison to the introspection of human nature that follows such atrocities caused by a single man.&#13;
&#13;
There is evil in our midst. Some things, some acts, some people, are so horrible as to merit the use of that overused epithet. Whether people are born into it or are brought into it, whether it is caused by neglect or ridicule, whether it festers or can be cured, there can be little denying that it does surface in our society. One man can come to embody evil in our lives. One man has ended dozens of lives and wreaked havoc on many others. One deeply troubled man can control our lives, drowning us in fear and sorrow.&#13;
&#13;
Yet, as we weep over the acts of one disturbed man, we must resist the temptation to gloss over all of humanity as grotesque and depraved. We do have a great capacity for ordinary heroism.&#13;
&#13;
Doctor Liviu Librescu was a Romanian-born Holocaust survivor. When the gunman tried to storm his classroom, Librescu blocked the door with his body and told his students to flee. At least nine of his students were able to jump out of the window to safety because of Librescu&amp;#39;s actions. Librescu died a hero.&#13;
&#13;
Ryan Clark was a jovial psychology major, a member of the Virginia Tech Band and a Resident Advisor in the West Ambler Johnson dorm. He was killed when he came to the aid of another student being attacked by Seung-Hui. Clark, too, died a hero.&#13;
&#13;
Every time we think we&amp;#39;ve reached our capacity as human beings, we need only look at the actions of others to realize that capacity might well be limitless. Heroes exist in everyday life. When put to the test, these people shine. They remind us of the good we all possess, of our capacity to do right even in the face of evil. We must remember to focus on the good of the heroes rather than the evil of the killer in the wake of this tragic event.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.thehullabaloo.com/media/storage/paper958/news/2007/04/20/Views/Questions.Arise.From.Tragedy.At.Va.Tech-2873511.shtml&gt; The Hullabaloo - April 20, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9967">
                <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="11879">
                <text>"Dickson, Drew D." &lt;ddickson@tulane.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13378">
                <text>Questions arise from tragedy at Va. Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1087">
        <name>repsonse to tragedy</name>
      </tag>
      <tag tagId="733">
        <name>student response</name>
      </tag>
      <tag tagId="1085">
        <name>tulane</name>
      </tag>
      <tag tagId="1088">
        <name>victims</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2800" public="1" featured="0">
    <fileContainer>
      <file fileId="1307">
        <src>https://www.april16.vtlibraries.net/files/original/no_media_sign_6cf3c5b53b.jpg</src>
        <authentication>40d3456f8cbd28c6357ae73015d7f8a1</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="75">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17908">
                    <text>492</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="76">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17926">
                    <text>382</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="77">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17944">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="78">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17962">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="82">
                <name>IPTC Array</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="18014">
                    <text>a:0:{}</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="8">
        <name>Contribution Form</name>
        <description>The set of elements containing metadata from the Contribution form.</description>
        <elementContainer>
          <element elementId="39">
            <name>Submission Consent</name>
            <description>Indicates whether or not the contributor of this Item has given permission to submit this to the archive. (Yes/No)</description>
            <elementTextContainer>
              <elementText elementTextId="1083">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Posting Consent</name>
            <description>Indicates whether or not the contributor of this Item has given permission to post this to the archive. (Yes/No)</description>
            <elementTextContainer>
              <elementText elementTextId="1084">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Online Submission</name>
            <description>Indicates whether or not this Item has been contributed from a front-end contribution form.</description>
            <elementTextContainer>
              <elementText elementTextId="1085">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="89">
            <name>Contributor is Creator</name>
            <description>Indicates whether or not the contributor of the Item is responsible for its creation.</description>
            <elementTextContainer>
              <elementText elementTextId="18026">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
      <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="3259">
                <text>Megan Minter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5237">
                <text>Megan Minter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9089">
                <text>One of the signs that went up on the buildings around campus shortly after Apr 16 directing the media to stay out of the campus buildings</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12571">
                <text>	You are contributing your stories and/or files to The April 16 Archive, which is developing a permanent digital record of the events surrounding the tragedy on the Virginia Tech campus on April 16, 2007. Your participation in this project will allow future researchers, and people such as yourself, to gain a greater understanding of these events and the responses to them.&#13;
		&#13;
	You must be 13 years of age or older to submit material to us. Your submission of material constitutes your permission for, and consent to, its dissemination and use in connection with The April 16 Archive in all media in perpetuity. If you have so indicated on the form, your material will be published on The April 16 Archive web site (with or without your name, depending on what you have indicated). Otherwise, your submitted materials will only be available to approved researchers using The April 16 Archive. The material you submit must have been created by you, wholly original, and shall not be copied from or based, in whole or in part, upon any other photographic, literary, or other material, except to the extent that such material is in the public domain. Further, submitted material must not violate any confidentiality, privacy, security or other laws.&#13;
&#13;
	By submitting material to The April 16 Archive you release, discharge, and agree to hold harmless The April 16 Archive and persons acting under its permission or authority, including a public library or archive to which the collection might be donated for purposes of long-term preservation, from any claims or liability arising out the The April 16 Archive's use of the material, including, without limitation, claims for violation of privacy, defamation, or misrepresentation.&#13;
&#13;
	The April 16 Archive has no obligation to use your material.&#13;
&#13;
	You will be sent via email a confirmation of your contribution to The April 16 Archive. We cannot return any material you submit to us so be sure to keep a copy. The April 16 Archive will not share your email address or any other information with commercial vendors.&#13;
	</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14396">
                <text>No More Media</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="424">
        <name>campus</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1065" public="1" featured="0">
    <fileContainer>
      <file fileId="531">
        <src>https://www.april16.vtlibraries.net/files/original/9z3lal0p_64dadf111d.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="14916">
                    <text>2007-08-14</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="16036">
                    <text>2007-08-14 10:44:05</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="2365">
                <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="4256">
                <text>Megan Weiland</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="6234">
                <text>2007-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8112">
                <text>&lt;b&gt;Students hold candlelight vigil, show support for Blacksburg&lt;/b&gt;&#13;
&#13;
By: Megan Weiland&#13;
Posted: 4/20/07&#13;
&#13;
Following closely on the heels of sophomore Beth Spiedel&amp;#39;s death and the two-year anniversary of a tragic off-campus house fire, Miami University&amp;#39;s community is now confronted with what has been termed by Virginia Polytechnic Institute students as a "college Columbine."&#13;
&#13;
"We are all feeling enormous sadness and grief at the thought of what happened in Virginia," said Miami University President David Hodge. "It&amp;#39;s overwhelming to know that 33 people died (Monday) and I think it causes fear for us as we live in this modern era, where it is hard to understand what would possess a person to do something like this. It&amp;#39;s a feeling of vulnerability."&#13;
&#13;
Friday, April 20, college campuses across the country will be joining together for an "Orange and Maroon Effect" Day, when all Americans are encouraged to wear Virginia Tech&amp;#39;s colors to show support.&#13;
&#13;
"This tradition began in 2002 to encourage the wearing of school colors to sporting events," said Kristen Lucia, a graduate student at Miami who received her bachelor&amp;#39;s degree from Virginia Tech in 2004. "We had two games a year, one where you had to wear orange, and the other maroon."&#13;
&#13;
Lucia added that the shirts were sold for only $5, and the first year caused a national shortage in orange T-shirts because of the popularity. It became a tradition at the school as well as across the nation to show "Hokie pride."&#13;
&#13;
"I think we have two choices," she said. "We can dress in black, mourn, and sink into the shadows. Or we can dress in bright orange and stand together. The actions of one person will not affect our unity."&#13;
&#13;
Lucia said that many people from Virginia Tech are worried about how Monday&amp;#39;s event will change the way others view their school.&#13;
&#13;
"Everyone&amp;#39;s fear right now is that people will think VA Tech is unsafe, but there was nothing anyone could have done to prevent this," Lucia said. "The first thing on our lips was, I want to be in Blacksburg not I want to get away from there but I want to be there with them."&#13;
&#13;
Miami students and faculty gathered together Tuesday night for a candlelight vigil honoring and remembering the students who were killed at Virginia Tech Monday.&#13;
&#13;
"A college student is a college student no matter where you go to school," said Stacey Brozio, a junior East Asian language and culture major who planned the event. "Whether we believe in something higher or not, we share a common belief in humanity at this vigil. We&amp;#39;re here in support for each other and for Virginia Tech."&#13;
&#13;
With more than 200 people in attendance, several students and faculty members shared thoughts, memories and wrote sympathy cards to families of the victims and the shaken community.&#13;
&#13;
"My own personal loss was very great," said sophomore Kristen Vliet, who lost a friend in the shooting. "There are just some things in life that don&amp;#39;t make sense. There&amp;#39;s no way we can look back at the victims of the fire and have it make sense. There&amp;#39;s no way we can look back at Beth (Speidel) and have it make sense. What does make sense is that we&amp;#39;re here grieving together."&#13;
&#13;
Both Wal-Mart and the Faith Lutheran Church and Campus Ministry donated candles, which were placed around the reflecting pool behind the Shriver Center at the conclusion of the vigil.&#13;
&#13;
"The hardest part for me is when people forget," said Paige Glattly, a first-year psychology major. "We need to remember the families. It changed the rest of their lives. They will remember this every minute of every day."&#13;
&#13;
President Hodge expressed his joy at seeing the Miami community gathering together and encouraged them to continue to talk through the grief.&#13;
&#13;
"We as college students didn&amp;#39;t really have a voice when Columbine happened," said junior Paul Morrow. "We didn&amp;#39;t have a platform to express our grief like we do here."&#13;
&#13;
Jane Lindsay, a first-year whose two friends live in West Ambler Johnston Hall at Virginia Tech, said talking about her feelings with those friends and with others is a way of showing support.&#13;
&#13;
"Virginia Tech is so similar to Miami," Lindsay said. "It&amp;#39;s not even a city, just a small town and a close community, like Blacksburg."&#13;
&#13;
Other students spoke on questioning their faith and having moments of utter disbelief that this would happen.&#13;
&#13;
"You have a finite amount of time in life," said Sarah Baumert, a senior accounting major. "You never get that time back and it&amp;#39;s wonderful of these students at Miami to give that time. The people that came out are saying you don&amp;#39;t have to talk, just know we&amp;#39;re here."&#13;
&#13;
Miami&amp;#39;s security assessment&#13;
&#13;
Miami is one of many universities in America right now re-evaluating its security policy and procedures.&#13;
&#13;
"I&amp;#39;ve gotten a number of e-mails from parents wanting to protect their kids," Hodge said. "I feel the exact same way."&#13;
&#13;
Currently, the university&amp;#39;s security policy involves emergency phones in locations across campus, 24-hour patrol by Miami University Police, campus crime alerts via e-mail and use of the myMiami homepage. Hodge added that in an emergency the administration could utilize the Miami Metro system, radio frequencies and local TV. He encouraged students and faculty to read tips on what to do in an emergency, available on the MUPD Web site.&#13;
&#13;
"Miami has been as prepared as we could for all situations," Hodge said. "I don&amp;#39;t know that anything would have even made a difference at Virginia Tech. Two hours is really a short period of time. People don&amp;#39;t realize how much time it takes to put a campus on lockdown."&#13;
&#13;
According to Hodge, a new hotline number, similar to the lines available at Middletown and Hamilton campuses, was added Tuesday to relay emergency information. They are also looking into the possibility of text messaging campus alerts.&#13;
&#13;
"We do have multiple layers of communication on campus that just depend on the situation," said Richard Little, senior director of university communications. "E-mail can be very spotty in terms of reaching the whole community. It requires sending 25,000-30,000 e-mails and hoping people check them."&#13;
&#13;
Little mentioned the employment of phone trees to notify staff and students in the area of the campus phones who would, in turn, notify others. The method of text messaging would require all students to register their cell phones with the university and keep the information updated.&#13;
&#13;
"Nothing is perfect," Little said. "Nothing can reach a whole campus in an instant and we have to be careful not to spread panic. The question is not the means of communication, but making sure you have the right information."&#13;
&#13;
According to Miami&amp;#39;s Web site, MUPD members are trained to respond and handle different emergency situations.&#13;
&#13;
"We have all kinds of training and drills," Little said. "You sit down and imagine the unthinkable because someday that unthinkable could happen. I wish we could do something to make sure this never happens again but I also know that isn&amp;#39;t a reality."&#13;
&#13;
Miami&amp;#39;s Student Counseling Service posted a link on its Web site Wednesday offering suggestions and information on coping with the Virginia Tech tragedy.&#13;
&#13;
"Grief affects us in several different ways," said Kip Alishio, director of the Student Counseling Service. "It breaks through the normal setting and makes us feel vulnerable. A vast majority of people will get what they are needing from significant others, the natural resources in their lives. You should seek professional resources when those natural resources are non-existent."&#13;
&#13;
Alishio added that Miami does have procedures for faculty to report concerns about a student.&#13;
&#13;
"We do get consultation requests from faculty who have students who have submitted disturbing works or were acting in a suspicious way," he said. "We decide how to approach or intervene if we find it necessary. A student may go through a mandatory psychological screening to determine if they are a risk to themselves or others."&#13;
&#13;
The Web site, sponsored by the American Psychological Association, suggests talking about feelings, taking frequent breaks and helping others do something productive. &#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.miamistudent.net/media/storage/paper776/news/2007/04/20/FrontPage/Miami.Reacts.To.Virginia.Tech.Tragedy-2870651.shtml&gt;The Miami Student - April 20, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10083">
                <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="11982">
                <text>"Skotzko, Stacey Nicole" &lt;skotzksn@muohio.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13484">
                <text>Miami reacts to Virginia Tech tragedy</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="215">
        <name>candlelight vigil</name>
      </tag>
      <tag tagId="1107">
        <name>miami university</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="809" public="1" featured="0">
    <fileContainer>
      <file fileId="441">
        <src>https://www.april16.vtlibraries.net/files/original/IMG_0878_99cbdbd97b.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="14828">
                    <text>2007-07-24</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="15948">
                    <text>2007-07-24 17:56: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="2124">
                <text>Meghan Day</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4015">
                <text>Meghan Day</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="5993">
                <text>2007-07-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7871">
                <text>A group of friends from Blacksburg High attending the Candlelight Vigil the day after the tragedy.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9842">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="26">
        <name>blacksburg</name>
      </tag>
      <tag tagId="282">
        <name>high school</name>
      </tag>
      <tag tagId="54">
        <name>students</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="747" 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="2066">
                <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="3957">
                <text>Meghan E. Woods</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="5935">
                <text>2007-07-16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7813">
                <text>&lt;b&gt;New leader reaching out to Va. Tech&lt;/b&gt;&#13;
&#13;
By: Meghan E. Woods, Staff Writer&#13;
Posted: 4/23/07&#13;
&#13;
Not even three weeks into her term, Student Body President Eve Carson has found herself trying to console both the UNC and Virginia Tech campuses.&#13;
&#13;
Hours after learning of the Va. Tech tragedy, in which 32 people were killed by a suicidal student gunman, Carson, along with student body presidents from other schools in the Atlantic Coast Conference, formed an e-mail listserv to send messages of condolence to Va. Tech student government leaders.&#13;
&#13;
"Hearing the news was just so incredibly shocking," Carson said. "The listserv was a way of reaching out. In a moment of need, there&amp;#39;s nothing like having someone to reach out to you."&#13;
&#13;
Carson said she hopes to expand the communication between the schools by encouraging UNC student leaders to reach out to their counterparts in Blacksburg.&#13;
&#13;
"We&amp;#39;re asking people to send their counterparts an e-mail or a letter," Carson said. "Just something to let them know you&amp;#39;re thinking about them. We thought it&amp;#39;d be important to show that we were caring about the Virginia Tech community."&#13;
&#13;
Carson said that the matchup program is a collaborative idea and that she has been motivated to reach out because of her experiences with the death of Jason Ray, the UNC senior who portrayed Rameses for three seasons .&#13;
&#13;
"When Jason Ray died, I received a number of letters from people expressing their sympathy," said Carson, who took office the week after Ray&amp;#39;s death. "I thought it was so incredible. It&amp;#39;s nice to know that others are with you and thinking of you."&#13;
&#13;
Carson also is talking to UNC athletics officials about putting Va. Tech emblems on baseball helmets and working with other ACC schools to coordinate a full-page advertisement in the Collegiate Times, the Va. Tech student newspaper, expressing support during the wake of the tragedy.&#13;
&#13;
Former Student Body President Seth Dearmin said communication among students was the path toward healing last March when nine people were injured after UNC alumnus Mohammad Taheri-Azar drove a rented sport utility vehicle through the Pit.&#13;
&#13;
"After the incident, communication was positive and crucial," he said. "As a result, we brought panels together and councils to talk about what had happened and what it meant on a larger scale."&#13;
&#13;
James Allred, who was student body president-elect at the time, said finding outlets for students&amp;#39; feelings was also important in handling the incident.&#13;
&#13;
"We really focused on how to help students express the shock and concern they felt," he said. "As president, I think the first duty is to make sure the student body has a way to cope."&#13;
&#13;
Dearmin said that even though the Pit incident was different than the Va. Tech tragedy, being student body president during any significant event is stressful.&#13;
&#13;
"It&amp;#39;s a lot of pressure that gets thrown on you," he said. "It&amp;#39;s pressure that comes out of nowhere for an event that you have no control over. It comes out of the blue, but it does provide a good learning experience."&#13;
&#13;
Carson said she hopes communication will help foster better ties between UNC and Va. Tech.&#13;
&#13;
"It&amp;#39;s important to show our commitment to Virginia Tech," she said.&#13;
&#13;
"We want to be in personal touch and personal communication with people at Virginia Tech. Hopefully, we&amp;#39;ll be better connected in the future."&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dailytarheel.com/media/storage/paper885/news/2007/04/23/University/Carson.Consoles.In.Tragedy-2873070.shtml&gt;The Daily Tar Heel - April 23, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9784">
                <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="11764">
                <text>Kevin Schwartz &lt;kschwartz@unc.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13207">
                <text>Carson consoles in tragedy</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="832">
        <name>coping</name>
      </tag>
      <tag tagId="864">
        <name>student body president</name>
      </tag>
      <tag tagId="857">
        <name>unc</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="187" 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="1551">
                <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="3442">
                <text>Meghan Griffin / GateHouse Media</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="5420">
                <text>2007-05-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7299">
                <text>By Meghan Griffin/salem@cnc.com&#13;
GateHouse Media&#13;
Wed Apr 25, 2007, 09:36 PM EDT &#13;
&#13;
SALEM - The vigil held at Salem State College on Monday began with the most important thing, the reason some 300 students and faculty had assembled: the 32-plus victims of the Virginia Tech shooting.&#13;
&#13;
Michael Mitchell, president of the Student Government Association, started the vigil by reading each of the victims&amp;#39; names.&#13;
&#13;
"We will keep them in our hearts forever," said Mitchell.&#13;
&#13;
The students and staff who congregated on the lawn of Salem State&amp;#39;s Central Campus were there to show their compassion and support in the aftermath of the Virginia Tech University massacre.&#13;
&#13;
The hundreds who gathered at Salem State held candles, and they were all outfitted in custom made T-shirts displaying the Virginia Tech logo on the front and the phrase, "Today We Are All Hokies," on the back in honor of the university&amp;#39;s mascot.&#13;
&#13;
Candles lined the walkway leading to Central Campus, and empathetic students stood in groups as they tried to make sense of the tragedy.&#13;
&#13;
The disaster unfolded April 16, at Virginia Tech University in Blacksburg, Va. The nation was shocked to hear that a student open fired and claimed the lives of 32 innocent victims, including 20-year-old Ross Alameddine of Saugus, before turning the gun on himself.&#13;
&#13;
Salem State&amp;#39;s commemoration began at 7 p.m., one week after the massacre. Mitchell, who played a large role in organizing the event, extended thanks to all those who helped organize the vigil, and to the Residence Hall Association for producing the T-shirts.&#13;
&#13;
President Nancy Harrington, who will retire at the end of the school year, addressed the situation and called the mayhem at Virginia Tech, "immeasurable." It is important for students to remain united in order to stay strong, she told the crowd.&#13;
&#13;
The vigil brought forward the realization that a disaster could strike unexpectedly at any time, and that no one is fully protected. "We hope and we pray that this is a safe campus," Harrington said, noting that there is no guarantee that such a tragedy will not occur in this violent world.&#13;
&#13;
"There is no real way to prevent something like this," Mitchell added.&#13;
&#13;
A recurring theme of the evening was the need for students to recognize those they may be alienating. Cho Seung-Hui, the student killer who went on the rampage at Virginia Tech, was reportedly a loner and outcast.&#13;
&#13;
"People shouldn&amp;#39;t feel alone in this world," said Salem State junior David Overton, who addressed the crowd when the organizers asked if anyone wanted to come up and say a few words.&#13;
&#13;
Dressed in all black, Overton told the Gazette the shooting had a personal effect on him. After the 1999 high school shooting in Columbine, he said, he was questioned by teachers and others at his school.&#13;
&#13;
Overton, a resident adviser at Salem State, said there should have been parts of the community to help Cho Seung-Hui, and that all schools need to be prepared for such an act before it is too late.&#13;
&#13;
A few people, like Overton, chose to share their personal thoughts with the crowd. Jay Carey, a Salem resident and employee at the college&amp;#39;s Center for Adult Learning, received an overwhelming applause after reading a poem he wrote about the incident.&#13;
"It&amp;#39;s a shame," he read, "that we only pull together in the rain."&#13;
&#13;
Students wrapped up the vigil by shaping a huge Virginia Tech logo on the lawn. Photographers captured the moment with aerial shots taken from the roof. Salem State plans to send the photo, along with five signed banners and two signed wooden Virginia Tech logos, to the Blacksburg school to show support.&#13;
&#13;
Harrington was impressed with the turnout. She credited Mitchell for spearheading the event, which was entirely student organized. "The tragedy at Virginia Tech touched everybody," she told the Gazette.&#13;
&#13;
Mitchell said they had to act quickly to pull together the vigil.&#13;
&#13;
"The purpose," he said after speaking to the crowd, "is to give people a chance to reflect."&#13;
&#13;
--&#13;
&#13;
Original source: &lt;a href="http://www.townonline.com/salem/homepage/x109703597"&gt;http://www.townonline.com/salem/homepage/x109703597&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc-nd/2.5/"&gt;Creative Commons Attribution-NonCommercial-NoDerivs 2.5&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9269">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12749">
                <text>Hundreds attend Salem State vigil for Virginia Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="287">
        <name>salem state college</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1184" 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="2471">
                <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="4362">
                <text>Melanie Hicken</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="6340">
                <text>2007-08-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8218">
                <text>By: Melanie Hicken&#13;
Posted: 4/26/07&#13;
&#13;
Aug. 1, 1966 - University of Texas at Austin&#13;
&#13;
From the top of a 27-story tower, Charles J. Whitman shot and killed 13 people and wounded 31 others before he was killed by police fire.&#13;
&#13;
&#13;
&#13;
July 12, 1976 - California State University at Fullerton&#13;
&#13;
A school custodian, Edward C. Allaway, shot and killed seven people and wounded two others in the basement of a library.&#13;
&#13;
&#13;
&#13;
Nov. 1, 1991 - University of Iowa&#13;
&#13;
Gang Lu, a graduate physics student, shot and killed five people and paralyzed another after he did not receive an award for his dissertation.&#13;
&#13;
&#13;
&#13;
Dec. 14, 1992 - Simon&amp;#39;s Rock College of Bard&#13;
&#13;
Wayne Lo shot and killed two people and wounded four others before surrendering to police.&#13;
&#13;
&#13;
&#13;
Aug. 15, 1996 - San Diego State University&#13;
&#13;
A 36-year-old graduate student Frederick Davidson shot and killed three professors while defending his engineering thesis.&#13;
&#13;
&#13;
&#13;
Aug. 28, 2000 - University of Arkansas at Fayetteville&#13;
&#13;
A 36-year-old student shot and killed a professor after being dropped from a doctoral program, and then killed himself.&#13;
&#13;
&#13;
&#13;
Jan. 16, 2002 - Appalachian School of Law&#13;
&#13;
A 43-year-old law student Peter Odighizuwa shot and killed three people and injured three others.&#13;
&#13;
&#13;
&#13;
Oct. 28, 2002 - University of Arizona Nursing College&#13;
&#13;
A 40-year-old student who was failing academically shot and killed three people.&#13;
&#13;
&#13;
&#13;
Sept. 2, 2006 - Shepherd University&#13;
&#13;
Douglas Pennington shot and killed his two sons, who were students at the school, and then himself.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailyorange.com/media/storage/paper522/news/2007/04/26/News/Virginia.Tech.History.Of.Major.Shootings.On.College.Campuses-2881639.shtml&gt;The Daily Orange - April 26, 2007&lt;/a&gt;&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10189">
                <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="11199">
                <text>The Daily Orange </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12041">
                <text>Peter Waack &lt;pwaack@dailyorange.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13589">
                <text>Virginia Tech | History of major shootings on college campuses</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1610">
        <name>syracusen university</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1188" 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="2474">
                <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="4365">
                <text>Melanie Hicken</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="6343">
                <text>2007-08-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8221">
                <text>By: Melanie Hicken&#13;
Posted: 4/26/07&#13;
&#13;
The first shooting at Virginia Tech happened at about 7:15 a.m., yet classes continued - a decision questioned by many in the last week.&#13;
&#13;
Right or wrong, it has led many Syracuse University students to ask: Who would make such a decision at SU?&#13;
&#13;
At SU, the decision would be a group effort made by Chancellor Nancy Cantor, Vice Chancellor Eric Spina and the Logistics Committee, which is headed up by SU Chief Financial Officer Louis Marcoccia and made up of representatives from various university departments (see: "What is the Logistics Committee?").&#13;
&#13;
"Clearly what we have on the committee is broad representation from across campus," Marcoccia said. "It&amp;#39;s a group that we hope can provide us the right kind of advice on any decision we would have to make."&#13;
&#13;
Cantor said she had little doubt classes could be canceled and students notified of this "very quickly" in the case of an immediate threat situation. The most recent cancellation of classes - a half-day cancellation due to snow - worked as a good practice for the system, Cantor said.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailyorange.com/media/storage/paper522/news/2007/04/26/News/Virginia.Tech.How.Are.Classes.Canceled-2881652.shtml&gt;The Daily Orange - April 26, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10192">
                <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="11201">
                <text>The Daily Orange </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12044">
                <text>Peter Waack &lt;pwaack@dailyorange.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13592">
                <text>Virginia Tech | How are classes canceled?</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1613">
        <name>syracuse university</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1190" 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="2476">
                <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="4367">
                <text>Melanie Hicken</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="6345">
                <text>2007-08-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8223">
                <text>By: Melanie Hicken&#13;
Posted: 4/26/07&#13;
&#13;
Oklahoma City. Columbine. 9/11.&#13;
&#13;
For a generation that came of age during such memorable acts of violence, tragedy is not new. But for the largest fatal shooting in U.S. history to occur on a college campus may hit a little too close to home.&#13;
&#13;
"I was shocked," said sophomore Catherine Long of her initial reaction to the Virginia Tech shooting. "But mostly I was shocked to hear it was a student. You don&amp;#39;t think of any of us doing that to other students."&#13;
&#13;
Long said she couldn&amp;#39;t help but have thoughts run through her head about what she would do in a similar situation.&#13;
&#13;
"What if you were sitting in class and all of a sudden that happened to us," said Long, advertising major. "What would I do?"&#13;
&#13;
Such scattered emotions ranged through campus last week as various members of the campus community explored their own feelings and connections to the incident.&#13;
&#13;
"The higher education world is a very interconnected world," said Dean of Hendricks Chapel Thomas Wolfe, who co-chairs the Critical Incident Management Team (CIMT). Faculty research with faculty from other campuses, students have friends from high school at schools across the country, and the connections continue, he said.&#13;
&#13;
"It&amp;#39;s rare that you&amp;#39;re not going to have had contact with or know someone at another campus," said Chancellor Nancy Cantor, comparing it to the "six degrees of separation" theory.&#13;
&#13;
And indeed, as more information became available, direct Syracuse University connections to Virginia Tech began to come to light, Wolfe said, including a student who lost a friend to the shooter.&#13;
&#13;
But even those not directly affected by the tragedy felt connected.&#13;
&#13;
"Some may argue that it is hard to truly grieve or relate in a situation that we are so &amp;#39;far removed from.&amp;#39; I beg to differ," wrote Student Association President Ryan Kelly in a letter published in The Daily Orange on April 18.&#13;
&#13;
"We are very close to this situation. Virginia Tech is a peer institution, with students that come from near and far to make that university their home, just like many of us at Syracuse University," Kelly said. "To have such a tragedy occur at a place that most call home for four years is truly devastating. This tragedy could have happened just as easily on our campus as any other in the United States."&#13;
&#13;
More than 400 students and members of the SU community expressed their emotions at a candlelight vigil held in Hendricks on April 17.&#13;
&#13;
Hundreds more signed blank white sheets with messages of sympathy and condolences. The sheets were recently sent to the Virginia Tech campus.&#13;
&#13;
Such events and activities were organized by the CIMT to help the campus cope with the tragedy.&#13;
&#13;
Wolfe compared events like the vigil to an outreached hand open to take in everyone&amp;#39;s scattered emotions after an earth-shattering event like Virginia Tech.&#13;
&#13;
"The point is that&amp;#39;s OK to feel this way," he said. "We are going to sort this stuff out over time, but right now this is the need and we will take our confusions, we&amp;#39;ll take our fears, we&amp;#39;ll take our anxieties, all those mixture of feelings and put them right here. And for today, that&amp;#39;s enough." &#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailyorange.com/media/storage/paper522/news/2007/04/26/News/Virginia.Tech.Too.Close.For.Comfort.Students.Cope.With.Shootings.On.Campus-2881656.shtml&gt;The Daily Orange - April 26, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10194">
                <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="11203">
                <text>The Daily Orange </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12046">
                <text>Peter Waack &lt;pwaack@dailyorange.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13594">
                <text>Virginia Tech | Too close for comfort: Students cope with shootings on campus</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1613">
        <name>syracuse university</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1191" public="1" featured="0">
    <fileContainer>
      <file fileId="601">
        <src>https://www.april16.vtlibraries.net/files/original/hx5r8109_c9d48e94b3.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="14979">
                    <text>2007-08-23</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="16099">
                    <text>2007-08-23 21:24:28</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="2477">
                <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="4368">
                <text>Melanie Hicken</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="6346">
                <text>2007-08-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8224">
                <text>By: Melanie Hicken&#13;
Posted: 4/26/07&#13;
&#13;
April 16, 2007. Another day to mourn. Another day Americans will never forget.&#13;
&#13;
But while the Virginia Tech community begins the healing process after the largest massacre in U.S. history, college campuses across the country are beginning a process as well - a reevaluation of protocols and procedures in place to help prevent or minimize such a tragedy.&#13;
&#13;
"Monday&amp;#39;s incident changes everything for universities around the country," said Interim Chief Tony Callisto, of Syracuse University&amp;#39;s Public Safety.&#13;
&#13;
It&amp;#39;s been a busy 10 days for Callisto.&#13;
&#13;
Interviews. Meetings. Phone calls. E-mails. All asking: What would we do if it happened here?&#13;
&#13;
SU was one of many college communities across the nation that were jarred by this scary realization - that something so violent, so tragic could occur on a campus just like its own.&#13;
&#13;
"I think we all know that this could have happened anywhere," said Dean of Hendricks Chapel Thomas Wolfe, who co-chairs the Critical Incident Management Team (CMIT).&#13;
&#13;
Within hours of the breaking news of the shootings, the SU Logistics Committee and the CIMT, two university bodies that help manage emergency and crisis situations, convened to discuss what this tragedy meant for SU and how the campus should respond.&#13;
&#13;
The Logistics Committee handles technical and physical needs in an emergency situation, while the CIMT manages all human responses.&#13;
&#13;
The CIMT and Public Safety will study the Virginia Tech incident to help enhance SU&amp;#39;s year of task force examinations dedicated to keeping the school continuously up to date in various areas including campus safety and communication in the case of an emergency, said Chancellor Nancy Cantor in an interview.&#13;
&#13;
"I have asked the CIMT and the Department of Public Safety to quickly analyze what we currently know about the Virginia Tech incident," said Cantor in an e-mail sent to the campus community on April 17. "That team will continue to meet with me and the University&amp;#39;s leadership in the coming days to examine our policies and protocols, and determine how we can learn from this tragedy."&#13;
&#13;
&#13;
&#13;
Safety first&#13;
&#13;
The Virginia Tech shootings exposed the vulnerability of college campuses as opposed to the more contained high school setting. The Columbine High School shooting on April 20, 1999, led to the idea of a lockdown procedure in case of such an emergency.&#13;
&#13;
And many Virginia Tech students and families questioned why their campus was not locked down after the first shooting.&#13;
&#13;
But for an open campus community - as opposed to a contained high school building - a lockdown is easier said than done, Callisto said.&#13;
&#13;
"I think any open university probably doesn&amp;#39;t have a solid procedure for a lockdown because it&amp;#39;s a community environment," he said. "It&amp;#39;s a community of buildings, so we need to come up with a community response to this kind of a challenge instead of a single institutional response."&#13;
&#13;
Currently, Callisto said, SU has two main procedures to be used in the case of emergency depending on the situation: to have people evacuate or to tell people to stay in their buildings.&#13;
&#13;
Additionally, all Public Safety officers are trained in "active shooter protocol," a procedure developed nationwide in 2003 partly as a result of the Columbine shootings, Callisto said. Prior to this training, officers would have to create a perimeter and wait for SWAT officers before entering a building with an active shooter, which could take more than an hour.&#13;
&#13;
Now, the first four arriving officers at the scene do an immediate assessment of the situation and enter the building.&#13;
&#13;
Immediately.&#13;
&#13;
"A few years ago, the Department of Public Safety was an unarmed, primarily security force that had limited ability to really manage a problem of this magnitude," Callisto said. "And today, with the active shooter training and the police academy, today within seconds you have eight to 10 Public Safety officers working any shift. Four of them can be there within seconds."&#13;
&#13;
In October 2003, New York Gov. George Pataki signed legislation that allowed SU to upgrade Public Safety officers to peace officer status. In February 2004, the University Senate made a recommendation to begin the training program, which then-Chancellor Kenneth Shaw accepted. This training program was completed in December, so all officers can now carry a weapon and use force if necessary.&#13;
&#13;
Prior to peace status, they could carry only batons and pepper spray.&#13;
&#13;
Although he said he is confident SU is prepared to react in the case of emergency, Callisto added the university is currently examining additional safety and communication measures as a part of a comprehensive plan to increase safety capabilities.&#13;
&#13;
Some things being looked into include: surveillance systems, turning the campus blue lights into loudspeaker-like devices and the ability to simulcast emergency notification to all university radio channels. Other processes are also being considered.&#13;
&#13;
As early as Monday afternoon, Callisto had joined an e-mail listserv of law enforcement administrators to discuss the Virginia Tech incident and what can be learned from it.&#13;
&#13;
"This is an opportunity," Callisto said. "It&amp;#39;s a tragic event, but it will be an opportunity for campus law enforcement to improve our ability to respond to these kinds of things."&#13;
&#13;
&#13;
&#13;
To text, or not to text&#13;
&#13;
One of the most controversial issues to come out of the Virginia Tech incident is how and when universities choose to notify students of a shooting or similar violent incident on campus.&#13;
&#13;
Although the Virginia Tech Police Department received a 911 call about shootings in a residence hall at 7:15 a.m., e-mail notification was not sent to students and faculty until 9:26 a.m.&#13;
&#13;
A second 911 call was phoned in at 9:45 a.m. Another shooting had occurred. This time, e-mail notification was sent within five minutes.&#13;
&#13;
Campus officials told the media they had reason to believe the first incident was an isolated domestic dispute, but many have still questioned why notification was not sent out earlier and why classes were not canceled.&#13;
&#13;
"I don&amp;#39;t understand their logic behind that," a Virginia Tech sophomore told The Los Angeles Times. "It does bother me. I feel like a lot of lives could have been saved and a lot fewer injuries."&#13;
&#13;
SU currently sends out e-mails to the campus community about campus safety incidents or important information within the hour, in accordance with the national Clery Act, Callisto said.&#13;
&#13;
The Clery Act was passed in Congress in 1990 and requires colleges and universities to issue annual reports on crime on campus as well as on security procedures. The law also requires that campuses provide "timely warning" when a crime poses a serious threat to students and employees. The law does not, however, provide a specific time frame that must be followed.&#13;
&#13;
At SU, "typically, the current process is when we know about an incident, usually within an hour, you know about it," Callisto said.&#13;
&#13;
But Virginia Tech has shown, he said, that even an hour may not be soon enough, and that this should perhaps be modified in extreme cases.&#13;
&#13;
Additionally, the university realizes e-mail notification may not be the most efficient method - especially in the case of an immediate threat to campus, Callisto said.&#13;
&#13;
For the past few weeks - before the Virginia Tech incident even occurred - a university task force has been looking into the possibility of a text message notification program. Students and faculty would be able to register their cell phone number and SU officials would be able to send out a notification blast to all registered phones.&#13;
&#13;
Cell phone notification is "the model that really works for technology today" since many students are much more likely to instantly receive a text than an e-mail, Callisto said.&#13;
&#13;
Many schools are looking into these text message notification programs, as reported in the April 27 issue of The Chronicle of Higher Education. Schools such as University of Maryland-Easter Shore, Monmouth University in New Jersey and Butler University, among others, already use such programs.&#13;
&#13;
SU sophomore Catherine Long said she thought a text message notification program would be a much better way to immediately contact students.&#13;
&#13;
"Not all people check their e-mail at all times. I could go days without checking my e-mail," said Long, advertising major. "But everyone has their cell phone with them on most of the time. And they are checking it all the time."&#13;
&#13;
&#13;
&#13;
Finding a balance&#13;
&#13;
In the light of such a tragedy, people often look to tightened security measures, and safety at SU will of course be examined, officials said. But many SU officials expressed a need for a balance between security and the openness that college campuses pride themselves on.&#13;
&#13;
"Are we going to choose to live in fear constantly and build walls? Or are we going to live in an open society?" Wolfe said. "But how do we live smart in that open society?&#13;
&#13;
I think that is going to be one of the big challenges in higher education because one of the values of higher education is it is an accessible community."&#13;
&#13;
Cantor echoed Wolfe&amp;#39;s thoughts.&#13;
&#13;
"At the heart of what makes colleges and universities great is their openness and their engagement with the world and with each other," she said. "You don&amp;#39;t want something that isolates the campus from that flow of information, the flow of interaction and the flow of people ... On the other hand, you obviously want to create a community that feels safe and comfortable so it can do its best work."&#13;
&#13;
Thus looking for a balance is key, said many SU officials.&#13;
&#13;
As SU officials at administrators at campuses across the country strive for that balance in the aftermath of this national tragedy, the Virginia Tech campus will simply strive for normalcy - to be the way it was before.&#13;
&#13;
The way it was before April 16, 2007. &#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailyorange.com/media/storage/paper522/news/2007/04/26/FrontPage/Virginia.Tech.In.Case.Of.Emergency.Vt.Tragedy.Spurs.Analysis.Of.Sus.Safety.Proc-2881578.shtml&gt;The Daily Orange - April 26, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10195">
                <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="12047">
                <text>Peter Waack &lt;pwaack@dailyorange.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13595">
                <text>Virginia Tech | In case of emergency: VT tragedy spurs analysis of SU&amp;#39;s safety procedures</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1613">
        <name>syracuse university</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1196" 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="2481">
                <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="4372">
                <text>Melissa Daniels</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="6350">
                <text>2007-08-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8228">
                <text>By: Melissa Daniels&#13;
Posted: 4/17/07&#13;
The doors to Hendricks Chapel remained open on Monday, with a candle lit at the end of an aisle. Chaplains were available throughout the day, willing to talk to anyone who wished to enter.&#13;
&#13;
The Virginia Tech shooting on Monday caused widespread raw emotion throughout the country, and Syracuse University was not exempt.&#13;
&#13;
"Everybody&amp;#39;s hearts are going out to Virginia Tech today," said Dean of Hendricks Chapel Thomas Wolfe. "This is a monumental disaster, a tragedy that has befallen them."&#13;
&#13;
An unidentified gunman opened fire in a Virginia Tech dorm in the morning, beginning the deadliest shooting rampage in U.S. history. By the end of the day, the death toll reached 33, including the death of the gunman himself.&#13;
&#13;
Sources had varying reports throughout the day about whether the gunman committed suicide or if he was killed by police. A two-hour gap between shootings raised the possibility of more than one shooter.&#13;
&#13;
Wolfe is also co-chair of the Critical Incident Management Team. The group touched base this morning after hearing about the shootings. The team, which focuses on human response in tragic events, encouraged contacting the counseling center and reflecting in Hendricks for students who may have been affected emotionally by the shooting.&#13;
&#13;
"When something like this happens," he said, "the whole university community feels it."&#13;
&#13;
Chancellor Nancy Cantor sent a letter to the president of Virginia Tech, extending Syracuse University&amp;#39;s sympathies. Wolfe described the letter as "a very genuine gesture."&#13;
&#13;
"The higher education world is a very connected world," he said.&#13;
&#13;
Interim Chief of Public Safety Tony Callisto said SU is prepared for unexpected violent incidents like Monday&amp;#39;s events at Virginia Tech as best as it can be.&#13;
&#13;
"Every incident results in learning for the next time," he said.&#13;
&#13;
Public Safety officers are trained in active shooting scenarios in case they would ever need to go after an armed suspect, Callisto said. They are also all trained as peace officers, meaning they are armed.&#13;
&#13;
Active shooting scenario training was created a year after the 1999 school shooting at Columbine High School in Littleton, Colo., which resulted in 15 fatalities.&#13;
&#13;
"Officers are very proactive," Callisto said. "There are eight to 10 officers that patrol Syracuse University grounds 24 hours a day."&#13;
&#13;
SU has close ties with the Syracuse Police Department, he said.&#13;
&#13;
"Response is relatively immediate," said Callisto about reaction in a crisis situation.&#13;
&#13;
Public Safety also has in-service training with the Office of Residence Life in the case of an assailant entering a dorm. On-duty resident advisers and residential security aides (RSAs) are instructed to call Public Safety if they see anything suspicious.&#13;
&#13;
RSAs have hand-held radios that are connected to Public Safety and Syracuse police lines.&#13;
&#13;
"Prevention is the best tool," Callisto said. "If you see something that&amp;#39;s unusual, call us. If you see something that doesn&amp;#39;t look right, call us. If something looks suspicious in any way, call us."&#13;
&#13;
Student response to the event is widespread. The constant television news coverage and Internet postings let the word spread about the event as updates came in.&#13;
&#13;
Anna Hadingham, president of the Student Peace Action Network at SU, expressed her concern about the recent violence.&#13;
&#13;
"It worries me that a student would have a reason or feel a need to unleash that," she said. "We are looking and exposing ourselves to chaos and carnage."&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailyorange.com/media/storage/paper522/news/2007/04/17/FrontPage/Su.Community.Reacts.To.Virginia.Tech.Massacre-2845381.shtml&gt;The Daily Orange - April 17, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10199">
                <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="11206">
                <text>The Daily Orange </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12051">
                <text>Peter Waack &lt;pwaack@dailyorange.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13599">
                <text>SU community reacts to Virginia Tech massacre</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1613">
        <name>syracuse university</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="72" public="1" featured="0">
    <fileContainer>
      <file fileId="55">
        <src>https://www.april16.vtlibraries.net/files/original/the stones_f4b8a0c9ad.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="14475">
                    <text>2007-05-01</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="15595">
                    <text>2007-05-01 23:26: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="1443">
                <text>Melissa Helms</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3334">
                <text>Melissa Helms</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="5312">
                <text>2007-05-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7193">
                <text>These are part of the 32 stones for the victims near Burruss Hall.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9161">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12658">
                <text>The Stones</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="77">
        <name>burruss</name>
      </tag>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="154">
        <name>stones</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="73" public="1" featured="0">
    <fileContainer>
      <file fileId="56">
        <src>https://www.april16.vtlibraries.net/files/original/a day of mourning_e285692467.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="14476">
                    <text>2007-05-01</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="15596">
                    <text>2007-05-01 23:29:19</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="1444">
                <text>Melissa Helms</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3335">
                <text>Melissa Helms</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="5313">
                <text>2007-05-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7194">
                <text>one of the many trees around the drillfield</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9162">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12659">
                <text>One Tree</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="46">
        <name>ribbon</name>
      </tag>
      <tag tagId="138">
        <name>tree</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="281" public="1" featured="0">
    <fileContainer>
      <file fileId="189">
        <src>https://www.april16.vtlibraries.net/files/original/balloon 20-1_022d231a50.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="14586">
                    <text>2007-05-28</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="15706">
                    <text>2007-05-28 22:46:36</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="1634">
                <text>Melissa Helms</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3525">
                <text>Melissa Helms</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="5503">
                <text>2007-05-28</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7382">
                <text>One of the balloons for the victims released at a Hokies United drillfield memorial service on the morning of Monday, April 23, 2007.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9352">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="282" public="1" featured="0">
    <fileContainer>
      <file fileId="190">
        <src>https://www.april16.vtlibraries.net/files/original/orange and maroon 2_f1006a8313.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="14587">
                    <text>2007-05-28</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="15707">
                    <text>2007-05-28 22:49: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="1635">
                <text>Melissa Helms</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3526">
                <text>Melissa Helms</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="5504">
                <text>2007-05-28</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7383">
                <text>Orange and maroon balloons released at a Hokies United drillfield memorial service on the morning of Monday, April 23, 2007.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9353">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="376">
        <name>april 23</name>
      </tag>
      <tag tagId="378">
        <name>balloons</name>
      </tag>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="377">
        <name>hokies united</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
