<?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://april16archive.org/items?output=omeka-xml&amp;page=27&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-04T13:07:09+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>27</pageNumber>
      <perPage>20</perPage>
      <totalResults>1884</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="714" 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="2036">
                <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="3927">
                <text>Editorial </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="5905">
                <text>2007-07-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7783">
                <text>Friday, May 18, 2007&#13;
&#13;
UCLA and university police proved Wednesday that, far from their recent assurances of campus safety, their emergency response does not provide nearly enough immediate notification, leaving the campus unaware of possible danger.&#13;
&#13;
Around 1:30 p.m. on Wednesday, local authorities received reports of an individual in the possession of some sort of weapon - possibly a rifle - in Westwood&amp;#39;s North Village.&#13;
&#13;
The reports sent a swarm of Los Angeles Police Department cruisers to the North Village. Cars blocked several streets in an attempt to control traffic and prevent individuals from walking into potentially dangerous areas.&#13;
&#13;
About three blocks away, UCLA continued to go about its business as if there were not a care in the world.&#13;
&#13;
In the wake of the Virginia Tech shootings, it is remarkable - and unacceptable - that any immediate danger to the UCLA community was not communicated promptly to the entire campus.&#13;
&#13;
Given the recent announcements and assurances made by UCLA officials regarding campus safety, it is natural to think the university would have a short-term plan in place to deal with emergencies until a more comprehensive plan were in effect.&#13;
&#13;
Thankfully, the individual was not in possession of a rifle, but rather a crossbow, and no one was injured. But the situation could have been very different - and more dangerous - based on the initial reports.&#13;
&#13;
In a recent public meeting, Acting Chancellor Norman Abrams addressed how UCPD has been prepared for active-shooter situations since the 1999 Columbine shootings, so we know the police do have a plan in place.&#13;
&#13;
Of course, it is not expected that at the slightest hint of danger UCLA would break out megaphones, sound alarms and call in the National Guard.&#13;
&#13;
But to leave the community completely in the dark until more than an hour after the incident is over is simply unacceptable, and the university should be working more vigorously with UCPD to develop a response plan for reports of danger in and around UCLA.&#13;
&#13;
As it was, many students, faculty and staff were left completely unaware of the situation unless they were at a computer to check either the UCPD or the Daily Bruin Web site for breaking news updates.&#13;
&#13;
By the end of the day, the only notification of the incident sent to any members of the UCLA community came in the form of an e-mail by K.C. Kainsinger, UCPD emergency medical services manager, sent to the Campus Safety listserv at 4:33 p.m., well after the incident had been resolved.&#13;
&#13;
One wonders why the one resource available to administrators - a campus-wide mass e-mail - was not utilized earlier to alert students, staff and faculty to the situation, a resource which could kill two birds with one stone by dispelling rumors about the incident simultaneously.&#13;
&#13;
In the end, regardless of the endless reasons UCLA officials can provide in order to explain the response - or lack thereof - there is really no excuse.&#13;
&#13;
The bottom line is that there was a potentially dangerous situation very near UCLA, in the heart of the off-campus student community, and both UCLA and UCPD did nothing to proactively alert campus community members.&#13;
&#13;
This needs to change immediately. It is understandable that a stronger plan for emergency response is in the works, but basic responses, such as campus-wide notification, need to be in place now.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.dailybruin.ucla.edu/news/2007/may/18/editorial-ucla-needs-emergency-notification-system/&gt;&#13;
The Daily Bruin - May 18, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9754">
                <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="11094">
                <text>The Daily Bruin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11734">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13177">
                <text>Editorial: UCLA needs emergency notification system now</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="836">
        <name>notification system</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
      <tag tagId="582">
        <name>university response</name>
      </tag>
      <tag tagId="835">
        <name>warning system</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="856" 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="2165">
                <text>Elva Orozco</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4056">
                <text>Periodista Digital.com</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="6034">
                <text>2007-07-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7912">
                <text>Creado por Periodista Digital&#13;
14.06.07 &#13;
&#13;
El asesinato de 32 personas por un estudiante desequilibrado el pasado mes de abril en la Universidad PolitÃ©cnica de Virginia, en Estados Unidos, ha propiciado que por primera vez en 10 aÃ±os el sacrosanto derecho a portar armas que impera en el paÃ­s vaya a ser matizado con un control mÃ¡s estricto en los puntos de venta y del historial (psiquiÃ¡trico y delictivo) de los compradores.&#13;
&#13;
La nueva ley ha sido propuesta por la ultraconservadora AsociaciÃ³n Nacional del Rifle (NRA, en sus siglas inglesas) y aprobada por aclamaciÃ³n ayer en la CÃ¡mara de Representantes. Ahora espera el trÃ¡mite final en el Senado.&#13;
&#13;
"Tal y como nos recordÃ³ el tiroteo de Virginia Tech, existe una urgente necesidad nacional de mejorar el sistema de antecedentes" para controlar a quiÃ©n llegan las armas, seÃ±alÃ³ la presidenta de la CÃ¡mara, la demÃ³crata Nancy Pelosi.&#13;
&#13;
SegÃºn el texto, los Estados que conforman EE UU se beneficiarÃ¡n de importantes incentivos financieros para poner al dÃ­a la base de datos sobre personas para las que estÃ¡ prohibido comprar un arma, en particular criminales y sujetos con problemas psiquiÃ¡tricos.&#13;
&#13;
AdemÃ¡s, los Estados serÃ¡n multados si no ponen en marcha estas medidas. Sin embargo, y como una concesiÃ³n a la NRA, la nueva legislaciÃ³n permitirÃ¡ tambiÃ©n que personas que hayan cometido "infracciones menores" sean eliminadas del fichero, asÃ­ como que los veteranos de guerra con problemas mentales incluidos en el mismo tengan la posibilidad de limpiar el registro.&#13;
&#13;
Una matanza evitable&#13;
&#13;
En el caso de Cho Seung-Hui, el estudiante que matÃ³ a 32 personas en Virginia, Ã©ste nunca debÃ­a haber obtenido el permiso para comprar un arma, dado que tenÃ­a antedecentes de problemas psiquiÃ¡tricos.&#13;
&#13;
Wayne La Pierre, vicepresidente de la NRA, ha precisado que la ley no "descalifica a nadie" que tenga la intenciÃ³n de comprar un arma legalmente, si no que, "al contrario, al contrario, da la oportunidad aquÃ©llos que han sido descalificados de "limpiar su nombre". "Los dueÃ±os de armas no pierden nada en la ley, tal y como estÃ¡ formulada por el momento", ha recordado La Pierre a los mÃ¡s de cuatro millones de miembros de su asociaciÃ³n. &#13;
&#13;
--&#13;
Fuente Original: Periodista Digital.com&#13;
&lt;a href="http://blogs.periodistadigital.com/tizas.php/2007/06/14/virginia_tech_armas_seung_rifle_9933"&gt;http://blogs.periodistadigital.com/tizas.php/2007/06/14/virginia_tech_armas_seung_rifle_9933&lt;/a&gt;&#13;
&#13;
Licencia de uso:&#13;
&lt;a href="http://creativecommons.org/licenses/by/2.5/"&gt; Creative Commons Attribution 2.5.&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9883">
                <text>spa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11818">
                <text>Creative Commons&#13;
