<?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=63&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-13T02:51:20+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>63</pageNumber>
      <perPage>20</perPage>
      <totalResults>1884</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1117" 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="2417">
                <text>Sara  Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4308">
                <text>Joe Bialek</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="6286">
                <text>2007-08-16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8164">
                <text>By: Joe Bialek&#13;
Posted: 5/2/07&#13;
&#13;
The shooting crisis at Virginia Tech has once again sparked the debate about gun control. The second amendment of the United States Constitution states: "A well regulated militia, being necessary to the security of a free State, the right of the people to keep and bear Arms, shall not be infringed." Obviously the need for a state militia has been replaced by the National Guard and Coast Guard whereby trained military personnel are entrusted with the defense of this country against domestic enemies. Their weapons are tightly controlled and safeguarded.&#13;
&#13;
The only two reasons for a citizen to own a firearm are for hunting or defense of the household from intruders. In either case, ownership of a handgun, shotgun or shoulder rifle is more than adequate to satisfy these purposes. There is absolutely no need for any U.S. civilian to own any weapon more powerful or sophisticated than these. Accordingly, all handguns, shotguns and shoulder rifles must be licensed and registered to the degree necessary to match weapon to owner at the click of a computer key. Furthermore, if we had prohibited the purchase of more sophisticated weapons, several innocent victims would not have died at the hands of Cho Seung-Hui.&#13;
&#13;
Joe Bialek&#13;
Cleveland, Ohio &#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.thelantern.com/media/storage/paper333/news/2007/05/02/Letters/Shooting.Proves.Need.For.Gun.Control.Laws-2891670.shtml&gt;The Lantern - May 2, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10135">
                <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="11997">
                <text>GERRICK LEWIS &lt;lewis.1030@osu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13535">
                <text>Shooting proves need for gun control laws</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="721">
        <name>campus safety</name>
      </tag>
      <tag tagId="87">
        <name>gun control</name>
      </tag>
      <tag tagId="1516">
        <name>ohio state university</name>
      </tag>
      <tag tagId="1514">
        <name>public safety</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="966" 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="2268">
                <text>Sara  Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4159">
                <text>Karyn Meshbane</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="6137">
                <text>2007-08-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8015">
                <text>Is UM prepared for a similar emergency?&#13;
By: Karyn Meshbane // Assistant News Editor&#13;
Posted: 4/20/07&#13;
Monday morning&amp;#39;s shooting rampage at Virginia Tech, the deadliest such incident in American history, has forced colleges and universities around the country, including the University of Miami, to reevaluate on-campus security.&#13;
&#13;
Once news broke of Monday&amp;#39;s events, UM&amp;#39;s Police Department and administrators reacted within hours. President Donna E. Shalala sent out a statement on Monday afternoon to all students concerning the Virginia Tech tragedy and spoke of a crisis plan, while David A. Rivero, director of public safety, increased police presence in order to avert a possible copycat incident.&#13;
&#13;
"We immediately communicated with everybody that&amp;#39;s on our emergency response plan so that everybody knew what was happening," Rivero said. "We increased our force by doubling the amount of cops, and we hired extra security guards to give students, faculty and UM employees an extra sense of safety."&#13;
&#13;
Rivero traveled to Tallahassee on Monday for a meeting with all police chiefs from the ACC schools to discuss security concerns and plans at the other universities.&#13;
&#13;
Officers from the Coral Gables Police Department have also been hired to patrol campus.&#13;
&#13;
Security Response&#13;
&#13;
Three weeks ago, Rivero met with SG President Danny Carvajal and decided to create the University of Miami Police Advisory Board. Rivero said the advisory board would revolve around student participation to offer an alternate perspectives on possible security vulnerabilities.&#13;
&#13;
Carvajal appointed Matthew Shpiner, vice president of operations for the &amp;#39;Canes Emergency Response (a organization comprised of students who assist the university in times of disaster preparation and recovery), as the chair of the University of Miami Police Advisory Board.&#13;
&#13;
Shpiner plans to have an official meeting this week to discuss the board&amp;#39;s goals and plan a response to the Virginia Tech shootings.&#13;
&#13;
Alan Fish, the vice president of Business Services, said the university is adequately prepared for a similar emergency on campus, based on the Emergency Preparedness Plan.&#13;
&#13;
"We&amp;#39;ve had a crisis management plan since the late &amp;#39;80s, which is constantly evolving every year as issues like [Virginia Tech] come up or technology changes," he said.&#13;
&#13;
Fish also told The Miami Hurricane the crisis plan includes a small emergency response team that includes a few "key" administrators, such as Shalala and Provost Thomas LeBlanc, who can meet on a moments notice. After the emergency response team meets, decisions are relayed to the crisis decision team, which includes approximately 100 people who carry out the smaller team&amp;#39;s desired plan.&#13;
&#13;
The larger crisis decision team is made up of representatives from 57 major areas of the university, such as the various colleges,, medical campus, Department of Public Safety, the Department of Residence Halls and Auxiliary Services.&#13;
&#13;
The decision team last met during hurricane season to decide a course of action, which included sending an e-mail notification to students that classes were cancelled as a result of Hurricane Ernesto. Fish said a similar e-mail notification system would be used to warn students in the case of other types of threats.&#13;
&#13;
Patricia A. Whitely, vice president for Student Affairs, and Gilbert Arias, assistant vice president for Student Affairs, said they encourage all students to update their cell phone numbers at myum.miami.edu so the university is able to send out voicemails and text messages to all students in the case of a crisis.&#13;
&#13;
Currently only 4,600 of roughly 15,670 students have updated their cell phone numbers.&#13;
&#13;
In 1996, Hurricane linebacker Marlin Barnes was beaten to death in his on-campus apartment. Whitely, who was the director of Student Life at the time, said UM increased security immediately after that incident and followed the crisis plan UM had at the time. She noted the emergency plan UM uses now has been drastically updated since then, but whether a crisis is large or small, the decision team follows the same guidelines.&#13;
&#13;
Shalala also noted in her statement that the Rosentiel and medical campuses also have emergency response procedures.&#13;
&#13;
Annie Reisewitz of Media Relations said RSMAS has security during operating hours and no unauthorized persons are allowed on campus. Whitely also noted that both the RSMAS and medical campuses have a comprehensive plan that follows the Disaster Preparation and Recovery Plan on UM&amp;#39;s website.&#13;
&#13;
Comparative Perspective&#13;
&#13;
Because most college campuses in the United States are sprawling by design with large open areas and free access to buildings that house classrooms, the use of unconventional security devices has been utilized by universities such as John Hopkins and Princeton.&#13;
&#13;
Johns Hopkins uses a "smart" video camera technology that employs computer algorithms to detect suspicious actions such as a person climbing a fence or loitering around a window. The university currently has 101 "smart" cameras installed on the main campus.&#13;
&#13;
At Princeton, professors and university officials are trained to spot depression and are told to contact mental health services when a student may need help. Also, after Columbine, many U.S. high schools installed metal detectors, though colleges and universities did not follow suit.&#13;
&#13;
Fish said UM is not planning to add security measures such as metal detectors or "smart" cameras, but he noted the university&amp;#39;s crisis team does convene annually to have an "awareness meeting" to discuss issues that may impact the crisis plan.&#13;
&#13;
Furthermore, Arias emphasized that during times of crisis the Department of Public Safety, located in the Flipse Building, is staffed around-the-clock by members of the Division of Student Affairs and the Office of Communications, who may be reached via the Hurricane Hotline at 305-284-5151.&#13;
&#13;
"We constantly update the hotline and the website," Arias said. He added that in times of crisis, such as hurricanes, "We even sleep at [the Department of] Public Safety to be available for students and parents in case they have any questions."&#13;
&#13;
More information about UM&amp;#39;s emergency preparedness may be found at www.miami.edu/prepare.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.thehurricaneonline.com/media/storage/paper479/news/2007/04/20/News/Shooting.Raises.Questions.Of.Safety-2871056.shtml&gt; The Miami Hurricane- April 20, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9986">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="11143">
                <text>The Miami Hurricane</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11897">
                <text>Greg Linch &lt;greglinch@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13390">
                <text>Shooting raises questions of safety</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="721">
        <name>campus safety</name>
      </tag>
      <tag tagId="1107">
        <name>miami university</name>
      </tag>
      <tag tagId="187">
        <name>security</name>
      </tag>
      <tag tagId="1100">
        <name>university of miami</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="733" 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="2053">
                <text>Sara  Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3944">
                <text>Blair Socci  </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="5922">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7800">
                <text>By Blair Socci&#13;
