<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://www.april16.vtlibraries.net/items?output=omeka-xml&amp;page=22" accessDate="2026-04-04T13:59:47+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>22</pageNumber>
      <perPage>20</perPage>
      <totalResults>1884</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1707" public="1" featured="0">
    <fileContainer>
      <file fileId="834">
        <src>https://www.april16.vtlibraries.net/files/original/P1020603_cf73222aa2.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="15197">
                    <text>2008-02-18</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="16317">
                    <text>2008-02-18 20:36:27</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="2847">
                <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="4738">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6716">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8594">
                <text>Prior to Virginia Tech&amp;#39;s candelight vigil for NIU, an attendee signs a message board on display along alumni mall. Photo taken Monday, February 18, 2008.&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc-sa/3.0/"&gt;Creative Commons Attribution-NonCommercial-ShareAlike 3.0&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10565">
                <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="12205">
                <text>Creative Commons Attribution-NonCommercial-ShareAlike 3.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13911">
                <text>VT for NIU</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="507">
        <name>message board</name>
      </tag>
      <tag tagId="1911">
        <name>niu</name>
      </tag>
      <tag tagId="1909">
        <name>northern illinois university</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1704" 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="2845">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4736">
                <text>Jon Offredo</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="6714">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8592">
                <text>Issue Date:Wednesday April 18, 2007   &#13;
Section: HeadLine News Section&#13;
By Jon Offredo, Staff Writer&#13;
&#13;
What if it happened here?&#13;
&#13;
Would West Virginia University be prepared for a horrific incident such as the tragedy that occurred at Virginia Tech on Monday?&#13;
&#13;
The answer is yes, University officials say.&#13;
&#13;
"Blacksburg is a lot like Morgantown, and if it could happen there, it could happen anywhere," said West Virginia University spokeswoman Becky Loftstead.&#13;
&#13;
"In light of this, we are going to review the emergency plan and look at it intensely to make sure that all of our &amp;#39;I&amp;#39;s are dotted and &amp;#39;T&amp;#39;s are crossed to make sure any event like this is covered," Loftstead said.&#13;
&#13;
Prior to the massacre in Blacksburg, WVU officials were in the process of finding vendors to provide University-wide text messaging services in the event of an emergency, Loftstead said.&#13;
&#13;
Currently, the University would broadcast announcements on MIX and forward them to WVU.edu e-mail addresses as it does when canceling class during the winter.&#13;
&#13;
Officials were also looking into the idea of large messaging centers that would be visible in high traffic areas.&#13;
&#13;
Dr. Dan Della-Giustina, a WVU professor and expert in public safety, also suggested the implementation of a University-wide alarm system.&#13;
&#13;
"My thought is to develop an air raid-like signal, similar to the ones during World War II," Della-Giustina said. "It would sound a siren, when the students would hear this, regardless of where they were, they would know to stay put and be on lock down.&#13;
&#13;
Yet, despite new proposals, University officials have always had a plan for the instant disaster were to strike WVU.&#13;
&#13;
If WVU were faced with the same situation that arose in Blacksburg, students would be urged to remain where they were and focus on protecting themselves.&#13;
&#13;
In what Roberts called an active shooter situation, DPS members have been trained in a program called "Active Shooter," and a team is also trained in Rapid Response. To correspond with the DPS response, Morgantown Police Department, West Virginia State Police and Morgantown Fire Department also became involved in the situation.&#13;
&#13;
In the Virginia Tech scenario, students and families were reunited at the alumni center in Blacksburg, but if the situation were to arise in Morgantown, that may not be the best protocol.&#13;
&#13;
"If you look at WVU, there is no single road. We are an expansive town," Roberts said. "We work with Morgantown Police Department, and that is a benefit, to say that there is a central location is not what we are advocating."&#13;
&#13;
The ideal plan would be for students and faculty to stay in place, secure doors and to wait for the green light.&#13;
&#13;
After a traumatizing event, students are likely to need some kind of counseling to deal with the shocking aftermath.&#13;
&#13;
"It&amp;#39;s crisis counseling, and always you need to assess the student&amp;#39;s concern, is there some sense of immediacy, friend or family involved," said Dr. Peter Kahn of the Carruth Center. "With any situation where there&amp;#39;s been some kind of a loss, you want to sit with the person and let them talk freely and open up about it."&#13;
&#13;
jon.offredo@mail.wvu.edu&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27578"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27578&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10563">
                <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="12203">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13909">
                <text>WVU looks at safety plans</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1552">
        <name>counseling</name>
      </tag>
      <tag tagId="1956">
        <name>emergency plan</name>
      </tag>
      <tag tagId="1959">
        <name>messaging centers</name>
      </tag>
      <tag tagId="399">
        <name>police</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1703" 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="2844">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4735">
                <text>Patrick Southern</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="6713">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8591">
                <text>Issue Date:Friday April 20, 2007   &#13;
Section: Sports Section&#13;
Patrick Southern, Sports Writer&#13;
&#13;
Sometimes it takes a life-changing event to shake you to your very core and remind you what really matters.&#13;
&#13;
For the countless people who are suffering in ways that defy comprehension following the stunning events at Virginia Tech, that lesson came in the toughest form possible.&#13;
&#13;
While I&amp;#39;m fortunate that I don&amp;#39;t have to mourn the loss of any personal friends or family, I sincerely feel the pain of those who do.&#13;
&#13;
As DA Sports Editor Tim Tassa eloquently said in his Tuesday column, such tragedies "make sports seem so petty, so irrelevant."&#13;
&#13;
It&amp;#39;s cliche to say so, but it&amp;#39;s true. I know that by noon on Monday, I cared a lot less about how my Boston Red Sox would fare in their Patriots Day game against the Angels than I had when I woke up.&#13;
&#13;
In the wake of the campus shooting, the Hokies called off the remainder of their spring football drills and canceled all sporting events scheduled for the following days.&#13;
&#13;
These moves were in the best interest of all involved. At that point, no one needed the distraction of competition when the hearts and minds of all of those at VT were elsewhere.&#13;
&#13;
After all, athletes and coaches deserve the chance to grieve too.&#13;
&#13;
However, the moratorium on athletics at Virginia Tech ends today, when the school&amp;#39;s baseball squad hosts Miami.&#13;
&#13;
To most, this event will mean little in light of the heartache the community has suffered. After all, college baseball games go on every day nationwide at this time of year.&#13;
&#13;
But in this case, the ping of the aluminum bat and the unmistakable snap of a solid fastball against a catcher&amp;#39;s mitt will be the first sound of life beginning to return to normal in Blacksburg.&#13;
&#13;
While it&amp;#39;s true that tragedy makes us realize how meaningless the wins and losses of our teams really are, it&amp;#39;s every bit as true that athletics are a significant part of our lives.&#13;
&#13;
Sporting events are more than just a good excuse for people to get together and drink a few beers while debating the merits of blitzing off the edge on third and long.&#13;
&#13;
No, in times like this, we&amp;#39;re reminded that sports are so important to us because they&amp;#39;re a sure sign of normal life in abnormal times.&#13;
&#13;
It&amp;#39;s that importance that made renditions of "The Star-Spangled Banner" and "God Bless America" take on such added meaning at baseball games following the attacks of 9/11.&#13;
&#13;
And it&amp;#39;s the sense of unity and togetherness that sports foster that led the thousands of mourners at Virginia Tech&amp;#39;s memorial convocation Tuesday to ditch button-down shirts and dress slacks in favor of their favorite maroon and orange Hokie T-shirt.&#13;
&#13;
When those in attendance at that same service struggled to express themselves beyond their tears, they went back to the same cheers that echo through Lane Stadium on any given Saturday in the fall.&#13;
&#13;
The mourners&amp;#39; chants of "Let&amp;#39;s go, Hokies" reverberated through Cassell Coliseum, punctuated with the rhythmic clapping and repetition that is typically better suited to sporting events than soul-searching.&#13;
&#13;
But in that moment, for those who gathered to find a sense of community when pain seemed poised to take over their lives, those three simple words took on all the meaning of a chorus of "Amazing Grace."&#13;
&#13;
Instead of rallying their athletic heroes to another victory, the Virginia Tech faithful were chanting to rally their own flagging spirits.&#13;
&#13;
It&amp;#39;s easy for us to make sports trivial in the wake of traumatic events, because tragedy always makes us step back and evaluate our priorities in life.&#13;
&#13;
But for the thousands of VT students who are longing for some sense of "normal," today&amp;#39;s first pitch is the first small step back toward simpler times in Blacksburg.&#13;
&#13;
Let&amp;#39;s go, Hokies.&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27626"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27626&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10562">
                <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="12202">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13908">
                <text>Sports for the soul</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1977">
        <name>9/11</name>
      </tag>
      <tag tagId="605">
        <name>sports</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1702" 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="2843">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4734">
                <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="6712">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8590">
                <text>Issue Date:Friday August 31, 2007   &#13;
