<?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/browse?output=omeka-xml&amp;page=45&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-06T11:06:29+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>45</pageNumber>
      <perPage>20</perPage>
      <totalResults>1884</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="879" 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="2188">
                <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="4079">
                <text>HÃ©ctor GonzÃ¡lez AvilÃ©s</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="6057">
                <text>2007-07-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7935">
                <text>Creado por HÃ©ctor GonzÃ¡lez AvilÃ©s&#13;
09/06/2007 a las 04:26 PM&#13;
&#13;
&#13;
El diecinueve de abril&#13;
del aÃ±o dos mil siete,&#13;
un coreano desquiciado,&#13;
enajenado por entes satÃ¡nicas,&#13;
acribillÃ³ a tiros en su universidad,&#13;
a sus compaÃ±eros, dÃ¡ndoles muerte.&#13;
&#13;
El asesino se suicidÃ³ como Balmaceda,&#13;
de un balazo en la siÃ©n,&#13;
el crimen conmoviÃ³ mucho&#13;
al pueblo norteamericano&#13;
y todo el mundo entero tambien.&#13;
&#13;
La muerte asolÃ³ las aulas&#13;
de la Universidad "Virginia Tech",&#13;
ya nada serÃ¡ igual,&#13;
pues la violencia y el terrorismo&#13;
voltearon el mundo al revÃ©s.&#13;
&#13;
--&#13;
Fuente Original: AtinaChile&#13;
&lt;a href="http://www.atinachile.cl/content/view/37554/1er_CONCURSO_INTERNACIONAL_DE_POESIA_LIBRE_ATINA_CHILE.html"&gt;http://www.atinachile.cl/content/view/37554/1er_CONCURSO_INTERNACIONAL_DE_POESIA_LIBRE_ATINA_CHILE.html&lt;/a&gt;&#13;
&#13;
Licencia de uso:&#13;
&lt;a href="http://creativecommons.org/licenses/by-nc-nd/2.0/cl/"&gt; Creative Commons AtribuciÃ³n-NoComercial-SinDerivadas 2.0 Chile.&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9906">
                <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="11833">
                <text>Creative Commons&#13;
AtribuciÃ³n-NoComercial-SinDerivadas 2.0 Chile</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13323">
                <text>Masacre de Virginia Tech (poema)</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="972">
        <name>poema</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1775" 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="2897">
                <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="4788">
                <text>John Tierney</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="6766">
                <text>2008-02-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8644">
                <text>Students, community members fill Basilica&#13;
&#13;
John Tierney&#13;
&#13;
Issue date: 4/18/07 Section: News&#13;
&#13;
Only a week after Easter, the Notre Dame community once again "finds [itself] at the foot of the Cross," said Father Pete McCormick during his homily at a memorial Mass for the Virginia Tech community Tuesday night at the Basilica of the Sacred Heart.&#13;
&#13;
"We always have the Cross in our life, but we do not grieve without hope," said McCormick, the assistant rector of Dillon Hall, who was just ordained on Saturday.&#13;
&#13;
The Mass, presided over by Vice President for Student Affairs Father Mark Poorman, was organized Monday after news of the 33-person massacre at Virginia Tech broke. Students were informed of the Mass by an urgent IrishLink email from Poorman late Monday.&#13;
&#13;
The Basilica was packed to a standing room only capacity, with the entire rear lobby of the church completely full. The Mass drew more people than last fall&amp;#39;s 9/11 five-year anniversary Mass.&#13;
&#13;
The congregation was made up largely of students, although many members of the outside community were also present. Some students came straight from the library, carrying their backpacks, while many dressed nicely for the service. Following the Mass, many students visited the Grotto to pray and reflect on the massacre.&#13;
&#13;
In his homily, McCormick emphasized the powerful emotions many Americans have felt in the past few days in response to the tragedy at Virginia Tech.&#13;
&#13;
"We have been overwhelmed with thoughts and emotions. [...] We are shocked, we are fearful, and we are angered," he said.&#13;
&#13;
McCormick also underlined the similarities between the Notre Dame and Virginia Tech communities.&#13;
&#13;
"We&amp;#39;ve heard the stories of students, staff and professors who died, and we realized that their goals and ambitions are not that different from our own," he said.&#13;
&#13;
Because of these similarities, McCormick said he believes the Notre Dame and Virginia Tech communities are "of one thought and mind." Like those at Virginia Tech&amp;#39;s candlelight vigil Tuesday night, the members of the Notre Dame community worshiping at the Basilica and praying at the Grotto "gathered to pray for the lost souls and for peace in their hearts, and in our own," he said.&#13;
&#13;
The Mass was meant to represent the concern for the spiritual unity of all humankind.&#13;
&#13;
"When one part of the human community suffers, we all suffer," McCormick said.&#13;
&#13;
McCormick said he believes members of the Notre Dame community can take strength in the Holy Spirit after Monday&amp;#39;s tragedy, which was the largest mass shooting in U.S. history.&#13;
&#13;
"The Holy Spirit allows us to move from a state of fear to faith," McCormick said. "We may be fearful, but it is faith, not fear, that transforms and heals our wounds."&#13;
&#13;
While Monday&amp;#39;s events were undoubtedly tragic, McCormick stressed the ability to overcome disaster and increase spiritual strength.&#13;
&#13;
"It is only for us now to find how even the Cross can be borne as a gift," he said to close his homily.&#13;
&#13;
The message of the Mass was not one of depression, but a more hopeful state of solidarity with fellow humans.&#13;
&#13;
"We must be a community with hope to bring. There is no failure that the Lord cannot reverse," McCormick said.&#13;
&#13;
&#13;
--&#13;
&#13;
Original Source:&#13;
&lt;a href="http://media.www.ndsmcobserver.com/media/storage/paper660/news/2007/04/18/News/Mass-For.Virginia.Tech.Provides.Consolation.Hope-2849116.shtml"&gt;http://media.www.ndsmcobserver.com/media/storage/paper660/news/2007/04/18/News/Mass-For.Virginia.Tech.Provides.Consolation.Hope-2849116.shtml&lt;/a&gt;&#13;
&lt;a href="http://media.www.ndsmcobserver.com/media/storage/paper660/news/2007/04/18/News/Mass-For.Virginia.Tech.Provides.Consolation.Hope-2849116-page2.shtml"&gt;http://media.www.ndsmcobserver.com/media/storage/paper660/news/2007/04/18/News/Mass-For.Virginia.Tech.Provides.Consolation.Hope-2849116-page2.shtml&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10615">
                <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="12253">
                <text>Christopher Hine &lt;chine@nd.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13960">
                <text>Mass for Virginia Tech provides consolation, hope</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1977">
        <name>9/11</name>
      </tag>
      <tag tagId="1995">
        <name>mass</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="2002">
        <name>notre dame</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="944" 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="2247">
                <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="4138">
                <text>Marta Dehmlow</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="6116">
                <text>2007-08-08</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7994">
                <text>&lt;b&gt;As Tulane officials rethink security policies, some Tulane students express personal grief over Monday&amp;#39;s events&#13;