Thursday, April 19, 2007&#13;
&#13;
In the aftermath of the shootings that occurred at Virginia Tech earlier this week, the University of California is now re-evaluating its own security policies.&#13;
&#13;
Authorities have been quick to assure the UCLA community that they are doing everything they can to assess current security measures, as well as to actively continue to seek out ways to improve safety.&#13;
&#13;
"What happened at Virginia Tech is a reminder that nobody is immune from violence and that we all need to remain vigilant in order to protect ourselves and our institution," UCLA spokesman Phil Hampton said.&#13;
&#13;
"In light of what has happened at Virginia Tech, this campus, as well as other UC campuses, will be solidifying (its) security policies."&#13;
&#13;
In the coming days and weeks, the university plans to review its policies and continue to examine new information that becomes available, UC President Robert Dynes said in a statement Monday.&#13;
&#13;
"As we learn more about the specific circumstances of the Virginia Tech shootings, we will apply those lessons as well," he said in the statement.&#13;
&#13;
At UCLA, authorities are currently devising new ways to improve mediums of response to emergencies and communication with the community, as well as providing care for people following any major incident.&#13;
&#13;
Some new methods being reviewed include notifying students personally on cell phones either by sending text messages or making phone calls, Hampton said.&#13;
&#13;
Another area that is being reviewed is the university&amp;#39;s psychological services.&#13;
&#13;
"We are also giving increased attention to student psychological support services and have begun phasing additional funding for these programs," Dynes said in his statement.&#13;
&#13;
But UCLA officials emphasized that the university already has various ways of dealing with an emergency.&#13;
&#13;
"The university has in place measures to guide us in case of an emergency," Hampton said.&#13;
&#13;
He said UCLA has regular training sessions in which they practice how to respond to and communicate during an emergency, as well as electronic means of notifying the community.&#13;
&#13;
"We have emergency mass e-mail, Web sites such as Gateway and MyUCLA that we can update, recorded telephone information and the campus radio station, which has recently been changed to 24-hour availability," Hampton said.&#13;
&#13;
University police also currently received training on how to respond to an emergency, said Nancy Greenstein, director of police community services for UCPD.&#13;
&#13;
"Our officers are highly trained individuals," she said.&#13;
&#13;
This training includes drills, special emergency-response shooter training and regular briefings educating officers on new security policies and discussion of current security methods.&#13;
&#13;
UCPD also uses a system called "active shooter training," which Greenstein said is based on real-life situations such as the shooting at Virginia Tech.&#13;
&#13;
"We want to be able to determine the cause and have an immediate response," she said.&#13;
&#13;
Greenstein said the state mandates law enforcement be involved in training every week and diligently prepare for all types of emergencies.&#13;
&#13;
She added that UCPD is hoping to learn from the Virginia Tech shooting, noting that as it is only a few days after the fact, changes will likely be made in the upcoming weeks when more information is available.&#13;
&#13;
A vigil co-sponsored by the Undergraduate Students Association Council Office of the President and the Office of Residential Life is planned for 8 p.m. in De Neve Plaza to give students an opportunity to express their condolences for the victims and their families, said Jesse Rogel, chief of staff at the USAC Office of the President.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.dailybruin.ucla.edu/news/2007/apr/19/shootings_spur_uc_assess_security_policies/&gt;The Daily Bruin - April 29, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9771">
                <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="11751">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13194">
                <text>Shootings spur UC to assess security policies</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="851">
        <name>security policies</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="508" 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="1840">
                <text>Sara  Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3731">
                <text>Jackie Bernstein</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="5709">
                <text>2007-06-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7587">
                <text>April 20, 2007&#13;