Attribution 2.5 </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13301">
                <text>EEUU endurece sus leyes sobre armas tras la matanza de Virginia Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="969">
        <name>cmara de representantes</name>
      </tag>
      <tag tagId="968">
        <name>control de armas</name>
      </tag>
      <tag tagId="970">
        <name>nancy pelosi</name>
      </tag>
      <tag tagId="971">
        <name>wayne la pierre</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2068" public="1" featured="0">
    <fileContainer>
      <file fileId="955">
        <src>https://april16archive.org/files/original/100_0251_f23f4ef771.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="15312">
                    <text>2008-04-09</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="16432">
                    <text>2008-04-09 09:32:26</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="2997">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4888">
                <text>Kacey Beddoes</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="6866">
                <text>2008-04-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8744">
                <text>A close-up of the note that accompanied the 32 eggs.  </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10715">
                <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="12338">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14059">
                <text>Egg note</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="2120">
        <name>eggs</name>
      </tag>
      <tag tagId="2107">
        <name>perspective gallery</name>
      </tag>
      <tag tagId="117">
        <name>squires</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2069" public="1" featured="0">
    <fileContainer>
      <file fileId="956">
        <src>https://april16archive.org/files/original/100_0282_98090c831e.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="15313">
                    <text>2008-04-09</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="16433">
                    <text>2008-04-09 09:35:25</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="2998">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4889">
                <text>Kacey Beddoes</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="6867">
                <text>2008-04-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8745">
                <text>These 32 eggs were made by a Blacksburg resident and former hokie. This is the back side of the note that accompanied the eggs. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10716">
                <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="12339">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14060">
                <text>Egg note</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="2120">
        <name>eggs</name>
      </tag>
      <tag tagId="2107">
        <name>perspective gallery</name>
      </tag>
      <tag tagId="117">
        <name>squires</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2066" public="1" featured="0">
    <fileContainer>
      <file fileId="953">
        <src>https://april16archive.org/files/original/100_0249_4532428d2a.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="15310">
                    <text>2008-04-09</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="16430">
                    <text>2008-04-09 09:27:13</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="2995">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4886">
                <text>Kacey Beddoes</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="6864">
                <text>2008-04-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8742">
                <text>These 32 eggs were made by a Blacksburg resident and former hokie.  </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10713">
                <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="12336">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14057">
                <text>Eggs</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="2120">
        <name>eggs</name>
      </tag>
      <tag tagId="2107">
        <name>perspective gallery</name>
      </tag>
      <tag tagId="117">
        <name>squires</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2067" public="1" featured="0">
    <fileContainer>
      <file fileId="954">
        <src>https://april16archive.org/files/original/100_0248_f77345134a.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="15311">
                    <text>2008-04-09</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="16431">
                    <text>2008-04-09 09:30:15</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="2996">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4887">
                <text>Kacey Beddoes</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="6865">
                <text>2008-04-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8743">
                <text>These 32 eggs were made by a Blacksburg resident and former hokie.  The note explains that the front of each egg is unique while the back of each egg is the same.  </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10714">
                <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="12337">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14058">
                <text>Eggs</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="2120">
        <name>eggs</name>
      </tag>
      <tag tagId="2107">
        <name>perspective gallery</name>
      </tag>
      <tag tagId="117">
        <name>squires</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2070" public="1" featured="0">
    <fileContainer>
      <file fileId="957">
        <src>https://april16archive.org/files/original/100_0281_2891f9b07f.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="15314">
                    <text>2008-04-09</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="16434">
                    <text>2008-04-09 09:38:14</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="2999">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4890">
                <text>Kacey Beddoes</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="6868">
                <text>2008-04-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8746">
                <text>These 32 eggs were made by a Blacksburg resident and former hokie. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10717">
                <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="12340">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14061">
                <text>Eggs</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="2120">
        <name>eggs</name>
      </tag>
      <tag tagId="2107">
        <name>perspective gallery</name>
      </tag>
      <tag tagId="117">
        <name>squires</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2071" public="1" featured="0">
    <fileContainer>
      <file fileId="958">
        <src>https://april16archive.org/files/original/100_0283_1bd874fd55.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="15315">
                    <text>2008-04-09</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="16435">
                    <text>2008-04-09 09:39:49</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="3000">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4891">
                <text>Kacey Beddoes</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="6869">
                <text>2008-04-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8747">
                <text>These 32 eggs were made by a Blacksburg resident and former hokie. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10718">
                <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="12341">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14062">
                <text>Eggs</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="2120">
        <name>eggs</name>
      </tag>
      <tag tagId="2107">
        <name>perspective gallery</name>
      </tag>
      <tag tagId="117">
        <name>squires</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2072" public="1" featured="0">
    <fileContainer>
      <file fileId="959">
        <src>https://april16archive.org/files/original/100_0284_0d29db1ff2.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="15316">
                    <text>2008-04-09</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="16436">
                    <text>2008-04-09 09:41:34</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="3001">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4892">
                <text>Kacey Beddoes</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="6870">
                <text>2008-04-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8748">
                <text>These 32 eggs were made by a Blacksburg resident and former hokie. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10719">
                <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="12342">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14063">
                <text>Eggs</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="2120">
        <name>eggs</name>
      </tag>
      <tag tagId="2107">
        <name>perspective gallery</name>
      </tag>
      <tag tagId="117">
        <name>squires</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="878" 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="2187">
                <text>Elva Orozco</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4078">
                <text>Alex</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="6056">
                <text>2007-07-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7934">
                <text>Publicado por Alex&#13;