By:&lt;/b&gt; &lt;a href="http://www.thehullabaloo.com/user/index.cfm?event=displayAuthorProfile&amp;authorid=2313160"&gt;Marta Dehmlow&lt;/a&gt;&#13;
&lt;b&gt;Posted:&lt;/b&gt; 4/20/07&#13;
&#13;
Students at Virginia Tech and all over the nation will remember April 16 as a day that shattered the security of college campuses everywhere.&#13;
&#13;
"How do you have openness and accessibility and make sure the campus is as safe as possible?" Tulane University president Scott Cowen asked in an April 18 interview with the Hullabaloo. "Campuses are sacred ground."&#13;
&#13;
This "sacred ground" was desecrated, however, when Cho Seung-Hui, a 22-year-old senior at Virginia Tech, shot and killed 32 students and injured 26 more before turning his gun on himself.&#13;
&#13;
The largest school shooting in history has torn apart the Virginia Tech college community in Blacksburg, Va., leaving college students nationwide doubtful about the security of their own institutions.&#13;
&#13;
"It can happen anywhere," senior neuroscience major Jen Velarde said. "Crazy people are out there. It can happen so easily; there&amp;#39;s such a fine line. As much as you secure a building, if a student is going to do this, it can happen."&#13;
&#13;
And it has happened a number of times before, university officials said.&#13;
&#13;
"This is not really an isolated incident," Tulane University Police Department director Ken Dupaquier said, citing past shootings on college campuses. "People think that it hasn&amp;#39;t happened before or in a long time, but it has."&#13;
&#13;
Nationwide, college students empathizing with their Virginia Tech counterparts have demonstrated their solidarity. Jonathan Horner, a senior microbiology major who has several close friends at Virginia Tech, showed support for the affected school by changing his facebook picture to one saying "Today we are all Hokies," referring to Virginia Tech&amp;#39;s mascot. He, like many other college students, also joined a facebook group memorializing the victims.&#13;
&#13;
"I also called and messaged all my friends," he said. "I told them I&amp;#39;m praying for them and their school."&#13;
&#13;
Other students were more immediately affected by the massacre at Virginia Tech.&#13;
&#13;
Maura Bowlin, a sophomore English major, spent her freshman year at Virginia Tech before transferring to Tulane in the fall of 2006.&#13;
&#13;
"It&amp;#39;s eerie to think I&amp;#39;ve walked the halls of [Ambler-Johnston Residence Hall and Norris Hall]," Bowlin said about the sites of the two shootings.&#13;
&#13;
Although she has many friends at the school, Bowlin said she has not quite felt the full effect of the situation.&#13;
&#13;
"It hasn&amp;#39;t really sunk in. We talk about it in every single class, which I wish we didn&amp;#39;t," Bowlin said.&#13;
&#13;
Bowlin explained that Cho was not a typical Virginia Tech student. As a senior, the gunman lived on campus, "which almost no one does after freshman year. So that was weird."&#13;
&#13;
She also had a friend who was supposed to be in one of the classrooms in Norris Hall.&#13;
&#13;
"She slept through the class," Bowlin said. "I knew a few people who just didn&amp;#39;t go to class because they had a feeling."&#13;
&#13;
Kerry Kraft, a sophomore communication major, spent Fall 2005 at Virginia Tech, where one-quarter of her high school class attends.&#13;
&#13;
"I was distraught when I tuned on the TV. I spent all day on the phone or in front of [it]," Kraft said.&#13;
&#13;
She knows a number of students at Virginia Tech, and she was very concerned, Kraft said.&#13;
&#13;
"I was lucky," Kraft said. "Everyone I know was all right, but they were all affected directly or indirectly. I was lucky not to be directly affected."&#13;
&#13;
The events have also caused Tulane&amp;#39;s administration and campus police force to reiterate their security measures and emergency preparedness plan.&#13;
&#13;
"All of our public safety officers are trained as police officers at the academy, like NOPD. Therefore they have at least been prepared," Cowen said.&#13;
&#13;
Prior to the Virginia Tech massacre and Hurricane Katrina, a decision was made to update the emergency response system.&#13;
&#13;
"We will have six different phone numbers for each student, plus e-mails will get blasted by information [in the event of an emergency]", Cowen said. The new system will also include the ability to text message students&amp;#39; cell phones.&#13;
&#13;
Dupaquier believes that with Tulane&amp;#39;s current protocol, an event such as this one would have been avoided.&#13;
&#13;
"Our protocol for dealing with students with similar traits to [Cho&amp;#39;s] is that we would have liked to intervene," Dupaquier said. "We have a mechanism in place between Public Safety, Student Affairs, the Educational Resource Center, the student health center and the deans that would catch this, hopefully."&#13;
&#13;
Tulane, like many other colleges, is also reassessing current systems. A task force is being created headed by Vice President Anne Banos. It will involve different arms of the university and several student leaders to help ensure that such a horrific event does not happen at Tulane.&#13;
&#13;
"We will see what changes, if any, need to be made in our protocol," Dupaquier said. "The president expects an answer in a timely manner. Not in a matter of months, but Cowen expects recommendations in a few weeks."&#13;
&#13;
While the administration and public safety department are concerned first and foremost with the well-being of Tulane students, they extend their sympathies to the Virginia Tech community.&#13;
&#13;
"Obviously, we are devastated for those that were killed, and their friends and family," Cowen said. "We are not strangers to tragedy, and we can identify. We will do whatever we can to help."&#13;
&#13;
Cowen said the school has offered counseling and Student Affairs personnel to offer help as students, staff and faculty at Virginia Tech cope with the tragedy.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.thehullabaloo.com/media/storage/paper958/news/2007/04/20/News/Massacre.At.V.t.Affects.Colleges.Across.Nation-2873327.shtml&gt;The Hullabaloo - April 20, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9965">
                <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="11877">
                <text>"Dickson, Drew D." &lt;ddickson@tulane.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13377">
                <text>Massacre at V.T. affects colleges across nation</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="721">
        <name>campus safety</name>
      </tag>
      <tag tagId="717">
        <name>grief</name>
      </tag>
      <tag tagId="733">
        <name>student response</name>
      </tag>
      <tag tagId="1085">
        <name>tulane</name>
      </tag>
      <tag tagId="1086">
        <name>unversity response</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="246" 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="1600">
                <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="3491">
                <text>Justin Baeder</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="5469">
                <text>2007-05-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7348">
                <text>Posted Tuesday, April 17th, 2007 at  1:43 AM by Justin&#13;
&#13;
I hate it how, whenever we have a national tragedy, journos just eat it up. The TV stations make logos for it, and slogans like "Massacre at Virginia Tech" that become ominous jingles as the anchors and announcers repeat them as a story unfolds.&#13;
&#13;
We&amp;#39;re watching Dateline NBC now (for the first time ever), and the exploitation of the V Tech tragedy is enraging. Matt Lauer is just getting too much mileage out of it.&#13;
&#13;
They take every aspect of the story and make it into an entertainment event. They interview grief counselors and find out how that works. They pull out footage of previous shootings. They interview paramedics and enlighten us about their work. It&amp;#39;s all for entertainment and to create viewership for the network.&#13;
&#13;
The other people who infuriate me when we have a tragedy is the "expert" morons who get on the tube saying how this could have easily been prevented. Their hindsight is perfect, and they get to promote themselves as experts every time an unpreventable tragedy happens. There&amp;#39;s a guy on Dateline now talking about how they should have sent in a massive anti-terrorism response team after the first two people were shot. Come on. We&amp;#39;re going to send in the ATF or the army or whomever every time there&amp;#39;s a shooting? Ten thousand people are shot to death each year in this country. We can&amp;#39;t treat each incident like an act of terrorism as this guy is suggesting.&#13;
&#13;
The other thing I hate about the "if only" experts is that they implicitly blame everyone involved. If only the campus police had done something different. If only the email had gone out sooner warning people to stay in lockdown. None of this was foreseeable - who could have known a campus shooting (like the one that happened in Seattle a few weeks ago) would turn into a massacre?&#13;
&#13;
I say, mourn with those who mourn, and stop exploiting them for publicity and our need to know.&#13;
&#13;
If that weren&amp;#39;t enough, they&amp;#39;re now doing a story about a guy who survived the Columbine massacre but lost his sister, Rachel Scott. Emotional aftermath and all that. Ugh. "Soon, even prayer was no match for the terror..."&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.radicalcongruency.com/20070416-massacre-at-virginia-tech-let-the-media-exploitation-begin"&gt;http://www.radicalcongruency.com/20070416-massacre-at-virginia-tech-let-the-media-exploitation-begin&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by/2.5/"&gt;Creative Commons Attribution 2.5&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9318">
                <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="11328">
                <text>Creative Commons Attribution 2.5</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12795">
                <text>Massacre at Virginia Tech: Let the Media Exploitation Begin</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="83">
        <name>blog</name>
      </tag>
      <tag tagId="240">
        <name>commentary</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="768" 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="2086">
                <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="3977">
                <text>Danielle Williamson/Daily News 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="5955">
                <text>2007-07-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7833">
                <text>By Danielle Williamson/Daily News staff&#13;