Opinion article&#13;
By Jackie Bernstein&#13;
&#13;
&#13;
It&amp;#39;s time for a game of Funny/Not Funny. First: A joke overheard in the CoHo on Monday referencing the Virginia Tech massacre. Not Funny. No one laughed, and someone said, "Too soon, too soon." Next: An off-hand comment made at the gym on Wednesday, poking fun at the ethnicity of the Korean shooter responsible for the assault, Cho Seung-Hui. Funny? At least, I heard people laugh in response. "Oh, man... that&amp;#39;s so wrong. Hahahahaha."&#13;
&#13;
How soon is too soon to use a tragedy as fodder for comedy? "Homer loves Flanders," a Simpsons episode in season five, parodies Charles Whitman, the University of Texas tower-sniper: Ned Flanders guns down multiple Homers from atop a bell tower. About 25 years after the massacre, FOX executives found the scene funny enough to air. How long will it take for South Park to run an episode satirizing the events at Virginia Tech?&#13;
&#13;
I think that the amount of time it takes for someone to find humor in tragedy is directly related to his connection to the incident. It is unlikely that the man who sold Sueng-Hui his gun will ever find anything humorous about the shooting. The student in the CoHo who made his joke last Monday probably doesn&amp;#39;t know anyone at Virginia Tech. I doubt that he feels any kind of personal connection to the event.&#13;
&#13;
However, we as Stanford students are actually deeply connected to the Virginia Tech massacre. Seung-Hui exploded at Virginia Tech. Maurice "Mo" Morsette imploded at Stanford. Both students&amp;#39; lives ended in tragedy.&#13;
&#13;
Maurice Moisette&amp;#39;s suicide is one of at least three reported at Stanford this academic year. Ranked in 2005 by The Princeton Review as the university with the "Happiest Students Overall" in the country, Stanford doesn&amp;#39;t seem to be living up to its reputation any longer.&#13;
&#13;
The Virginia Tech tragedy will undoubtedly lead the Stanford administration and various support groups on campus to reexamine how issues of mental health are handled on campus. This response seems to deal with only part of a greater problem.&#13;
&#13;
No matter how many aggressive programs a school funds, no matter how many 24-hour hotlines they provide or psychologists they hire, nothing can change without a change in the student culture itself.&#13;
&#13;
Unfortunately, the type of student elite universities admit is not going to change anytime soon. We are a nation obsessed with getting into college. And the most obsessed end up here. As a result, we are a campus full of top-heavy people. We are world-class debaters, writers and chemists, fully actualizing our intellectual potential. But these skills have come at the loss of developing more basic skills. By the end of winter quarter of my freshman year, 40 percent of my all-frosh dorm had never been kissed. Throwing these types of kids into the collegiate world is bound to result in extreme feelings of alienation, confusion and anger. College is a place where many get their first taste of freedom, but learning how to handle independence isn&amp;#39;t part of any AP Physics textbook.&#13;
&#13;
I know that this article goes to print during Admit Weekend, and, as such, I was reluctant to write this week about our collective failings as members of the academic world. As a tour guide who couldn&amp;#39;t imagine having gone anywhere else (and who enthusiastically tells this to hoards of high school juniors on a regular basis), I want to make sure that I am very clear: I have had a remarkable experience at Stanford, and I know that I made the right choice in coming here. Quite a few of my friends feel the same way. The problems of socially handicapped hyper-achievers are not unique to a few schools. Rather, this situation is endemic across the country.&#13;
&#13;
I decided to write this article after I watched a mother and her ProFro daughter walk through the activities fair yesterday. The daughter was texting on her cell phone, and her mom kept on taking papers from the student tables, asking the students working the booths a slew of questions: "How many hours a week do you volunteer? How many other activities do you do? Do you put your activities on your resume? How many activities should my daughter do?" The mother was so involved in her daughter&amp;#39;s life that I wondered if she had opened her daughter&amp;#39;s acceptance letter for her.&#13;
&#13;
My hope is that the mother I overheard reads this week&amp;#39;s column. I hope that she realizes that her daughter is probably exhausted from pushing herself through four incredibly difficult years and almost certainly will need guidance on how to be a well-adjusted citizen, not how to build a resume, as she enters adulthood. My hope is that ProFros read this column and realize that coming to college is not going to be easy, wherever they choose to go. Part of growing up is facing failure and difficulty, and there is no shame in asking for help, even if it seems as though everyone else is doing fine. They aren&amp;#39;t.&#13;
&#13;
Our complete inability to cope with the pressures of today may eventually be funny. But for now, it&amp;#39;s definitely too soon to turn the tragedy of our extreme emphasis on academic intelligence and achievement into a quick one-liner glibly delivered at the Manzanita brunch table.&#13;
&#13;
Jackie Bernstein can be reached at jaber@stanford.edu.&#13;
&#13;
--&#13;
&#13;
&lt;a href="http://daily.stanford.edu/article/2007/4/20/sickSadWorldALessonFromVirginiaTech"&gt; Stanford Daily - April 20, 2007 &lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9558">
                <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="11549">
                <text>Permissions granted by&#13;
James Hohmann&#13;
Editor-in-Chief&#13;
The Stanford Daily&#13;
&lt;jhohmann@stanford.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13002">
                <text>Sick Sad World: A lesson from Virginia Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="602">
        <name>humor</name>
      </tag>
      <tag tagId="591">
        <name>stanford</name>
      </tag>
      <tag tagId="603">
        <name>suicide</name>
      </tag>
      <tag tagId="17">
        <name>tragedy</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="667" public="1" featured="0">
    <fileContainer>
      <file fileId="399">
        <src>https://www.april16.vtlibraries.net/files/original/Cox_46b5ac43d6.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="14789">
                    <text>2007-07-06</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="15909">
                    <text>2007-07-06 17:35:11</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="1992">
                <text>Chad Newswander</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3883">
                <text>Kelly Harris</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5861">
                <text>2007-07-06</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7739">
                <text>Cox Driving Range on Prices Fork expresses its support for Virginia Tech. &#13;
&#13;
Orginial Source &lt;a href=" http://www.flickr.com/photos/kellybeth7/467693906/in/set-72157600091083431/"&gt; http://www.flickr.com/photos/kellybeth7/467693906/in/set-72157600091083431/&lt;/a&gt;&#13;
&#13;
Photo courtesy of Kelly Harris&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9710">
                <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="11693">
                <text>Permission:&#13;
Kelly Harris &#13;
kellybeth7@gmail.com</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13137">
                <text>Sign at Cox&amp;#39;s Golf Driving Range</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="795">
        <name>retail</name>
      </tag>
      <tag tagId="794">
        <name>stores</name>
      </tag>
      <tag tagId="3">
        <name>support</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="582" 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="1911">
                <text>Sara  Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3802">
                <text>Michael Juel-Larsen</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="5780">
                <text>2007-06-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7658">
                <text>By Michael Juel-Larsen&#13;
Princetonian Senior Writer&#13;
&#13;
    Though Monday&amp;#39;s shootings at Virginia Tech had already cast a shadow over campus, the news yesterday morning that the gunman&amp;#39;s older sister is a recent Princeton alumna brought the tragedy even closer to home.&#13;
&#13;
    Sun-Kyung Cho &amp;#39;04 was an economics major who interned at the U.S. Embassy in Bangkok during the summer before her senior year and wrote briefly for The Daily Princetonian. She now works as a "State Department contractor," The Washington Post reported yesterday, and was listed on Princeton&amp;#39;s alumni directory as living in Centreville, Va., with her parents.&#13;
&#13;
    The shooter was identified early yesterday morning as 23-year-old Virginia Tech senior Cho Seung-Hui. Later in the morning, the Chicago Tribune&amp;#39;s "The Swamp" blog reported that Cho had a sister who graduated from the University.&#13;
&#13;
    Sun-Kyung Cho&amp;#39;s and Cho Seung-Hui&amp;#39;s home addresses in Centreville, Va., are identical. Reached on her cell phone yesterday afternoon,  Sun-Kyung declined to be interviewed for this article.&#13;
&#13;
    At Princeton, Cho wrote her senior thesis on "ethnic enclave[s] and wage earning" among Korean immigrants in California. Her thesis adviser, economics professor Orley Ashenfelter, could not be reached for comment yesterday.&#13;
&#13;
    In the past two days, intense national media scrutiny has been focused on the Cho family as the public struggles to understand the shootings.&#13;
&#13;
    University spokeswoman Cass Cliatt &amp;#39;96 said the Office of Communications had received inquiries from at least seven media organizations yesterday about whether the shooter&amp;#39;s sister had gone to Princeton, including ABC, CNN, the Newark Star-Ledger and The Washington Post.&#13;
&#13;
    Cliatt said she could not disclose any information on Sun-Kyung Cho besides the fact that she had been a student, what she studied and when she graduated.&#13;
&#13;
    Cliatt added that she also received a call from an alumna who was unrelated to the shooter and whose last name was also Cho. "She was concerned that she was receiving a lot of calls" from reporters regarding the shootings, Cliatt said.&#13;
