<?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=25&amp;sort_field=added" accessDate="2026-04-04T17:23:41+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>25</pageNumber>
      <perPage>20</perPage>
      <totalResults>1884</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="685" public="1" featured="0">
    <fileContainer>
      <file fileId="402">
        <src>https://april16archive.org/files/original/VTbook4_cb86bb9cb5.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="14792">
                    <text>2007-07-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="15912">
                    <text>2007-07-11 03:13:22</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="2009">
                <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="3900">
                <text>Steve Green</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="5878">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7756">
                <text>Members of the Vanderbilt community expressed their support for Virginia Tech by signing a leather-bound message book emblazoned with the Vanderbilt seal, a gift for Virginia Tech&amp;#39;s student government organization.&#13;
&#13;
Photo by Steve Green</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9727">
                <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="11089">
                <text>Vanderbilt University Daily Register</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11709">
                <text>Joan Brasher &lt;joan.brasher@vanderbilt.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13154">
                <text>Message Book from Vanderbilt to VT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="810">
        <name>memory book</name>
      </tag>
      <tag tagId="723">
        <name>outreach</name>
      </tag>
      <tag tagId="808">
        <name>vanderbilt</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="686" public="1" featured="0">
    <fileContainer>
      <file fileId="403">
        <src>https://april16archive.org/files/original/VT vigil_f39d6fdc15.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="14793">
                    <text>2007-07-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="15913">
                    <text>2007-07-11 03:20: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="2010">
                <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="3901">
                <text>Neil Brake</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="5879">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7757">
                <text>Vigil draws mourners for Va. Tech tragedy  &#13;
&#13;
A memorial and candlelight service for the students and faculty slain or inured during the April 16 shooting at Virginia Tech was held April 18 at Benton Chapel. Pictured (l-r) are Virginia Tech Alumna Kathy Boyer and Vanderbilt&amp;#39;s Presbyterian campus minister Jennifer Fouse. The event was sponsored by the Middle Tennessee Chapter of the Virginia Tech Alumni Association.&#13;
&#13;
Donations for the families of those affected by the tragedy may be made to the Virginia Tech Foundation, University Development, 902 Prices Fork Road (0336), Blacksburg, VA 24061.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9728">
                <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="11090">
                <text>Vanderbilt University Daily Register</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11710">
                <text>Joan Brasher &lt;joan.brasher@vanderbilt.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13155">
                <text>Vigil for VT at Vanderbilt</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="811">
        <name>rememberance</name>
      </tag>
      <tag tagId="808">
        <name>vanderbilt</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="687" public="1" featured="0">
    <fileContainer>
      <file fileId="404">
        <src>https://april16archive.org/files/original/VTribbon_2f02b31a5e.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="14794">
                    <text>2007-07-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="15914">
                    <text>2007-07-11 03:27:55</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="2011">
                <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="3902">
                <text>Vanderbilt Staff Member</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="5880">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7758">
                <text>Members of the Vanderbilt community are encouraged to wear orange and maroon today to honor those killed in the tragic events on the Virginia Tech campus. Commemorative ribbons will be distributed on the Sarratt Promenade from 9 a.m. to 4 p.m.&#13;
&#13;
At noon, a moment of silence will be observed across campus as the Kirkland Hall bell toll once for each of the victims of the shooting.&#13;
&#13;
Members of the Vanderbilt community are encouraged to sign a bound leather volume with a Vanderbilt University seal, located at the Sarratt desk. It will be sent to the Virginia Tech Student Government. For times when it will be available to be signed, click here.&#13;
&#13;
Vanderbilt Student Government is sponsoring the campus-wide orange and maroon day. &#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href= http://www.vanderbilt.edu/register/articles?search_string=virginia+tech&amp;x=29&amp;y=9&amp;id=34164&gt;Vanderbilt Daily Register - 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="9729">
                <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="11711">
                <text>Joan Brasher &lt;joan.brasher@vanderbilt.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13156">
                <text>Wear orange and maroon today for Va. Tech </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="812">
        <name>maroon and orange day</name>
      </tag>
      <tag tagId="3">
        <name>support</name>
      </tag>
      <tag tagId="808">
        <name>vanderbilt</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="670" 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="1995">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3886">
                <text>keh619 / Tales of a Back Seat Prime Minster (blog)</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="5864">
                <text>2007-07-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7742">
                <text>April 18, 2007&#13;