4/19/2007 10:13:00 AM&#13;
&#13;
Veintitres aÃ±os. Treinta y dos cadÃ¡veres. Una Universidad y un resentimiento compartido que vuelve a reabrir el debate sobre las armas de fuego en los Estados Unidos de AmÃ©rica y su uso tan poco controlado como aseguran las propias vÃ­ctimas y familiares de la matanza del Virginia Tech. Cho Seung-Hui es un estudiante surcoreano que estuvo ingresado en un psiquiÃ¡trico en 2005, un hecho que hace preguntarse a los afectados un "porquÃ©" al tan poco control de esta situaciÃ³n, un "porquÃ©" al tan facil acceso a las armas de fuego (simplemente con un cuestionario a la ARF y las huellas dactilares es suficiente en la mayorÃ­a de los Estados, 18 aÃ±os necesarios para armas largas como rifle de uso habitual para caza y 21 para armas de mano (EFE)&#13;
El homicida, ahora vilipendiado y criticado ahÃ­ donde se oye su nombre, tenÃ­a desde hace tiempo una conducta violenta y que sus compaÃ±eros llegaron a temer; y que ahora se preguntan si todo esto no se podrÃ­a haber evitado. A lo largo de Internet, este apoyo masivo no se llegaba a conocer desde los atentados del 11-S o del 11-M, y ahora la simple menciÃ³n de Virginia en logs de todo tipo o anuncios en principios informativos se ha convertido inevitablemente en un primer resultado en todos los buscadores de la net. Es mÃ¡s, a lo largo de los blogs como en el que estamos ahora mismo se han dejado caer una serie de comentarios de lo mÃ¡s variados, como podemos ver aquÃ­, o aquÃ­. (No es de mÃ¡s ver que en technorati, una herramienta que une a gran parte de los blogs que existen en el mundo la matanza de Virginia Tech es lo mÃ¡s buscado)&#13;
Desde aquÃ­ y desde casi toda la net, se han repetido una continuada serie de avisos, comentarios y apoyo a los afectados. Entre ellos, por ejemplo podemos ver los comentarios dejados por los lectores de El PaÃ­s, o de cualquier otro log o lugar improvisado a lo largo de la red que se ha vuelto en un apoyo masivo en una lanza de crespones negros, palomas al viento y que cada vez recuerda mÃ¡s al movimiento popular y humano que se ha generado tanto dentro como fuera de las fronteras estadounidenses, mas dentro de estas cabe destacar el ya popularmente conocido como "movimiento naranja", por el uniforme universitario del equipo de rugby, un movimiento que tocÃ³ su hito mÃ¡s importante en la concentraciÃ³n de familiares, alumnos y profesores en los pasados dÃ­as en los que se encendieron cientos de velas como recuerdo a los fallecidos.&#13;
Ahora bien, con tal de que comprendais hasta dÃ³nde ha llegado este hecho, quisiera vincularos una serie de pÃ¡ginas en las que se referencia este trÃ¡gico hecho, como periÃ³dicos en los que se habla de esto a lo largo del globo como es el caso de El ClarÃ­n de Argentina, El Comercio de Ecuador, o El Universal de MÃ©xico en cuanto al habla hispana que compartimos, pero de igual manera quisiera relacionar una serie de pÃ¡ginas que me han llamado la atenciÃ³n por la repercusiÃ³n no ya mediÃ¡tica sino humana que conlleva, desde el apoyo incondicional de estudiantes de todo el mundo como sucede en facebook, un lugar de encuentro; casi rozando el morbo con la publicaciÃ³n de unas obras de teatro de caracter macabro del homicida; hasta un artÃ­culo en la wikipedia que sin duda ayude a recordar este trÃ¡gico suceso, mÃ¡s allÃ¡ de cualquier controversia.&#13;
&#13;
--&#13;
Fuente Original: Vade Retro&#13;
&#13;
&lt;a href="http://norvae.blogspot.com/"&gt;http://norvae.blogspot.com/&lt;/a&gt;&#13;
&#13;
Licencia de uso:&#13;
&lt;a href="http://creativecommons.org/licenses/by-nc-nd/2.5/es/"&gt; Creative Commons Reconocimiento-NoComercial-SinObraDerivada 2.5 EspaÃ±a.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9905">
                <text>spa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11832">
                <text>Creative Commons&#13;
Reconocimiento-NoComercial-SinObraDerivada 2.5 EspaÃ±a</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13322">
                <text>El Movimiento Naranja en la Red </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="172">
        <name>facebook</name>
      </tag>
      <tag tagId="985">
        <name>movimiento naranja</name>
      </tag>
      <tag tagId="986">
        <name>wikipedia</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="801" 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="2116">
                <text>Elva Orozco</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4007">
                <text>20MINUTOS.ES.</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="5985">
                <text>2007-07-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7863">
                <text>20MINUTOS.ES. 18.04.2007 - 04:54h &#13;
&#13;
&lt;ul&gt;&lt;li&gt;Ban Ki-moon, el Papa o Javier Solana han mostrado su pesar.&lt;/li&gt;&lt;li&gt;PaÃ­ses &amp;#39;enemigos&amp;#39; como IrÃ¡n o Venezuela tambiÃ©n han condenado los asesinatos.&lt;br&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;La matanza perpetrada el lunes&lt;/b&gt; en la Universidad PolitÃ©cnica de Virginia, que dejÃ³ 33 muertos, incluido el atacante, ha sido condenada por lÃ­deres polÃ­ticos y religiosos de todo el mundo. &#13;
&#13;
El primer ministro britÃ¡nico, &lt;b&gt;Tony Blair&lt;/b&gt;, en nombre del Reino Unido, expresÃ³ su &lt;b&gt;"profunda tristeza"&lt;/b&gt; y solidaridad a los estadounidenses, en especial a las familias de las vÃ­ctimas". &#13;
&#13;
&lt;b&gt;La reina Isabel II&lt;/b&gt;, que tiene previsto viajar a Estados Unidos en mayo prÃ³ximo, tambiÃ©n manifestÃ³ que estÃ¡ "conmocionada y entristecida" por la tragedia. &#13;
&#13;
Desde Ciudad del Vaticano se informÃ³ de que &lt;b&gt;el Papa&lt;/b&gt; Benedicto XVI reza por las vÃ­ctimas y familiares de esta &lt;b&gt;"tragedia sin sentido"&lt;/b&gt;, como fue calificada por el sumo pontÃ­fice. &#13;
&#13;
&lt;b&gt;El secretario general de la ONU&lt;/b&gt;, Ban Ki-moon, &lt;b&gt;surcoreano como el presunto asesino&lt;/b&gt;, el estudiante Cho Seung Hui, de 23 aÃ±os, rechazÃ³ el mÃºltiple crimen y afirmÃ³ que "la matanza rampante de civiles inocentes es inaceptable, por lo que lo condeno en los tÃ©rminos mÃ¡s enÃ©rgicos." &#13;
&#13;
Javier Solana fue profesor durante cuatro aÃ±os de la universidad atacada&#13;
&#13;
El Alto Representante para la PolÃ­tica Exterior y de Seguridad ComÃºn de la UE, &lt;b&gt;Javier Solana&lt;/b&gt;, que fue profesor de la Universidad PolitÃ©cnica de Virginia, expresÃ³ su pena desde MÃ©xico, donde se encuentra realizando una visita oficial.&#13;
&#13;
"Para mÃ­ es un acontecimiento mÃ¡s doloroso, si cabe, porque he pasado cuatro aÃ±os de mi vida en esa universidad dando clase y &lt;b&gt;recuerdo con gran emociÃ³n los aÃ±os que pasÃ© allÃ­"&lt;/b&gt;, seÃ±alÃ³.&#13;
&#13;
&lt;b&gt;Incluso los &amp;#39;enemigos&amp;#39;&lt;/b&gt; &#13;
&#13;
&lt;b&gt;IrÃ¡n&lt;/b&gt;, un paÃ­s que ha sido acusado por EE.UU. de apoyar a grupos insurgentes en Irak e intentar desarrollar un programa nuclear secreto y que no tiene relaciones diplomÃ¡ticas con Washington desde principios de los aÃ±os ochenta, &lt;b&gt;se sumÃ³ a la cadena de condolencias.&lt;/b&gt;&#13;
&#13;
Una nota emitida por el portavoz del Ministerio de Exteriores, Mohamad Ali Huseini, dice que "las acciones que perjudican a los civiles inocentes, cualquiera que sea su etnia, religiÃ³n o nacionalidad, son condenables y &lt;b&gt;contrarias a los valores de la Humanidad".&lt;/b&gt; &#13;
&#13;
El presidente de Venezuela, &lt;b&gt;Hugo ChÃ¡vez,&lt;/b&gt; que encabeza la oposiciÃ³n a EEUU en LatinoamÃ©rica, tambiÃ©n &lt;b&gt;manifestÃ³ sus "condolencias al pueblo&lt;/b&gt; y a las familias de las vÃ­ctimas de esta horrible masacre". &#13;
&#13;
Desde &lt;b&gt;Ecuador,&lt;/b&gt; paÃ­s en sintonÃ­a con Venezuela, el vicepresidente, Lenin Moreno, seÃ±alÃ³: "estoy muy apenado y quiero manifestÃ¡rselo asÃ­ al pueblo de EEUU, ese gran pueblo, del que tenemos tantas cosas que imitar y tantas cosas que no imitar". &#13;
&#13;
&lt;b&gt;RepÃºblica Dominicana&lt;/b&gt; se sumÃ³ a la corriente de pesar y su presidente, Leonel FernÃ¡ndez, enviÃ³ una carta a su colega estadounidense, George W. Bush, en la que seÃ±alÃ³ que es "importante" que EEUU sienta el apoyo moral y la solidaridad "que deseamos expresarle las naciones que &lt;b&gt;apreciamos el valor de la vida&lt;/b&gt; y respetamos los derechos humanos". &#13;
&#13;
El &lt;b&gt;Consejo Mundial de las Iglesias&lt;/b&gt; (CMI), expresÃ³ desde Ginebra (Suiza) su pesar y tambiÃ©n su &lt;b&gt;inquietud por el uso de las armas de fuego en Estados Unidos.&lt;/b&gt;&#13;
&#13;
El secretario general del CMI, Samuel Kobia, seÃ±alÃ³ que "todos somos virginianos en nuestras simpatÃ­as (hacia las vÃ­ctimas), pero muchos en el mundo &lt;b&gt;nos preguntamos tambiÃ©n por la vulnerabilidad de los ciudadanos&lt;/b&gt; de Virginia ante el mal uso de las armas no reguladas".&#13;
&#13;
--&#13;
&#13;
Fuente Original: 20 Minutos.es - EspaÃ±a&#13;
&lt;a href="http://www.20minutos.es/noticia/224436/0/mundo/expresa/condolencias/"&gt;http://www.20minutos.es/noticia/224436/0/mundo/expresa/condolencias/&lt;/a&gt;&#13;
&#13;
Derechos Reservados:&#13;
&lt;a href="http://creativecommons.org/licenses/by/2.1/es/"&gt; Creative Commons Reconocimiento 2.1 EspaÃ±a&lt;/a&gt;.&lt;/p&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9834">
                <text>spa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11797">
                <text>Creative Commons&#13;
Reconocimiento 2.1 EspaÃ±a</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13253">
                <text>El mundo entero expresa sus condolencias por la masacre de Virginia</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="932">
        <name>condolencias</name>
      </tag>
      <tag tagId="939">
        <name>ecuador</name>
      </tag>
      <tag tagId="934">
        <name>el vaticano</name>
      </tag>
      <tag tagId="937">
        <name>iran</name>
      </tag>
      <tag tagId="936">
        <name>javier solana</name>
      </tag>
      <tag tagId="935">
        <name>onu</name>
      </tag>
      <tag tagId="933">
        <name>reino unido</name>
      </tag>
      <tag tagId="940">
        <name>republica dominicana</name>
      </tag>
      <tag tagId="938">
        <name>venezuela</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2324" public="1" featured="0">
    <fileContainer>
      <file fileId="1148">
        <src>https://april16archive.org/files/original/100_0408_0ee41ca176.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="15500">
                    <text>2008-05-09</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="16620">
                    <text>2008-05-09 16:09:18</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="3199">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5090">
                <text>Kacey Beddoes</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="7068">
                <text>2008-05-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8946">
                <text>One of the items on display at the Alumni Center Art Exhibit. On 4/16/08, as part of the Day of Remembrance observance, the Holtzman Alumni Center Museum displayed examples of art, crafts, quilts, and other memorabilia contributed since April 16, 2007. This is one of over 60,000 items that will eventually go to Special Collections at Newman Library.&#13;
&#13;
A poster sent from Martin Luther King Elementary School.  Pictures of the students surround a  message that says, &#13;
&#13;
"The students of Martin Luther King Elementary School wish to express our sympathy, and encourage you to keep the dream alive!"</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10917">
                <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="12520">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14261">
                <text>Elementary school poster</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1651">
        <name>alumni center</name>
      </tag>
      <tag tagId="1989">
        <name>anniversary</name>
      </tag>
      <tag tagId="2234">
        <name>elementary school</name>
      </tag>
      <tag tagId="2226">
        <name>exhibit</name>
      </tag>
      <tag tagId="270">
        <name>poster</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="497" public="1" featured="0">
    <fileContainer>
      <file fileId="323">
        <src>https://april16archive.org/files/original/Yale Daily News - Elis decry ban on stage weapon use_8f5dae3414.pdf</src>
        <authentication>null</authentication>
        <elementSetContainer>
          <elementSet elementSetId="1">
            <name>Dublin Core</name>
            <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
            <elementContainer>
              <element elementId="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14717">
                    <text>2007-06-11</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="15837">
                    <text>2007-06-11 23:57:52</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1830">
                <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="3721">
                <text>Sara  Hood</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="5699">
                <text>2007-06-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7577">
                <text>Published: Monday, April 23, 2007&#13;
&#13;
&#13;
Cullen Macbeth&#13;
Staff Reporter&#13;
&#13;
Members of Yale&amp;#39;s undergraduate theater community reacted with anger over the weekend to Dean of Student Affairs Betty Trachtenberg&amp;#39;s decision to bar performance groups â€” at least temporarily â€” from using life-like weapons in their productions.&#13;
&#13;
The new rule is meant to protect audience members who may have connections to last week&amp;#39;s deadly gun massacre at Virginia Tech University or who may react adversely to violence on stage because of personal experiences, Trachtenberg said. But many students said the new restrictions represent inappropriate censorship of student artwork and that Trachtenberg should not have implemented them without soliciting student input beforehand.&#13;
&#13;
The new restrictions were put in place to protect people in the Yale and New Haven communities who live or have friends who live in Virginia, or who have seen people die by gun violence, Trachtenberg said. She said the outcry from students upset with her decision has been exaggerated.&#13;
&#13;
"I think people should start thinking about other people rather than trying to feel sorry for themselves and thinking that the administration is trying to thwart their creativity," Trachtenberg said. "They&amp;#39;re not using their own intelligence. ... We have to think of the people who might be affected by seeing real-life weapons."&#13;
&#13;
The new restrictions do not ban all types of stage weapons, Trachtenberg said. She said she did not prevent an instructor in theater studies who talked to her on Friday from using a dulled knife to cut a cabbage head in a production, for example.&#13;
&#13;
This weekend&amp;#39;s productions of "Red Noses" and "Orpheus in the Underworld" were affected by the rule change. "Red Noses" had to substitute wooden swords for more realistic-looking ones after learning of the rule from Trachtenberg on Thursday.&#13;
&#13;
The University overstepped its bounds by prohibiting the ways in which students can express themselves on stage, said Dara Lind &amp;#39;09, who has managed and produced several campus performances.&#13;
&#13;
"Personally, I am very strongly anti-censorship as far as the arts are concerned," she said. "I don&amp;#39;t understand what gives the college the right to try to circumscribe artistic expression like that."&#13;
&#13;
Lind is a staff columnist for the News.&#13;
&#13;
Students should be left to decide for themselves what is appropriate to include in their productions and should be able to use theater to realistically portray a range of topics, including those relating to gun violence, Yale Drama Coalition Vice President Mike Leibenluft &amp;#39;10 said. While he was in high school, Leibenluft said, he worked on a show about the Columbine High School shootings that documented witnesses&amp;#39; reactions to the violence.&#13;
&#13;
"I think the fact that it assumes that we first of all can&amp;#39;t deal with these issues in a dramatic setting and also we can&amp;#39;t take responsibility for the theater that is produced and the reaction it has from Yale students is pretty shocking," he said. "I was incredibly surprised by it. I think it&amp;#39;s totally inappropriate."&#13;
&#13;
Leibenluft said Trachtenberg should have consulted with students before implementing the new regulation.&#13;
&#13;
But Yale Dramatic Association President Emmett Zackheim &amp;#39;08 said he is not concerned by the ban because he thinks the normal rules governing the use of weapons in theatrical productions will be reinstated before long.&#13;
&#13;
"I don&amp;#39;t think it&amp;#39;s a disaster for everyone involved in theater," he said. "It essentially doesn&amp;#39;t concern me. I probably wouldn&amp;#39;t have done the same thing necessarily, but I&amp;#39;m not really concerned by it."&#13;
&#13;
Trachtenberg has not yet decided whether the new restrictions will be in place permanently and will review the decision as "things settle down," she said. She said she consulted with representatives from the Theater Studies Program and did not make a "unilateral decision" about the rule.&#13;
&#13;
Lind and several other students formed a "FEAR NO ART" Facebook group over the weekend to protest Trachtenberg&amp;#39;s decision and discussed ways to try to get the rule reversed. The groups have not yet decided on a definite plan, she said, but they may stage a rally on Beinecke Plaza or attempt to set up a meeting with Trachtenberg to discuss the rule.&#13;
&#13;
"As far as collaboration is concerned, it will probably just be easiest to take public action," Lind said. "The best way to prove that art gives much more to the student body than it takes away is to have public art and demonstrate to people what the benefit is of having unrestricted artistic expression."&#13;
&#13;
The continuation of the new restrictions could hamper the theater community&amp;#39;s willingness and ability to put on a wide variety of shows, YDC founder Eyad Houssami &amp;#39;07 said. He said he would have "strong reservations" about agreeing to produce a show that requires stage weapons â€” such as the one he put on for his senior project, which required a shotgun â€” if the ban on realistic props remains in place.&#13;
&#13;
"When you&amp;#39;re using realistic props, it doesn&amp;#39;t make sense to substitute them with children&amp;#39;s toys, because you are making a mockery of the play and of the character," Houssami said. "I feel like by banning weapons from the stage at Yale, we are kind of silencing a potentially fruitful debate on violence and the nature of violence in America today."&#13;
&#13;
The University had rules in place before last week that limited the kinds of weapons students could use in productions, Trachtenberg said, but she does not know the exact provisions.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.yaledailynews.com/articles/view/20886"&gt; Yale Daily News - 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="9548">
                <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="11540">
                <text>Editor-in-Chief, Yale Daily News - Sarah Mishkin &lt;sarah.mishkin@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12992">
                <text>Elis decry ban on stage weapon use</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="318">
        <name>guns</name>
      </tag>
      <tag tagId="583">
        <name>theater</name>
      </tag>
      <tag tagId="582">
        <name>university response</name>
      </tag>
      <tag tagId="580">
        <name>yale</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2059" public="1" featured="0">
    <fileContainer>
      <file fileId="947">
        <src>https://april16archive.org/files/original/100_0239_2f5462d208.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="15304">
                    <text>2008-04-09</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="16424">
                    <text>2008-04-09 08:47:10</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2989">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4880">
                <text>Kacey Beddoes</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="6858">
                <text>2008-04-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8736">
                <text>This VT ribbon made out of paper cranes was recently sent to Virginia Tech&amp;#39;s from Elon College in North Carolina with wishes for healing. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10707">
                <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="12330">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14051">
                <text>Elon gift</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="2113">
        <name>paper cranes</name>
      </tag>
      <tag tagId="2107">
        <name>perspective gallery</name>
      </tag>
      <tag tagId="46">
        <name>ribbon</name>
      </tag>
      <tag tagId="117">
        <name>squires</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="112" 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="1481">
                <text>Jane  Lehr</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3372">
                <text>Jane  Lehr</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="5350">
                <text>2007-05-04</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7231">
                <text>On 4/16/07 12:21 PM, "jlehr@vt.edu" &lt;jlehr@vt.edu&gt; wrote:&#13;
Subject Line: DO NOT COME TO CAMPUS&#13;
&#13;
All, please do not attempt to drop off the paper that is due today. I will send an update.&#13;
 &#13;
BE SAFE. I AM SO SORRY.&#13;
Please be safe. I hope that you are all okay.&#13;
 &#13;
Jane Lehr&#13;
&#13;
-- &#13;
Dr. Jane L. Lehr&#13;
Department of Science &amp; Technology in Society&#13;
Virginia Tech, Mail Code 0247&#13;
Blacksburg, VA 24061&#13;
IM/IChat: janengcult&#13;
&#13;
&#13;
On 4/16/07 7:57 PM, "jlehr@vt.edu" &lt;jlehr@vt.edu&gt; wrote:&#13;
Subject Line: today&amp;#39;s events&#13;
&#13;
Students,&#13;
I am very worried about you all. If you have a moment, and if I have not already spoken with you by IM/phone/email, I would very much appreciate it if you would send me an email letting me know that you are alright. I very much hope that you all are. I wish there were something I could do. And if you wish to talk, etc., if I can be of any assistance, feel free to call at the number below.&#13;
&#13;
JL&#13;
 &#13;
-----&#13;
 &#13;
Blackboard Announcement [Posted by Jane Lehr at 1:55 pm]&#13;
Mon, Apr 16, 2007 -- Papers, etc.&#13;
Students, your primary responsibility today is to yourselves, your friends, and your family. Please do not come to campus to drop off your papers. You can turn in hard copies on Thursday in class (assuming classes are not canceled). I understand if you are unable to turn in electronic copies by 5 pm. Please just do so as soon as possible.&#13;
 &#13;
I have spoken with a number of you by IM. I sincerely hope that all of my students are safe, as are your friends. My thoughts are with you. If for any reason you need to speak with me, you can call me at 540-320-5137. You can also reach me by IM/I-chat at janengcult.&#13;
 &#13;
I also understand that may need to reschedule your online chat. 	 &#13;
&#13;
-- &#13;
Dr. Jane L. Lehr&#13;
Department of Science &amp; Technology in Society&#13;
Virginia Tech, Mail Code 0247&#13;
Blacksburg, VA 24061&#13;
IM/IChat: janengcult&#13;
&#13;
&#13;
On 4/19/07 4:48 PM, "jlehr@vt.edu" &lt;jlehr@vt.edu&gt; wrote:&#13;
Subject Line: Thu, Apr 19, 2007 -- Procedure for the Completion of the Spring 2007 Academic Semester&#13;
&#13;
Dear Students,&#13;
I can only begin to convey my sorrow and grief regarding the events of last Monday. Like many of you, I have struggled to find words -- and found it a nearly impossible task. My attention is now focused on developing a plan of action for the rest of the semester. You will find a copy of university procedures for the completion of the Spring 2007 academic semester below. I will be posting an updated schedule and list of assignments shortly, for students who wish to complete all or a portion of the Humanities, Technology and the Life Sciences class.&#13;
&#13;
Our challenge, as a class, is to determine how, if at all, perspectives and tools we have explored and/or were scheduled to explore in this course can assist us in beginning to imagine the post-April 16th world. We are also encouraged by many to return to &amp;#39;everyday life&amp;#39; and &amp;#39;everyday tasks&amp;#39; -- even though there is nothing &amp;#39;everyday&amp;#39; about the situation in which we find ourselves. Building off of Dr. McNamee&amp;#39;s statement below, I want to emphasize that I recognize that different students will have different needs and desires -- as well as differing abilities to return to campus or to our class. I am committed to a policy and practice of flexibility. I am committed to supporting you in any way in which I am able. I am committed to you and this university. We all are -- amidst all the diversity of this campus and within our course -- Virginia Tech.&#13;
&#13;
If you did not attend the convocation, and have not done so already, I strongly encourage you to read the transcript of Nikki Giovanni&amp;#39;s convocation address: http://www.vt.edu/tragedy/giovanni_transcript.php&#13;
&#13;
Finally, Governor Kaine has declared Friday, April 20, 2007 a statewide day of mourning for the victims of Monday&amp;#39;s tragedy. In many communities, this will include prayer services beginning at noon. In many cases, these prayer services will be predominantly or fully-oriented within the Christian faith. I recognize that there are some students who either are not involved in a faith community or who do not identify as Christian. I recognize that these students may feel particularly challenged in locating resources or support options. Thus, again, I wish to state that my door is open to all, whether or not you continue in the course; that my door is open to students of all faiths, practices, and philosophies; and that I will work with you to assist you in locating the resources you need, no matter what these are.&#13;
&#13;
With much sorrow ... &#13;
&#13;
-- &#13;
Dr. Jane L. Lehr&#13;
Department of Science &amp; Technology in Society&#13;
Virginia Tech, Mail Code 0247&#13;
Blacksburg, VA 24061&#13;
IM/IChat: janengcult&#13;
&#13;
&#13;
&#13;
On 4/21/07 3:55 PM, "jlehr@vt.edu" &lt;jlehr@vt.edu&gt; wrote:&#13;
Subject line: Important Update: Humanities, Technology &amp; the Life Sciences&#13;
&#13;
Dear Students,&#13;
In the past day or so, I have begun to reflect on how privileged I am, in a way, that I, as the instructor of 2 Spring 07 classes, have been forced to turn my attention away to logistical considerations. &#13;
 &#13;
I realize that, to date, I have responded to this tragedy primarily as an &amp;#39;educator at Virginia Tech&amp;#39; -- seeking to track down all of &amp;#39;my&amp;#39; students, feeling immense relief each time I hear from one of you, crying when I read  your IM away messages (my poor student from Engineering Cultures who was lab partners with Henry Lee ...), even starting a website for other educators entitled &amp;#39;Teaching After April 16th&amp;#39;. &#13;
&#13;
While not yet announced, the wiki section of this site will be located at: &#13;
http://www.cddc.vt.edu/after.april.16/wiki/ &#13;
&#13;
This has protected me, I think, from being overwhelmed by my response to these events as a former student -- as someone who spent 8 years here earning two degrees; as someone who surprised herself while living in London by answering that she was "from Virginia, from Blacksburg, from Virginia Tech" ... As someone who was thrilled when the men&amp;#39;s basketball team was invited to play in the NCAA tournament this year ... How surprising to me, a northeast girl who grew up mainly in PA who eschewed Penn State as an undergraduate college because it was "too big," because it was "too football," because it was "too  ..." to find that I, in fact, love this university. &#13;
 &#13;
That said, I am writing with an update on our course. &#13;
 &#13;
* We will meet on T Apr 24 at our regular time. I encourage all of you, whether or not you believe you will complete any more assignments, to come to class. &#13;
&#13;
* Many of you have already submitted Analysis #2 in Blackboard, and I have received a number of hard copies in my mailbox. If you have not done so already, please, if you are able, bring a hard copy to class when you return. If you have not yet completed Analysis #2, it would be fantastic if I could receive these by F Apr 27th -- however, I am also flexible on this, so please get in touch to discuss.&#13;
 &#13;
* If you decide to not complete any additional assignments, for most of you your grade will be based on:&#13;
1) Blackboard Homepage   1 point   &#13;
2) Class Lead   5 points  &#13;
3) Analysis #1 (5-7 pages)   5 points   &#13;
4) Analysis #2 (5-7 pages)   10 points   &#13;
5) Online Discussion 1 (IM) (2)  4 points   &#13;
6) Blog:  Reading/Class Discussion Responses   15 points   &#13;
7) Blog: Film Diary   7.5 points&#13;
8) Blog: Participation Journal   5 points   &#13;
9) Blog: Responses to Cohort Members   7.5 points   &#13;
10) In-Class Participation   10 points   &#13;
 &#13;