GHS&#13;
Tue Apr 17, 2007, 12:07 AM EDT &#13;
&#13;
NO DATA - For Bill Saam, the slaughter yesterday at his alma mater resurrected the shock, sadness and anger he felt when terrorists attacked the World Trade Center.&#13;
&#13;
"On a personal level, the feeling I had today was very much the way I felt on 9/11," said Saam, a Northborough resident and 1992 Virginia Tech graduate.&#13;
&#13;
An active member of the college&amp;#39;s alumni association, Saam was in touch yesterday with other classmates who struggled to comprehend the news.&#13;
&#13;
"It&amp;#39;s very much a tight-knit community," he said. "I hope no one from New England is directly affected by this."&#13;
&#13;
Saam described Blacksburg as a "small, rural area."&#13;
&#13;
"You don&amp;#39;t hear about crime down there, never mind shootings," he said.&#13;
&#13;
For Milford native Jim Pyne, a 1993 Virginia Tech graduate, yesterday&amp;#39;s murders are a sad reflection on the state of society.&#13;
&#13;
"We have people who fly planes into buildings ... and screwballs who have guns and shouldn&amp;#39;t have them," said Pyne, a former professional football player. "It&amp;#39;s the society we live in, and it&amp;#39;s just despicable."&#13;
&#13;
Pyne, who was an All-American at Virginia Tech and played nine seasons in the NFL, said he watched much of the news yesterday but "couldn&amp;#39;t keep watching it. It doesn&amp;#39;t seem real."&#13;
&#13;
"I&amp;#39;ve been in all those buildings. I took classes there," Pyne said. "I feel for the parents of the 33 kids and I&amp;#39;m horrified about what happened and what it&amp;#39;s like for them."&#13;
&#13;
Peter Darby of Charlestown, who leads the New England chapter of Virginia Tech&amp;#39;s alumni association, said the Boston area has 1,300 alumni, many of whom were in contact with each other yesterday.&#13;
&#13;
"We&amp;#39;re stunned just numb," Darby said.&#13;
&#13;
For Waltham native Marcus Ly, the shootings were particularly difficult to comprehend.&#13;
&#13;
"I called a lot of my friends in Blacksburg. They&amp;#39;re all OK," said Ly, a Virginia Tech grad student speaking by phone yesterday from Minneapolis. "But it&amp;#39;s just a lot of confusion, they don&amp;#39;t really know anything more than we do reading the headlines."&#13;
&#13;
A 1995 Waltham High School graduate, Ly finished a graduate school program in industrial and systems engineering at Virginia Tech last winter.&#13;
&#13;
"It&amp;#39;s really the equivalent of something like this happening in Weston," said Ly, trying to describe the town of Blacksburg, home to the 2,600-acre Virginia Tech campus. "It&amp;#39;s one of the safest cities I&amp;#39;ve ever lived in and I&amp;#39;ve lived in a lot of cities."&#13;
&#13;
Natick&amp;#39;s Chris Mitchell, a junior at Virginia Tech, never imagined such horror could occur on the campus.&#13;
&#13;
"It&amp;#39;s a small town and a university where everybody knows everybody," Mitchell, an economics major, told WCVB-TV. "It&amp;#39;s the last place where you&amp;#39;d think something like this would happen."&#13;
&#13;
Newton resident Theodore Fritz recognized the buildings photographers captured throughout the day.&#13;
&#13;
"I&amp;#39;m certainly transfixed here," said Fritz, a 1961 Virginia Tech graduate who watched television reports throughout the day.&#13;
&#13;
A Boston University professor, the killings affected Fritz both as a college educator and a Virginia Tech alumnus.&#13;
&#13;
"I think this probably could have happened anywhere," he said.&#13;
&#13;
Danielle Williamson can be reached at 508-490-7475 or dwilliam@cnc.com. Daily News staff writers Albert Breer and Nicole Haley contributed to this story.&#13;
&#13;
--&#13;
&#13;
Original Source:Framingham,MA - The MetroWest Daily News&#13;
&lt;a href="http://www.metrowestdailynews.com/local_news/x1298126656"&gt;http://www.metrowestdailynews.com/local_news/x1298126656&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc-nd/3.0/"&gt;Creative  Commons Attribution-NonCommercial-NoDerivs 3.0&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9804">
                <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="11784">
                <text>Creative  Commons Attribution-NonCommercial-NoDerivs 3.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13224">
                <text>Massacre of 32 at Virginia Tech shocks alumni in MetroWest</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="84">
        <name>alumni</name>
      </tag>
      <tag tagId="895">
        <name>boston university</name>
      </tag>
      <tag tagId="893">
        <name>massacre</name>
      </tag>
      <tag tagId="894">
        <name>metrowest</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1393" public="1" featured="0">
    <fileContainer>
      <file fileId="716">
        <src>https://www.april16.vtlibraries.net/files/original/1342165648_ab5981e723_b_58396b5229.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="15082">
                    <text>2007-09-22</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="16202">
                    <text>2007-09-22 13:40:37</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="2644">
                <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="4535">
                <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="6513">
                <text>2007-09-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8391">
                <text>As master of ceremonies, Dave Matthews introduces fellow performers at A Concert for Virginia Tech, September 6, 2007.&#13;