&#13;
    Marc Fisher &amp;#39;80, a columnist with The Washington Post who was at the Chos&amp;#39; Centreville townhouse yesterday along with dozens of other journalists, described the situation as a "puzzle with virtually blank pieces."&#13;
&#13;
    Close media scrutiny of the family&amp;#39;s life was motivated, he said, by a "very human need to know and understand."&#13;
&#13;
    "Partly out of courtesy and partly out of the urge that people have to just find meaning, there&amp;#39;s a rush to delve into the shooter&amp;#39;s life," he said, "and usually we come up fairly empty in that pursuit, and the competitive juices get flowing, so you end up with a lot of scenes that are almost comical, such as having 50 reporters standing outside an empty townhouse."&#13;
&#13;
    The Chos had been escorted from their home before Fisher got to Centreville and have not spoken to the press.&#13;
&#13;
    Fisher said the media&amp;#39;s close attention to the Cho family would likely continue for at least another week. "I think we&amp;#39;re just at the very beginning of that process of trying to figure out who he was and the family story and how they got here and how he got to such an extreme point," he said.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.dailyprincetonian.com/archives/2007/04/18/news/18129.shtml"&gt; Daily Princetonian - April 18, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9629">
                <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="11614">
                <text>Kavita Saini &lt;ksaini@Princeton.EDU&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13073">
                <text>Sister of Virginia gunman belongs to Class of 2004</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="713">
        <name>backlash</name>
      </tag>
      <tag tagId="719">
        <name>cho family response</name>
      </tag>
      <tag tagId="711">
        <name>princeton</name>
      </tag>
      <tag tagId="714">
        <name>sunkyung cho</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1018" public="1" featured="0">
    <fileContainer>
      <file fileId="517">
        <src>https://www.april16.vtlibraries.net/files/original/DSC00137_7c9029b7db.JPG</src>
        <authentication>null</authentication>
        <elementSetContainer>
          <elementSet elementSetId="1">
            <name>Dublin Core</name>
            <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
            <elementContainer>
              <element elementId="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14902">
                    <text>2007-08-13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16022">
                    <text>2007-08-13 19:22:02</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2320">
                <text>Na Mi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4211">
                <text>Jinfeng Jiao</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6189">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8067">
                <text>One week after the shooting,people set six flags on the lawn of the drillfield to mourn the victims.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10038">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13439">
                <text>Six flags of VT in drillfield</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1414">
        <name> flags</name>
      </tag>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="1109">
        <name>shooting</name>
      </tag>
      <tag tagId="1088">
        <name>victims</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="314" public="1" featured="0">
    <fileContainer>
      <file fileId="214">
        <src>https://www.april16.vtlibraries.net/files/original/Second Life II_b0fd932398.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="14611">
                    <text>2007-05-30</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="15731">
                    <text>2007-05-30 12:16:14</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1664">
                <text>Chad Newswander</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3555">
                <text>Janet Powell </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="5533">
                <text>2007-05-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7411">
                <text>Tonight (4/16) at 8pm SLT, turn the grid dark, midnight in rememberance of those lost in the Virginia Tech mass murder. There will be a candelight vigil in the Kula Coloseum from 8pm until midnight. Monument by Perefim Coa. &#13;
&#13;
Original source: &lt;a href=" http://www.flickr.com/photos/janet_powell/462239359/"&gt; http://www.flickr.com/photos/janet_powell/462239359/&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href=" http://creativecommons.org/licenses/by-nc/2.0/"&gt;Creative Commons Attribution-NonCommerical 2.0&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9382">
                <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="11383">
                <text>Permission:&#13;
Janet Powell&#13;
http://www.flickr.com/photos/janet_powell/462239359&#13;
Creative Commons Attribution-NonCommerical 2.0&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12852">
                <text>SL Memorial for Virginia Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="92">
        <name>internet</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="91">
        <name>second life</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="54" public="1" featured="0">
    <fileContainer>
      <file fileId="37">
        <src>https://www.april16.vtlibraries.net/files/original/SL-VT-Memorial_dc97839f48.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="14461">
                    <text>2007-04-30</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="15581">
                    <text>2007-04-30 10:21:33</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="1426">
                <text>Ã…sa Rosenberg</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3317">
                <text>Ã…sa Rosenberg</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="5295">
                <text>2007-04-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7176">
                <text>At about 15 PM SLT/PST 16 April 2007 a group of Second Life residents started working on a memorial space for the VT-tragedy. People from all over the world helped out. This shapshot shows the InfoIsland memorial at 18 PM PST 16 April 2007 and the same place three days later, 19 April 2007 17 PM PST when hundreds of visitors had come by to leave flowers and pay their final respects.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9144">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12647">
                <text>SL VT Memorial</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="92">
        <name>internet</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="91">
        <name>second life</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1055" public="1" featured="0">
    <fileContainer>
      <file fileId="528">
        <src>https://www.april16.vtlibraries.net/files/original/100_1454_8076e89c68.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="14913">
                    <text>2007-08-14</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16033">
                    <text>2007-08-14 09:11:42</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="2356">
                <text>Kathryn Kuhn</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4247">
                <text>Kathryn Kuhn</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="6225">
                <text>2007-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8103">
                <text>Students at Saint Louis University sent nearly a dozen message board to Tech in the weeks following the tragedy. SLU also hosted a memorial mass in honor of the Tech students and professors who died.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10074">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13475">
                <text>SLU supports Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="429">
        <name>message boards</name>
      </tag>
      <tag tagId="1492">
        <name>saint louis university</name>
      </tag>
      <tag tagId="1495">
        <name>slu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2276" public="1" featured="0">
    <fileContainer>
      <file fileId="1110">
        <src>https://www.april16.vtlibraries.net/files/original/2419491591_9e9accc000_b_c1b5667ce9.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="15462">
                    <text>2008-05-03</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="16582">
                    <text>2008-05-03 14:15:17</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3161">
                <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="5052">
                <text>Kevin Cupp</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="7030">
                <text>2008-05-03</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8908">
                <text>Taking pictures on A Day of Remembrance, 4/16/08, photographers stand above the memorial site on the drillfield.&#13;
&#13;
Photo by Kevin Cupp.&#13;
&#13;
--&#13;
&#13;
Original Source:&#13;
&lt;a href="http://www.flickr.com/photos/kevincupp/2419491591/"&gt;http://www.flickr.com/photos/kevincupp/2419491591/&lt;/a&gt; </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10879">
                <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="12483">
                <text>Kevin Cupp &lt;k@vt.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14223">
                <text>Smile</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1989">
        <name>anniversary</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="2213">
        <name>photographers</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2314" public="1" featured="0">
    <fileContainer>
      <file fileId="1138">
        <src>https://www.april16.vtlibraries.net/files/original/100_0345_83c69cec71.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="15490">
                    <text>2008-05-09</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16610">
                    <text>2008-05-09 13:03:07</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="3189">
                <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="5080">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7058">
                <text>2008-05-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8936">
                <text>One of the items on display at the Alumni Center Art Exhibit. On 4/16/08, as part of the Day of Remembrance observance, the Holtzman Alumni Center Museum displayed examples of art, crafts, quilts, and other memorabilia contributed since April 16, 2007. This is one of over 60,000 items that will eventually go to Special Collections at Newman Library.&#13;