That means that, for most of you, 70 points are currently possible. &#13;
 &#13;
Some of you may have already posted responses in your blog about one or more cultural event(s). Each cultural event is worth an additional 2.5 possible points.&#13;
&#13;
Some of you have not yet done a class lead. If you were scheduled to do a class lead after April 15, your total possible points, to date, are 65.&#13;
 &#13;
* Remaining Assignments: As you know, you have the option of choosing to complete any or all remaining assignments. These include:&#13;
1) Class evaluations: 1.5 points&#13;
2) IM Chat 2: 3.5 points&#13;
3) Feminist/Anti-Racist Sci-Fi Project: 10 points&#13;
4) Analysis #3: 10 points&#13;
5) Blog: Cultural Events: 5 points&#13;
 &#13;
Any additional blog postings will only boost your grade. I encourage you, if you wish, to transform your blog into a site of reflection regarding recent events. They are your blogs -- you own them. Do with then what you will.&#13;
 &#13;
* Sci-Fi Presentations: On Tuesday, you will have the opportunity to talk with your cohort, if you have not done so already, about whether or not you wish to complete this assignment either as a cohort or individually. So far, I have come up with a number of different completion scenarios. These include:&#13;
1) You can choose to present in class on either Th Apr 26 or T May 1; &#13;
2) You can choose to present to me (and any other members of our class who want to come) on Reading Day (Th May 3) -- off-campus location TBA; &#13;
3) You can create a webpage or powerpoint presentation by Fri May 4, that I will make available/link to on our Blackboard site for other people to look at. &#13;
&#13;
* 2nd IM Chat -- again, on Tuesday you can discuss with your cohort. &#13;
 &#13;