&#13;
Photo courtesy of Kevin Cupp.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.flickr.com/photos/kevincupp/1342165648/"&gt;http://www.flickr.com/photos/kevincupp/1342165648/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10362">
                <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="12126">
                <text>Kevin Cupp (k@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13725">
                <text>Master of Ceremonies, Dave Matthews</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1554">
        <name>concert</name>
      </tag>
      <tag tagId="1553">
        <name>concert for virginia tech</name>
      </tag>
      <tag tagId="1679">
        <name>dave matthews</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="620" public="1" featured="0">
    <fileContainer>
      <file fileId="364">
        <src>https://www.april16.vtlibraries.net/files/original/President 187_16226126bd.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="14757">
                    <text>2007-06-28</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15877">
                    <text>2007-06-28 12:57:38</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="1949">
                <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="3840">
                <text>Garry Thompson</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="5818">
                <text>2007-06-28</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7696">
                <text>This photo captured Matt La Porte&amp;#39;s hokie stone.&#13;
&#13;
Photo Courtesy of Garry Thompson&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9667">
                <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="11651">
                <text>Permission:&#13;
Garry Thompson&#13;
sthomp2813@aol.com</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13107">
                <text>Matt La Porte</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="371">
        <name>hokie rock</name>
      </tag>
      <tag tagId="372">
        <name>Hokie stone</name>
      </tag>
      <tag tagId="743">
        <name>la porte</name>
      </tag>
      <tag tagId="744">
        <name>matthew la porte</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2169" public="1" featured="0">
    <fileContainer>
      <file fileId="1016">
        <src>https://www.april16.vtlibraries.net/files/original/003 Matthew Gregory Gwaltney_ba2bda6822.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="15372">
                    <text>2008-04-21</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16492">
                    <text>2008-04-21 15:37: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="3069">
                <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="4960">
                <text>Teri H. Hoover</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6938">
                <text>2008-04-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8816">
                <text>Items left at the memorial plaque of Matthew Gwaltney on the drillfield.  Photo taken on 5-1-07.&#13;
&#13;
Photo by Teri H. Hoover.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10787">
                <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="12392">
                <text>Teri H. Hoover &lt;crystalirisphotos@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14131">
                <text>Matthew Gregory Gwaltney</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="522">
        <name>gwaltney</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2177" public="1" featured="0">
    <fileContainer>
      <file fileId="1023">
        <src>https://www.april16.vtlibraries.net/files/original/009 Matthew Joseph La Porte_7d68ebc76c.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="15379">
                    <text>2008-04-21</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16499">
                    <text>2008-04-21 15:53:39</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="3076">
                <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="4967">
                <text>Teri H. Hoover</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6945">
                <text>2008-04-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8823">
                <text>Items left at the memorial plaque of Matthew La Porte on the drillfield.  Photo taken on 5-1-07.&#13;
&#13;
Photo by Teri H. Hoover.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10794">
                <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="12399">
                <text>Teri H. Hoover &lt;crystalirisphotos@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14138">
                <text>Matthew Joseph La Porte</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="743">
        <name>la porte</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="274" public="1" featured="0">
    <fileContainer>
      <file fileId="183">
        <src>https://www.april16.vtlibraries.net/files/original/Mattthew Gwaltnev_75423091d6.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="14580">
                    <text>2007-05-28</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15700">
                    <text>2007-05-28 09:44:01</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="1627">
                <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="3518">
                <text>Krissy Watson</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="5496">
                <text>2007-05-28</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7375">
                <text>A second from Richmond...graduate of Thomas Dale High School in Chesterfield.&#13;
&#13;
Original source: &lt;a href=" http://share.shutterfly.com/action/slideshow?a=67b0de21b3292af30542&amp;auto=0&amp;idx=7&amp;m=1&amp;d=1180361530851"&gt; http://share.shutterfly.com/action/slideshow?a=67b0de21b3292af30542&amp;auto=0&amp;idx=7&amp;m=1&amp;d=1180361530851&lt;/a&gt;&#13;
&#13;
Photo courtesy of Krissy Watson</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9345">
                <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="11352">
                <text>Photo courtesy of Krissy Watson&#13;
krissywatson@gmail.com</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12820">
                <text>Mattthew Gwaltney</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="522">
        <name>gwaltney</name>
      </tag>
      <tag tagId="371">
        <name>hokie rock</name>
      </tag>
      <tag tagId="372">
        <name>Hokie stone</name>
      </tag>
      <tag tagId="363">
        <name>mattthew gwaltnev</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="365">
        <name>rock</name>
      </tag>
      <tag tagId="373">
        <name>stone</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2184" public="1" featured="0">
    <fileContainer>
      <file fileId="1030">
        <src>https://www.april16.vtlibraries.net/files/original/016 Maxine Shelly Turner_bb6ff14c4c.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="15386">
                    <text>2008-04-21</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16506">
                    <text>2008-04-21 16:18:04</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="3083">
                <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="4974">
                <text>Teri H. Hoover</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6952">
                <text>2008-04-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8830">
                <text>Items left at the memorial plaque of Maxine Turner on the drillfield.  Photo taken on 5-1-07.&#13;
&#13;
Photo by Teri H. Hoover.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10801">
                <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="12406">
                <text>Teri H. Hoover &lt;crystalirisphotos@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14145">
                <text>Maxine Shelly Turner</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="2187">
        <name>turner</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2272" public="1" featured="0">
    <fileContainer>
      <file fileId="1107">
        <src>https://www.april16.vtlibraries.net/files/original/2419173833_52163aa3f0_b_6e13323e17.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="15459">
                    <text>2008-05-02</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="16579">
                    <text>2008-05-02 17:12: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="3158">
                <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="5049">
                <text>Brian Sewell</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="7027">
                <text>2008-05-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8905">
                <text>Memorial stone of Lauren Ashley McCain on 4/16/08.&#13;
&#13;
Photo by Brian Sewell.&#13;
&#13;
--&#13;
&#13;
Original Source:&#13;
&lt;a href="http://flickr.com/photos/briansewell/2419173833/in/set-72157604577382666/"&gt;http://flickr.com/photos/briansewell/2419173833/in/set-72157604577382666/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10876">
                <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="12480">
                <text>Brian Sewell &lt;bwsewell@vt.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14220">
                <text>McCain memorial</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1989">
        <name>anniversary</name>
      </tag>
      <tag tagId="104">
        <name>mccain</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="373">
        <name>stone</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1274" 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="2541">
                <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="4432">
                <text>Jake Meador</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="6410">
                <text>2007-09-03</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8288">
                <text>By: Jake Meador / Freshman English major&#13;
Posted: 4/25/07&#13;
The heroes of the Protestant Reformation had an old saying that man is simultaneously both saint and sinner, and the truth of this statement is impossible to argue. In the 20th century alone there lived people as awful as Adolf Hitler and Joseph Stalin and as wonderful as Mother Teresa and Martin Luther King Jr.&#13;
&#13;
The irony of the saying is that it&amp;#39;s often when the sinners are at their worst that we get the clearest picture of the saints. The lives of great men and women become most beautiful when confronted with great tragedy.&#13;
&#13;
Mother Teresa would be an unknown if it weren&amp;#39;t for the horrors of poverty, the oppressive caste system and the ruins of India left behind by British imperialism. Likewise, King would be long forgotten if it weren&amp;#39;t for the horrors of racism and segregation. We saw one more example of this truth last week in the tragedy at Virginia Tech.&#13;
&#13;
By now everyone has heard the name Cho Seung-Hui, and we should call him by his name, not by some title we make up to avoid the harsh reality that a human being committed this crime. We&amp;#39;ve heard of how the 23-year-old senior English major killed 32 individuals and then himself in the worst school shooting in U.S. history.&#13;
&#13;
Some have even seen the disturbing video he made prior to the massacre. We&amp;#39;ve heard about his dark, sad life that ended so violently. But few have told the story of another man involved in the tragedy.&#13;
&#13;
76-year-old engineering professor Liviu Librescu was one of the 32 to be killed by Seung-Hui. But if it weren&amp;#39;t for a courageous act of sacrifice on Librescu&amp;#39;s part, there may have been more casualties. Librescu was teaching a class in Norris Hall when gunshots were first heard in a distant corner of the building.&#13;
&#13;
Students in the classroom initially hid, but as the sound came closer and closer, Librescu instructed students to flee through the window. He then, in the ultimate act of sacrifice, braced the door with his own body, being shot through the door several times as his students escaped. When police entered the room, they found the professor dead by the door with five bullet wounds.&#13;
&#13;
Additionally, 32-year-old Egyptian doctorate student Waleed Muhammad Shaalan, who had been shot once already, distracted Seung-Hui long enough to allow several other students to escape.&#13;
&#13;
Seung-Hui reminds us of all that is broken in our world: the fractured relationships, the alienation so many of us feel, the violence we often witness and the self-centeredness that so often characterizes us. Librescu and Shaalan, on the other hand, are a heroic reminder of all that is good in life and all that is a cause for hope.&#13;
&#13;
And Librescu didn&amp;#39;t just become that with his act of sacrifice. His whole life was characterized by bravery, generosity and love.&#13;
&#13;
Born in 1930 in Romania, he lived through the Holocaust as an adolescent. Despite such difficulties, he excelled in school, studying aerospace engineering and becoming one of the finest engineering students in Romania.&#13;
&#13;
He earned his doctorate degree in the late 1950s and then taught various engineering courses for 20 years before losing his job in the 1970s due to his opposition to the ruling Communist party.&#13;
&#13;
Thanks to the intercession of the Israeli government, he was allowed to leave the country, and he moved to Tel Aviv, Israel, to teach at the university there for several years.&#13;
&#13;
After Tel Aviv, he moved to the United States to teach at Virginia Tech, which he had done since 1986. Throughout his career at Virginia Tech, he was known for being one of the finest researchers in the world, as well as a great man. As one colleague put it, "He was a very pleasant, jolly fellow who enjoyed joking around a little with the staff. An everyone&amp;#39;s-friend sort of guy." One student said he treated all of his students like his own children.&#13;
&#13;
So it isn&amp;#39;t surprising that last week when the lives of his students were threatened, Librescu did what a father would do in such a situation. He sacrificed his own safety to protect the lives of his students, and for that Librescu is a hero. And it&amp;#39;s important we remember that during these dark days following such a tragic event.&#13;
&#13;
There&amp;#39;s no shortage of darkness in our world, and consequently there&amp;#39;s no shortage of negativity and cynicism. But Librescu&amp;#39;s example reminds us that ultimately love triumphs over all these things.&#13;
&#13;
There is something about human beings that cannot be kept down by hatred, violence or oppression, and Librescu&amp;#39;s life is the perfect portrait of that something: narrowly escaping a young death at the hands of Hitler, resisting an oppressive Communist regime in his home country and ultimately giving up his own life in order to save others.&#13;
&#13;
So as we reflect on the tragedy at Virginia Tech and have conversations about how to prevent a similar tragedy from happening again (and we need to have those conversations: We need to talk about gun control and loving the hard-to-love and additional safety measures to protect students), we also must remember Librescu&amp;#39;s heroic sacrifice.&#13;
&#13;
It is because of his selfless act that today 20-30 students are still alive and 20-30 families aren&amp;#39;t burying their sons or daughters.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailynebraskan.com/media/storage/paper857/news/2007/04/25/Opinion/Meador.Heroes.Arise.Out.Of.Tragic.Events.At.Virginia.Tech-2878361.shtml&gt;Daily Nebraskan - April 25, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10259">
                <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="11242">
                <text>Daily Nebraskan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12093">
                <text>Josh Swartzlander &lt;jdwriter19@yahoo.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13658">
                <text>MEADOR: Heroes arise out of tragic events at Virginia Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1669">
        <name>university of nebraska </name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1270" 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="2538">
                <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="4429">
                <text>Sara AA Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6407">
                <text>2007-09-03</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8285">
                <text>By: Jake Meador / Freshman English major&#13;
Posted: 4/30/07&#13;
When I first sat down to write my column after the massacre at Virginia Tech on April 16, my thoughts were two-fold: First, to write a column advocating stricter gun control. Second, to write a column praising the selfless heroism of Leviu Lebrescu and Waleed Muhammad Shaalan. I did the latter, but I&amp;#39;ve since decided not to do the former.&#13;
&#13;
Gun control is such a divisive issue; the last thing we need right now is further division between people. Today is a day for reconciliation, not debate. Besides, if 33 dead bodies, including the gunman&amp;#39;s, won&amp;#39;t change your mind (one way or the other), then 850 words probably won&amp;#39;t either.&#13;
&#13;
But as I browsed the Internet reading stories of the awful event, sometimes wondering what sick curiosity drives us to such exploration, I stumbled across a link with pictures and a brief bio for each victim. Many of the pictures were highly pixilated - a sad reminder that they were never intended for such use. And at that moment I realized I, and many others, have forgotten to talk about the most important lesson to come from Virginia Tech.&#13;
&#13;
And it has nothing to do with gun control or stricter campus security policies.&#13;
&#13;
Among those killed were husbands and fiancÃ©s, wives and mothers, fathers and sons, daughters and sisters, Muslims, Jews, Christians and Hindus. One was a resident assistant who was in the marching band. Another was trying to find a cure for cerebral palsy. Still another had started a sorority for female engineering students. Another was in the dance ensemble.&#13;
&#13;
I&amp;#39;m listing all these things for two reasons. Each individual was unique and had diverse interests and a never-before-seen personality. And when these individuals died, it wasn&amp;#39;t just another tally on Cho Seung-Hui&amp;#39;s killing spree; it wasn&amp;#39;t a nameless number.&#13;
&#13;
It was the loss of a unique human being that God created and knew intimately. We&amp;#39;ve heard the number over and over, "32 dead," but we haven&amp;#39;t heard about them as individuals, and if we keep repeating the number, it&amp;#39;s easy for us to forget that there are 32 families in mourning, as well as countless friends and others who were touched by these individuals.&#13;
&#13;
There is another reason I listed all those individual traits. Despite their differences in interests, age, ethnicity, political beliefs, gender and religion, they shared a common humanity (something also shared between the victims and Seung-Hui, incidentally.).&#13;
&#13;
Sadly, in the wake of this tragedy, many of us have spent more time discussing those differences than the commonality. We&amp;#39;ve spent lots of time debating gun control, religion, university security policies, etc. And, of course, we need to talk about all of those issues. You might be like me and think stricter gun control is needed; you might be like many of my friends and think this event is the greatest argument possible for carrying concealed weapons.&#13;
&#13;
You might be like me and think the only final solution to this event is through some sort of metaphysical belief that transcends debate about public policy. I spoke with a Buddhist monk on the day of the shooting, and he was convinced the problem is one of ignorance. I&amp;#39;m convinced it&amp;#39;s the problem of a sinful human heart, and all the knowledge in the world can&amp;#39;t change that - only Jesus can.&#13;
&#13;
You might be like me and think tighter security measures might be a good idea, but you have no idea how they&amp;#39;d be implemented. Or perhaps you think they&amp;#39;re important enough that significant sacrifices in student freedoms are necessary to ensure our safety.&#13;
&#13;
I say all of that because these conversations are important. Having strong opinions is not a bad thing, but you have to know how to express them. So often as we have these conversations we lose sight of the fact that, ultimately, we&amp;#39;re all human, and even if someone disagrees with you, he or she is not your enemy. If you&amp;#39;re a Democrat, Republicans are not the enemy; if you&amp;#39;re Christian, atheists are not the enemy. Because of the intensity of the events at Virginia Tech and the topics being discussed, it&amp;#39;s easy to develop the idea that people with differing ideas are hindrances to progress - if they&amp;#39;d just believe like me, maybe we&amp;#39;d get somewhere.&#13;
&#13;
But it&amp;#39;s never that simple, and even if it were, arrogance gets us nowhere. So listen, learn, respect - and love every moment of it. To quote the late Kurt Vonnegut, "Welcome to Earth. It&amp;#39;s hot in the summer and cold in the winter. It&amp;#39;s round and wet and crowded. At the outside, babies, you&amp;#39;ve got about a hundred years here. There&amp;#39;s only one rule that I know of, babies - God damn it, you&amp;#39;ve got to be kind."&#13;
&#13;
I&amp;#39;ve got about 100 words left this year, but rather than waste them on further elaboration, I thought it&amp;#39;d be appropriate to print the names of the 32 victims. As you read, remember each of these people had friends, family, hopes and dreams, just like you. And right now those dreams have gone to the grave with them, and their friends and families are still mourning two weeks later. Even if some of us have already forgotten:&#13;
&#13;
Ryan Clark, 22. Emily Jane Hilscher, 19. Christopher James Bishop, 35. Daniel Perez Cueva, 21. G.V. Loganathan, 51. Ross Abdallah Alameddine, 20. Mary Karen Read, 19. Caitlin Hammaren, 19. Kevin Granata, 46. Liviu Librescu, 76. Brian Bluhm, 25. Austin Cloyd, 18. Jocelyne Couture-Nowak, 49. Matthew Gregory Gwaltney, 24. Jeremy Herbstritt, 27. Rachel Elizabeth Hill, 18. Jarrett Lane, 22. Matt La Porte, 20. Henry Lee (Henh Ly), 20. Partahi Lumbantoruan, 34. Lauren McCain, 20. Daniel O&amp;#39;Neil, 22. Juan Ortiz, 26. Minal Panchal, 26. Erin Peterson, 18. Michael Pohle, 23. Julia Pryde, 23. Reema Samaha, 18. Waleed Mohammed Shaalan, 32. Leslie Sherman, 20. Maxine Turner, 22. Nicole White, 20.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailynebraskan.com/media/storage/paper857/news/2007/04/30/Opinion/Meador.Virginia.Tech.Shootings.Show.Need.For.Humanity-2887492.shtml&gt;Daily Nebraskan - April 30, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10256">
                <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="11240">
                <text>Daily Nebraskan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12090">
                <text>Josh Swartzlander &lt;jdwriter19@yahoo.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13655">
                <text>MEADOR: Virginia Tech shootings show need for humanity</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1669">
        <name>university of nebraska </name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1301" public="1" featured="0">
    <fileContainer>
      <file fileId="635">
        <src>https://www.april16.vtlibraries.net/files/original/im_070417_april16_054_e3e9c90bc1.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="15005">
                    <text>2007-09-04</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="16125">
                    <text>2007-09-04 20:52:46</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="2565">
                <text>Haeyong Chung</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4456">
                <text>Ivan V. Morozov</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="6434">
                <text>2007-09-04</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8312">
                <text>2007.04.17.&#13;
Ever present media is setting up to report from the Drill Field about the candlelight vigil.&#13;
&#13;
Photo courtesy of Ivan V. Morozov</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10283">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13682">
                <text>Media </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1672">
        <name>broadcast</name>
      </tag>
      <tag tagId="342">
        <name>drill field</name>
      </tag>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="344">
        <name>reporter</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1088" 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="2388">
                <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="4279">
                <text>Lawrence G. Hincker</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="6257">
                <text>2007-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8135">
                <text>Date: Tue, 14 Aug 2007 22:09:39 -0400&#13;
From: Virginia.Tech.news@vt.edu&#13;
To: Multiple recipients &lt;LISTSERV@LISTSERV.VT.EDU&gt;&#13;
Subject: Media and the return to school&#13;
&#13;
Wednesday, August 15, 2007&#13;
&#13;
TO: The students, faculty, and staff of Virginia Tech&#13;
 &#13;
RE: Media and the return to school&#13;
 &#13;
With the beginning of the fall 2007 semester, there will be intense media interest in the Virginia Tech community in light of the events of April 16. While some may prefer otherwise, there will again be many broadcasters, reporters, and cameras on the campus. Indeed, some already are on campus.&#13;
 &#13;
Our university is public property. Our roads are public thoroughfares. We cannot bar the media from campus. However, although our buildings are open to the public, residence halls, offices, and classrooms are restricted. Faculty members control entry to classrooms while teaching there. Labs are open only to those authorized. Offices are semi-private spaces open to anyone with a reason to be there. University residence halls are living quarters and open only to those living there and their guests.&#13;
 &#13;
What should you do if a member of the news media approaches you for an interview? You are never REQUIRED to speak to the media. Politely telling a reporter "no thank you" will suffice. If a reporter is particularly troublesome, just walk away and do not feel guilty about doing so.&#13;
 &#13;
However, I am proud -- very, very proud -- of our university community and how we have represented ourselves to the world through the media over the past several months. You have shown the world the special nature of Hokie Spirit. If you are comfortable, feel free to speak about yourselves, your involvement with the university, or your feelings about the future. I wouldn&amp;#39;t be surprised if reporters want to take you back to April 16. You control discussion and you talk about what you want to talk about. It&amp;#39;s your time.&#13;
 &#13;
Should you engage a reporter, take advantage of the opportunity to share some Hokie Spirit. The world mourned with us and maintains an interest in the collective health of our extended university community. I believe that most reporters share this concern and compassion. With so many reporters present, this is a unique opportunity to again convey the character of our community and tell a little about why Virginia Tech and Blacksburg are such very special places.&#13;
 &#13;
Sincerely yours,&#13;
Lawrence G. Hincker&#13;
Associate Vice President&#13;
University Relations</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10106">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13506">
                <text>Media and the return to school</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1363">
        <name>hincker</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="139">
        <name>reporters</name>
      </tag>
      <tag tagId="1522">
        <name>return to school</name>
      </tag>
      <tag tagId="115">
        <name>university relations</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="262" 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="1616">
                <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="3507">
                <text>Charles Warner</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="5485">
                <text>2007-05-26</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7364">
                <text>Charles Warner / &lt;a href="http://www.mediacurmudgeon.com/"&gt;Media Curmudgeon Blog&lt;/a&gt;&#13;
&#13;
Television has once again gone on a rampage of gluttony over the tragic murders at Virginia Tech.  However, it depends on your definition of what constitutes gluttony and what kind of TV you&amp;#39;re talking about.&#13;
&#13;
First, all television is not cut from the same cloth.  CNN, MSNBC, and Fox are all-news cable channels, so they have a 24-hour news hole to fill.  Because TV is inelastic, the three national news channels can neither expand or contract time nor add or subtract hours to the clock.  Thus they fill those 24-hours with what each thinks the majority of their viewers will find compelling.  And, of course, they all choose the same stories in what has become a cycle of competitive reinforcement, confirmation, and excess.&#13;
&#13;
If CNN airs a story, then Fox and MSNBC producers say, "That confirms that the story is importantÃƒÂ¢Ã¯Â¿Â½Ã¯Â¿Â½CNN (Fox, MSNBC) is running it."  They also say, "We&amp;#39;ve got to run the story more often and devote more resources to it or viewers will go elsewhere."  Thus, the news cycle spins out of control.  Furthermore, the three cable news networks have structured their programming in hour-long blocks, often with personality-hosts who do talk segments (Larry King, Lou Dobbs, Bill O&amp;#39;Reilly), and the assumption, generally, is that viewers watch for about an hour, so they have to repeat the news cycle and the top stories every hour. In all-news radio, the news cycles are usually shorter.  For example, New York&amp;#39;s WINS has the famous tagline, "Give us 20 minutes and we&amp;#39;ll give you the world."  TV and radio all-news outlets are like a news faucet.  The notion is that you can turn on a news station or channel at any time and the latest, most important news spews out. &#13;
&#13;
Therefore, if you watch a TV news channel for longer than an hour, which happens with breaking news like the Virginia Tech story, you see the top story repeated, giving the impression of saturation and excess. And if you get sick of the coverage on one cable news network and turn to another, you see the same top story repeated, which increases the perception of excess coverage.&#13;
&#13;
Furthermore, TV has much greater impact than any other medium because it engages viewers&amp;#39; emotions through its blend of sight, sound, motion, and emotion. Thus videos of airplanes crashing into buildings or a killer&amp;#39;s deadly ramblings leave much more dramatic and lasting impressions.  And it is these impressions that magnify the perception of excess.&#13;
&#13;
TV and radio are real-time linear; you can&amp;#39;t rewind or fast forward.  They are linear-accessed push media for which the audience can&amp;#39;t control what is pushed out; their only option is turn off or switch outlets.  Conversely, print media and the Internet are non-linear pull media in which the audience can select what they want, go back and forth, and have random access to content they are interested in.  Therefore, when people have no control over what is pushed to them, they are more frustrated than when they can control their content, can pull what they want as often as they want. &#13;
&#13;
With these parameters in mind, we can now ask several questions: 1) Should NBC have released the video, pictures, and ramblings of Cho Seung-Hui?  2) Overall, was the media coverage of the Virginia Tech massacre excessive and insensitive?  3) Is the media leading the charge to assign blame? 4) What is Cho&amp;#39;s proper name?&#13;
&#13;
1. Should NBC have released the video, pictures, and ramblings of Cho Seung-Hui?   NBC News President Steve Capus made the right decision to release the images and ramblings, not only to show them on NBC but also to release them to other news organizations.  First, it was in the public interest to have information about the psychopathic killer distributed for a number of reasons, not the least of which was to bring closure to the horror and reassure people that there was no larger plot.  Also, as Jack Shafer of &lt;a href="http://www.slate.com/id/2164717/nav/tap1/"&gt;Slate&lt;/a&gt;, writes: "NBC News needn&amp;#39;t apologize to anybody for originally airing the Cho videos and pictures. The Virginia Tech slaughter is an ugly story, but the five W&amp;#39;s of journalismÃƒÂ¢Ã¯Â¿Â½Ã¯Â¿Â½who, what, where, when, and whyÃƒÂ¢Ã¯Â¿Â½Ã¯Â¿Â½demand that journalists ask the question &amp;#39;why?&amp;#39; even if they can&amp;#39;t adequately answer it.  If you&amp;#39;re interested in knowing why Cho did what he did, you want to see the videos and photos and read from the transcripts. If you&amp;#39;re not interested, you should feel free to avert your eyes."&#13;
&#13;
NBC could not have kept the pictures for itself and away from other news organizations.  But did it run the images too often?  Yes, and it admitted as much by restricting their use after complaints from victims&amp;#39; families, and Virginia Tech and Virginia officials. And while we don&amp;#39;t know if the complaints had anything to do with the decision, I think they probably did.  However, the manner in which NBC promoted the video tapes on Brian William&amp;#39;s "Nightly News" was a little too self-congratulatory, and MSNBC was clearly over the top in its greedy self-promotion. Chris Matthews, in particular, should be pistol-whipped for his callous, gloating promotion of the Cho videos. But what&amp;#39;s so surprising about that?  NBC&amp;#39;s grade is B minus for sharing the material and eventually restricting the use of the images to no more than 10 percent of any news program. MSNBC&amp;#39;s grade is F.  CNN&amp;#39;s grade is D, mostly for contributing to the feeding-frenzy coverage.  Fox News&amp;#39; grade is F, for using the videos, as MSNBC did, as video wallpaper.  NPR&amp;#39;s grade is A.  Without pictures, radio doesn&amp;#39;t have the impact of TV, so NPR could be more thoughtful and do more meaningful, sensitive sidebars, which it did.&#13;
&#13;
2. Overall, how was the media coverage of the Virginia Tech massacre; was it excessive and insensitive?  Yes and yes.  The amount of coverage was excessive because of the nature of cable and radio all-news outlets, particularly in the use of the killer&amp;#39;s video on TV.  Worse, in my view, was the invasion and occupation of the Virginia Tech campus by hordes of insensitive reporters who bombarded the privacy of the university, the campus, students, victims, and their families in a frenzy to get scoops.  NPR recounted the story of a female student who lived in the dorm where the first killings took place.  Her dorm was locked down, but, somehow, a female magazine reporter gained access, entered her room and asked her for an interview.  The weeping student asked the reporter to leave and quit badgering her, and the reporter responded by handing the distraught student her business card and asked, "Call me."  The student apparently replied, "What makes you think I&amp;#39;d call you after what you just did?"&#13;
&#13;
CNN sent four anchors to the campus and broadcast from there on Thursday.  Was that necessary? Absolutely not. It was excessive, intrusive, and insensitive.  Freedom of speech, yes.  Invasion of privacy, yes.  Come on, CNN, can&amp;#39;t you see the ironic insensitivity in overkill on an overkill?&#13;
&#13;
If the major media news organizations don&amp;#39;t find a way to control this expensive, invasive, counter-productive feeding frenzy on major stories, they leave themselves vulnerable to the Federal government stepping in and regulating news coverage, which would be terrible.  However, people are sick of this insensitive type of coverage, which gives them yet another reason for hating the media. So, slapping regulatory controls on the media by the government would more than likely be a popular move.  The VT shootings might result in pool coverage of major stories, or guidelines or standards under the auspices of the Radio Television News Directors Association (RTNDA), but, whatever, the big news organizations had better do something.&#13;
&#13;
3. Is the media leading the charge to assign blame?  Yes.  According to &lt;a href="http://mediamatters.org/items/200704190009"&gt;Media Matters for America&lt;/a&gt;, on the April 19 edition of "MSNBC Live" Boston radio host Michael Graham told MSNBC&amp;#39;s David Gregory that the whole story of the mass shooting "is a story of people just freezing, of just letting him have their way [sic], except that one brave professor put himself in between the gunman and his students."  So Graham blames the victims and MSNBC let him get away with it.  &lt;a href="http://www.time.com/time/nation/article/0,8599,1612492,00.html"&gt;TIME magazine&lt;/a&gt; ran a commentary by John Cloud titled "Viewpoint: Va. Tech&amp;#39;s President Should Resign," which blames Virginia Tech president, Dr. Charles W. Steger, for the massacre, which is ridiculous.  Others in the media have blamed "passive students," Virginia&amp;#39;s mental health providers, the campus police, the state&amp;#39;s gun control laws, Cho&amp;#39;s family, and South Koreans.  All are hysterical over-reactions, except perhaps the reaction to gun-control laws.&#13;
&#13;
Perhaps the media gets in a frenzy trying to find scapegoats to blame because it is trying deflect blame from itself to avoid the usual kill-the-messenger attitude of the public.&#13;
&#13;
4. What&amp;#39;s Cho&amp;#39;s proper name?  The New York Times, NBC, and MSNBC, among others, used the name Cho Seung-Hui, according to the Korean tradition of putting a family name first (thus, I would be Curmudgeon Media).  CNN, NPR, and ABC, among others, used the American version of the name, Seung-Hui Cho, which I believe is proper because Cho&amp;#39;s parents came to America when he was very young and he is a product of American culture, having gone to grade school, high school, and college in this country (his sister graduated from Princeton). Therefore, he should not have been referred to as "South Korean," which caused a rash of hate directed unfairly at Americans of South Korean decent and at South Koreans. Furthermore, the media confused the American public by using two different versions of his name.  So, even though The New York Times used the Korean version, all the other media should have gone along, standardized the usage, and explained the American usage, as NPR did, in order to avoid confusion. &#13;
&#13;
And what is the overall grade for the media? A failing grade of D.  When will the media get its act together? It probably won&amp;#39;t as long as it tries to appeal to people&amp;#39;s baser instincts in its competition for ratings and in its attempt to find the lowest level of taste and decency.  I think NBC, ABC, and, at times, CBS are trying, but they are not succeeding, just barely getting a passing grade.  The cable channels aren&amp;#39;t even trying to be decent; they&amp;#39;re just trying to beat each other.&#13;
&#13;
Posted by Charles Warner at April 21, 2007 10:36 AM&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.mediacurmudgeon.com/archives/2007/04/media_coverage.html"&gt;http://www.mediacurmudgeon.com/archives/2007/04/media_coverage.html&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nd/1.0/"&gt;Creative Commons Attribution-NoDerivs 1.0&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9334">
                <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="11343">
                <text>Creative Commons Attribution-NoDerivs 1.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12811">
                <text>Media Coverage of the Virginia Tech Massacre</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="83">
        <name>blog</name>
      </tag>
      <tag tagId="240">
        <name>commentary</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1142" 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="2440">
                <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="4331">
                <text>Tammesia Green</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6309">
                <text>2007-08-19</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8187">
                <text>By Tammesia Green			&#13;