&#13;
&lt;i&gt;I apologize in advance for the tone of this piece. I thoroughly appreciate the devastating gravity of the situation, and I extend my heartfelt condolences to those families and friends affected.&lt;/i&gt;&#13;
&#13;
Blacksburg, Virginia.&#13;
&#13;
Less than a week ago, nothing would have sprung to mind. In fact, many would not even have known this small town existed.&#13;
&#13;
Now, for obvious reasons, it&amp;#39;s on the map.&#13;
&#13;
The events of April 16 serve as a reminder - a reminder that society is imperfect; that society is unpredictable; and that society is unprepared.&#13;
&#13;
In fairness to those involved, the events at Virgina Tech could not have been predicted with any ease. What happened was not a commonplace, run-of-the-mill, every-day happening.&#13;
&#13;
I won&amp;#39;t even go so far as to say that what happened could have been prevented - there is no reasonable way of knowing that. What I will do, however, is take a few quick shots at the aftermath.&#13;
&#13;
Everyone has their own concocted theory on how to respond to this type of situation. Pat Brown, for example, argues that whoever was the owner of the weapons used in the attack should be held accountable for the deaths of each and every student and professor on Monday. She believes that somehow, this would prevent a psychopath from acquiring the weapons they would choose to employ for such causes.&#13;
&#13;
The real world begs to differ, Pat.&#13;
&#13;
What we need to take away from the Virginia Tech Massacre is very simple - there are people out there that need help. Guns didn&amp;#39;t kill those students; the Asian man didn&amp;#39;t kill those professors; what transpired at Virginia Tech is exactly what happened at Columbine, Taber, Montreal, and every other mass shooting.&#13;
&#13;
These people were neglected.&#13;
&#13;
Do I believe in any way that whatever circumstances the shooter may have been put through justify his actions? No. Reciprocity, particularly when it involves violence, solves nothing.&#13;
&#13;
With that said, however, how do we take ownership of Monday&amp;#39;s events? Do we pretend that this was an isolated incident - a single student lashing out at random? Did this man wake up on the wrong side of the bed, and decide that morning to take the lives of 32 innocent people?&#13;
&#13;
I don&amp;#39;t think so.&#13;
&#13;
Society perpetuates the attitude and the atmosphere that leads these people to commit horrendous acts. If this young man had been cared for, appreciated, respected, and amongst friends, would there still be 32 innocent people dead? Would the thought ever have even crossed his mind that he could be capable of such an atrocity?&#13;
&#13;
These murderers are not the product of their own tendencies - they are products of society, as are we all. Maybe they needed medical attention, or maybe they had deep-rooted psychological issues; that could absolutely be a contributing factor.&#13;
&#13;
At the end of the day, however, someone pushed this young man over the edge, and was repaid in the most horrific kind.&#13;
&#13;
DO NOT fool yourself into believing that we are not responsible for what happened. Each and every one of us, through our thoughts, words, or actions, could spur or prevent the next Virginia Tech. We point fingers at the school&amp;#39;s administration, the local police, the county flower... ultimately, we must all hold ourselves and one-another accountable for the citizens we are.&#13;
&#13;
Blacksburg, you have our thoughts and prayers. If nothing else, remember:&#13;
&#13;
This too shall pass.&#13;
&#13;
In mourning, this is BSPM, signing off.&#13;
&#13;
Posted by keh619 on April 18, 2007 05:08 PM&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://blogs.usask.ca/politics/2007/04/guns_dont_kill.html"&gt;http://blogs.usask.ca/politics/2007/04/guns_dont_kill.html&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-sa/1.0/"&gt;Creative Commons Attribution-ShareAlike 1.0&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9713">
                <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="11695">
                <text>Creative Commons Attribution-ShareAlike 1.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13140">
                <text>Guns Don&amp;#39;t Kill People, Kids Who Play Video Games Kill People...</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="83">
        <name>blog</name>
      </tag>
      <tag tagId="82">
        <name>reaction</name>
      </tag>
      <tag tagId="799">
        <name>responsibility</name>
      </tag>
      <tag tagId="555">
        <name>society</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="688" 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="2012">
                <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="3903">
                <text>Editorial Staff</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="5881">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7759">
                <text>&lt;strong&gt;Emory&amp;#39;s Campus No Place For Guns&lt;/strong&gt;&lt;br /&gt;&#13;
Issue date: 5/1/07&lt;br /&gt;&#13;
Section: Editorials&#13;
&#13;
The recent controversy concerning funding for a College Republicans&amp;#39; trip to a shooting range has brought the issues of gun control and campus safety to the forefront of the Emory discourse.&#13;
&#13;
Last Wednesday, College Council denied the College Republicans funding to help pay for a trip to a local shooting range. The College Republicans said they hoped the trip would promote safe and responsible gun handling and ownership. College Council legislators say they withheld the funds due to safety concerns, even going so far as to propose an amendment to the organization&amp;#39;s monetary code prohibiting the use of College Council funds to purchase or rent firearms and ammunition.&#13;
&#13;
Generally speaking, we believe College Council should be able to fund activities like a trip to the shooting range. Shooting is a sport recognized by the NCAA, and shooting range sessions monitored by professionals are exceedingly safe. Amending the monetary code to prevent such trips is unwarranted.&#13;
&#13;
It&amp;#39;s unfortunate that the shootings at Virginia Tech took place just weeks before the scheduled date for the trip, but given that the College Republicans had been planning this event for quite some time, we don&amp;#39;t believe the shootings are an adequate reason for the trip to be cancelled. Although some could perceive the trip as insensitive, there is still an immense difference between safely firing a gun at a target and using a gun to commit mass murder. If the College Republicans want to take a trip to the shooting range, then they should receive the same support given to any other group.&#13;
&#13;
What we cannot condone is the College Republicans&amp;#39; plan to request permission from University President James W. Wagner to carry concealed weapons on campus. This idea was proposed by nationally syndicated radio host Lars Larson on whose show Tittsworth appeared to discuss the Council&amp;#39;s decision to deny funding.&#13;
&#13;
Under current Georgia law, it is illegal for a civilian to carry any sort of weapon or explosive compound while on school property. There&amp;#39;s a reason such a law was passed. We understand the need for protection and the value of feeling safe at school, but we do not believe that allowing more guns on campus will help foster the open learning environment we want at the University.&#13;
&#13;
Allowing guns on campus would propagate an atmosphere tinged with the spectre of possible violence. This would make us less safe, rather than moreso. The only people who should be allowed guns on campus are those who have gone through rigorous training to become certified in their use and have taken an oath to protect the citizenry - in this case, the Emory Police Department.&#13;
&#13;
The College Republicans should realize that by tying the issue of funding from College Council to the ludicrous question of concealed weapons on campus, they are only hurting their prospects of getting that money in the future. Who would want to give money for a shooting range trip to a group that has expressed its desire to carry concealed weapons on campus?&#13;
&#13;
As the Second Amendment states, there is a place for guns in our society. The shooting range is one of those places - Emory&amp;#39;s campus is not.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href= http://media.www.emorywheel.com/media/storage/paper919/news/2007/05/01/Editorials/Our-Opinion.Gun.Control-2889391.shtml&gt; Emory Wheel - May 1, 2007&lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9730">
                <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="11712">
                <text>"Christopher H. Megerian" &lt;cmegeri@LearnLink.Emory.Edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13157">
                <text>Our Opinion: Gun Control</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="813">
        <name>emory</name>
      </tag>
      <tag tagId="87">
        <name>gun control</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="689" 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="2013">
                <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="3904">
                <text>Susan McMillan</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="5882">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7760">
                <text>By: Susan McMillan&lt;br /&gt;&#13;