* Current grades: I need to go through all of your blogs as soon as possible to determine your current blog grades. If you have been completing all your required postings and responding to your cohort members, your blog grade will be in the B+ to A+ range. I will do this as soon as possible. &#13;
 &#13;
I also expect that grades on Analysis #2 will be no lower than a B/B- (based on past work) and that a large number of you will receive As, as was the case with Analysis #1.  &#13;
 &#13;
* Updated reading schedule: Please see Blackboard. If you are scheduled to do a class lead, please let me know as soon as possible if you plan to do so. (If you have not yet done a class lead and are not scheduled, yet want to do one, please let me know, too.)&#13;
&#13;
Students, you each are so precious -- I can only begin to imagine the pain and grieving of those who have lost someone close. &#13;
 &#13;
I am so sorry. &#13;
&#13;
I very much hope to see each of you again in class. If you cannot come to class, please remember that you are still welcome to come speak with me.&#13;
 &#13;
I am so sorry.&#13;
 &#13;
&#13;
-- &#13;
Dr. Jane L. Lehr&#13;
Department of Science &amp; Technology in Society&#13;
Virginia Tech, Mail Code 0247&#13;
Blacksburg, VA 24061&#13;
IM/IChat: janengcult</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9199">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12692">
                <text>Emails to VT STS 2154 students dated Mon Apr 16 to Sat Apr 21, 2007</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="211">
        <name>class</name>
      </tag>
      <tag tagId="210">
        <name>course</name>
      </tag>
      <tag tagId="112">
        <name>email</name>
      </tag>
      <tag tagId="209">
        <name>faculty</name>
      </tag>
      <tag tagId="113">
        <name>messages</name>
      </tag>
      <tag tagId="54">
        <name>students</name>
      </tag>
      <tag tagId="208">
        <name>teacher</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="739" 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="2058">
                <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="3949">
                <text>Elyse McCoy</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="5927">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7805">
                <text>By: Elyse McCoy, Staff Writer&#13;