&#13;
A drawing of the victims.  Accompanying this drawing was a letter dated June 28, 2007 and addressed to President Charles Steger in which the artist, Samuel X Holloway #201510, explains that he hopes the drawing can serve as a "tool in creating inspirational projects and raising money".  Holloway gave all copy rights for the artwork to Virginia Tech.  He was inspired to create the piece after seeing the victims&amp;#39; photos in The Richmond Times newspaper.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10907">
                <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="12510">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14251">
                <text>Smiling Faces</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1651">
        <name>alumni center</name>
      </tag>
      <tag tagId="1989">
        <name>anniversary</name>
      </tag>
      <tag tagId="2226">
        <name>exhibit</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1220" 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="2503">
                <text>Sara AA Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4394">
                <text>Mark Norris</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="6372">
                <text>2007-08-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8250">
                <text>By: Mark Norris, Editor In Chief, mnorris@smu.edu&#13;
Posted: 4/17/07&#13;
SMU officials say they are prepared if an incident like the one at Virginia Tech happens here. As recently as December 2006 an active shooter scenario exercise was held according to Lee Arning, the director of emergency preparedness and business continuity.&#13;
&#13;
But the shootings at the Blacksburg, Va., campus have changed things.&#13;
&#13;
"Today&amp;#39;s event has rewritten the rulebook," Arning said in an interview Monday evening.&#13;
&#13;
A gunman killed 32 people at Virginia Tech in the deadliest shooting rampage in United States history. The victims were massacred in two attacks two hours apart on opposite sides of the school&amp;#39;s campus, with Tech&amp;#39;s police force unable to warn anyone before the carnage ensued. It ended with the gunman committing suicide - making the final death toll 33.&#13;
&#13;
Arning said he would attend a meeting Tuesday morning with other administrators to discuss the incident and its ramifications for the SMU community.&#13;
&#13;
At SMU, in the event of such an incident, the building managers would be responsible for either locking down their buildings or taking other measures necessary to keep its occupants safe according to Arning. They could also pass along information through a network of people within each building.&#13;
&#13;
The next wave of communication would come electronically: via e-mail, the official university Web site and phone tree messages. Any messages could also be announced on an intercom system; however, there is not a central intercom system and not every building on campus has one to begin with.&#13;
&#13;
One thing that will not happen, Arning said, is police officers driving around the campus notifying people over speakers or bullhorns. He said that would make the police cars and officers targets.&#13;
&#13;
SMU has emergency "Lockdown/Take Cover" guidelines that Arning said he discusses during the annual campus fire drills at buildings.&#13;
&#13;
The guidelines say if a person perceives a threat of violence to dial 911 immediately or call SMU police at (214) 768-3333. It adds that evacuation alarms should not be sounded.&#13;
&#13;
It says to close, lock and barricade doors to reduce the potential risk of a violent person reaching the area where people are. The guidelines say the best way to secure oneself is by not moving around, crouching down and either getting out of sight or getting low on the floor. It says to remain silent because studies have shown that shooters will fire at things that move or make sounds. The guidelines also say to be prepared to remain in a lockdown state for an extended period of time.&#13;
&#13;
It will be safe to leave only when police on the scene gives an "all clear" message.&#13;
&#13;
"Your safety is dependent on compliance that may be uncomfortable for a little while," Arning said.&#13;
&#13;
Some Virginia Tech students told media outlets that the school failed to properly notify them of what was occurring and also accused the school of acting irresponsibly by not closing down the campus after the first shooting.&#13;
&#13;
Arning said if there were a similar incident at SMU, the school would err on the side of caution and shut down the campus.&#13;
&#13;
He said SMU PD, which would be the first responders to any incident on campus, has attended multi-day response training camps and would be ready for such events. Arning said it is likely SMU PD will go through more training after the events at Virginia Tech.&#13;
&#13;
"Their training is a strong part of their job," Arning said.&#13;
&#13;
The active shooter exercise held in December 2006 is another part of that training.&#13;
&#13;
Representatives of Highland Park PD, University Park PD, Dallas SWAT and SMU PD attended along with UP public affairs, SMU emergency management and public affairs.&#13;
&#13;
Arning said the scenario was based on research of previous incidents and allowed the different groups to have an idea of what it would be like to work together. At various points during the scenario, the group would stop and each agency would discuss what they would be doing at that point and how they could do their job better.&#13;
&#13;
"Everything is critically integrated," Arning said.&#13;
&#13;
After the scenario concluded the agencies discussed opportunities for improvement. Arning said the exercise was not the first one for the school, and credited SMU for continuing to refine its response to different events.&#13;
&#13;
He said meetings and discussions occurred twice already this semester in response to the incident at the Laura Lee Blanton Building with the suspicious envelope that wound up containing cooking powder and the meningitis infection that was on campus shortly before Spring Break.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.smudailycampus.com/media/storage/paper949/news/2007/04/17/News/Smu-Says.Its.Ready.For.Campus.Emergencies-2845885.shtml&gt;SMU Daily Campus - April 18, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10221">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="11225">
                <text>SMU Daily Campus</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12072">
                <text>"Norris, Mark William" &lt;mnorris@mail.smu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13621">
                <text>SMU says it&amp;#39;s ready for campus emergencies</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1617">
        <name>southern methodist university</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="885" 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="2194">
                <text>Sara  Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4085">
                <text>Hamza Shaban</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="6063">
                <text>2007-07-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7941">
                <text>After reading Kurt Vonnegut&amp;#39;s "Slaughterhouse Five," my 11th grade English teacher asked us, "Is death meaningful?" The question forced us to think about the line that appeared over and over in Vonnegut&amp;#39;s book, the line that appeared after anyone died: "So it goes." My classremained silent, thinking.&#13;