Issue date: 4/24/07&lt;br /&gt;&#13;
Section: News&#13;
&#13;
 &#13;
Emory will establish an Office of Critical Event Preparedness and Response to coordinate responses to catastrophic events, University officials announced Thursday. The office, CEPAR, will report directly to University President James W. Wagner.&#13;
&#13;
Although the announcement about CEPAR comes close on the heels of last week&amp;#39;s shooting rampage at Virginia Tech, its director, Alexander Isakov, said the timing is coincidental.&#13;
&#13;
"What brought this to the foreground was the University&amp;#39;s effort in the fall of 2005 to address the challenges of a pandemic strain of influenza," said Isakov, an associate professor of emergency medicine.&#13;
&#13;
The office was recommended by the Avian Influenza Task Force, which evaluated Emory&amp;#39;s ability to respond to a flu pandemic, and it was first officially proposed in January 2006. CEPAR will also work on drawing up plans to deal with natural disasters, campus violence, disease outbreak and other situations.&#13;
&#13;
Isakov will assume his new position on May 1, and funding for the office begins Sept. 1, the start of the University&amp;#39;s fiscal year.&#13;
&#13;
He said the staff of CEPAR will identify current emergency response plans in place across Emory&amp;#39;s divisions and coordinate them to eliminate duplication. By making planning more efficient and cohesive, Isakov said, the University can ensure more effective responses to catastrophic events.&#13;
&#13;
In addition, by bringing together Emory&amp;#39;s emergency planning and response functions, CEPAR will be able to serve as a "central command and control center" in the case of a crisis, Isakov said.&#13;
&#13;
Emory also plans to enhance its emergency notification systems with a handful of new technologies, Emory Police Department Chief Craig Watson said. He said the timing of the announcement of the enhancements is also coincidental, since they emerged as recommendations from a task force last fall.&#13;
&#13;
"We&amp;#39;ve been working on this for quite a while now," Watson said.&#13;
&#13;
One suggestion was a siren and public address system that could be used for inclement weather warnings or voice messages. Another addition would be a computerized paging system that could target key groups, such as building managers, or be used more broadly, like a text-message warning sent to registered cell phones.&#13;
&#13;
Less direct notification systems proposed include banners for Emory&amp;#39;s cable TV system and the creation of an AM radio station that could also provide traffic and campus directions when there is no emergency.&#13;
&#13;
Watson said funding has been secured for these improvements and that they are expected to be in place by the end of 2007, if not sooner.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.emorywheel.com/media/storage/paper919/news/2007/04/24/News/Administration.Emory.To.Open.Crisis.Office-2876089.shtml&gt; Emory Wheel - April 24, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9731">
                <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="11713">
                <text>"Christopher H. Megerian" &lt;cmegeri@LearnLink.Emory.Edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13158">
                <text>Administration: Emory to Open Crisis Office</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="813">
        <name>emory</name>
      </tag>
      <tag tagId="582">
        <name>university response</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="690" 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="2014">
                <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="3905">
                <text> Martha Kim</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="5883">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7761">
                <text>By: Martha Kim&#13;
Issue date: 4/24/07&#13;
Section: Letters to the Editor&#13;
&#13;
&#13;
To the editor:&#13;
&#13;
As a Korean-American, I am appalled at the media&amp;#39;s focus on the fact that the Virginia Tech killer was a "resident alien" from South Korea, even though he has lived in the U.S. for 15 of his 23 years of life.&#13;
&#13;
Had Cho Seung-Hui been born in a Western European country, his nationality would not have been a focal point of the news coverage.&#13;
&#13;
I feel that Koreans in America, or even those in Korea, should not feel the need or obligation to apologize for the actions of one man.&#13;
&#13;
Cho did not speak or act on behalf of Koreans everywhere, and he most certainly does not represent the attitudes Koreans have. My parents emigrated from Korea and many of my friends are also the children of Korean immigrants, yet none of us feel any desire to repeat what this man has done.&#13;
&#13;
So why should the Korean community in America fear a backlash? Should this group feel the need to make amends for a stranger&amp;#39;s actions?&#13;
&#13;
As a Virginian, I grieve with the families and peers of the victims. I have many friends who attend Virginia Tech, and I was terrified for their well-being, both physically and psychologically, upon hearing the news.&#13;
&#13;
But I did not feel the necessity to apologize for his deeds. Had he been from Kansas, should all residents of Kansas have felt compelled to apologize?&#13;
&#13;
Yes, he was a resident alien from Korea who was socially inept and shunned by his classmates, but there are other aspects of his character that should be addressed instead of his ethnicity, such as the fact that he was mentally ill or that he was suicidal.&#13;
&#13;
We should be focused on recognizing signals of a troubled person and preparing to handle it appropriately instead of hounding on his race.&#13;
&#13;
I felt no shame to be Korean after this incident. Why does the world insist that I must?&#13;
&#13;
Martha Kim&#13;
&#13;
Class of 2010&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.emorywheel.com/media/storage/paper919/news/2007/04/24/LettersToTheEditor/Korean.Students.Shouldnt.Have.To.Fear.Backlash-2875982.shtml&gt;Emory Wheel - April 24, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9732">
                <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="11091">
                <text>Emory Wheel</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11714">
                <text>"Christopher H. Megerian" &lt;cmegeri@LearnLink.Emory.Edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13159">
                <text>Korean Students Shouldn&amp;#39;t Have to Fear Backlash</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="713">
        <name>backlash</name>
      </tag>
      <tag tagId="813">
        <name>emory</name>
      </tag>
      <tag tagId="607">
        <name>ethnic identities</name>
      </tag>
      <tag tagId="358">
        <name>korean</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="695" 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="2017">
                <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="3908">
                <text>Editorial Staff</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="5886">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7764">
                <text>By THE DARTMOUTH EDITORIAL BOARD,&#13;