&#13;
Following the massacre that occurred at Virginia Tech University on April 16, many have come to question their own safety at universities across the country. The profile of a school shooter, once narrowed to a lonely white male high-school student with a fascination with and open access to guns, was quickly re-examined as we discovered the shooter to be 23-year-old Cho Seung-Hui. But before the news had been released that the shooter was Asian, the question on everyone&amp;#39;s mind was whether this catastrophe could have been prevented. This question is a good one, and should be debated, but reflecting on the length of time the press devoted to this subject was unsettling for me.&#13;
&#13;
&#13;
I remember going to class the morning of the shooting and hearing news reports that two people had been shot at a Virginia Tech dormitory. Upon my return five hours later I was shocked to see the death toll had escalated to 33. Immediately, I wanted to know what had happened and if the killer had been caught. Watching the news, all I could find were reporters asking questions like, "Why wasn&amp;#39;t the school placed on lockdown? What time was the first e-mail sent to students?  Why wasn&amp;#39;t more done to prevent this tragedy?"&#13;
&#13;
&#13;
It became clear that I would not learn anything about what actually took place on the campus that could account for the casualty numbers rising; I had to resort to the Internet to try to make sense of all that was happening. After getting a clear account, I was upset at the amount of time the network news channels devoted to placing blame on officials at Virginia Techâ€”only, the "placing blame" was not seen for what it was. Instead, it was promoted as good investigative journalism.&#13;
&#13;
&#13;
I understand that it is the job of a journalist to ask the hard questions and uphold a level of accountability toward officials. However, I found that the questions posed by reporters in press conferences regarding Virginia Tech were not necessarily out of line, but a result of constant criticism of their inability to question authority in high-stakes situations.&#13;
&#13;
&#13;
Past disasters such as Hurricane Katrina and the logic behind going to war with Iraq played their roles in the types of questions posed to Virginia Tech President Charles Steger. These questions were simply a ploy to preemptively avoid any backlash from the public for not addressing accountability. &#13;
&#13;
&#13;
Following the invasion of Iraq and never finding weapons of mass destruction, the public began to demand that journalists not be afraid to question authority and command answers from high-ranking officials. Hurricane Katrina allowed for reporters to regain some credibility by analyzing slow relief efforts and the lack of preparation from the government. It is no surprise that in order to keep credibility and uphold the public&amp;#39;s faith in reporters, journalists continued to grow a backbone and demanded answers from those in power. &#13;
&#13;
&#13;
The word "accountability" is ultimately what forced the media to focus on how administrators screwed up and not the shooter. But accountability is not to be placed on school administrators and campus police when the act was really the work of one man, and only he can be blamed. Real investigative journalism would have been to expose the motives of Cho, not debate whether an e-mail should have been sent earlier or been more detailed. Even as students from the Virginia Tech campus were being interviewed and asked if their administration at the university should have done more, the look of "Are you really asking me this now?" ran across most of their faces. They, like me, could not understand why their administrators were being harassed as if they made the events unfold, and not Cho.&#13;
&#13;
&#13;
There is no way administrators at Virginia Tech could have predicted that a domestic dispute incident would be cause for the closing of an entire university. Anyone who thinks they would have had the notion to suspend classes and not think of the first attack as an isolated incident is thinking in the context of hindsight. Colleges enroll large quantities of students, equivalent to the population of some U.S. cities. Just like a city, Virginia Tech did not shut down when evidence of a homicide was discovered. &#13;
&#13;
&#13;
It is nice to want to believe that our college campuses are the last step before entering the real world, and are therefore void of the many threats society holds. But evil does exist and it knows no bounds. This evil of one individual is the only factor that should matter in evaluating who is accountable for the Virginia Tech massacre.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.newuniversity.org/showArticle.php?id=5789&gt;New University - April 30, 2007&lt;/a&gt;&#13;
&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10158">
                <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="11195">
                <text>New University</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12013">
                <text>Zachary Gale &lt;newueic@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13558">
                <text>Media Coverage of VT Tragedy Irresponsible</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1108">
        <name>criticism</name>
      </tag>
      <tag tagId="539">
        <name>journalism</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="297">
        <name>media coverage</name>
      </tag>
      <tag tagId="1563">
        <name>university of california - irvine</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2399" public="1" featured="0">
    <fileContainer>
      <file fileId="1188">
        <src>https://www.april16.vtlibraries.net/files/original/P1030025_4cef95c36b.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="15540">
                    <text>2008-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="16660">
                    <text>2008-05-30 13:28:40</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3241">
                <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="5132">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7110">
                <text>2008-05-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8988">
                <text>Special instructions for the media, on display at a "Remembering Through Art Creation" event in Squires Student Center. Photo taken on April 16, 2008, A Day of Remembrance.&#13;