Section: Editorial Section&#13;
&#13;
West Virginia University, like many colleges around the country, has been dealing with a ripple effect of concern from faculty, students and parents alike in regards to the shooting at Virginia Tech earlier this year.&#13;
&#13;
A report, commissioned by Virginia Gov. Tim Kaine yesterday, revealed the failings of the Virginia Tech response to the situation.&#13;
&#13;
Earlier this week, The Daily Athenaeum ran a story about our college considering a variety of crisis options, including one widely thrown around by the media: text messaging.&#13;
&#13;
According to the Aug. 24 article, "Chief Bob Roberts of WVU&amp;#39;s Department of Public Safety, the University may try mass text messaging, siren alerts, video displays and safety awareness programs."&#13;
&#13;
"We are currently trying to evaluate how we would put this all together," Roberts said in the article. The communication and notification committee are going to meet together to discuss final issues regarding these plans."&#13;
&#13;
While it is important that the University and its law enforcement officials corroborate on ideas to better alert and inform the WVU community about possible dangers, it is also necessary that we take a step back and encourage truly practical ideas, designed not for flashiness but for mass utilization and for the clearest, most direct announcement of danger.&#13;
&#13;
While text messaging is a great idea, some cell phones and carriers have reputations for messages arriving days late. Additionally, not everybody has them.&#13;
&#13;
Plastering LCD screens everywhere on campus that will regularly need replacing, the visibility of such screens may be too low to properly alert everyone.&#13;
&#13;
The University could most benefit from a University-wide speaker system, an idea highlighted in the DA article.&#13;
&#13;
A centralized speaker system that could be piped into classrooms, much like those in K-12 schoolrooms, could easily be channeled into the PRT and its stations (which are both already equipped with its own radio system), and in the open areas between buildings. This would be an effective way to alert those in danger and issue appropriate lockdown procedures.&#13;
&#13;
It is the unfortunate gain of the rest of us in the college community throughout rest of the country - that we are able to reassess our handicaps and flaws in regards to our emergency response systems.&#13;
&#13;
It is also unfortunate that it is left up to national situations like the shooting at Virginia Tech to spearhead such movements.&#13;
&#13;
Those that perished on April 16 paid the ultimate price, in part, due to "missed opportunities" to seize gunman Cho.&#13;
&#13;
Let us hope that we, as colleges, are able to learn from this tragedy, and are able to avoid our own "missed opportunities" if, God forbid, anything like the tragic events at Virginia Tech should happen here.&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=29638"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=29638&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10561">
                <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="12201">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13907">
                <text>Practical emergency ideas needed</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1976">
        <name>centralized speaker system</name>
      </tag>
      <tag tagId="1973">
        <name>emergency response systems</name>
      </tag>
      <tag tagId="1974">
        <name>siren alerts</name>
      </tag>
      <tag tagId="1958">
        <name>text messaging</name>
      </tag>
      <tag tagId="1975">
        <name>video displays</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1701" 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="2842">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4733">
                <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="6711">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8589">
                <text>Issue Date:Monday October 15, 2007   &#13;
Section: Editorial Section&#13;
&#13;
Six months after the tragedy at Virginia Tech, West Virginia University and others institutions across the country have taken positive steps to reevaluate their security approaches, but there is still work to be done.&#13;
&#13;
On Friday, the University president, student body president and head of the campus police announced a new system to send text messages and e-mail alerts in the case of crimes, weather delays and closures, and other emergencies at WVU. Everyone is encouraged to sign up now for the service at &lt;a href="http://emergency.wvu.edu"&gt;http://emergency.wvu.edu&lt;/a&gt;.&#13;
&#13;
University President Mike Garrison has a history of emphasizing security at WVU. When he was president of the student body in the early 1990s, he worked on lighting issues around campus, as well as block captains and watch programs in Sunnyside. And now, as president, he is moving in the right direction.&#13;
&#13;
But the system doesn&amp;#39;t solve everything.&#13;
&#13;
The University has a history of suppressing the true number of crimes it is required by federal law to report. Three years ago, Security on Campus, Inc., a watchdog group, filed a federal complaint against WVU for crime misreporting and said the University&amp;#39;s behavior represented "the worst case of corruption we have encountered to date."&#13;
&#13;
Hopefully all the problems have been worked out. But it&amp;#39;s hard to be sure if the University is doing better or worse on campus safety issues if we can&amp;#39;t rely on figures from the past.&#13;
&#13;
Nor has the administration made good choices about weather cancellations and delays. In March, the University canceled classes for a snowstorm only after power had been lost and restored on the Evansdale Campus, the PRT had been unreliable or shut down, buses ran behind schedule and professors and students endured a dangerous day of trying to make it to class or sitting in nearly empty classrooms.&#13;
&#13;
These are not things that a new text system will solve - this is decision-making and the decision about what to do in a situation has nothing to do with the ability to announce it.&#13;
&#13;
Hopefully no one ever gets a message that there is a fire or shooting. But, if the unfortunate should happen, the language of the text should be as clear and concise as possible.&#13;
&#13;
Casual text message language, replacing numbers for letters and abbreviations that don&amp;#39;t make sense should be avoided.&#13;
&#13;
Remember that officials at Virginia Tech said their campus was safe after the first death in the morning. Then there were 31 more.&#13;
&#13;
It&amp;#39;s good that the University has entered a new era and is getting in touch with students via the medium of our time. We just hope they also change their approach and utilize this new message system properly.&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=30553"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=30553&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10560">
                <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="12200">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13906">
                <text>Sign up for new text alert system</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1972">
        <name>campus crime</name>
      </tag>
      <tag tagId="1957">
        <name>e-mail</name>
      </tag>
      <tag tagId="1971">
        <name>text alert system</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1700" public="1" featured="0">
    <fileContainer>
      <file fileId="831">
        <src>https://www.april16.vtlibraries.net/files/original/2007-04-19_27613_38bde75d8a.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="15195">
                    <text>2008-02-18</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="16315">
                    <text>2008-02-18 10:50:51</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="2841">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4732">
                <text>Tricia Fulks (Author)/Billy Wolfe (Photo)</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="6710">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8588">
                <text>Issue Date:Thursday April 19, 2007   &#13;