Published on Friday, April 20, 2007&#13;
&#13;
There is no easy answer to the question, What could have prevented the Virginia Tech massacre? Perhaps nothing could have been done. However, gun violence occurs every day across America and the ready availability of guns exacerbates the problem.&#13;
&#13;
After Ali Abu Kamal shot and killed seven atop the Empire State Building 10 years ago, then-New York Mayor Rudolph Giuliani called for Congress to "do more" in monitoring the ownership of guns in this country. It is unfortunate that it takes tragedies of these magnitudes to jumpstart conversation about gun control, but gun control has been an issue long before the events in Blacksburg or Columbine or New York City. It is our hope that the heinous acts of one man on one college campus will awaken college students at Dartmouth and across the country to force this issue to the forefront of the national political arena - and that it stays there.&#13;
&#13;
It&amp;#39;s easy to present statistics seemingly demonstrating that the presence of handguns either increases or decreases senseless deaths. One thing is for sure: The debate here hinges on safety and the prevention of violence - not the peripheral goals of hunters and the gun industry. Guns are an unfortunate part of the American tradition. No one can seriously suggest that arming students or classrooms would be valid measures to combat violence. The non-sporting arguments against gun control contend that citizens should have the right to have firearms in their home to protect against intruders. No reasonable individual thinks people should carry weapons around. A rational measure that could help prevent another Virginia Tech massacre would be the institution of more in-depth checks and restrictions on those who want to purchase guns.&#13;
&#13;
As for the Dartmouth community, we are in a unique position. Every presidential candidate who is serious about winning the White House will be visiting Dartmouth in the coming months. When they come, we must force them to address gun control. Research candidates&amp;#39; positions. Ask pointed questions. In the wake of the Virginia Tech attack, Giuliani, like many of the candidates, is now hiding behind the Second Amendment, declining to talk about ways to make this country safer. Regardless of where each of us stands, we should make it our duty to put the spotlight on gun control and force the candidates to do so as well.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href= http://thedartmouth.com/2007/04/20/opinion/vatech/&gt;The Dartmouth - April 20, 2007&lt;/a&gt;&#13;
&#13;
Reprinted with the permission of The Dartmouth</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9735">
                <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="11092">
                <text>The Dartmouth</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11717">
                <text>"Edward D. Kalletta III" &lt;publisher@thedartmouth.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13162">
                <text>Va. Tech and the N.H. primary</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="814">
        <name>dartmouth</name>
      </tag>
      <tag tagId="816">
        <name>new hampshire primary</name>
      </tag>
      <tag tagId="312">
        <name>politics</name>
      </tag>
      <tag tagId="817">
        <name>presidential election 2008</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="691" 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="2015">
                <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="3906">
                <text>Allie Lowe</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="5884">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7762">
                <text>By Allie Lowe, The Dartmouth Staff&#13;
April 17, 2007&#13;
&#13;
&#13;
Braving the rain and wind, approximately 100 members of the Dartmouth community gathered on Collis porch Monday night to recognize the individuals killed in that morning&amp;#39;s shootings at Virginia Tech in Blacksburg, Va.&#13;
&#13;
The two shootings, the first of which occurred in a dormitory and the second in a classroom building, took place two hours apart and left 32, plus the gunman, dead. The event marks the most deadly shooting in U.S. history.&#13;
&#13;
Monday night&amp;#39;s vigil was organized by Haley Morris &amp;#39;08 and Heather Strack &amp;#39;07. Morris first had the idea to plan the event after receiving word of the events in an e-mail sent to her sorority, Sigma Delta.&#13;
&#13;
"These are our peers in another institution and I thought that they shouldn&amp;#39;t be alone right now," Morris said.&#13;
&#13;
Other campus organizations, including the Tucker Foundation, the Panhellenic Council and several Greek houses, provided funding and support.&#13;
&#13;
"This event was really pulled together by an interesting network of Blitzing," Strack said. "In an hour, it was done."&#13;
&#13;
At the ceremony, Strack and Morris read excerpts from an e-mail received from Julie Walters Steele of Virginia Tech&amp;#39;s Unions and Student Activities office, thanking Dartmouth for its support.&#13;
&#13;
Following a brief moment of silence, the Ladies of Logos, an a cappella group comprised of members of the Gospel Choir, sang to the crowd.&#13;
&#13;
"I&amp;#39;m really proud of Dartmouth," RuDee Lipscomb &amp;#39;08, a member of the Ladies of Logos, said. "[This event] restores your faith in the College."&#13;
&#13;
After the event, students were invited to sign several large cards which will remain in Collis during the day tomorrow, and then be sent to Virginia Tech on Wednesday.&#13;
&#13;
Dean of the College Dan Nelson characterized the administration&amp;#39;s reaction to the event as "one of profound sorrow and shock."&#13;
&#13;
"It&amp;#39;s hard to imagine how any community deals with such a shocking, senseless, awful tragedy," Nelson said.&#13;
&#13;
Though he emphasized Dartmouth&amp;#39;s safety, Nelson said that no campus can consider itself resistant to all violence.&#13;
&#13;
"We&amp;#39;ve all learned in reading newspapers and watching the news over the years that disturbed people can do senseless tragic things everywhere," Nelson said. "This is a relatively safe community, but in our lives none of us are ultimately absolutely protected or immune from something like that."&#13;
&#13;
Hanover Police Chief Nicholas Giaccone agreed that the event shows that there exists the potential for violence in any community.&#13;
&#13;
Giaccone said that the Hanover Police Department&amp;#39;s officers are prepared to respond to events like those that occurred at Virginia Tech on Monday.&#13;
&#13;
"Our officers are trained and are equipped to handle a dynamic event when it first starts," Giaccone said. "Although we have access to a SWAT team, putting a SWAT team in operation would be at least an hour&amp;#39;s wait, so the officers that are on duty have to handle the situation, and go where the shots are being heard and try to neutralize it."&#13;
&#13;
Giaccone did note one potential obstacle in the Police Department&amp;#39;s response to an emergency.&#13;
&#13;
"The College for whatever reason refuses to give police access to the dorms, so if the situation should arise on campus the police may be a little hamstrung in getting in and out of dorms should a situation like that occur."&#13;
&#13;
New Hampshire, Giaccone said, has relatively lax gun laws as a result of a strong gun lobby. It is legal in New Hampshire, for example, to carry an exposed firearm, as long as the carrier does not have a felony record. Students wishing to have a gun at Dartmouth are required to store it with Safety and Security.&#13;
&#13;
College Proctor and Director of Safety and Security Harry Kinne was unavailable for comment by press time.&#13;
&#13;
Throughout the day on Monday, students, faculty, and staff sought to share updates and information about the tragedy.&#13;
&#13;
E-mail with news updates circulated around many Greek houses, as well as among other campus organizations.&#13;
&#13;
Kappa Kappa Gamma sorority president Abby Reed &amp;#39;08 said that members of her sorority sent out e-mails with updates throughout the day. Members were also encouraged to attend Monday&amp;#39;s vigil.&#13;
&#13;
"It obviously came as a big shock," Reed said. "It makes us aware of the dangers that go on at all college campuses, even though we all feel really safe here."&#13;
&#13;
Many students were impacted by the parallels between Dartmouth and Virginia Tech.&#13;
&#13;
"I&amp;#39;ve never cried watching the news before," Kelly McLaughlin &amp;#39;07 said. "It sounded so much like it could happen here in a way."&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://thedartmouth.com/2007/04/17/news/virginia/&gt; The Dartmouth - April 17, 2007&lt;/a&gt;&#13;
&#13;
&#13;
Reprinted with the permission of The Dartmouth</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9733">
                <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="11715">
                <text>"Edward D. Kalletta III" &lt;publisher@thedartmouth.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13160">
                <text>Well-wishers react to Va. shooting</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="814">
        <name>dartmouth</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
      <tag tagId="815">
        <name>well wishers</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="694" public="1" featured="0">
    <fileContainer>
      <file fileId="407">
        <src>https://april16archive.org/files/original/article-3296-1026_f403000fcd.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="14795">
                    <text>2007-07-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="15915">
                    <text>2007-07-11 14:32:36</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2016">
                <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="3907">
                <text>Maggie Goldstein</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="5885">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7763">
                <text>A participant in Monday night&amp;#39;s vigil ceremony, sporting a Virginia Tech hat, signs a giant card in Collis Cafe. It will be sent to the university Wednesday.&#13;