Posted: 7/5/07&#13;
&#13;
The University is in the initial stages of development for the Public Information Emergency Response Communication Management System, or PIER, an Internet-based communication tool used to help relay emergency-related content and messages.&#13;
&#13;
Students, faculty and staff will be alerted in the event of a crime, unexpected weather emergency or other event that requires immediate warning through a secure Web page that will look like a regular UNC-Chapel Hill Web page. Using the PIER system, campus security officials can post key emergency materials; templates of information prepared in advance about certain scenarios; detailed information about how to reach the University&amp;#39;s key constituents, including students, faculty and staff; and background information about the campus, maps and emergency policies and procedures.&#13;
&#13;
PIER also provides the capability to track and respond to questions from key stakeholders or the general public.&#13;
&#13;
Following the Virginia Tech shootings, the University has strengthened its already extensive plans and procedures, but plans for developing a contract with the PIER vendor for the 16-campus UNC system have been in existence since the aftermath of Hurricane Katrina.&#13;
&#13;
UNC-Wilmington and UNC-Charlotte have been the most involved campuses to date, with Wilmington being designated the first campus to begin its PIER-related work and training several months ago.&#13;
&#13;
The PIER system&amp;#39;s clients include the U.S. Coast Guard - which used the system during Hurricane Katrina, the University of Houston, and several major corporations.&#13;
&#13;
UNC-Chapel Hill has just recently begun training a small group of key people most likely to be involved with using PIER as a communication tool in an emergency situation, including those involved in University relations, public safety and information technology departments.&#13;
&#13;
"We have started working on training issues as the spring semester was winding down and will continue over the summer," said Mike McFarland, the director of University communications.&#13;
&#13;
"We believe PIER can help complement resources the University already uses and are developing, such as a siren system and the Rave system to communicate quickly, accurately and effectively with students, faculty, staff and other University-related audiences or the general public," McFarland said. Unlike the PIER system, which is primarily focused around managing information in an emergency, the Rave system is part of a broader effort to extend the campus to mobile phones.&#13;
&#13;
"Rave has much more day-to-day impact on the lives of our students," said Brian Payst, the director of Technology &amp; Systems Support.&#13;
&#13;
"We certainly can, and will if needed, use Rave to send emergency broadcast messages, but it does much, much more than that for us."&#13;
&#13;
The Rave system is used to provide bus arrival times for all the Chapel Hill Transit routes and stops, the ability to read UNC e-mail, information from slice.unc.edu about student events, Blackboard alerts, Rave Guardian (an enhanced personal safety service), group messaging, polls and more on students&amp;#39; mobile phones. The University&amp;#39;s partnership with Rave Wireless also enables the University to offer a steeply discounted cell phone program to students living in residence halls on campus in order to allow access to these services at the lowest possible cost.&#13;
&#13;
The campus Emergency Notification committee has been coordinating efforts to integrate the PIER and Rave systems as much as possible to reduce duplication where it exists.&#13;
&#13;
"We plan to integrate the information coming from PIER into a spot in the UNC mobile phone interface so you can easily check for closings or other important announcements coming from PIER," Payst said.&#13;
&#13;
Payst does not think that the implementation of both the PIER system and the Rave system will be confusing to either students or their parents.&#13;
&#13;
"They do different things, so we do not think it will be all that confusing, and we will work hard to clearly communicate the distinctions where they arise."&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dailytarheel.com/media/storage/paper885/news/2007/07/05/University/Emergency.Management.Comes.To.Unc-2921381.shtml&gt;The Daily Tar Heel - July 05, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9776">
                <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="11105">
                <text>The Daily Tar Heel</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11756">
                <text>&#13;
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="13199">
                <text>Emergency management comes to UNC</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="858">
        <name>emergency response</name>
      </tag>
      <tag tagId="857">
        <name>unc</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1293" 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="2559">
                <text>Sara AA Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4450">
                <text>Philip Caruso</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="6428">
                <text>2007-09-03</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8306">
                <text>By Philip Caruso&#13;