Section: HeadLine News Section&#13;
By Tricia Fulks, Staff Writer&#13;
&#13;
There was an overwhelming turnout at Wednesday night&amp;#39;s vigil in Woodburn Circle for those lost in Monday&amp;#39;s tragedy at Virginia Tech.&#13;
&#13;
The event was hosted by the Student Government Association.&#13;
&#13;
President David Hardesty offered some remarks to all that gathered.&#13;
&#13;
"Any explanation we may offer may seem inadequate ... we must not give up hope for a better world," he said. "Violence can erupt in even the most peaceful of places ... each one of you is precious to your family and friends and to this University and to the future of this nation."&#13;
&#13;
Students have been showing their support throughout the week since the tragedy took place Monday in Blacksburg, Va.&#13;
&#13;
Jason Parsons, SGA vice president, said the student response has been poignant since Monday. As of Tuesday, more than 800 electronic cards and 350 hand-written cards were sent to the Virginia Tech campus from students at WVU.&#13;
&#13;
On Wednesday SGA set out banners for the campus community to sign and to send messages of hope to those affected at Virginia Tech. Parsons said two banners were filled, and SGA members handed out over 1,000 maroon and orange ribbons for students to show their support for the Hokies.&#13;
&#13;
"It&amp;#39;s been amazing to see the hearts of students on campus," Parsons said.&#13;
&#13;
The Center for Civic Engagement has also played a big part in sending thoughts and prayers to the students and faculty at Virginia Tech.&#13;
&#13;
Brett White, the administrative assistant of the Center for Civic Engagement, said besides helping SGA plan Wednesday night&amp;#39;s vigil, they also have a booth set up in the Mountainlair for students to write their messages on index cards. The cards, which read "From Your Mountaineer Friends," will be sent by the Center of Civic Engagement to the Virginia Tech campus.&#13;
&#13;
But perhaps the most moving part of the week was Wednesday night&amp;#39;s service. Over 3500 students and Morgantown residents gathered outside Woodburn Hall and held candles to honor the victims and their families of the Virginia Tech massacre.&#13;
&#13;
SGA President David Kirkpatrick welcomed the crowd. Then there was a moment of silence.&#13;
&#13;
At exactly 9 p.m., three chimes rang from the bell of the U.S.S. West Virginia which sits outside Oglebay Hall and is used as a memorial to students who have died.&#13;
&#13;
"We hope that tonight&amp;#39;s vigil, through words and music and reflection, begins healing," Kirkpatrick said.&#13;
&#13;
"Thirty-three men and women lost their lives in Blacksburg on Monday, and tonight our heartfelt prayers go out to the families," Parsons said.&#13;
&#13;
He then introduced Seyran Celik, a Morgantown resident who attends Virginia Tech.&#13;
&#13;
Celik shared her story from Monday with the crowd, saying through tears that she lost two friends that day. She said she has received numerous e-mails from friends and family at WVU with the same recurring sentence: "WVU stands with VT."&#13;
&#13;
"I am honored that West Virginia University has become an extension to the Virginia Tech family," Celik said.&#13;
&#13;
Kasey Hott, a journalism major and the Mountaineer Idol winner, and Justin Johnson, a history major, sang "There You&amp;#39;ll Be."&#13;
&#13;
Kirkpatrick then gave closing remarks, letting students and faculty know activities will take place throughout the rest of the week for the WVU campus to continue their loving support to the Virginia Tech community.&#13;
&#13;
tricia.fulks@mail.wvu.edu&#13;
&#13;
--&#13;
&#13;
Photo by:Billy Wolfe&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27613"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27613&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10559">
                <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="12199">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13905">
                <text>WVU mourns</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="118">
        <name>banners</name>
      </tag>
      <tag tagId="215">
        <name>candlelight vigil</name>
      </tag>
      <tag tagId="1969">
        <name>cards</name>
      </tag>
      <tag tagId="1970">
        <name>maroon and orange ribbons</name>
      </tag>
      <tag tagId="763">
        <name>moment of silence</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1699" 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="2840">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4731">
                <text>tmf</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="6709">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8587">
                <text>Issue Date:Wednesday April 18, 2007   &#13;
Section: State &amp; Local Section&#13;
&#13;
The Student Government Association is hosting a candlelight vigil tonight to mourn the April 16 tragedy at Virginia Tech.&#13;
&#13;
Monday&amp;#39;s massacre at Virginia Tech began at a residence hall and moved across campus to Norris Hall, the university&amp;#39;s engineering building, leaving 33 people dead and many injured. The shooting is considered the worst mass killing in U.S. history.&#13;
&#13;
Throughout the day, students can send messages of hope on a banner in the Mountainlair. SGA will also be handing out orange and maroon ribbons, in support for Virginia Tech, according to a press release.&#13;
&#13;
The vigil will then take place tonight at 9 p.m. in Woodburn Circle, weather permitting.&#13;
&#13;
"We want to do our part on our campus to extend our condolences to those and their families at Virginia Tech," said SGA Vice President Jason Parsons. "We encourage all students and those in the community to come out."&#13;
&#13;
SGA President David Kirkpatrick and President David C. Hardesty are scheduled to speak.&#13;
&#13;
â€” tmf&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27582"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27582&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10558">
                <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="12198">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13904">
                <text>Virginia Tech vigil held on campus today</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="215">
        <name>candlelight vigil</name>
      </tag>
      <tag tagId="1942">
        <name>condolences</name>
      </tag>
      <tag tagId="1968">
        <name>messages of hope</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1698" 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="2839">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4730">
                <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="6708">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8586">
                <text>ssue Date:Tuesday April 17, 2007   &#13;
Section: Editorial Section&#13;
&#13;
By Monday afternoon, the nation was shocked by the tragedy that occurred at Virginia Tech.&#13;
&#13;
At least 32 people were killed and more than 20 were left wounded in the nation&amp;#39;s most violent school shooting ever.&#13;
&#13;
Though the campus of West Virginia University did not directly experience the tragedy, Mountaineer students found themselves anxious and alarmed as the news spread across the country. Some were distracted from their studies, while others waited with bated breath to hear word from their Hokie friends.&#13;
&#13;
Every student on every college campus is affected when an event like this occurs.&#13;
&#13;
As Virginia Tech mourns the loss of its students in the coming days, and some continue to mourn for many years to come, the staff of The Daily Athenaeum sends out our thoughts and sympathy to those who lost loved ones in Monday&amp;#39;s shooting.&#13;
&#13;
When an event like this occurs, no matter what college campus you call home, you are taken out of your comfort zone. It&amp;#39;s hard to fathom what Virginia Tech students, staff, faculty and families are going through.&#13;
&#13;
As a peer institution and ultimately a friend of Virginia Tech, we hope that they will be able to mend after such a horrifying occurrence.&#13;
&#13;
As the end of the semester draws near, it is hard enough to deal with the stress of classes, projects and final exams. Now, Virginia Tech students will be faced with even bigger obstacles.&#13;
&#13;
While we go through the next few weeks, take the time to remember those who were lost in this unspeakable tragedy. Enjoy every day, and take time to tell your friends and family that you care about them.&#13;
&#13;
It&amp;#39;s unfortunate, but sometimes we are so wrapped up with our daily lives that it takes an event like this to bring us back to reality and remind us to be thankful.&#13;
&#13;
Again, our hearts and thoughts go out to those affected by the shooting. We will continue to think about you as we undergo the mourning process alongside college students across the nation.&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27549"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27549&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10557">
                <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="12197">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13903">
                <text>Our hearts go out to those at VT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="747">
        <name>student reactions</name>
      </tag>
      <tag tagId="157">
        <name>sympathy</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1689" public="1" featured="0">
    <fileContainer>
      <file fileId="828">
        <src>https://www.april16.vtlibraries.net/files/original/8250f3am_be23095ced.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="15192">
                    <text>2008-02-18</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="16312">
                    <text>2008-02-18 08:04: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="2830">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4721">
                <text>David Xia (Author)/Key Nguyen (Photo)</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="6699">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8577">
                <text>By David Xia&#13;