&#13;
Photo: Maggie Goldstein/The Dartmouth Staff&#13;
&#13;
&#13;
Reprinted with the permission of The Dartmouth</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9734">
                <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="11716">
                <text>"Edward D. Kalletta III" &lt;publisher@thedartmouth.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13161">
                <text>Dartmouth Responds</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="814">
        <name>dartmouth</name>
      </tag>
      <tag tagId="113">
        <name>messages</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="696" 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="2018">
                <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="3909">
                <text>Richard Crocker</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="5887">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7765">
                <text>By Richard Crocker, College Chaplain &#13;
Friday, April 20, 2007&#13;
&#13;
To the Editor:&#13;
&#13;
We mourn the deaths of students and faculty at Virginia Tech ("Virginia Tech gunman kills 32 in bloodbath," April 17). It is appropriate and natural that we should do so. We identify with the victims and their friends and families, because they are like us. They are students and staff at a university in a very pastoral location. Our own sense of security is threatened by this violence.&#13;
&#13;
Already, in e-mails and blogs, I am hearing calls for greater college security, ranging from arming campus police to allowing students to arm themselves. Our sense of invulnerability at Dartmouth has, despite some very tragic events, remained rather strong. Last year I attended my son&amp;#39;s graduation from a college in New York City; all guests went through metal detectors and had their belongings examined. This is, of course, a great contrast to the Dartmouth graduation.&#13;
&#13;
While I understand that conversations about campus security will inevitably, and perhaps productively, occur, I hope that one important fact does not get ignored: senseless violence is horrible wherever it occurs, whether in Darfur or Israel or Palestine or Iraq. The deaths at Virginia Tech are devastating, but their number is a fraction of those being killed daily in Iraq or Darfur. This does not mean that we should grieve these students&amp;#39; deaths less; rather, it means that we should grieve all violent deaths more. And, unless our grief produces opposition to violence, it is futile. Every life lost at Virginia Tech was precious; the loss is incalculable. But every life lost to violence anywhere is equally precious. Let us remember, and speak.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href= http://thedartmouth.com/2007/04/20/opinion/blacksburg/&gt; The Dartmouth - April 20, 2007&lt;/a&gt;&#13;
&#13;
Reprinted with the permission of The Dartmouth</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9736">
                <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="11718">
                <text>"Edward D. Kalletta III" &lt;publisher@thedartmouth.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13163">
                <text>Lessons from Blacksburg</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="818">
        <name>antiviolence</name>
      </tag>
      <tag tagId="814">
        <name>dartmouth</name>
      </tag>
      <tag tagId="819">
        <name>opinion piece</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="704" 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="2026">
                <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="3917">
                <text>Gordon Gee</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="5895">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7773">
                <text>&lt;i&gt;Message to the Vanderbilt community from Chancellor Gordon Gee regarding the April 16 tragedy at Virginia Tech&lt;/i&gt;&#13;