&#13;
The Department of Public Safety, in conjunction with the Milwaukee Police Department and other government emergency agencies, has an emergency plan and training in the event a major security issue should occur.&#13;
&#13;
MPD is training all officers for an active shooter situation.&#13;
&#13;
"There may be a situation when an officer can&amp;#39;t wait for the SWAT team," MPD spokeswoman Anne E. Schwartz said. "We hope we never have to use it."&#13;
&#13;
Public Safety officers are trained to carry semi-automatic weapons, batons and pepper spray. The university purchases bulletproof vests for Public Safety officers that they are required to wear.&#13;
&#13;
Cameras have been placed around campus to aid in preventing crime.&#13;
&#13;
Emergency blue light phones, which immediately connect with Public Safety dispatch, are stationed around campus.&#13;
&#13;
IDs are required in order to enter residence halls and Raynor Library.&#13;
&#13;
"Students and faculty should take any threatening-type comments heard from a friend or acquaintance as a serious threat and should be reported immediately," Associate Director of DPS Capt. Russ Shaw said.&#13;
&#13;
--&#13;
&#13;
Original Sourc:&lt;a href=http://media.www.marquettetribune.org/media/storage/paper1130/news/2007/04/17/News/you-Dont.Think.This.Would.Happen-2844599.shtml&gt;Marquette Tribune - April 19, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10277">
                <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="11258">
                <text>Marquette Tribune</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12111">
                <text>"Sheaffer, Amanda" &lt;amanda.sheaffer@marquette.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13676">
                <text>Emergency plan and safety measures information</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1670">
        <name>marquette university</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2046" public="1" featured="0">
    <fileContainer>
      <file fileId="940">
        <src>https://april16archive.org/files/original/emergency_274f6b379b.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="15297">
                    <text>2008-04-08</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="16417">
                    <text>2008-04-08 12:25:26</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="2982">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4873">
                <text>Kacey Beddoes</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="6851">
                <text>2008-04-08</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8729">
                <text>These signs were placed in classrooms at Virginia Tech after the April 16 shootings.  &#13;