&#13;
"So it goes," sounds light, almost casual. It would describe the feeling most of us get when we read some headline "30 dead in Iraq," or "Tsunami Claims Countless." Vonnegut&amp;#39;s line seems fitting for some far off death, very distant from us, almost unimportant. But would I say "So it goes" after I learned my mother died, or my wife was killed? Would I say that casual line after yesterday&amp;#39;s events at Tech? The death I once thought was far off, remote and alien, has now struck my life, my family and a campus just two hours away.&#13;
&#13;
Yesterday people said things like, "It could have happened to us," and "I have a close friend in that dorm." Yesterday people were "shocked" and "humbled." So if the university were to answer my 11th grade teacher&amp;#39;s question, "Is death meaningful?" We would all shout, "of course it is!" Butsadly we only answer this now because of a vicious reminder. Death has become real, close and tangible. Only now do we recognize it.&#13;
&#13;
Of all the hypothetical questions and "what ifs" that plague our minds everyday, we seldom reflect on the one possibility that is certain -- our own deaths. We worry about Arab history midterms, internshipapplications, and getting a date for semi-formal, but we never think about the only thing in our lives that definitely will happen.&#13;
&#13;
Vonnegut&amp;#39;s &amp;#39;so it goes&amp;#39; was not meant to cheapen life, but was a useful reminder that death will happen to us all. Do you remember that angry wind yesterday? The wind that burned your face and made your eyes water? We should carry a little bit of that wind with us every day, not to makeus hurt and weep, but to remind ourselves that we are all fragile and finite. If we do that, we won&amp;#39;t need tragedy to wake us up. We will carry a vigor for life wherever we go. Because now we know each day has meaning, and we will strive to live each moment to its potential.&#13;
&#13;
Hamza Shaban&#13;
CLAS II&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.cavalierdaily.com/letters.asp?pid=1583&gt;The Cavalier Daily - April 18, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9912">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="11133">
                <text>The Cavalier Daily </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11839">
                <text>Meggie Bonner &lt;meggiebonner@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13329">
                <text>So it goes</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="183">
        <name>death</name>
      </tag>
      <tag tagId="163">
        <name>mortality</name>
      </tag>
      <tag tagId="72">
        <name>uva</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="108" 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="1478">
                <text>Kim Norris</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3369">
                <text>Kim Norris</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="5347">
                <text>2007-05-03</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7228">
                <text>So this is how it feels...Thoughts on April 16, 2007&#13;