&#13;
Dear Members of the Vanderbilt Community,&#13;
&#13;
Today our support goes out to our colleagues, our peers, our brothers and sisters at Virginia Tech. Words fail to encompass a calamity of such magnitude. At this raw stage, we can offer our attention, our consideration, and our sympathy. We respond with the best part of ourselves.&#13;
&#13;
At a moment like this, we want you to know that the Vanderbilt community stands ready to offer help and guidance to all who seek it through the Psychological and Counseling Center (2-2571), the Office of Religious Life and Affiliated Ministries (2-2457), and, for students, your resident adviser, head resident, or assistant director. In addition, All Faiths Chapel on the first floor of the divinity school (below Benton Chapel) will be open Tuesday through Thursday from 8 a.m. to 10 p.m. for personal reflection, meditation, and prayer. In light of this incident, we are also evaluating Vanderbilt&amp;#39;s safety and emergency preparedness procedures. Please feel free to share this information with your parents and colleagues as well.&#13;
&#13;
Universities empower humans to understand the world by gathering us together in an atmosphere of implicit trust, mature safety, and mutual discussion and exchange. May that power not be shattered or compromised by the horrible and aberrant events of this day. May we, as a community and as individuals, continue to create and support conditions in which acts of violence like these are less likely to arise.&#13;
&#13;
Universities are strong of themselves, but we are stronger together. Individuals are strong of themselves, but we are stronger together. Please keep the people of Virginia Tech, and their families, and their friends and all who depend on them and know them, at the front of your minds and your hearts.&#13;
&#13;
Cordially,&#13;
Gordon Gee&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://www.vanderbilt.edu/register/articles?search_string=virginia+tech&amp;x=29&amp;y=9&amp;id=34058&gt; Vanderbilt Daily Register  - April 17, 2007&lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9744">
                <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="11093">
                <text>Vanderbilt University Daily Register</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11726">
                <text>Joan Brasher &lt;joan.brasher@vanderbilt.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13169">
                <text>Chancellor responds to Virginia Tech tragedy  </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="822">
        <name>chancellor</name>
      </tag>
      <tag tagId="821">
        <name>message of sympathy</name>
      </tag>
      <tag tagId="808">
        <name>vanderbilt</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="705" public="1" featured="0">
    <fileContainer>
      <file fileId="415">
        <src>https://april16archive.org/files/original/VTflag1_20caf9166e.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="14803">
                    <text>2007-07-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="15923">
                    <text>2007-07-11 23:58:59</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
      <file fileId="416">
        <src>https://april16archive.org/files/original/VTflag1_136c6e2c0d.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="14804">
                    <text>2007-07-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="15924">
                    <text>2007-07-11 23:59:45</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2027">
                <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="3918">
                <text>Uncredited</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="5896">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7774">
                <text>The American flag at half mast in honor of the victims of the Virginia Tech shootings. (Uncredited photo)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9745">
                <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="11727">
                <text>Joan Brasher &lt;joan.brasher@vanderbilt.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13170">
                <text>Half Mast Flag on Vanderbilt Lawn</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="78">
        <name>flag</name>
      </tag>
      <tag tagId="808">
        <name>vanderbilt</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="708" public="1" featured="0">
    <fileContainer>
      <file fileId="419">
        <src>https://april16archive.org/files/original/police_ba90b5b7a8.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="14807">
                    <text>2007-07-12</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15927">
                    <text>2007-07-12 16:23:29</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="2030">
                <text>Chad Newswander</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3921">
                <text>Roger Gupta</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="5899">
                <text>2007-07-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7777">
                <text>Several officers tie the Hokie ribbon on their motorcycles. &#13;
&#13;
Orginial Source: &lt;a href="http://www.flickr.com/photos/spector1/sets/72157600104116028/"&gt;http://www.flickr.com/photos/spector1/sets/72157600104116028/&lt;/a&gt;&#13;
&#13;
Photo courtesy of Roger Gupta&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9748">
                <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="11729">
                <text>Permission:&#13;
Roger Gupta&#13;
http://www.flickr.com/photos/spector1/sets/72157600104116028/&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13171">
                <text>Va State Police with Hokie Ribbons</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="399">
        <name>police</name>
      </tag>
      <tag tagId="46">
        <name>ribbon</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="711" public="1" featured="0">
    <fileContainer>
      <file fileId="422">
        <src>https://april16archive.org/files/original/we will prevail_1edf277733.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="14810">
                    <text>2007-07-12</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15930">
                    <text>2007-07-12 16:42:29</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="2033">
                <text>Chad Newswander</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3924">
                <text>Roger Gupta</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="5902">
                <text>2007-07-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7780">
                <text>A simple painting with a powerful message: We will prevail.&#13;
&#13;
Orginial Source: &lt;a href="http://www.flickr.com/photos/spector1/sets/72157600104116028/"&gt;http://www.flickr.com/photos/spector1/sets/72157600104116028/&lt;/a&gt;&#13;
&#13;
Photo courtesy of Roger Gupta&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9751">
                <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="11732">
                <text>Permission:&#13;