PUBLISHED APRIL 18, 2007&#13;
&#13;
Approximately 300 students, faculty, and administrators gathered together at the sundial last night for a candlelight vigil held in memory of the 32 victims of the Virginia Tech shootings.&#13;
&#13;
University Chaplain Jewelnel Davis delivered a message of inspiration and hope to those gathered at the base of the sundial. Davis said that during this time of national mourning, it was crucial for members of the Columbia community to band together in solidarity and offer their condolences and prayers to those grieving over Virginia Tech.&#13;
&#13;
"Life will always overcome the darkness of hate, despair, and violence," Davis said.&#13;
&#13;
The undergraduate student councils provided 1,500 white candles, according to Ana Ortiz, CC &amp;#39;07 and Columbia College Student Council vice president of campus life, who spoke at the event.&#13;
&#13;
As the candles were lit and the flames passed along in silent respect, those in attendance exchanged glances of support.&#13;
&#13;
"We who believe in learning believe in hope," Davis said. "Light, when it is shared, overcomes darkness and spreads more light."&#13;
&#13;
Only the soft pattering of the drizzling rain was audible as attendees, heads lowered in respect, observed a moment of silence.&#13;
&#13;
Ortiz stated the names of the 32 students who were killed.&#13;
&#13;
"One great thing about the Columbia community is that when a horrible incident like this happens, we are able to come together as a family," Dean of Student Affairs Chris Colombo said after the event.&#13;
&#13;
For Mark Johnson, CC &amp;#39;09 and vice president of the CCSC class of 2009, the shootings in Blacksburg, Va. struck very close to home. Johnson, whose hometown is Virginia Beach, said it was unsettling to see such a tragedy occur at a place he considers home. "I&amp;#39;m happy we had something like this. It allowed me to vent," he said.&#13;
&#13;
&#13;
--&#13;
&#13;
Photo By: Key Nguyen&#13;
&#13;
Original Source: Columbia Spectator&#13;
&lt;a href="http://www.columbiaspectator.com/node/24914"&gt;http://www.columbiaspectator.com/node/24914&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10548">
                <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="12188">
                <text>Tom Faure (tomfaure@gmail.com)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13894">
                <text>Students Hold Vigil for Va. Tech Victims</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="215">
        <name>candlelight vigil</name>
      </tag>
      <tag tagId="1922">
        <name>columbia</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1697" public="1" featured="0">
    <fileContainer>
      <file fileId="830">
        <src>https://www.april16.vtlibraries.net/files/original/2007-04-26_27796_182bad82d2.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="15194">
                    <text>2008-02-18</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="16314">
                    <text>2008-02-18 09:16:31</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="2838">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4729">
                <text>Angela Moscaritolo (Author)/Andy Smith (Photo)</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="6707">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8585">
                <text>Issue Date:Thursday April 26, 2007   &#13;
Section: HeadLine News Section&#13;
Angela Moscaritolo, Staff Writer&#13;
&#13;
Three West Virginia University journalism students are putting together a memorial Web site for Virginia Tech.&#13;
&#13;
Stephen Matthews, Missy Brown and Andy Smith traveled to Virginia Tech last week to cover the tragedy for a Web site to honor the victims.&#13;
&#13;
"Our mission is to tell the story of the students that were there," Matthews said.&#13;
&#13;
The Web site will focus on the victims and their friends and families. There will be no coverage of the killer as part of the Web site, Matthews said.&#13;
&#13;
The night before their drive to Virginia Tech, Matthews and Brown searched the Internet for contacts. Matthews heard back from the best friend of victim Ross Alameddine.&#13;
&#13;
"I&amp;#39;ve honestly never heard someone&amp;#39;s voice who was so disturbed," Matthews said.&#13;
&#13;
When they got to the Virginia Tech campus, Matthews, Brown and Smith were met with a flood of other media. They saw stations covering the tragedy from Spain, Russia, Canada and more, Matthews said.&#13;
&#13;
On campus there were "hundreds upon hundreds" of flowers and signatures filling large white poster boards, Brown said. Also, no one ever spoke above a whisper, Matthews added.&#13;
&#13;
They saw inspirational messages sent from other colleges, such as New York University and Auburn University.&#13;
&#13;
"That just shows that it&amp;#39;s affected all schools," said Matthews.&#13;
&#13;
The three students took audio and video recordings along with still photography for the multimedia Web site.&#13;
&#13;
Matthews, Brown and Smith are aiming to complete the Web site by May 13 but because of finals, the deadline for the project may get pushed back.&#13;
&#13;
Through their experience at Virginia Tech, Matthews, Brown and Smith said they learned real-world lessons about journalism. Smith was shooting photographs of the campus and came across Virginia Tech students crying in front of Norris Hall. He made an ethical decision not to take photos of the students.&#13;
&#13;
"The last thing they needed was a guy sticking a camera in their face," Smith said.&#13;
&#13;
--&#13;
&#13;
Photo By: Andy Smith&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27796"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27796&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10556">
                <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="12196">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13902">
                <text>Web site commemorates those lost in Virginia Tech tragedy</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="539">
        <name>journalism</name>
      </tag>
      <tag tagId="1967">
        <name>memorial web site</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1690" public="1" featured="0">
    <fileContainer>
      <file fileId="829">
        <src>https://www.april16.vtlibraries.net/files/original/3r31p575_4c296f82c7.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="15193">
                    <text>2008-02-18</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="16313">
                    <text>2008-02-18 08:10:00</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="2831">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4722">
                <text>Armin Rosen (Author)/Shana Rubin (Photo)</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="6700">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8578">
                <text>By Armin Rosen&#13;
PUBLISHED APRIL 19, 2007&#13;
&#13;
It unfolded like a terrifying set-piece, and each new item of information seemed more trite and intuitive than the next: the killer had been a student. He had been a social outcast, homicidally contemptuous of the society that he felt had cast him out. The guns used had been purchased legally. And there had been warning signs that now seem to have stopped tantalizingly short of portending the coming carnage. "When this is all said and done," the online magazine Slate cited one blogger as writing a few hours after the shooting, "we will likely have an unhappy young person who probably had an unhealthy obsession with guns, violence, gory video games, and over the top blood-fest movies"-which means that, even in its horrifying randomness, the Virginia Tech shooting takes on a grim aspect of predictability.&#13;
&#13;
But what should this predictability teach us? Since noted poet and Virginia Tech English professor Lucinda Roy found Cho Seung-Hui unstable enough to justify contacting campus counseling services over 18 months prior to the attack, it could be argued that universities and society in general should be more aggressive in administering psychological help to those who obviously need it. We Americans are great believers in therapy: with nearly one in four adults seeking professional help and Adderall alone bringing in over a quarter-billion dollars in annual revenue, we, arguably, have put more faith in the redemptive powers of the clinical or prescriptive than any other society on earth. But it would be a mistake to let this past week&amp;#39;s events reinforce this notion that normalcy can be clinically prescribed, or, as some have recommended, clinically imposed. As author Deepak Chopra appropriately noted in an interview with CNN, psychologist Abraham Maslow maintains that love and belonging are as fundamental to human existence as food and shelter. And the professional concern of a therapist for her patient can&amp;#39;t fill basic emotional or social voids any better than social relationships alone can cure mental illness.&#13;
&#13;
Does this teach us that our society predisposes people to committing horrific killing sprees? I, for one, appreciate a certain irony in the fact that this event has ultimately strengthened the very community from which Cho felt so excluded. However, it is patently insensitive to blame the Virginia Tech community for excluding someone who was so invisible to it. And, by all accounts, Cho was not just invisible to those around him, but invisible to himself as well: by shaving off his weapons&amp;#39; serial numbers, carrying no identification, and committing suicide in a way that would obscure his most individual physical feature-his face-he argued against his own humanity and individuality. So if we are to blame the community as a whole for its exclusivity, then it would be disingenuous because we too fail to reach out to those in potential danger of lapsing into a permanent state of social and personal non-existence.&#13;
&#13;
But is the existence of such people alone enough to teach us that our society is somehow structured to produce killing sprees like the one at Virginia Tech? In his seminal work, Suicide (1897), sociologist Emile Durkheim poses a similar question, and proceeds to argue that the social and historical consistency of the suicide rate proves the act to be an unalterable "social fact," built into the social structure. It&amp;#39;s terrifying to think of the destructive confluence of mental instability, exclusion and a propensity for violence as one such "social fact." But reactions to the massacre suggest that that&amp;#39;s exactly how a lot of people feel: for instance, New York Times columnist Bob Herbert blamed a "staggering amount of murders" on "feelings of inadequacy, psychosexual turmoil and the easy availability of guns." According to Herbert, the only item over which we, as a society, have conscious control is the last.&#13;
&#13;
Yet, if we learn one thing from the Virginia Tech massacre, it should be the importance of using what sliver of control we do have. We can encourage people like Cho to seek the help they desperately need without expecting that help to be a cure-all. We can reach out to the socially alienated, and make an effort to acknowledge those people who we would usually ignore. We can also limit the availability of handguns. Most importantly, we can insist that this past Monday&amp;#39;s event were not structural, and avoid lapsing into the kind of cynicism that might have made such an event possible in the first place.&#13;
&#13;
Scores of Facebook groups have a name derived from the phrase "Today, we are all Hokies." The phrase was meant as a show of solidarity with a university suffering in ways none of us can imagine. But as long as we keep internalizing, tolerating, or even ignoring the factors that led to Monday&amp;#39;s attack it, also functions as a cynical truth: we are all vulnerable. And in that respect, we are all Hokies.&#13;
&#13;
&#13;
--&#13;
&#13;
Photo By: Shana Rubin&#13;
&#13;
Original Source: Columbia Spectator&#13;
&lt;a href="http://www.columbiaspectator.com/node/24952"&gt;http://www.columbiaspectator.com/node/24952&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10549">
                <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="12189">
                <text>Tom Faure (tomfaure@gmail.com)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13895">
                <text>Lessons from Blacksburg</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1922">
        <name>columbia</name>
      </tag>
      <tag tagId="482">
        <name>mental illness</name>
      </tag>
      <tag tagId="1938">
        <name>predictability</name>
      </tag>
      <tag tagId="1939">
        <name>psychological help</name>
      </tag>
      <tag tagId="603">
        <name>suicide</name>
      </tag>
      <tag tagId="1585">
        <name>therapy</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1696" 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="2837">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4728">
                <text>Ry Rivard</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="6706">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8584">
                <text>Issue Date:Tuesday April 17, 2007   &#13;