&#13;
Thank you for this archive. My world view changed on this day, and I appreciate having a place to store my memories. I&amp;#39;m not writing this as one who was there first hand. I am writing as a VT alumnus (B.A. Theater Arts and M.A. English) and a resident of the community, to share with others who weren&amp;#39;t there first hand either, to witness how much it still hurt for this to happen to Virginia Tech, to Blacksburg.&#13;
&#13;
That Monday morning, I was at work at my former job in Salem, VA (I work in Blacksburg now) when the plant manager, whose wife works on campus, got a call from a friend. "Wife is fine...in lock down, and can&amp;#39;t call." The call was another friend who had heard from her sister, who works in Norris Hall. Her sister had managed to get a cellphone call out from the cleaning supply closet she and a co-worker locked themselves in after the shooting started. &#13;
&#13;
I logged onto the web. The news headline read "Shooting at VT. 1 dead, 1 injured."  I called my husband, who works second shift, woke him up, and told him to see if he could get some current news. He said he&amp;#39;d call right back. In the meantime...&#13;
&#13;
My friend and co-worker, got a call from her little sister, an EMT for Christiansburg/ Montgomery County. She was on the scene, and her casualty numbers were much higher. She&amp;#39;d heard emergency radio reports of 30 dead or injured already...she said the first response workers were going room to room in Norris Hall, and reporting in what they found.&#13;
&#13;
The news on the web went up to 22 dead. My husband called with the confirmed count: 33 dead including the shooter; injury reports still coming in. Suddenly, we knew how it felt to be members of the community that is the site of the "worst mass shooting in U.S. history." I had the sensation of the ground falling out from under me. So that&amp;#39;s how it feels... &#13;
&#13;
I immediately tried to call a close friend who is an English instructor at Va Tech. (This is well before Cho is identified as an English major.) I couln&amp;#39;t get through. I sent an email, Let me hear from you soonest...". (It would be Tuesday morning before I would hear she was okay - as okay as any of us were at that point.) My husband called back to say he&amp;#39;d gotten in touch with another friend whose wife teaches in Norris Hall. She didn&amp;#39;t teach on  Monday...thank Heaven. But how many co-workers or students did she know?&#13;
&#13;
I got through the work day, survived the I-81 commute home, and checked messages. There were two: my sister, also a VT graduate, and my mom. Both said the same thing. "This is awful. Call me and tell me how you are." I wept, appreciating the long distance hugs. Who was I to need a hug though? It hadn&amp;#39;t happened to me. So I thought. Then I turned on the local TV news.&#13;
&#13;
Probably nothing could bring it harder home to me, just how messed up the day had been, than to see every major news channel reporting live from what I still consider my town (although I live in the next town over now). My sweet, small, safe town. I knew then that everything had changed. Blacksburg and VT had lost something that could never be regained, that sense of, "that could never happen here." We all  had to grow up that day. Students, Alumni, and residents alike. Time to shed those wonderful rose-colored blinders that life in a sweet, small, safe town can afford you, and see the world, and know that there was never any protecting ourselves from this. We still aren&amp;#39;t safe. How do you shield against madness?&#13;
&#13;
My phone rang all night that April 16. College friends I hadn&amp;#39;t heard from in years called to share their horror and sadness. (The next day I got a card from my ill-tempered and often-estranged mother-in-law, "Hope your friends are all right...")&#13;
&#13;
My husband got home from work Monday night around 11:45 pm and handed me a small ribbon, orange and maroon layered on black. A co-worker of his had spent the day making 100 of them to hand out at work. I pinned mine to my lapel with a VT logo earring (one of a pair I bought to wear at the 2000 Sugar Bowl in New Orleans). For a few moments I had the only ribbon like it...&#13;
&#13;
Nikki Giovanni got it right at the convocation. We will prevail. Whether the media moves on or not. That Wednsday, a Virginia-based newspaper reporter called our house, and my husband answered. Our last name is Norris. Were we any relation to the namesake of Norris Hall, and if so how did we feel about this tragedy happening in that particular building? (We aren&amp;#39;t related.)&#13;
&#13;
Here on May 3, the funerals are over, the tears are still flowing, but now the media is backing off, at least on a national level. The scab isn&amp;#39;t being ripped off as frequently, and maybe some true healing can begin. But there&amp;#39;s no going back to who we were. Only moving forward. Let&amp;#39;s go Hokies!</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9196">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12689">
                <text>So This is How it Feels...</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="191">
        <name>account</name>
      </tag>
      <tag tagId="186">
        <name>reflection</name>
      </tag>
      <tag tagId="194">
        <name>story</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1817" 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="2922">
                <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="4813">
                <text>Alyssa S. Navares</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="6791">
                <text>2008-03-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8669">
                <text>Issue date: 4/19/07 Section: News&#13;
By Alyssa S. Navares&#13;
Ka Leo Managing Editor&#13;
&#13;
More than 1,000 Facebook groups and MySpace pages started in response to Monday&amp;#39;s deadly shooting, some supporting victims and others blaming 23-year-old gunman Cho Seung-Hui.&#13;
&#13;
Blogs and social network sites have changed ways of communicating and coping with tragedy, as younger generations use the Internet to discuss and to express feelings about the massacre. On many pages, people have removed their profile photos and replaced them with a black ribbon and Virginia Polytechnic University logo.&#13;
&#13;
Thousands of miles from Blacksburg, VA, University of Hawai&amp;#39;i at M?noa students recognized the online mourning by adding the UH logo and the phrase, "All One Ohana. Today, we are all Hokies" to the profile photo. UHM alum Gary McRawr and sociology major Milena Kulig created separate Facebook groups, both of which have more than 200 members.&#13;
&#13;
"I&amp;#39;m hoping to get UH alums and current students [and] faculty involved," McRawr said, "and possibly even the community colleges across the state to be aware of the situation." McRawr started the group "UH is praying for Virginia Tech" the day 32 people and the gunman were killed, becoming the deadliest shooting in U.S. history.&#13;
&#13;
Thirty people joined Kulig&amp;#39;s group, "UH Manoa Supports Virginia Tech," within the first five minutes of creating it Monday evening, and by Tuesday it had grown to more than 200 members. Kulig started the group after joining one from another school and realizing that UHM did not have one.&#13;
&#13;
"The turnout is way better than I thought it would be," she said. "Honestly, I was just thinking that a few people who were as shocked and saddened by the situation like I was would join."&#13;
&#13;
Other people have used these social networks to vent about the shooting and its killer. More than 200 online groups on both Facebook and MySpace started in response to the Virginia Tech senior and immigrant from South Korea. Virginia Tech students described him as a loner who said little.&#13;
&#13;
"He should of just shot himself and not killed anyone, but no, he had to make everyone suffer," wrote Cory Hills, a student from Wellsville Senior High School in New York, in the "I Hope Cho Seung-Hui Burns in Hell" group.&#13;
&#13;
Racist remarks about Cho appeared throughout online blogs and social sites in response to his South Korean ethnicity. Some bloggers called him "a Kim Chee eating mofo," while others referred to him as a "slanted eye freak."&#13;
&#13;
But having a negative reaction after a tragedy is typical, according to the American Psychological Association. University psychologists nationwide created a Web site with advice on how to cope with the Virginia Tech shooting.&#13;
&#13;
Negative viewpoints should be balanced to maintain a healthier perspective of one&amp;#39;s self and the world, the APA Web site states.&#13;
&#13;
In Facebook group "Cho Seung-Hui is pure evil," Tennessee Brentwood High School student Leigh Durham was the first out of the 85 members to comment in support of Cho, sparking crude remarks from others in the group.&#13;
&#13;
"How about people stop focusing on this guy and think about all the people that were affected by this," she wrote on the posting wall. "Wasting your time bashing this guy isn&amp;#39;t going to make things any better."&#13;
&#13;
One student from Drexel University in Pennsylvania called Durham a moron and an idiot an hour after she posted her comment.&#13;
&#13;
Asking for support, online or in-person, can be comforting and helps because speaking with others who share similar experiences prevents feelings of loneliness, according to the APA site.&#13;
&#13;
Because cellphone networks, like Verizon Wireless, became stressed hours after the shooting, people shifted to the Internet. Virginia Tech students created an "I&amp;#39;m ok at VT" group in Facebook, which included a list of murdered and injured victims. The West Virginia Blogger compiled personal sites for those killed as an online memorial. Others traded photos and videos online as well.&#13;
&#13;
&#13;
&#13;
Online networks related to Virginia shooting&#13;
&#13;
&#13;
Facebook - about 450 groups&#13;
"UH M?noa supports Virginia Tech"&#13;
"Cho Seung-Hui is pure evil"&#13;
&#13;
&#13;
MySpace - about 550 sites&#13;
www.myspace.com/thehokies&#13;
www.myspace.com/virginiatechshooting&#13;
&#13;
&#13;
Blogs - about 350 sites&#13;
The West Virginia Blogger: www.bloggingwv.com&#13;
Virginia Tech Blog: www.VTtragedy.com&#13;
&#13;
--&#13;
&#13;
Original Source: The Voice - Ka Leo&#13;
&lt;a href="http://media.www.kaleo.org/media/storage/paper872/news/2007/04/19/News/Social.Networking.Sites.Help.Students.Cope-2869752.shtml"&gt;http://media.www.kaleo.org/media/storage/paper872/news/2007/04/19/News/Social.Networking.Sites.Help.Students.Cope-2869752.shtml&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10640">
                <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="12275">
                <text>Kumari Sherreitt &lt;editor@kaleo.org&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13985">
                <text>Social networking sites help students cope - 1000-plus online groups created after VA Tech massacre</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="172">
        <name>facebook</name>
      </tag>
      <tag tagId="2043">
        <name>social network sites</name>
      </tag>
      <tag tagId="2038">
        <name>uhawaii</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1014" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  Note that facsimiles or images of texts are still of the genre text.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2316">
                <text>Elva Orozco</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4207">
                <text>MarÃ­a Luisa Azpiazu</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6185">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8063">
                <text>Actividades en honor a los fallecidos marcan el regreso a virginia tech &#13;
&#13;
Publicado por MarÃ­a Luisa Azpiazu&#13;
EFE&#13;
04-24-2007 &#13;
&#13;
&#13;
Washington, D.C â€” Mucho dolor, impresionantes minutos de silencio y 32 campanadas en memoria de las vÃ­ctimas de la peor matanza de la historia estudiantil de E.U. marcaron ayer el regreso a clase de los alumnos de la Universidad PolitÃ©cnica de Virginia. &#13;
&#13;
Fueron miles los alumnos que regresaron ayer para rendir tributo a sus compaÃ±eros y profesores fallecidos. &#13;
&#13;
Justo una semana antes, Cho Seung-Hui, un estudiante coreano de 23 aÃ±os, decidiÃ³ cambiar el ritmo devida en esta Universidad del sur del estado de Virginia y matÃ³ a 32 personas. &#13;
&#13;
Las solemnes conmemoraciones comenzaron muy pronto. El primer minuto de silencio se guardÃ³ a las 7:10 de la maÃ±ana en el edificio en el que Cho cobrÃ³ sus dos primeras vÃ­ctimas. Algo mÃ¡s de dos horas despuÃ©s, la gran concentraciÃ³n se llevÃ³ a cabo en el campus central, donde los estudiantes colocaron miles de recuerdos, flores, velas y escritos en recuerdo de las vÃ­ctimas. &#13;
&#13;
Entre los objetos, alguien puso una bandera de PerÃº y otra de Israel en memoria de dos de las vÃ­ctimas, el estudiante peruano Daniel PÃ©rez Cuevas y el profesor Liviu Librescu, quien, segÃºn testigos, bloqueÃ³ con su cuerpo la entrada a su clase del agresor y salvÃ³ la vida de varios de sus alumnos, aunque perdiÃ³ la suya. &#13;
&#13;
La maÃ±ana fue brillante, soleada y cÃ¡lida, lo que contribuyÃ³ a que el acto fuera aÃºn mÃ¡s solemne. Los estudiantes portaron 33 banderas blancas que representaban tanto a las vÃ­ctimas como al agresor. &#13;
&#13;
Una pequeÃ±a banda de mÃºsica interpretÃ³ el himno "America the Beautiful" cerca del lugar donde se habÃ­a instalado un semicÃ­rculo con 33 piedras en recuerdo de los fallecidos. &#13;
&#13;
Junto a la piedra del agresor, alguien colocÃ³ una carta en la que se asegura que este joven "subestimÃ³ nuestra fuerza, coraje y compasiÃ³n" y en la que se asegura que "rompiste nuestros corazones pero no nuestros espÃ­ritus". &#13;
&#13;
Este es el resumen de un convencimiento que impera en esta Universidad, decidida a superar el gran trauma. &#13;
&#13;
"Tenemos que seguir adelante", aseguran desde las pÃ¡gina del "Collegiate Times", el periÃ³dico universitario. que ha jugado un papel fundamental tanto en la ayuda a los estudiantes como en la informaciÃ³n en los momentos posteriores de la tragedia. &#13;
&#13;
La consigna es clara- "Vamos HokiesÂ¡Â¡", que es el nombre con el que se denominan los estudiantes de esta Universidad. &#13;
&#13;
Alumnos, familiares y profesores, escucharon, en medio de un gran recogimiento, las 32 campanadas. Una por cada una de las vÃ­ctimas. Terminada la letanÃ­a, los estudiantes lanzaron 32 globos blancos al cielo seguidos de otros mil de colores naranja y marrÃ³n, la enseÃ±a de la Universidad. &#13;
&#13;
Muchos, todavÃ­a, no podÃ­an contener las lÃ¡grimas y, en declaraciones a medios locales, aseguran que aÃºn no saben si volverÃ¡n a la Universidad o darÃ¡n el curso por terminado ya, dos semanas antes de lo previsto. &#13;
&#13;
La Universidad permitirÃ¡ a todo aquel que no quiera volver a las clases repetir el semestre o quedarse con las notas que tenÃ­a hasta el momento.Para los que decidan volver, la Universidad tiene una baterÃ­a de psicÃ³logos que a ayudarÃ¡ a superar el trauma. &#13;
&#13;
Se estÃ¡n poniendo en marcha igualmente imaginativas terapias, como la que ha llevado a la Cruz Roja a llevar a este campus decenas de perros amaestrados para ser especialmente cariÃ±osos, que acompaÃ±arÃ¡n a los estudiantes. &#13;
&#13;
Se trata, en definitiva, de ofrecer calma y paz para evitar mÃ¡s episodios tristes como el vivido el fin de semana por la familia Soriano. &#13;
&#13;
Su hijo Jeff, un estudiante de Virginia Tech que habÃ­a sobrevivido a la tragedia, se matÃ³ en la carretera el viernes, poco antes de llegar a su casa, en Norfolk (Virginia). &#13;
&#13;
Su padre, Enrique Soriano, asegura que su hijo es "la vÃ­ctima nÃºmero 33" de la tragedia. EFE &#13;
&#13;
--&#13;
Fuente Original: Diario La Raza - Chicago&#13;
&lt;a href="http://www.laraza.com/news.php?nid=43429&amp;pag=0"&gt;http://www.laraza.com/news.php?nid=43429&amp;pag=0&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10034">
                <text>spa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11940">
                <text>Jorge Mederos&#13;
Executive Editor&#13;
La Raza Chicago Inc.&#13;
jorge.mederos@laraza.com&#13;
August, 13 2007</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13435">
                <text>Solemnes momentos de recordaciÃ³n</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1357">
        <name> vamos hokies</name>
      </tag>
      <tag tagId="441">
        <name>collegiate times</name>
      </tag>
      <tag tagId="435">
        <name>librescu</name>
      </tag>
      <tag tagId="105">
        <name>perez</name>
      </tag>
      <tag tagId="1356">
        <name>recuerdos</name>
      </tag>
      <tag tagId="1355">
        <name>regreso a clases</name>
      </tag>
      <tag tagId="1358">
        <name>soriano</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="668" 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="1993">
                <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="3884">
                <text>fallenposters / Do Not Cross (Blog)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5862">
                <text>2007-07-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7740">
                <text>April 17th, 2007&#13;
&#13;
As a part of my Homicide Investigation class at George Washington University, my instructor has asked us to write a brief analysis of the killings that occurred at Virginia Tech on Monday. Even though I am only a student and haven&amp;#39;t had the experience, statistically speaking, there are many things that are common when this type of crime occurs. I am in no way stating that any of the following is fact, it is just my interpretation of the events as based on my knowledge gained in my Homicide Investigation course.&#13;
&#13;
* * *&#13;
&#13;
It appears that the offender&amp;#39;s motivation for the first shooting is domestic. There have been much speculation as to the offender&amp;#39;s relationship with the female victim. Some feel that they may have been in a relationship or that Cho had feelings for the female victim. It is possible that his motivation to kill her was caused by Cho&amp;#39;s apparent hatred for "spoiled, rich kids." Is it possible that Cho had feelings for the female and was rejected? Thus taking his hatred out on her? Based on the fact that Cho walked across campus (at least half a mile) to Norris Hall to commit his crimes shows he had been planning this. The killings at Norris were not spontaneous at all.&#13;
&#13;
Cho wanted to destroy what symbolized the high class that he felt such disdain for. Since he associated many, if not all, students at Virginia Tech as being in this class, he felt that everyone encountered could potentially be his victims.&#13;
&#13;
This murder seems most likely to be an authority murder. The perceived authority being the higher class. If Cho grew up in a middle or lower income family, then this could explain his problem with the higher class. Northern Virginia can have very large gaps in the income levels among families. Cho probably felt this gap during his time in school in Northern Virginia and this is what probably helped escalate his hatred.&#13;
&#13;
But the question remains of who was his primary target? Was it the first two victims? Or was his primary target someone in Norris Hall? Usually in an authority killing, the killing ends once the primary target is killed. Did Cho find his primary target in Norris Hall, then end his life?&#13;
&#13;
Weapon stockpiling and verbalization of hatred towards a particular authority is also common in this type of murder.  It seems that Cho did both of these things by purchasing two semiautomatic handguns and writing disturbing poetry and plays in his creative writing classes.&#13;
&#13;
Cho probably had a history of mental illness, including isolation, paranoid behavior, etc.  Cho&amp;#39;s post offensive behavior did not seem to change at all. Especially since he shot two people, and calmly went back to his own dorm, then walked across campus to execute another batch of killings. Cho&amp;#39;s history of being isolated and calm continues to his post-offensive behavior. This is probably why nothing was suspected of his behavior in between the two shooting incidents.&#13;
&#13;
--&#13;
&#13;
Original Source: fallenposters / Do Not Cross (Blog) &lt;a href="http://fallenposters.wordpress.com/2007/04/17/some-analysis-of-the-killings-at-virginia-tech/"&gt;http://fallenposters.wordpress.com/2007/04/17/some-analysis-of-the-killings-at-virginia-tech/&lt;/a&gt;&#13;
&#13;
This work is licensed under a &lt;a href="http://creativecommons.org/licenses/by-nc-nd/3.0/"&gt;Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9711">
                <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="11694">
                <text>Creative Commons Attribution-Noncommercial-No Derivative Works 3.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13138">
                <text>Some Analysis of the Killings at Virginia Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="796">
        <name>analysis</name>
      </tag>
      <tag tagId="83">
        <name>blog</name>
      </tag>
      <tag tagId="797">
        <name>homicide investigation</name>
      </tag>
      <tag tagId="798">
        <name>motives</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