Roger Gupta&#13;
http://www.flickr.com/photos/spector1/sets/72157600104116028/&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13174">
                <text>We Will Prevail</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="824">
        <name>painting</name>
      </tag>
      <tag tagId="823">
        <name>we will prevail</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="669" public="1" featured="0">
    <fileContainer>
      <file fileId="400">
        <src>https://april16archive.org/files/original/Candlelightvigil_with Jewish Community _fe07e2e4a9.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="14790">
                    <text>2007-07-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="15910">
                    <text>2007-07-09 13:29: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="1994">
                <text>Patrick Donohoe</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3885">
                <text>Patrick Donohoe</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="5863">
                <text>2007-07-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7741">
                <text>My wife (Nina), Katie (son&amp;#39;s fiancee), her friend Rachel and I attended the Candlelight Vigil @ the drillfield after the events of 4/16. We happened to meet w/ some of the Jewish Community (Sue Kurtz, her husband, Alicia Cohen and others) @ Virginia Tech.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9712">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13139">
                <text>Candlelight Vigil w/ Jewish Community</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="122">
        <name>april 17</name>
      </tag>
      <tag tagId="215">
        <name>candlelight vigil</name>
      </tag>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="757">
        <name>jewish</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="712" public="1" featured="0">
    <fileContainer>
      <file fileId="423">
        <src>https://april16archive.org/files/original/what_to_expect_37b9f6d421.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="14811">
                    <text>2007-07-13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15931">
                    <text>2007-07-13 13:58:09</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="2034">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3925">
                <text>Family Therapy Center at Virginia Tech</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="5903">
                <text>2007-07-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7781">
                <text>(PDF, 3 pages, 144KB)&#13;
&#13;
Prepared by the Family Therapy Center at Virginia Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9752">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13175">
                <text>Adjusting to Campus Crisis: What to Expect and How to Cope</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="829">
        <name>behavioral</name>
      </tag>
      <tag tagId="832">
        <name>coping</name>
      </tag>
      <tag tagId="825">
        <name>crisis</name>
      </tag>
      <tag tagId="828">
        <name>emotional</name>
      </tag>
      <tag tagId="830">
        <name>ptsd</name>
      </tag>
      <tag tagId="831">
        <name>resources</name>
      </tag>
      <tag tagId="827">
        <name>stress</name>
      </tag>
      <tag tagId="826">
        <name>traumatic event</name>
      </tag>
    </tagContainer>
  </item>
  <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="713" 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="2035">
                <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="3926">
                <text>Edward Truong  </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="5904">
                <text>2007-07-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7782">
                <text>&lt;i&gt;Community members criticize level of communication during Wednesday&amp;#39;s incident&lt;/i&gt;&#13;
&#13;
By Edward Truong&#13;
Friday, May 18, 2007&#13;
&#13;
Some students and staff expressed concern that the university did not communicate quickly enough with the community following Wednesday&amp;#39;s weapon scare in Westwood.&#13;
&#13;
But officials said the community was not in danger and so they focused on controlling rumors.&#13;
&#13;
L.A. police shut down several blocks in the North Village in response to reports of an armed individual in the area Wednesday afternoon. In the investigation, police found a crossbow rather than a gun, and university officials did not take any formal action on campus.&#13;
&#13;
Nancy Greenstein, director of police community services for UCPD, said it was a "self-contained potential incident. ... The police (had) it under control."&#13;
&#13;
"There appeared to be no risk to campus or population," she said.&#13;
&#13;
But some believe the university should have informed students and staff about the incident sooner.&#13;
&#13;
Ruth Tesfamichael, a second-year English student, said she had no real information about what was going on, except she heard rumors from another student that there was a gunman in the area.&#13;
&#13;
"Word of mouth spread really quickly," she said. "Everyone was misinformed."&#13;
&#13;
She said she hoped the university would have found a way to reach students.&#13;
&#13;
"I expected an e-mail (from the university), but didn&amp;#39;t get anything," she said.&#13;
&#13;
Nancy Chakravarty, director of admissions for Corinne A. Seeds University Elementary School, said she was especially concerned about the lack of communication because parents were calling in to the school with questions and she was able to offer no response.&#13;
&#13;
"We had no idea that anything was going on," Chakravarty said. "One of our teachers came up and asked what ... the helicopters (flying around the area) were for."&#13;
&#13;
She said her staff was entirely unaware of the situation until concerned parents started contacting the office.&#13;
&#13;
"Parents had called and said there had been a shooting on campus."&#13;
&#13;
Lawrence Lokman, assistant vice chancellor of University Communications, called the incident a "rumor-control" issue for the university.&#13;
&#13;
He said media relations officials spent Wednesday contacting City News Service and other media outlets to correct reports, such as KCBS&amp;#39;s report of a "UCLA Gunman" which was later removed.&#13;
&#13;
"We all realize we&amp;#39;re in a fast media environment," he said. "These kinds of things always drive home (a) level of angst. ... (It&amp;#39;s) important not to add to the angst."&#13;
&#13;
Greenstein said e-mails were later sent out to various mailing lists or list-servs that went to building coordinators and residence halls.&#13;
&#13;
"The e-mail that people are talking about was addressing the rumor control," she said, referring to the list-serv notice at around 4 p.m., after the incident was over.&#13;
&#13;
E-mails were not sent out to the entire UCLA community.&#13;
&#13;
"One thing (we) want to avoid is over-noticing people. Focus groups (formed after the Virginia Tech shooting) have said if they get too much information or bulletins, they stop looking at them," Greenstein said. "When it&amp;#39;s really important, we&amp;#39;re going to tell you."&#13;
&#13;
Chakravarty contacted UCPD and was told there was no shooting and the students were not in danger.&#13;
&#13;
There are 435 students who attend the on-campus elementary school, which is the laboratory school of the UCLA Graduate School of Education &amp; Information Studies, according to the school&amp;#39;s Web site.&#13;
&#13;
The school day ends at 2:40 p.m. and students wait to be picked up in the carpool area at 2:45 p.m. The incident was first reported at around 1:30 p.m., according to witnesses, and police re-opened the streets by 3:20 p.m.&#13;
&#13;
She said it was good that officials tried to lower people&amp;#39;s anxiety, but believes she should have been notified immediately, even if her school was not at risk.&#13;
&#13;
"(It&amp;#39;s) important that we be informed so that we can take action if we need to, and we can allay the fears of the parents," she said. "Parents hear things, they get worried, they call us and they expect us to know."&#13;
&#13;
Since the Virginia Tech shooting on April 16, university campuses nationwide have been sensitive to campus safety issues.&#13;
&#13;
Greenstein said Wednesday&amp;#39;s incident was not an issue of public safety and was not similar to the events at Virginia Tech.&#13;
&#13;
But she added that emergency protocols would have been enacted had the situation been similar to the Virginia Tech shooting.&#13;
&#13;
"(They are) totally not comparable situations," she said.&#13;
&#13;
Lokman said there are trained officials and processes in place if there had been a more serious incident.&#13;
&#13;
He said that depending on the situation, university administrators could choose to use one or more different means of mass communication for safety purposes, such as loudspeakers on police cars, and the campus television station on channel 3 and the emergency radio station, 1630 AM.&#13;
&#13;
He said there is also technology in place, created before the Virginia Tech shooting, that would allow the university to instant message the community and override Web sites such as the UCLA home page and MyUCLA.&#13;
&#13;
"That is technology we&amp;#39;re evaluating to add to our mix of options," he said.&#13;
&#13;
Gabe Rose, Undergraduate Students Association Council president-elect, said university administrators should consider alternative methods of communication.&#13;
&#13;
He said since students do not constantly check their e-mails, "(it&amp;#39;s) important to look for other ways to distribute the message. ... E-mail is not effective."&#13;
&#13;
Instead, Rose said student leaders and university officials should rethink the current policies to come up with different ways to reach students in case of emergencies, such as a text-message system.&#13;
&#13;
"It&amp;#39;s important to not get caught up in the status quo, but to be creative and think harder," he said, adding that students should express their concerns and share ideas with student government leaders on how to make the campus safer.&#13;
&#13;
"If you don&amp;#39;t feel safe on campus, that&amp;#39;s a huge problem," he said.&#13;
&#13;
Greenstein said it is important to distinguish between rumors and official university notices but said the incident on Wednesday was relatively minor.&#13;
&#13;
"(There were) very few people who had issues. ... Many people saw it for what it was worth," Greenstein said.&#13;
&#13;
-- &#13;
&#13;
Original Source:&lt;a href=http://www.dailybruin.ucla.edu/news/2007/may/18/scare_response_scrutinized/&gt;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="9753">
                <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="11733">
                <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="13176">
                <text>Scare response scrutinized</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="187">
        <name>security</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
      <tag tagId="582">
        <name>university response</name>
      </tag>
      <tag tagId="834">
        <name>weapon scare</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="715" 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="2037">
                <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="3928">
                <text>Jackie Barber  </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="5906">
                <text>2007-07-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7784">
                <text>&lt;b&gt;University will focus on solving issues involving wages, safety through transition to Gene Block&lt;/b&gt;&#13;
&#13;
By Jackie Barber&#13;
Wednesday, May 9, 2007&#13;
&#13;
Acting Chancellor Norman Abrams addressed myriad staff concerns such as Chancellor-elect Gene Block, employee compensation, and campus security on Tuesday afternoon during a staff meeting.&#13;
&#13;
About 100 staff members attended the meeting, hosted by Staff Assembly President Shelley Brown.&#13;
&#13;
Abrams began his speech by praising the staff&amp;#39;s contributions to UCLA, calling the unique sense of community fostered on campus "a treasure" for such a large university and said he is impressed with Block.&#13;
&#13;
"You will find him open, a quick study, and one whose values are all in the right place," Abrams said. "I&amp;#39;m confident he will make a great chancellor."&#13;
&#13;
Abrams said the biggest challenge for Block will be "recruitment and retention of both staff and faculty."&#13;
&#13;
He cited the high cost of housing in Los Angeles as an obstacle in attracting employees from elsewhere, as potential employees have expressed concern about their ability to afford quality local housing.&#13;
&#13;
Each year the university attempts to increase the salaries of its faculty and staff, but these salaries have fallen below market, Abrams said, adding that a long-term goal for the university is to bring salaries back to market value.&#13;
&#13;
Raises for the university&amp;#39;s lowest-paid workers is also a current focus, Abrams added. He said the university has been working with the unions toward this goal.&#13;
&#13;
Abrams called the salary concern "a work in progress," but said he believes Block is up to the task and is familiar with similar issues because of his experience serving as president of the University of Virginia.&#13;
&#13;
UCLA employee compensation is a major concern not only for the UCLA community, but also for the Los Angeles area, said Nicole Moore, lead organizer for the American Federation of State, County and Municipal Employees union Local 3299.&#13;
&#13;
"Custodians (at UCLA) are paid 25 percent below what community college custodians are paid, and many people here are without a living wage," she said. "We have many concerns about the budgeting process. We want to make sure UCLA is not creating poverty in the Los Angeles community."&#13;
&#13;
She said the university must address its role in providing quality jobs and affordable health care.&#13;
&#13;
Abrams enlisted Karl Ross, chief of university police, to address campus security in light of the recent Virginia Tech shootings.&#13;
&#13;
Ross said there are 61 campus officers, and after the Columbine shootings in 1999, these officers have been trained for active-shooter situations.&#13;
&#13;
The department is also "tied into a terrorism early-action task force," Ross said.&#13;
&#13;
Ross said a group from the department meets with Student Psychological Services weekly to monitor possible threats.&#13;
&#13;
The most likely disaster on campus, though, is an earthquake, Ross said.&#13;
&#13;
Abrams pointed to the new Ronald Reagan UCLA Medical Center, which is not yet open, as a positive development this year.&#13;
&#13;
"It&amp;#39;s going to be the most technologically advanced hospital in the United States, and possibly the world," he said.&#13;
&#13;
Brown read anonymous questions submitted for Abrams by the staff, including a question on the "lingering challenge" of course and space availability.&#13;
&#13;
The session also gave Abrams the opportunity to speak about the renovation of Pauley Pavilion, and he said a committee has formed to raise money and make decisions on the project.&#13;
&#13;
The building&amp;#39;s name will not change, nor will the basic structure, but the committee has hired a firm to do preliminary designs, which Abrams has seen and called "very exciting," he said.&#13;
&#13;
Design ideas include reconstructing the bleachers to create better viewing angles and building a concourse to encase the building. Digging underneath Pauley to build a practice court is also a possibility, though an expensive one, he said.&#13;
&#13;
The renovation may be constructed by John Wooden&amp;#39;s 100th birthday in about three years, Abrams said, prompting enthusiastic chatter from the audience.&#13;
&#13;
Dinora Duarte, Staff Assembly historian and secretary and an organizer of the event, said though there were no surprises, she was pleased with Abrams&amp;#39; presentation.&#13;
&#13;
"Considering he won&amp;#39;t be here after July 31, I thought he had a good grasp on where the university is going," she said.&#13;
&#13;
She added she believes the assembly gave the staff a valuable opportunity to hear ideas firsthand from the chancellor.&#13;
&#13;
"We actually really look forward to the event," she said of the annual assembly.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.dailybruin.ucla.edu/news/2007/may/09/chancellor_discusses_campus_concerns/&gt; The Daily Bruin - May 9, 2007&lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9755">
                <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="11735">
                <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="13178">
                <text>Chancellor discusses campus concerns</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="837">
        <name>chancellor responds</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