Section: Editorial Section&#13;
Ry Rivard, City Editor&#13;
&#13;
By the end of the Monday it was obvious that the media had begun selling the day&amp;#39;s horrors at Virginia Tech. No matter the gravity or magnitude of a tragedy, this country&amp;#39;s commentators veer from events as they are, in and of themselves horrible, to a decontextualized, surreal account of things so they can be sold to and consumed by us.&#13;
&#13;
The shooting - the deadliest shooting in American history - quickly became, for some people, another chance to make various political points. It became, by the time Wolf Blitzer&amp;#39;s show aired, a sort of tragic-porn, a way for the media to provoke rather than inform. Commentators tried to politicize it, politicians tried to comment on it, the news channels tried to heighten the drama with their usual parade of loud music and epic comparisons, "This is worse than ... " or "This is the biggest ... " Was what happened not enough in and of itself?&#13;
&#13;
Glenn Reynolds, law professor at University of Tennessee, quickly posted a 52-page paper on his popular Weblog arguing that the best way to prevent shootings like Monday&amp;#39;s is to permit concealed handguns. It was the day&amp;#39;s most academic approach to the event, but it was also one of the most callous.&#13;
&#13;
Written by two economists, the paper concluded that "the only policy factor to influence multiple victim public shootings is the passage of concealed handgun laws." Reynolds and several others who followed his lead took the deaths of 33 students to advance an agenda which, although done in an attempt to stop such events in the future, made them into a policy argument.&#13;
&#13;
Similarly, the Drudge Report, a conservative news site, dragged out a fourth-month old story from Roanoke Times about failed piece of legislation that would have permitted concealed handguns.&#13;
&#13;
It reported, "Virginia Tech spokesman Larry Hincker was happy to hear the bill was defeated. &amp;#39;I&amp;#39;m sure the university community is appreciative of the General Assembly&amp;#39;s actions because this will help parents, students, faculty and visitors feel safe on our campus.&amp;#39;"&#13;
&#13;
The point was: if students hadn&amp;#39;t had to wait for the police to arrive, Monday&amp;#39;s shootings would have been an incident and not a tragedy. The effect of their ill-made point was that gun control advocates were somehow responsible for the shooting.&#13;
&#13;
In response, the Huffington Post highlighted a story that the White House affirmed the "president believes that there is a right for people to bear arms." Their point: if only there had been a law against carrying weapons (and there is - VT&amp;#39;s handbook doesn&amp;#39;t permit guns on campus), this wouldn&amp;#39;t have happened. The effect of that point was that somehow the Second Amendment or the Bush Administration was responsible for the shooting.&#13;
&#13;
The politicians, meanwhile, all took care to come out and say how horrible the events were. Perhaps they thought if they didn&amp;#39;t grandstand on TV with their condolences, someone might mistake their silence for support?&#13;
&#13;
The news channels proved again that constant, breathless coverage undermines the fundamental tragedy, horror and fact of an event. CNN escalated its description of the shootings from "monumental" to a "rampage" to a "massacre," to a "bloodbath," as if their appellations signified anything but their desire to sell the story.&#13;
&#13;
By Monday evening, each station had begun saying as often as possible how tragic the obvious tragedy was, and how horrible the horror was - and at the same time they plugged their own brand: "Stay tuned to us for ... " For what? For whatever scarce news they could pry from any student on the VT campus they could pull aside and, occasionally, attempt to provoke into more tears with probing, useless questions.&#13;
&#13;
CNN kept mentioning their "I Reporters," which is their way of saying "people who sent us pictures from their cell phones."&#13;
&#13;
If the media&amp;#39;s reaction Monday was a sign of the American psyche, we are a country that cannot understand an event outside of a political framework, and we are a country that cannot understand an event as it is.&#13;
&#13;
There were two terrible but - compared to the media&amp;#39;s carnival barker commentary - honest accounts from Monday. The first was cell phone video footage taken outside the building of the shootings that captured the sounds of 27 shots being fired, presumably into somebody. It was replayed and replayed and, after a while, it became a selling point for CNN rather than a way to describe the day&amp;#39;s events.&#13;
&#13;
The second account, reminiscent of Sept. 11, came from a student who told ABC News, "Everyone started panicking and jumping out the window."&#13;
&#13;
But there is nothing anyone can say that makes it make sense, so, from Lord Byron:&#13;
&#13;
And thou art dead, as young and fair&#13;
&#13;
As aught of mortal birth;&#13;
&#13;
And form so soft, and charms so rare,&#13;
&#13;
Too soon return&amp;#39;d to Earth!&#13;
&#13;
Though Earth receiv&amp;#39;d them in her&#13;
&#13;
bed,&#13;
&#13;
And o&amp;#39;er the spot the crowd may&#13;
&#13;
tread&#13;
&#13;
In carelessness or mirth,&#13;
&#13;
There is an eye which could not brook&#13;
&#13;
A moment on that grave to look.&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27550"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27550&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10555">
                <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="12195">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13901">
                <text>When tragedy is for sale, it isnâ€™t tragic enough</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1964">
        <name>commentators</name>
      </tag>
      <tag tagId="1966">
        <name>concealed handgun laws</name>
      </tag>
      <tag tagId="1965">
        <name>drama</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="312">
        <name>politics</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1695" 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="2836">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4727">
                <text>Kellen Henry</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="6705">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8583">
                <text>Issue Date:Friday September 7, 2007   &#13;
Section: HeadLine News Section&#13;
By Kellen Henry, Staff Writer&#13;
&#13;
Many students gathered for candlelight vigils and wore ribbons in support of Virginia Tech after the April 16 shooting. While most students did not fear for their lives on campus, they realized such a tragedy could just as easily occur in Morgantown.&#13;
&#13;
Last week, a panel appointed by Virginia Gov. Tim Kaine reported findings on the shooting rampage by student Seung-Hui Cho that killed 32 people in Blacksburg, Va.&#13;
&#13;
The report presented more than 70 recommendations to advise law enforcement, school officials and medical personnel.&#13;
&#13;
They also intended to help other colleges choose proper security solutions for their own campuses.&#13;
&#13;
This week, West Virginia University officials announced a plan to send mass text messages in an emergency. The University will also provide better quality lighting in key pedestrian areas such as sidewalks between the Downtown Library Complex, the Mountainlair, the PRT and residence halls.&#13;
&#13;
The panels&amp;#39; report criticized Virginia Tech&amp;#39;s emergency response plan because it lacked guidelines for a shooter scenario and did not allow police to play a major role in emergency decision making.&#13;
&#13;
"We don&amp;#39;t see that as an issue here at WVU. As the first responders here, it makes sense for us to have an active role," said Chief Bob Roberts of the University Department of Public Safety.&#13;
&#13;
Administrators here began revising its policies in December 2005 to align it with the federal Department of Homeland Security&amp;#39;s National Incident Management System. The University&amp;#39;s new plan will be unveiled in October said Becky Lofstead, executive director of internal communications.&#13;
&#13;
It will include emergency training for students and staff and job action checklists. There is a Web site planned for relaying emergency information, Lofstead said.&#13;
&#13;
At Virginia Tech, police had no means of sending emergency alerts themselves and also failed to warn the administration that a gunman could still be loose on campus.&#13;
&#13;
The initial emergency e-mail and phone alerts to students and staff came too late and were too vague to be effective, the report found.&#13;
&#13;
"Warning the students, faculty and staff might have made a difference," the panel wrote. "So the earlier and clearer the warning, the more chance an individual had of surviving."&#13;
&#13;
With a large student body sprawling between two campuses, WVU sees the dire need to refine its emergency alert system.&#13;
&#13;
The Tech panel advised a multi-level alert, for instance alert sirens that signal students to check texts or e-mails for emergency updates.&#13;
&#13;
The Virginia Tech shootings also reinforced the importance of solid mental health care for students and faculty.&#13;
&#13;
The panel found that university and health officials did not coordinate information and intervene efficiently after concerns surfaced about the shooter.&#13;
&#13;
"No one knew all the information and no one connected all the dots," the report said.&#13;
&#13;
WVU&amp;#39;s Carruth Center for Counseling already tries to communicate information while protecting privacy, said director Catherine Yura. A crisis committee joins counselors with resident life, police and student affairs representatives.&#13;
&#13;
"What we do is discuss situations that come up and try to understand if it is something to be concerned about," Yura said.&#13;
&#13;
kellen.henry@mail.wvu.edu&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=29759"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=29759&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10554">
                <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="12194">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13900">
                <text>Virginia Tech panel recommends security solutions for colleges</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1932">
        <name>candlelight vigils</name>
      </tag>
      <tag tagId="1552">
        <name>counseling</name>
      </tag>
      <tag tagId="1962">
        <name>emergency response plan</name>
      </tag>
      <tag tagId="1961">
        <name>mass text messages</name>
      </tag>
      <tag tagId="1960">
        <name>panel</name>
      </tag>
      <tag tagId="1">
        <name>ribbons</name>
      </tag>
      <tag tagId="1963">
        <name>warning students</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1694" 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="2835">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4726">
                <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="6704">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8582">
                <text>Issue Date:Wednesday April 18, 2007   &#13;
Section: Editorial Section&#13;
&#13;
There are still many questions left for the Blacksburg, Va., community as police and federal agents continue to investigate the gunman&amp;#39;s trail.&#13;
&#13;
But there is one startling fact we are all aware of: Students and the rest of the university&amp;#39;s community were not notified of the first shooting until nearly two hours later. And when they were notified, many did not take the message seriously until, in many cases, they saw bloodshed for themselves.&#13;
&#13;
It&amp;#39;s hard not to think about how West Virginia University and others across the country would respond if a similar situation took place on their campuses.&#13;
&#13;
As explained in a news story in today&amp;#39;s Daily Athenaeum, WVU officials say they do have an emergency plan in place.&#13;
&#13;
But does it need to be modified to be made more efficient?&#13;
&#13;
In a much less dire situation, WVU administrators took several hours to cancel classes when roads were too icy to drive on during a snowstorm last March.&#13;
&#13;
When Virginia Tech officials did notify the campus of the shootings, the message was mass delivered through an e-mail. Many VT students wondered aloud to the media if the tragedy could have only been an incident if they were notified earlier.&#13;
&#13;
And what if e-mails simply can&amp;#39;t be read when the power shuts off or students and faculty don&amp;#39;t check their accounts?&#13;
&#13;
We&amp;#39;re glad to hear University officials are looking into campus-wide text messaging and messaging centers that are visible to traffic. Innovative measures such as these are some of the best ways to reach everybody at once nowadays. Still, in an emergency, cell phone network lines could become loaded, making messages hard to send. That&amp;#39;s why universities, including WVU, need to work with local companies and networks to make plans for mass communication during security threats.&#13;
&#13;
Of course, nothing can change Monday&amp;#39;s monstrosity. But if communities and administrators work together now, they may be able to prevent another tragedy.&#13;
&#13;
--&#13;
&#13;
Originial Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27573"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27573&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10553">
                <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="12193">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13899">
                <text>Better safety measures needed</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1957">
        <name>e-mail</name>
      </tag>
      <tag tagId="1956">
        <name>emergency plan</name>
      </tag>
      <tag tagId="1959">
        <name>messaging centers</name>
      </tag>
      <tag tagId="981">
        <name>safety measures</name>
      </tag>
      <tag tagId="1958">
        <name>text messaging</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1693" 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="2834">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4725">
                <text>Tim Tassa</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="6703">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8581">
                <text>Issue Date:Tuesday April 17, 2007   &#13;
Section: Sports Section&#13;
By Tim Tassa, Sports Editor&#13;
&#13;
Monday morning&amp;#39;s events make sports seem so petty, so irrelevant.&#13;
&#13;
Every year there are one or two tragedies of monumental proportion that unite people and draw to mind that there is more to life than a rivalry, a goal post, a field and a coach.&#13;
&#13;
And, unfortunately, April 16, when at least 32 people at Virginia Tech were killed by a deranged gunman, was one of those days. It marked the beginning of a time to reach out to the Virginia Tech community, for so many at West Virginia University - through geography, friends and family - are connected to the institution.&#13;
&#13;
The day after the deadliest shooting on a college campus in United States history brings nothing but disbelief, outrage, curiosity and grief.&#13;
&#13;
As we often do during times of bewilderment and mourning, we ask, "Why do bad things happen to good people?"&#13;
&#13;
And still, there is no answer.&#13;
&#13;
As a University that is familiar with Virginia Tech, whether on the playing field, academically or socially, it is only human to keep southwest Virginia in our thoughts just a day after such a disaster.&#13;
&#13;
But the effects are much more widespread.&#13;
&#13;
After the images displayed on network television, Monday&amp;#39;s violence will be remembered just as the Kent State, University of Texas and Columbine shootings - except at an even larger level.&#13;
&#13;
In addition, the events may be a catalyst for change in the way higher education is conducted nationwide. Or at least in security procedures.&#13;
&#13;
For those of us sitting in large lecture halls and residing in campus dormitories, the anxiety and horror of what happened in Blacksburg, Va., doesn&amp;#39;t seem very far.&#13;
&#13;
The realization is that tragedies of this magnitude can happen on any campus, big or small. For current WVU students, sitting in class today will feel much different than it did last Tuesday.&#13;
&#13;
In speaking with a few VT students on Monday, the realities of the events had yet to hit them.&#13;
&#13;
By day&amp;#39;s end it surely had.&#13;
&#13;
It was certainly felt by VT&amp;#39;s most familiar face.&#13;
&#13;
"How could one person cause so many senseless deaths? I&amp;#39;m in shock," said head football coach Frank Beamer, according to espn.com. "This is such a caring, friendly place. This is a college town. And now one person has an impact like this?"&#13;
&#13;
But on a day, and by a person whose words are normally revered, his thoughts were no more telling than the voices and words of the students who called in on CNN to tell their stories.&#13;
&#13;
In watching the cable network, a Virginia Tech student, Matt Waldron, was interviewed and spoke of his interactions with well-wishers and friends.&#13;
&#13;
Among them: a U.S. Soldier in Iraq who ironically faces similar dangers daily.&#13;
&#13;
And in watching Monday&amp;#39;s death toll grow from 22 to 25 to 30 to 32, I wondered why the deaths in Iraq do not collect the same disbelief, outrage, curiosity and grief.&#13;
&#13;
But as violence in war is unfortunately expected, bloodshed in the classroom is unimaginable.&#13;
&#13;
timothy.tassa@mail.wvu.edu&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27545"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27545&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10552">
                <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="12192">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13898">
                <text>Remember the Hokies</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1780">
        <name>beamer</name>
      </tag>
      <tag tagId="478">
        <name>iraq</name>
      </tag>
      <tag tagId="187">
        <name>security</name>
      </tag>
      <tag tagId="605">
        <name>sports</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1692" 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="2833">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4724">
                <text>cls</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="6702">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8580">
                <text>Issue Date:Tuesday April 17, 2007   &#13;
Section: HeadLine News Section&#13;
&#13;
In response to the shootings at Virginia Tech, West Virginia University President David Hardesty said Monday afternoon in a statement that the "campus police are alert to the incident and are monitoring the situation as it unfolds. If deemed necessary, increased coverage by our campus police will be initiated."&#13;
&#13;
Students in need of counseling are encouraged to visit the Carruth Center in the Student Services Center next to the Mountainlair. The center, open between 9 a.m. and 5 p.m., offers walk-in counseling services and an after-hour emergency phone consultation service (293-4431). On Monday, the center extended its walk-in services to 8 p.m.&#13;
&#13;
A candlelight vigil to remember the victims of the shootings will be held Wednesday at 9 p.m. in Woodburn Circle on the Downtown Campus. The University community and the general public are invited to attend.&#13;
&#13;
The WVU United Methodist Student Movement will sponsor an interfaith vigil today at 9 p.m. in the Mountainlair Ballrooms.&#13;
&#13;
â€” cls&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27564"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27564&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10551">
                <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="12191">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13897">
                <text>WVU Reaction</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="215">
        <name>candlelight vigil</name>
      </tag>
      <tag tagId="1552">
        <name>counseling</name>
      </tag>
      <tag tagId="1955">
        <name>interfaith vigil</name>
      </tag>
      <tag tagId="399">
        <name>police</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1691" 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="2832">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4723">
                <text>Christian Alexandersen</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="6701">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8579">
                <text>Tuesday April 17, 2007   &#13;
Section: Editorial Section&#13;
Christian Alexandersen, Senior Staff Writer&#13;
&#13;
As I write this column, I, like most people in the world, am in disbelief of the terrible shootings that occurred on the Virginia Tech campus that claimed the lives of at least 33 people.&#13;
&#13;
First and foremost, I want to say that the thoughts and prayers of everyone at West Virginia University go out to everyone affected by the shootings at Virginia Tech. Words cannot begin to describe the pain and sorrow all college students are feeling on the worst day in our college careers.&#13;
&#13;
While this is now the worst public shooting ever to occur in the nation&amp;#39;s history, it is the responsibility of college students, faculty and staff everywhere to act responsibly following these tragic events.&#13;
&#13;
Directly after the shooting at Columbine High School in April 1999, schools all over the country began instituting extremely strict policies to deter future acts of violence in American schools. Growing up in the post-Columbine school system, students today remember the heightened security measures that were taken.&#13;
&#13;
Superintendents everywhere were no longer allowing students to carry backpacks around schools or go out for lunch.&#13;
&#13;
While it is impossible to know if those new precautions actually deterred anyone from shooting people in school, one of the most important lessons to take from both the Columbine and Virginia Tech shootings is that no matter the security precautions you take, nothing can stop a killer.&#13;
&#13;
It is crucial for WVU as well as all other colleges and universities around the country to act accordingly following the Virginia Tech massacre. However, higher learning institutions should not make unnecessary and costly security upgrades because of an isolated incident at Virginia Tech.&#13;
&#13;
During a press conference, Virginia Tech President Charles Steger said, "(We) can&amp;#39;t have an armed guard in front of every classroom." When asked if the campus had enough security to protect their students, Steger said, "It&amp;#39;s very difficult because we are an open society and an open campus."&#13;
&#13;
Other than the shooting that occurred at the University of Texas at Austin in 1966, there has not been an event that can compare to the one that occurred on Monday.&#13;
&#13;
Hopefully, school presidents will comprehend that placing metal detectors, instituting increased security or having people rummaging through our belongings is not the answer.&#13;
&#13;
Unfortunately, there are no remedies for tragic events like this.&#13;
&#13;
The only thing universities and colleges can do is take minor precautions to protect their students, faculty and staff. If Sept. 11 has taught us anything, it is that people who want to cause violence will find a way to do it. Wasting thousands or even millions of dollars on security upgrades is not going to solve anything.&#13;
&#13;
I am not saying, however, that precautions should not be taken at all; I am simply saying that adding SWAT teams to patrol campuses is unnecessary. ID scans and similar campus precautions are good ideas and should be considered by all institutions.&#13;
&#13;
Though the shootings at Virginia Tech are tragic and terrible, we have to remember to act sensibly and not rashly. Being prepared for situations like this is important, but we have to remember that this isolated incident is not an excuse to allow college presidents to overreact and start spending money on frivolous security measures.&#13;
&#13;
Once again, I want to say that the thoughts and prayers of every West Virginia University student, faculty and staff member are with the people at Virginia Tech.&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27552"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27552&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10550">
                <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="12190">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13896">
                <text>Shootings donâ€™t call for unreasonable security</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1033">
        <name>columbine</name>
      </tag>
      <tag tagId="1953">
        <name>increased security</name>
      </tag>
      <tag tagId="1954">
        <name>unreasonable security</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1680" 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="2822">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4713">
                <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="6691">
                <text>2008-02-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8569">
                <text>By&#13;
PUBLISHED APRIL 17, 2007&#13;
&#13;
On Monday morning, 32 students at Virginia Tech were killed and about 30 others injured by a shooting at the hands of a fellow student. This tragedy raises questions about the nature of events like this and what Columbia might do in a similar situation. Yet the administration was slow in publicly responding to the event, and when it did, it failed to address the crucial question about what the University&amp;#39;s response plan would be. The University should have expressed its sympathy, explained the counseling options available to students, and addressed safety concerns on Monday when the shootings occurred.&#13;
&#13;
The tragedy hit especially close to home on campus-first, because the victims were fellow students, and second, because many students here have friends and acquaintances at Virginia Tech. The University&amp;#39;s immediate response should have been to give some notification telling students where they could go for counseling if desired. Tonight a candlelight vigil will be held on Low Steps for the victims, and the Counseling and Psychological Services office will be open until 11 p.m. for students who need its services. This is a good step on the University&amp;#39;s part, but it should have made those resources available more quickly and opened CPS for extended hours.&#13;
&#13;
Questions have also been asked about how effective Virginia Tech officials were in securing the campus after the first round of shooting. Naturally, these questions raise concerns about Columbia&amp;#39;s own emergency management plan and the safety and security of its campus. University of Pennsylvania President Amy Gutmann and Dartmouth College President James Wright have released statements offering condolences to the Virginia Tech community and providing information about the security of their respective campuses, as well as publicizing the counseling services that they have available. University President Lee Bollinger should follow suit and send an e-mail to the entire University explaining the details of its response plan.&#13;
&#13;
Obviously, students do not need the University to hold their hands. But the University does have the responsibility to help them get through tragedies such as this and to encourage them to seek help if needed. Merely informing students more quickly of what counseling options were available would have been of significant help to students, as would have information about what the University would do if a similar crisis occurred here. Tonight at the candle light vigil, Columbia students will come together in solidarity. The University must do the same, providing students help and support.&#13;
&#13;
--&#13;
&#13;
Originial Source: Columbia Spectator&#13;
&lt;a href="http://www.columbiaspectator.com/node/24900"&gt;http://www.columbiaspectator.com/node/24900&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10540">
                <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="12181">
                <text>Tom Faure (tomfaure@gmail.com)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13886">
                <text>STAFF EDITORIAL: Providing Comfort</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1922">
        <name>columbia</name>
      </tag>
      <tag tagId="1552">
        <name>counseling</name>
      </tag>
      <tag tagId="1924">
        <name>emergency management plan</name>
      </tag>
      <tag tagId="1923">
        <name>univeristy response</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1681" 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="2823">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4714">
                <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="6692">
                <text>2008-02-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8570">
                <text>PUBLISHED APRIL 17, 2007&#13;
&#13;
Beginning today and lasting at least through the end of the semester, students will no longer work as card-swipers at the front desks of on-campus residences and Lerner Hall.&#13;
&#13;
The change, announced yesterday, came in response to Monday&amp;#39;s shootings at Virginia Tech University and is aimed at increasing security. According to Rosemary Keane, assistant vice president for communications in the Division of Student Services, students currently working at those desks will be reassigned and will not become unemployed. Columbia University public safety officers will take their card-swiping jobs.&#13;
&#13;
"In response to Virginia Tech, our goal was to make sure that we have uniformed officers in each residence hall and in Lerner for the rest of the semester for added security precautions," Lisa Hogarty, executive vice president for Student and Administrative Services, said last night.&#13;
&#13;
One student, who was working at the front desk of Lerner Hall last night and declined to be named for fear of losing her job, said that she felt the move would have little impact on security. "I don&amp;#39;t like the idea of turnstiles, anyways," she said, noting that two of the three turnstiles were broken and that anybody can walk through without swiping. "If people really want to get into the building, they&amp;#39;ll find a way."&#13;
&#13;
In an e-mail sent to Columbia students last night, Hogarty announced that there will be a candlelight vigil at the sundial tonight at 9 p.m. in remembrance of the 33 students who died during the shooting. University Chaplain Jewelnel Davis is scheduled to speak. The University has also extended today&amp;#39;s office hours for Counseling and Psychological Services until 11 p.m. today.&#13;
&#13;
"The entire Columbia University community mourns the loss of these individuals and we send our prayers and condolences to their friends and families and to all the students, staff and faculty at Virginia Tech," Hogarty wrote in the e-mail.&#13;
&#13;
--&#13;
&#13;
Original Source: Columbia Spectator&#13;
&lt;a href="http://www.columbiaspectator.com/node/24884"&gt;http://www.columbiaspectator.com/node/24884&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10541">
                <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="12182">
                <text>Tom Faure (tomfaure@gmail.com)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13887">
                <text>Public Safety Takes Over as Card-Swipers</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="721">
        <name>campus safety</name>
      </tag>
      <tag tagId="1922">
        <name>columbia</name>
      </tag>
      <tag tagId="1926">
        <name>dorms</name>
      </tag>
      <tag tagId="1925">
        <name>on-campus residences</name>
      </tag>
      <tag tagId="1927">
        <name>public safety officers</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1682" 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="2824">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4715">
                <text>Evan Cohen</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="6693">
                <text>2008-02-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8571">
                <text>By Evan Cohen&#13;
PUBLISHED APRIL 26, 2007&#13;
&#13;
Eleven years ago, I played in a band that rehearsed in a basement downtown. On one side of the basement was an illegal two-bedroom apartment that the landlord slapped together with drywall. My friend Matt lived there with a roommate. I didn&amp;#39;t know anything about the roommate other than that he was black.&#13;
&#13;
One afternoon, my bandmate, George, and I went down to rehearsal early and checked in on Matt. We were in his room talking about the then non-hit TV show, Homeboys in Outer Space. George was saying that it was a low rent rip-off of the Britcom, Red Dwarf. I chimed in with "It&amp;#39;s more like Red Nigger!"&#13;
&#13;
Matt hissed at me, "My roommate&amp;#39;s home, stupid!"&#13;
&#13;
Oh shit. I was going to die.&#13;
&#13;
I never felt so low in all my life. I began to shake, and clenched my suddenly churning bowels to keep them from releasing. "Oh my god, he&amp;#39;s gonna kill me!"&#13;
&#13;
"Relax," George said.&#13;
&#13;
We heard our drummer Michael walking down the basement steps. Matt opened the door and I walked out as quickly as possible. I didn&amp;#39;t see the roommate. Thank god. Hopefully he didn&amp;#39;t hear anything.&#13;
&#13;
We played for two hours and I almost forgot the sickening feeling in my gut. As we were packing up our equipment, George said, "You have to apologize."&#13;
&#13;
"What?"&#13;
&#13;
"You have to apologize to Matt&amp;#39;s roommate."&#13;
&#13;
"But maybe he didn&amp;#39;t even hear me say it!" I pleaded. "Like, what if he didn&amp;#39;t hear anything and then it makes it look ten times worse!"&#13;
&#13;
"You have to apologize."&#13;
&#13;
Oh shit.&#13;
&#13;
I slowly walked across the basement to the apartment, wondering if I&amp;#39;d soon have any teeth left. I knocked on the door, hoping that he was gone. The roommate opened up the door. "Yes?"&#13;
&#13;
"Hi. I just... well... I want to apologize for something I said earlier in Matt&amp;#39;s room, and I just want to let you know that I&amp;#39;m sorry if you may have been offended."&#13;
&#13;
"Okay," he said, and shut the door. I then ran upstairs and out of the building.&#13;
&#13;
Matt didn&amp;#39;t talk to me for a long time after that. He would eventually tell me that relations with his roommate from then on were pretty awkward. We continued to rehearse there, but I never saw the roommate again. So what did I learn?&#13;
&#13;
When I think about this incident, I still feel uncomfortable. Had Matt&amp;#39;s roommate not been home, or even existed, it wouldn&amp;#39;t have been an issue. It would have been just another comment. The difference was that I got caught, and all things considered, I got off pretty easy. I think that, worst of all, what I said wasn&amp;#39;t even funny.&#13;
&#13;
If you think I&amp;#39;m going to say that I learned my lesson and don&amp;#39;t use language like that anymore, you&amp;#39;re wrong. I still use "inappropriate" language, so much so that when the same word was symbolically banned by the NYC city council, I got half a dozen e-mails from friends saying, "So what are you going to do now?"&#13;
&#13;
But I know when to say certain things and when not to (when I don&amp;#39;t forget, of course). I know context. I don&amp;#39;t speak the same way to my professors as I do to my friends, but I don&amp;#39;t believe that certain words should "belong" to certain groups and not others. Language and humor shouldn&amp;#39;t have limits. What&amp;#39;s key here is the intent behind the words, and more so, behind actions.&#13;
&#13;
Words were big news recently. For two weeks, pundits brimming with self-righteous indignation discussed whether Don Imus was within his bounds to refer to the Rutgers women&amp;#39;s basketball team as "nappy-headed hos." His defenders said that he was paid to be inappropriate and was just earning his paycheck, but he was ultimately fired.&#13;
&#13;
On the afternoon of Monday, April 16, while the cable news channels were reporting the increasingly unbelievable details of the Virginia Tech massacre, Oprah was airing the first of a two-part town hall show all about Don Imus and the pain words can cause. I tuned in for about two minutes and it all seemed so silly. What caused more harm, three words on a radio show, or a mentally disturbed college student armed with two legally purchased firearms?&#13;
&#13;
Before the shootings in Blacksburg occurred, Matee Ajavon of the Rutgers team said, "This has scarred me for life." I think there are 33 families who would take issue with that statement, not to mention the survivors who will suffer physical and psychological trauma for years to come.&#13;
&#13;
We&amp;#39;re quick to jump on people who say the "wrong" thing, whether it&amp;#39;s Michael Richards&amp;#39; meltdown in a comedy club, or Joe Biden referring to Barack Obama as "clean." But does calling them out solve the problem? There are local politicians and police officials all over this country who would never use those words in public but who harbor true hatred. I&amp;#39;d be more worried about their abuses of power than what I heard on the radio.&#13;
&#13;
So the next time you hear something that rubs you the wrong way, stop and think. Who&amp;#39;s saying it, and what&amp;#39;s the context? What was the real intent? Who is it really hurting, and what how does that hurt fit into the greater scheme of things? Words are just that, words. Actions cause real damage, but actions can also heal. Choose your action.&#13;
&#13;
--&#13;
&#13;
Original Source: Columbia Spectator&#13;
&lt;a href="http://www.columbiaspectator.com/node/25087"&gt;http://www.columbiaspectator.com/node/25087&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10542">
                <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="12183">
                <text>Tom Faure (tomfaure@gmail.com)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13888">
                <text>Sticks and Stones and Rhetoric</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1930">
        <name>actions</name>
      </tag>
      <tag tagId="1922">
        <name>columbia</name>
      </tag>
      <tag tagId="1491">
        <name>opinion</name>
      </tag>
      <tag tagId="1928">
        <name>rhetoric</name>
      </tag>
      <tag tagId="1929">
        <name>words</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