&#13;
The signs say: &#13;
&#13;
IN CASE OF EMERGENCY &#13;
REMAIN CALM AND FOLLOW THESE INSTRUCTIONS&#13;
&#13;
FIRE&#13;
*Activate the nearest fire alarm and call 9-1-1 if possible. If there are no fire alarms, knock on doors and yell "fire" as you exit the building.&#13;
*Evacuate the building.&#13;
*Do not use elevators.&#13;
*Close doors as you leave.&#13;
*Feel closed doors with the back of your hand. Do not open if doors are hot.&#13;
*Move well away from the building when evacuating.  &#13;
&#13;
SUSPICIOUS PERSON/OBJECT&#13;
SUSPICOUS PERSON&#13;
*Do not physically confront the person.&#13;
*Do not let anyone into a locked building or office.&#13;
*Do not block the person&amp;#39;s access to an exit. &#13;
*Call 9-1-1. Provide as much information as possible about the person and his or her direction of travel.  &#13;
&#13;
SUSPICIOUS PACKAGE&#13;
*Do not touch or disturb the object.&#13;
*Call 9-1-1.&#13;
*Notify your supervisor.&#13;
*Be prepared to evacuate.&#13;
&#13;
BOMB THREAT/EXPLOSION&#13;
*Notify Virginia Tech Police Department at 9-1-1.&#13;
*As you evacuate, look around for anything suspicious.  &#13;
&#13;
HAZARDOUS MATERIALS&#13;
*If an emergency develops or if anyone is in danger, call 9-1-1. &#13;
*Move away from the site of the hazard to a safe location.&#13;
*Follow the instructions of emergency personnel.&#13;
*Alert others to stay clear of the area. &#13;
*Notify emergency personnel if you have been exposed to the hazard or have information about the release. &#13;
&#13;
POWER FAILURE&#13;
*Remain calm; provide assistance to others if necessary.&#13;
*Move cautiously to a lighted area.  Exits may be indicated by lighted signs if the emergency power is operating.&#13;
*Turn off and unplug computers and other voltage-sensitive equipment.&#13;
*For localized outages, contact Facilities at 231-4300. &#13;
*For information about a prolonged outrage, check www.vt.edu or call 231-6668.&#13;
&#13;
CAMPUS WARNING SIRENS&#13;
*Seek shelter: get inside. &#13;
*Shut all doors and windows.&#13;
*Stay away from exterior windows.&#13;
*Seek information: call 231-6668 or point your Web browser to www.vt.edu. &#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10700">
                <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="12323">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14044">
                <text>Emergency signs</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="2106">
        <name>classroom sign</name>
      </tag>
      <tag tagId="2105">
        <name>emergency sign</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="974" 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="2276">
                <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="4167">
                <text>Lisa Davis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6145">
                <text>2007-08-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8023">
                <text>&lt;b&gt;President announces plans to improve system&lt;/b&gt;&#13;
&#13;
By: Lisa Davis&#13;
Posted: 5/18/07&#13;
&#13;
Boston University will be prepared to contact almost all students and staff in emergencies this fall with a mass communications system that uses text messaging, voicemail and email, President Robert Brown announced Wednesday in an email sent to the community.&#13;
&#13;
The "Send Word Now" system -- which uses all three message types -- was introduced to the campus this year to some extent, but it will be developed more over the summer, Brown said in the email.&#13;
&#13;
"In light of the deadly tragedy at Virginia Tech University, we are reviewing Boston University&amp;#39;s emergency response plans and communication systems to ensure that they are the best available," Brown said in the email.&#13;
&#13;
The improved system would also notify response teams "within minutes" of an emergency, Brown said. In an email to The Daily Free Press, Brown said he expects the school would be able to contact everyone in less than 10 minutes.&#13;
&#13;
Students are not required to register their cellphone numbers in the school directory, which is one flaw in reaching everyone in an emergency, Brown said in an April 27 interview. However, in his email to the community, Brown said incoming students will be required to register cellphone numbers or alternative contact numbers, and he encouraged current students to do so on the Student Link website.&#13;
&#13;
"We will require the information for all students studying on our Boston campuses," Brown said in the email to the Free Press. "Otherwise, the system would only reach a fraction of our students."&#13;
&#13;
The communications system "has been in place," said BU spokesman Colin Riley. "Texting is just one avenue of reaching people. We&amp;#39;re trying to find the most effective system possible," he added.&#13;
&#13;
The method was introduced about a year ago at a university meeting that addressed a possible avian flu outbreak, Riley said.&#13;
&#13;
"This assessment is to ensure and reinforce our view that students&amp;#39; safety is our highest priority," Riley said. "The best that will come out of this is that everyone is aware, and the seriousness of these systems are recognized and appreciated. We&amp;#39;re always looking to enhance communications with students."&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailyfreepress.com/media/storage/paper87/news/2007/05/18/News/EmergencyResponse.Communications.To.Reach.Phones-2905215.shtml&gt;Daily Free Press - May 18, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9994">
                <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="11147">
                <text>Daily Free Press</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11904">
                <text>Matt Negrin &lt;editor@dailyfreepress.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13398">
                <text>Emergency-Response Communications to Reach Phones</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="895">
        <name>boston university</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2188" public="1" featured="0">
    <fileContainer>
      <file fileId="1034">
        <src>https://april16archive.org/files/original/019 Emily Jane Hilscher_815b85c96b.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="15390">
                    <text>2008-04-21</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="16510">
                    <text>2008-04-21 16:25:40</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="3087">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4978">
                <text>Teri H. Hoover</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="6956">
                <text>2008-04-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8834">
                <text>Items left at the memorial plaque of Emily Hilscher on the drillfield.  Photo taken on 5-1-07.&#13;
&#13;
Photo by Teri H. Hoover.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10805">
                <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="12410">
                <text>Teri H. Hoover &lt;crystalirisphotos@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14149">
                <text>Emily Jane Hilscher</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="2189">
        <name>hilscher</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