&#13;
Photo by Brent Jesiek. &#13;
&#13;
Licensed under Creative Commons&#13;
&lt;a href="http://creativecommons.org/licenses/by-nc-sa/3.0/"&gt;Attribution-NonCommercial-ShareAlike 3.0&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10959">
                <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="12548">
                <text>Brent Jesiek (bjesiek@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14291">
                <text>Media Directives</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1989">
        <name>anniversary</name>
      </tag>
      <tag tagId="2262">
        <name>media message</name>
      </tag>
      <tag tagId="2239">
        <name>remembering through art</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="721" 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="2042">
                <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="3933">
                <text>Mark Humphrey  </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="5911">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7789">
                <text>By Mark Humphrey&#13;
Monday, April 23, 2007&#13;
&#13;
It&amp;#39;s no secret that the news media exercises bad judgment at times.&#13;
&#13;
Granted, we, as journalists, try to make informed decisions about what to cover and how. For example, during summer training at the Daily Bruin, we did a news-judgment exercise involving an actual story.&#13;
&#13;
The story was about a baby who had been murdered by her father, and the story also highlighted how a welfare program had failed the family. The issue was whether to run a photo of a coroner holding a bag that had the baby&amp;#39;s body in it - was the photo just simply shocking, or did it further the purpose of the story?&#13;
&#13;
We ultimately decided we would run the photo. Our reasoning was that the photo, while shocking and potentially in poor taste, further hammered home the main point of the story - how social programs had failed this family so terribly.&#13;
&#13;
Judging by the mainstream media&amp;#39;s recent coverage of certain events, I think many journalists would do well to take part in this same exercise.&#13;
&#13;
In the past few weeks we&amp;#39;ve been bombarded by three stories. First came radio douche bag Don Imus&amp;#39; derogatory remarks about the Rutgers women&amp;#39;s basketball team. Then came NBC&amp;#39;s decision to broadcast Virginia Tech killer Cho Seung-Hui&amp;#39;s videotaped rantings. Finally, there came Alec Baldwin&amp;#39;s disturbing phone message to his daughter.&#13;
&#13;
Aside from showing the ugly side of humanity, these stories have one thing in common: They were all covered in a misguided fashion.&#13;
&#13;
With Imus, people were right to be up in arms. He defamed a group of talented young women at what was supposed to be their finest moment. Unfortunately, this story got hammered into the ground, filling the airwaves at every single second of the day. Why was this a problem? Because of media hypocrisy.&#13;
&#13;
One of the main reasons the media gave for covering this so relentlessly was to right Imus&amp;#39; wrong: defaming a group of women because of what he thought of their physical appearance.&#13;
&#13;
Yet, by covering this so excessively, Imus&amp;#39; comments have been replayed so many times it&amp;#39;s gotten to the point where some would associate the Rutgers women less with basketball and more with Imus. It doesn&amp;#39;t matter how untrue his remarks are, as the Rutgers women have almost solely been associated with Don Imus since their season ended because of the media firestorm.&#13;
&#13;
Then there&amp;#39;s Alec Baldwin&amp;#39;s voice-mail tirade, where he refers to his 11-year-old daughter as a "thoughtless little pig" and vows to "straighten (her) out." Once again, media hypocrisy rears its ugly head. Ironically, so much has been said about the well-being of Baldwin&amp;#39;s daughter while the real issue has gone ignored.&#13;
&#13;
Namely, how well does it serve Baldwin&amp;#39;s daughter to not only hear her parents&amp;#39; dirty laundry aired in public, but also to hear the phone message repeated on television? Wouldn&amp;#39;t most sane people say that divorce hurts children, and that the more public the divorce, the more negative the effect on the child?&#13;
&#13;
Bad news judgment reached its zenith with NBC&amp;#39;s decision to air videos made by Virginia Tech killer Cho Seung-Hui. Naturally, the videos are all over YouTube.&#13;
&#13;
Not only was the decision to air these videos in poor taste, but it didn&amp;#39;t serve any purpose from a news standpoint. These videos added no new information and, more importantly, gave Cho exactly what he wanted: attention. Cho died, but NBC&amp;#39;s airing of his videos got his message out to everyone.&#13;
&#13;
In journalism, as much as some hate to admit it, the bottom line is still the bottom line. NBC aired these videos to get a jump on the competition, just like every news outlet jumped on them immediately afterward. Anyone who&amp;#39;s shocked when the media does something sensational is hopelessly naive. If it bleeds, it leads and, more importantly, makes money.&#13;
&#13;
When the media covers stories like this, it often claims moral superiority. It proclaims outrage and to know what is best for everyone. But if the way these situations have played out is any indication, it&amp;#39;s clear that much of the time, the media doesn&amp;#39;t have a clue.&#13;
&#13;
While I&amp;#39;m often disgusted by what gets covered and how, I can&amp;#39;t begrudge the news media for making a living.&#13;
&#13;
But if they&amp;#39;re going to proclaim they know what is best for everyone, they should think about who their coverage is really hurting first.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.dailybruin.ucla.edu/news/2007/apr/23/imedia_doesnt_always_know_besti/&gt;The Daily Bruin - April 23, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9760">
                <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="11740">
                <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="13183">
                <text>Media doesn&amp;#39;t always know best</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="847">
        <name>media response</name>
      </tag>
      <tag tagId="848">
        <name>tragedy response</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
