<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://www.april16.vtlibraries.net/items?output=omeka-xml&amp;page=64&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-13T03:57:46+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>64</pageNumber>
      <perPage>20</perPage>
      <totalResults>1884</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="113" 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="1482">
                <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="3373">
                <text>Gary Downey</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="5351">
                <text>2007-05-04</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7232">
                <text>Friends, Since a number of you asked to receive further installments, I decided to send this out to everyone who wrote to offer support.  I have greatly appreciated it, profoundly so.  Yesterday I used the basketball court for stress relief and to connect with another group of friends.  One friend, a productive scholar, said he had just arrived at the point of beginning to plan what he might try to accomplish next week.  That pretty much described my head as well.  I may add entries in coming weeks as thoughts and feelings spiral, but I don&amp;#39;t know.  For now I&amp;#39;m done.  I look forward to following up individually with each of you.  Warmly, Gary&#13;
&#13;
 &#13;
&#13;
Friends, I&amp;#39;m getting too many messages to respond individually.  I&amp;#39;m grateful for your concern. Below is a series of messages I&amp;#39;ve been sending out to those who have contacted me.&#13;
&#13;
 &#13;
&#13;
Monday afternoon&#13;
&#13;
I and my family are ok.  I was in my office 3 buildings away when the mass shootings took place, about 9:45.  I didn&amp;#39;t hear the shots.  I learned of the lockdown from a loudspeaker announcing an emergency.&#13;
&#13;
The 2nd floor of Norris Hall is home to the engineering science and mechanics dept, as well as the dean&amp;#39;s office for the college of engineering.  I have many friends in both.  I don&amp;#39;t believe anyone in STS teaches in that building.  No names have been released.  I&amp;#39;m holding my breath.&#13;
&#13;
This is beyond comprehension.&#13;
&#13;
Love, gary&#13;
&#13;
 &#13;
&#13;
[Note: much later I was reminded that I have taught in Norris Hall many times, in the big lecture hall, on the other end of the building from the shootings.  I know the building well.]&#13;
&#13;
 &#13;
&#13;
Tuesday AM:&#13;
&#13;
One of the professors killed was my friend, G.V. Loganathan, an Indian man from civil engineering. Last year he won the University&amp;#39;s top award for teaching.  His students had written passionately about the lengths he had gone to help them, both in the classroom and beyond. He was in his classroom.&#13;
&#13;
I also knew the German instructor, Jamie Bishop, a delightful, unassuming young man.  He also taught courses in web design.  I was enrolled in one last year as part of what is called here the Faculty Development Institute.&#13;
&#13;
Dr. Librescu held the door shut in his classroom to give his students time to jump out of the window.&#13;
&#13;
The loss is devastating.&#13;
&#13;
 &#13;
&#13;
Tuesday PM:&#13;
&#13;
At the convocation today, a father nearly collapsed and the proceeding stopped while he received care and was helped out of the Coliseum along with his family.  Nikki Giovanni, the poet, concluded the event with a wonderfully stirring call for persistence and community--but to me it&amp;#39;s not time yet.  All those families.&#13;
&#13;
 &#13;
&#13;
Wednesday AM:&#13;
&#13;
I awoke thinking about how what happened here on Monday happens every day in Iraq.    &#13;
&#13;
The sensationalism in U.S. news coverage is becoming the story.  This country seems to know what it is only when it has an enemy.  Virginia Tech has lost its innocence.  It&amp;#39;s now the object of a broader search for self-definition.  Today the word Columbine means one thing.  Is that what&amp;#39;s happening to Virginia Tech?&#13;
&#13;
 &#13;
&#13;
Wednesday PM:&#13;
&#13;
I&amp;#39;m watching two things, both in others and in myself.&#13;
&#13;
On the one hand, a genuine sense of questioning about the decision not to announce that a gunman was at large.  I&amp;#39;m glad President Steger asked the governor to appoint a commission to investigate what took place.  That strikes me as the right course of action.&#13;
&#13;
On the other hand, a sense of being attacked by the deluge of coverage and an urge to join together to fight it off.  The intrusion makes it difficult to conceptualize a new sense of community, let alone build it.&#13;
&#13;
 &#13;
&#13;
Thursday AM:&#13;
&#13;
My resistance to intrusion has grown.  The relentless demands for clarity in the national media have become overwhelming to me.  A nation uncertain about its identity lusts for the clarity of evil, identified and exorcised.  Those who were complicit must be punished.  But for the nation to gain its clarity and regain its self-assurance, we have to be torn apart. I&amp;#39;m watching decent people being challenged to admit fundamental failure, so others elsewhere can relax and resume. For me, the only way out is to accept the ambiguity.  I&amp;#39;m just not sure how. &#13;
&#13;
Note: Yesterday I deleted an expression of anguish from Monday about the 2 hour delay.  At the time, the anguish was my own.  But by Wednesday, it had been appropriated by the machinery of external demands for clarity.  I had lost possession of it.  It no longer said what I meant. It took me till today to understand that.&#13;
&#13;
I sent a letter to the Roanoke Times affirming that Virginia Tech is part Korean.  Many people feel similarly. Race may not become an issue. &#13;
&#13;
 &#13;
&#13;
Thursday PM:&#13;
&#13;
I didn&amp;#39;t want to go to a Department gathering at noon. I thought we might have difficulty coming together.  We didn&amp;#39;t.  It was a meaningful experience.  We helped one another. They are my people.  We&amp;#39;re going to gather again on Saturday.&#13;
&#13;
I was wrong when I said STS teaches no classes in Norris.  One of my graduate students, an international student, teaches a Friday discussion section of Engineering Cultures in 206.  That was G.V.&amp;#39;s room.&#13;
&#13;
 &#13;
&#13;
Friday PM:&#13;
&#13;
Yesterday I gave a long interview to the Toronto Star.  He wanted to discuss the increase in mass shootings.  I said it was about increased audience. In part because of the expansion of communications technologies.  But mainly because of the dependence of national renewal on finding an enemy we can all share. Doesn&amp;#39;t happen in Canada.  I think Montreal was different. They were all women.&#13;
&#13;
Today I am at UVA with my son, Michael, hosted by Admissions. Having two kids go here split my identity between my institution and its rival. Today is different.  Orange and maroon everywhere. A memorial site where many students are writing letters to Tech students. All stop at noon as the Chapel bell slowly tolls 33 times. I read that many of the candles at Tuesday&amp;#39;s vigil came from UVA.  Every time I see the Hoos for Hokies sign, I cry.  And I&amp;#39;ve never considered myself a Hokie. I&amp;#39;ve learned this week that I am indeed Virginia Tech.&#13;
&#13;
Higher education can no longer be called sanctuary.  Virginia Tech is of the world. Our theory must catch up.&#13;
&#13;
 &#13;
&#13;
Saturday&#13;
&#13;
One of my daughters, Megan, has flown in.  Telephone, email, and obsessive reading had not been enough.  She needed to be here.  The father of the Blacksburg girl who died wrote an open letter to the community inviting us to cherish the memories we&amp;#39;re creating with our loved ones, for one day that&amp;#39;s all we might have.&#13;
&#13;
I bought a Virginia Tech tshirt for the first time.&#13;
&#13;
Marta and I hosted a gathering for STS families.  Megan, Leah, and Michael did all the work while Marta and I attended the memorial service for G.V.  His graduate students called him Gobichettypalayam Vasudevan, his name.  We shared the food all had brought.  The youngest kids chased our cats. We talked. We laughed. We discussed what to do in class the first day back. &#13;
&#13;
 &#13;
&#13;
Sunday&#13;
&#13;
Last night I was told that after killing G.V. and the woman sitting closest to the door, the shooter ordered the civil engineering grad students to put their heads down on their desks.  He then put three bullets into each head.  In the French class, the shooter left and came back.  The wounded teacher tried to hold the door shut with a table, unsuccessfully. &#13;
&#13;
I signed the petition supporting Charles Steger and Wendell Flinchum.&#13;
&#13;
Tomorrow is the oral defense of a Ph.D. qualifying exam.  I&amp;#39;m on the committee.&#13;
&#13;
 &#13;
&#13;
Thursday&#13;
&#13;
My biggest difficulty has been accepting the ambiguity.  My career is about pursuing ambiguity, confronting ambiguity, wrestling with ambiguity, interpreting ambiguity, constructing narratives about ambiguity.  But always ambiguity as object, external challenge, something to figure out.  The deep, abiding acceptance of ambiguity is another thing altogether.  I&amp;#39;m not so good at that.  It came to a head for me yesterday at the crowded memorial gathering for the two faculty and fifteen students in the Department of Foreign Languages and Literatures.  Fifteen kids extending themselves past their boundaries, learning another language, led forward by teachers with relentless, sometimes infuriating, enthusiasm. &#13;
&#13;
Yet the acceptance of ambiguity just may be serving as the vehicle of new community around here.  I&amp;#39;ve always defined community as sharedness that is the product of work, sharedness that assumes initial difference.  This week the regular boundaries among us have blurred, if only temporarily, and everyone everywhere seems to be reveling in the joys of simple encounters, recognizing and acknowledging their privilege.  A staff member brings her toddler and her dog to the office, to the celebration of all.  A dean and a provost feel liberated to openly express and share emotion.  The horror is starting to become a thing.  It&amp;#39;s not going away, nor will it be explained.  Sharedness seems to lie in our diverse struggles to accept.&#13;
&#13;
 &#13;
&#13;
&#13;
Friday&#13;
&#13;
I played basketball today.  Lost all three games.  It was wonderful.&#13;
&#13;
 &#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9200">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12693">
                <text>some thoughts (April 16-27, 2007)</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="191">
        <name>account</name>
      </tag>
      <tag tagId="209">
        <name>faculty</name>
      </tag>
      <tag tagId="212">
        <name>journal</name>
      </tag>
      <tag tagId="186">
        <name>reflection</name>
      </tag>
      <tag tagId="194">
        <name>story</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="378" 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="1720">
                <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="3611">
                <text>Ryan Lanham </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="5589">
                <text>2007-06-05</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7467">
                <text>April 18th, 2007 by &lt;a href="http://ryanlanham.wordpress.com/author/ryanlanham/"&gt;Ryan Lanham&lt;/a&gt;&#13;
&#13;
I know very little about profoundly deviant behavior of this sort. It has never much interested me. I tend to turn off the channels where it is dealt with.&#13;
&#13;
I have extended familial ties to some protracted and difficult cases but rarely anything profoundly deviant like this. I have also had many friends and acquaintances who cope with various forms of mental illness in their relationships both near and extended. But this seems to be of a different sort...I think. I so far believe it isn&amp;#39;t a "9" on a scale where many folks are showing up at the mental health center with a level 4 or 5 problem. But on that I may be sadly wrong. Things erode rapidly sometimes. Tear out hope from people and prospects go decay in a hurry. But people are usually self-destructive first...not outwardly destructive. Something is different when people need to spread a blight.&#13;
&#13;
It seems to me that the Virginia Tech murderer reached several cross-over points. For example, he constructed an identity of persecution. I am sure he had opportunities to back out of this, but he chose not to. He wanted to be persecuted. I notice this desire in many larger groups...sometimes whole nations. It is a need to be selected as a target of unfairness. At some level we all feel it. It is very hard to look for a job, for example, in academia without some sense of constant rejection. Maybe it is luck to get help or a positive turn, and some folks just aren&amp;#39;t lucky. Maybe Cho never got cut a break. But it seems like he did get at least a few breaks to hear it from his roommates. He CHOSE to not find happiness.&#13;
&#13;
Perhaps that paranoia is an element of a broader delusional identity, but all that sounds annoyingly redundant. I must say that the psychological descriptions of these things feel inadequate. It is as if there are things unsaid or said as categorizations that seem deficient to offer any insight beyond a label. There is a Peanuts cartoon with Lucy psychoanalyzing Charlie Brown&amp;#39;s fears. She says that if we can find out what he is afraid of..."we" can label it. It ends there to some ironic comic effect.  The label is all Charlie Brown is going to get.  DSM IV is my sister-in-law&amp;#39;s bible on these things.  I have seen her read it at length.  But from what I have seen of it, it is often very uncertain and highly generalized in its descriptions.  Can anyone be paranoid on a given day?   I often wonder whether people who are less than nice all the time carry the burden of common labels.   Identity is profound in all these cases.&#13;
&#13;
Universities clearly gather many people who are loners, focused, obsessive, and often politically extreme. But violence is not the usual outlet, so far as I can tell. I think I have read that suicides are typically higher amongst graduate students than the norm, but that might be also readily expected from the stress. One sees faculty and students alike who demonstrate all sorts of unsual forms of expression or self-awareness. Sometimes it comes as a rarified sense of aesthetic or insight. Other forms come as a need to be "in" or considered "bright." Some thrive on power or influence over others as a teacher or mentor or special peer. Still other forms come as a need to be considered of a particular ethical purity. Usually it is exacting in my experience. There is a need for precision far beyond what could be taken as usual or appropriate.&#13;
&#13;
This sort of intensity is a form of boundary spanning that can be innovative if benign. Or it can be destructive, and often minimally policed. Given the general collapse of collective standards in the academy, I think these sorts of explosions are my likely than we&amp;#39;d like to think. I also think they are playing out in mini versions all too often. But people find means of coping and controlling themselves. Here that control was not present. An artist or innovator must also loosen the bounds of control, but there is a commitment to not hurt. It is almost like the difference between the responsible community business person and the naked aggression of a self-serving capitalist. There is a different...ethic. But is there a different psychology? And what would that mean?  The identity is formed as it encounters situations.  Context is everything...but also not everything.  We must know actors, actor prior states, and contexts.  But perhaps we must also know context prior states.  It is difficult to say the least.&#13;
&#13;
Original source: &lt;a href=" http://ryanlanham.wordpress.com/2007/04/18/some-thoughts-on-the-cho-identity-and-mass-murder/"&gt; http://ryanlanham.wordpress.com/2007/04/18/some-thoughts-on-the-cho-identity-and-mass-murder/&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href=" http://creativecommons.org/licenses/by-sa/3.0/"&gt;Creative Commons Attribution-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="9438">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12901">
                <text>Some thoughts on the Cho identity and mass murder</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="83">
        <name>blog</name>
      </tag>
      <tag tagId="323">
        <name>cho</name>
      </tag>
      <tag tagId="359">
        <name>identity</name>
      </tag>
      <tag tagId="467">
        <name>lanham</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="231" 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="1586">
                <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="3477">
                <text>lithiumfailed / MayB</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="5455">
                <text>2007-05-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7334">
                <text>I woke up today&#13;
&#13;
This mirror doesn&amp;#39;t reflect me&#13;
No one that I know of&#13;
Has time passed so quickly?&#13;
Did you give the final shove?&#13;
&#13;
Save us from evil&#13;
Save us from evil&#13;
&#13;
Is this what I&amp;#39;ve become?&#13;
A heart left untouched&#13;
My wounds have come undone&#13;
I hold your lives in a clutch&#13;
&#13;
((Save us from evil))&#13;
And all I have to say&#13;
((Save us from evil))&#13;
Is that I never walked that way&#13;
((Save us from evil))&#13;
Can the night save the day?&#13;
((Save us from evil))&#13;
I woke up today&#13;
&#13;
Is this the end of me?&#13;
And all I&amp;#39;d hoped to be?&#13;
I can only save myself&#13;
Through the blood of someone else&#13;
&#13;
((Save us from evil)&#13;
I cannot walk this way&#13;
((Save us from evil))&#13;
I will not live to say&#13;
((Save us from evil))&#13;
That I walked that way&#13;
((Save us from evil))&#13;
I can&amp;#39;t wake up today&#13;
&#13;
And all this pain I see&#13;
Reflects right back at me&#13;
I&amp;#39;ve been where you were before&#13;
But I ignored that door&#13;
&#13;
((Save us from evil))&#13;
I&amp;#39;m proud to say&#13;
((Save us from evil))&#13;
I never walked that way&#13;
((Save us from evil))&#13;
I&amp;#39;ve finally found my day&#13;
((Save us from evil))&#13;
My eyes are open today&#13;
&#13;
Save us from evil&#13;
I woke up today&#13;
&#13;
--&#13;
&#13;
&lt;b&gt;Author&amp;#39;s Comments&lt;/b&gt;&#13;
&#13;
Inspired by the events at Virginia Tech. Rest in peace :heart:&#13;
&#13;
MayB&#13;
&#13;
--&#13;
&#13;
Original submitted to deviantart.com on April 18, 2007: &lt;a href="http://www.deviantart.com/deviation/53516419/"&gt;http://www.deviantart.com/deviation/53516419/&lt;/a&gt;&#13;
&#13;
Licensed under a &lt;a href="http://creativecommons.org/licenses/by-nc-nd/2.5/"&gt;Creative Commons Attribution-Noncommercial-No Derivative Works 2.5 License&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9304">
                <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="11314">
                <text>Creative Commons Attribution-Noncommercial-No Derivative Works 2.5 License</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12781">
                <text>SONG: 'That Way' by lithiumfailed</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="150">
        <name>poem</name>
      </tag>
      <tag tagId="151">
        <name>poetry</name>
      </tag>
      <tag tagId="325">
        <name>song</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1103" public="1" featured="0">
    <fileContainer>
      <file fileId="560">
        <src>https://www.april16.vtlibraries.net/files/original/F200704180757522799116952_7661f71670.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="14943">
                    <text>2007-08-15</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="16063">
                    <text>2007-08-15 17:00: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="2403">
                <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="4294">
                <text>çŽ¯çƒåœ¨çº¿</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="6272">
                <text>2007-08-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8150">
                <text>People mourned for the victims on the drillfield.  Vigil on April 17&#13;
&#13;
Original Source:hqchinadaily.cn&#13;
&#13;
&lt;a href="http://egsky.cn/default.asp?distype=normal&amp;tag=%E7%BE%8E%E5%9B%BD"&gt;http://egsky.cn/default.asp?distype=normal&amp;tag=%E7%BE%8E%E5%9B%BD&lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10121">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13521">
                <text>Sorrowful moment</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
      <tag tagId="14">
        <name>virginia tech</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1096" public="1" featured="0">
    <fileContainer>
      <file fileId="553">
        <src>https://www.april16.vtlibraries.net/files/original/deaabbd0d661055f1669a7eefa9d9fb0_fb34f829ea.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="14936">
                    <text>2007-08-15</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="16056">
                    <text>2007-08-15 14:16:36</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2396">
                <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="4287">
                <text>Yucheng Ying</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="6265">
                <text>2007-08-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8143">
                <text>Numerous people visited the Hokie stone memorial site on the drillfield.  They placed flowers and gifts around this memorial site.  We will always remember the victims.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10114">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13514">
                <text>Sorrowful people on the drillfield</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="372">
        <name>Hokie stone</name>
      </tag>
      <tag tagId="1529">
        <name>memorial stone</name>
      </tag>
      <tag tagId="1088">
        <name>victims</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1438" 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="2684">
                <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="4575">
                <text>Kang Shin-who</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="6553">
                <text>2007-10-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8431">
                <text>By Kang Shin-who&#13;
Staff Reporter&#13;
&#13;
Virginia Tech (VT) students didn&amp;#39;t want to think about the massacre incident any more during the press conference with Korean media. &#13;
&#13;
Eighteen students and two professors of the school visited Konkuk University on Tuesday where they will attend summer school programs for a month.&#13;
&#13;
When it came to the shooting rampage by a South Korean immigrant student, they were firm in not talking about the past, saying none of them personally knew the killer or were at the scene of the crime.&#13;
&#13;
``We do not judge Korea on the actions of one. We really ask that the media respect our grieving process,&amp;#39;&amp;#39; said Adnan Barqawi, 19, who is studying accounting and information system at VT. ``I personally lost two friends during the incident, I think that being on my own and being with my friends is what is going to help me.&amp;#39;&amp;#39;&#13;
&#13;
``Coming to Korea happened because this is a part of my education. We have an increasing participation of the people of this world. My intention is not to stop my education because of adversity. I am here to learn and pursue my education,&amp;#39;&amp;#39; Adnan added.&#13;
&#13;
All students were wearing maroon and orange ribbons on their shirts. Asked the meaning of the ribbons, Cheryl Tait, 22, said that they represent the support of VT from all the universities in the United States. ``The ribbons symbolize our hope and all the support for one another,&amp;#39;&amp;#39; she said.&#13;
&#13;
Instead, VT members were excited about their new experience in Korea and wanted to talk about the programs they are scheduled to take part in here. &#13;
&#13;
``This study abroad program was planned before the shooting. The students signed up and although they could have cancelled their decision to come, none of them did,&amp;#39;&amp;#39; VT professor Devi Gnyawali said. ``The study abroad program is a joint one with Japan and Korea. To learn about the culture and to tour various Korean companies for example Samsung and Hyundai, we came here.&amp;#39;&amp;#39;&#13;
&#13;
Lastly, they confirmed that the brutal incident will not affect Korean people at all. ``Generalizing a group of people because of the action of one person, in my opinion, would be wrong because Cho was sick, he had mental illness which could effect everyone and so I think to associate Koreans with ill will is wrong,&amp;#39;&amp;#39; said Daniel Lesneski, 20, who is studying finance.&#13;
&#13;
``I agree with Daniel, I am a Korean American and I know from personal experience there was no hostility toward us _ we are a big community and no one was singled out,&amp;#39;&amp;#39; said Elizabeth Chin, 20, who is majoring in accounting.&#13;
&#13;
kswho@koreatimes.co.kr&#13;
&#13;
Jung Joo-yang, Joan Kim, Korea Times interns, contributed to this article.&#13;
&#13;
--&#13;
&#13;
Original Source: Korea Times&#13;
&lt;a href="http://www.koreatimes.co.kr/www/news/nation/nation_view.asp?newsIdx=3760&amp;categoryCode=117&#13;
"&gt;http://www.koreatimes.co.kr/www/news/nation/nation_view.asp?newsIdx=3760&amp;categoryCode=117&lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10402">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13752">
                <text>Sour Memory Disturbs Va. Tech Students</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1801">
        <name>korea times</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1949" public="1" featured="0">
    <fileContainer>
      <file fileId="920">
        <src>https://www.april16.vtlibraries.net/files/original/2356328702_e95677e2c3_b-1_e1a816bc95.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="15278">
                    <text>2008-03-26</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="16398">
                    <text>2008-03-26 16:46:23</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="2958">
                <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="4849">
                <text>Rachel VanPelt</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="6827">
                <text>2008-03-26</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8705">
                <text>Free seat cushions given out at Yankees vs. Hokies baseball game on March 18,2008.&#13;
&#13;
Photo by Rachel VanPelt&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.flickr.com/photos/hokiefacs/2356328702/in/set-72157604217657636/"&gt;http://www.flickr.com/photos/hokiefacs/2356328702/in/set-72157604217657636/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10676">
                <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="12303">
                <text>Rachel VanPelt (rvanpelt@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14021">
                <text>Souvenir seat cushion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="2065">
        <name>baseball game</name>
      </tag>
      <tag tagId="2089">
        <name>seat cushion</name>
      </tag>
      <tag tagId="2088">
        <name>souvenir</name>
      </tag>
      <tag tagId="2064">
        <name>yankees</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1072" 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="2372">
                <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="4263">
                <text>Matt Sohn</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="6241">
                <text>2007-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8119">
                <text>By: Matt Sohn&#13;
Posted: 4/20/07&#13;
Nobody&amp;#39;s quite sure what to expect when the Miami University football players don the Red and White for Friday&amp;#39;s annual spring scrimmage. On the one hand, injuries have continued to decimate a team still smarting from its 2-10 campaign of 2006, but on the other hand, the RedHawks return the core of the fastest team in the MAC.&#13;
&#13;
The question of whether they&amp;#39;re reeling or ready will soon be answered.&#13;
&#13;
No such questions exist for the football team of Virginia Tech. Led by one of the nation&amp;#39;s elite defenses, the Hokies stand as the overwhelming favorite to win the ACC next season.&#13;
&#13;
Thousands of fans were expected to pack Lane Stadium for Saturday&amp;#39;s spring game in anticipation of a banner season in Blacksburg, Va. But, because of a cascade of bullets that ripped through the heart of the Hokie nation, no such game will be played.&#13;
&#13;
Shouts of "Hokie Hokie Hokie High!" have been replaced by the tearful hysteria of a campus coming to grips with the fact that their lives will never be the same.&#13;
&#13;
When looking back at my college career, the one constant I could always count on was change. Midway through my first year, I was assigned a new roommate. I&amp;#39;ve switched my major. I&amp;#39;ve fallen in love and have had my heart broken. I&amp;#39;ve been praised for my writing and have received hate mail.&#13;
&#13;
Nowhere has the concept of change been more pervasive than in the world of sports.&#13;
&#13;
As a wide-eyed first-year in 2002, I was among the tens of thousands in the Yager Stadium bleachers as Miami was just a few minutes shy of toppling an Iowa team that would go undefeated in Big Ten play. Two years ago, I was one of just a couple hundred to witness Bowling Green pound the RedHawks in a 42-14 romp in tornado-like conditions. I&amp;#39;ve seen the North Dakota hockey team shut Miami out in the opening game of 2005, only to watch Miami climb to No. 1 in the polls later that season. There was the nostalgic farewell to Goggin, the groundbreaking of the Steve Cady Arena and hard times on the hardwood followed by Doug Penno&amp;#39;s heroism.&#13;
&#13;
In sports and in life, hope springs eternal.&#13;
&#13;
So what do you say to a Virginia Tech community whose indelible image of college is that of their classmates, friends, professors and lovers senselessly slaughtered? How does a mother cope with seeing her son&amp;#39;s farewell to Blacksburg be in a body bag instead of on a graduation podium? The sad truth is that for the grieving Hokie family, there&amp;#39;s no salve for their wound.&#13;
&#13;
Even with all the advancements in medical science, there&amp;#39;s no painkiller for this kind of hurt - no stadium construction, buzzer-beater or championship ring that will ever change the reality of those dealing with premature death.&#13;
&#13;
What these men and women can do is remind themselves that to make the most of every moment as the universal healing power of time runs its course.&#13;
&#13;
A similar lesson applies to everyone, everywhere. For those of us biding our final days in Oxford, let&amp;#39;s not bemoan our imminent departure, but rather celebrate our journey. For those continuing your collegiate experience, make plans for making the most of your time here.&#13;
&#13;
And this is where the beauty of sport lies for everybody. For the majority of us, our life&amp;#39;s course won&amp;#39;t be affected by athletics. It won&amp;#39;t give us a raise or get us fired, won&amp;#39;t find us happiness or despair in romance, nor will it ease the agony from the families of Virginia Tech and others coping with tragedy.&#13;
&#13;
What it can do, however, is provide us with a needed respite from the constant grind of life. When the Hokie football team storms the field Sept. 1 for its season-opening clash with Eastern Carolina, nobody will forget the massacre that afflicted their campus months earlier. But, for a three-hour stretch on a Saturday afternoon, they can turn their attention away from grief, schoolwork and jobs, and onto the raucous adulation that transpires on the field.&#13;
&#13;
As Tom Cochran&amp;#39;s song reminds us, "Life is a highway," and as sports remind us, there are many rest stops along the way.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.miamistudent.net/media/storage/paper776/news/2007/04/20/Sports/Sports.Can.Help.Ease.Pain.At.Vt-2870599.shtml&gt;The Miami Student - 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="10090">
                <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="11182">
                <text>The Miami Student</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11987">
                <text>"Skotzko, Stacey Nicole" &lt;skotzksn@muohio.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13491">
                <text>Sports can help ease pain at VT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="717">
        <name>grief</name>
      </tag>
      <tag tagId="654">
        <name>healing</name>
      </tag>
      <tag tagId="1107">
        <name>miami university</name>
      </tag>
      <tag tagId="605">
        <name>sports</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1703" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  Note that facsimiles or images of texts are still of the genre text.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2844">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4735">
                <text>Patrick Southern</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6713">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8591">
                <text>Issue Date:Friday April 20, 2007   &#13;
Section: Sports Section&#13;
Patrick Southern, Sports Writer&#13;
&#13;
Sometimes it takes a life-changing event to shake you to your very core and remind you what really matters.&#13;
&#13;
For the countless people who are suffering in ways that defy comprehension following the stunning events at Virginia Tech, that lesson came in the toughest form possible.&#13;
&#13;
While I&amp;#39;m fortunate that I don&amp;#39;t have to mourn the loss of any personal friends or family, I sincerely feel the pain of those who do.&#13;
&#13;
As DA Sports Editor Tim Tassa eloquently said in his Tuesday column, such tragedies "make sports seem so petty, so irrelevant."&#13;
&#13;
It&amp;#39;s cliche to say so, but it&amp;#39;s true. I know that by noon on Monday, I cared a lot less about how my Boston Red Sox would fare in their Patriots Day game against the Angels than I had when I woke up.&#13;
&#13;
In the wake of the campus shooting, the Hokies called off the remainder of their spring football drills and canceled all sporting events scheduled for the following days.&#13;
&#13;
These moves were in the best interest of all involved. At that point, no one needed the distraction of competition when the hearts and minds of all of those at VT were elsewhere.&#13;
&#13;
After all, athletes and coaches deserve the chance to grieve too.&#13;
&#13;
However, the moratorium on athletics at Virginia Tech ends today, when the school&amp;#39;s baseball squad hosts Miami.&#13;
&#13;
To most, this event will mean little in light of the heartache the community has suffered. After all, college baseball games go on every day nationwide at this time of year.&#13;
&#13;
But in this case, the ping of the aluminum bat and the unmistakable snap of a solid fastball against a catcher&amp;#39;s mitt will be the first sound of life beginning to return to normal in Blacksburg.&#13;
&#13;
While it&amp;#39;s true that tragedy makes us realize how meaningless the wins and losses of our teams really are, it&amp;#39;s every bit as true that athletics are a significant part of our lives.&#13;
&#13;
Sporting events are more than just a good excuse for people to get together and drink a few beers while debating the merits of blitzing off the edge on third and long.&#13;
&#13;
No, in times like this, we&amp;#39;re reminded that sports are so important to us because they&amp;#39;re a sure sign of normal life in abnormal times.&#13;
&#13;
It&amp;#39;s that importance that made renditions of "The Star-Spangled Banner" and "God Bless America" take on such added meaning at baseball games following the attacks of 9/11.&#13;
&#13;
And it&amp;#39;s the sense of unity and togetherness that sports foster that led the thousands of mourners at Virginia Tech&amp;#39;s memorial convocation Tuesday to ditch button-down shirts and dress slacks in favor of their favorite maroon and orange Hokie T-shirt.&#13;
&#13;
When those in attendance at that same service struggled to express themselves beyond their tears, they went back to the same cheers that echo through Lane Stadium on any given Saturday in the fall.&#13;
&#13;
The mourners&amp;#39; chants of "Let&amp;#39;s go, Hokies" reverberated through Cassell Coliseum, punctuated with the rhythmic clapping and repetition that is typically better suited to sporting events than soul-searching.&#13;
&#13;
But in that moment, for those who gathered to find a sense of community when pain seemed poised to take over their lives, those three simple words took on all the meaning of a chorus of "Amazing Grace."&#13;
&#13;
Instead of rallying their athletic heroes to another victory, the Virginia Tech faithful were chanting to rally their own flagging spirits.&#13;
&#13;
It&amp;#39;s easy for us to make sports trivial in the wake of traumatic events, because tragedy always makes us step back and evaluate our priorities in life.&#13;
&#13;
But for the thousands of VT students who are longing for some sense of "normal," today&amp;#39;s first pitch is the first small step back toward simpler times in Blacksburg.&#13;
&#13;
Let&amp;#39;s go, Hokies.&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27626"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27626&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10562">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12202">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13908">
                <text>Sports for the soul</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1977">
        <name>9/11</name>
      </tag>
      <tag tagId="605">
        <name>sports</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="876" 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="2185">
                <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="4076">
                <text>Eric Kolenich</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="6054">
                <text>2007-07-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7932">
                <text>&lt;b&gt;Web sites such as Thesabre.com, Techsideline.com provide forum for discussion, communication after yesterday morning&amp;#39;s shootings at Virginia Tech&lt;/b&gt;&#13;
&#13;
Eric Kolenich, Cavalier Daily Senior Associate Editor&#13;
&#13;
In the wake of yesterday&amp;#39;s tragedy at Virginia Tech, online sports message boards served a more important purpose, providing an outlet for people to report information about the shootings that killed 33 people.&#13;
&#13;
With cell phone coverage limited yesterday in the Blacksburg area, many turned to sports message boards to communicate news reports as well as personal reactions to the day&amp;#39;s events. In fact, the two largest message boards for Virginia and Virginia Tech sports -- Thesabre.com and Techsideline.com -- have become completely devoted to discussion of the shootings.&#13;
&#13;
Sabre administrators posted a message on the Tech site to inform users that the message boards could help facilitate dialogue and updates about the shootings.&#13;
&#13;
"We at The Sabre understand that you may have periodic problems accessing the TSL and VT Web sites," the message stated. "When this happens, you are welcome to use TheSabre.com&amp;#39;s off-topic message board to communicate and retrieve necessary information on today&amp;#39;s tragic events. You have our support and prayers during this trying time. Please pass the link around to your friends."&#13;
&#13;
News of the shootings first spread on the two boards around noon yesterday.&#13;
&#13;
"Breaking news -- shooting on VT campus!" one user wrote.&#13;
&#13;
Soon after, a number of bloggers reported the status of family and friends at Tech.&#13;
&#13;
"All family members at VT accounted for. I&amp;#39;m praying hard for others less fortunate," one said.&#13;
&#13;
Some individuals also expressed relief upon learning that loved ones had not been victimized.&#13;
&#13;
"Little bro is ok..... phew..... locked down in one of the dorms...," another wrote.&#13;
&#13;
Many posted information reported on news broadcasts and gave their own reactions to the shootings. Soon, sports conversation had ceased altogether.&#13;
&#13;
"Everyone is a Hokie today," another blogger wrote. One Virginia fan suggested that Virginia students wear maroon and orange in support of Tech students and families.&#13;
&#13;
As the day progressed, the two sites were crowded with comments expressing the powerful emotion evoked across the country. Commentary touched on the political fallout of the killings, as many users posted messages conveying frustration with reporters and pundits who accused Tech administrators of mishandling the tragedy as it unfolded.&#13;
&#13;
Fans from other schools have used the message boards as a platform to offer their prayers to Virginia Tech, while local communities of Hokies across the country announced planned vigils.&#13;
&#13;
"What a horrendous day for not only Virginia Tech but the entire state," wrote one blogger on the Tech Sideline site. "You can count on prayers from Lynchburg from the Liberty University family for all of the victims, their families and friends."&#13;
&#13;
Virginia students also posted messages relaying information about vigils to be held around Grounds this week.&#13;
&#13;
Cavalier fans have put their rivalry aside and are calling themselves "brothers" with fellow students and alumni at Virginia Tech.&#13;
&#13;
"Never thought I&amp;#39;d say this, but Go Hokies," wrote one blogger on the Sabre board.&#13;
&#13;
Virginia Tech has canceled all athletic activities today. Neither the University nor the ACC have announced any plans to cancel other athletic events. &#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.cavalierdaily.com/CVArticle.asp?ID=30164&amp;pid=1582&gt;The Daily Cavalier - April 17, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9903">
                <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="11127">
                <text>The Cavalier Daily </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11830">
                <text>Meggie Bonner &lt;meggiebonner@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13320">
                <text>Sports message boards find new use after tragedy</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="429">
        <name>message boards</name>
      </tag>
      <tag tagId="605">
        <name>sports</name>
      </tag>
      <tag tagId="157">
        <name>sympathy</name>
      </tag>
      <tag tagId="72">
        <name>uva</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="352" 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="1696">
                <text>Elliott Gordon</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3587">
                <text>Elliott Gordon</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="5565">
                <text>2007-06-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7443">
                <text>"I belong."&#13;
&#13;
I still remember vividly that emotion as I stood outside Burress Hall overlooking the gorgeous, expansive view of the Virginia Tech campus on a cool, sunny morning back in the spring of 1990. It was college-tour season for graduating high-school seniors, and I had found my home for the next four years.&#13;
&#13;
The tragedy this past week has only deepened and strengthened my affection for the university. Once a Hokie, always a Hokie.&#13;
&#13;
A lot has been vocalized and written by alumni, students, friends, business leaders, politicians, athletes, the media -- really anyone with a shred of a tie to Blacksburg -- about how tranquil and safe and welcoming the campus and surrounding community has always been. And they are not exaggerating.&#13;
&#13;
Virginia Tech and the city of Blacksburg are synonymous. Graduates own local businesses. Former students now teach. Former athletes now coach.&#13;
&#13;
This part of the country used to be just Hokie Nation -- now it is Hokie Nationwide.&#13;
&#13;
The nationwide reaction to this senseless tragedy has also crystallized for me how in a time of grief -- even if just for a few, fragile hours -- sports provides an outlet and plays a role on the road to recovery. The outpouring of support has raised school spirits during this dark time.&#13;
&#13;
I applaud the Washington Nationals for donning Virginia Tech caps during their game Tuesday, caps that will now take a spot in the Baseball Hall of Fame next to its 9/11 memorial.&#13;
&#13;
I applaud NASCAR for placing memorial, VT logo decals on the cars, especially given the deep roots many of the teams and drivers have with that region of the country.&#13;
&#13;
I applaud Atlanta Falcons QB Michael Vick -- arguably the most popular and well-known athlete ever to wear a Virginia Tech jersey -- for his generous donation to the university for the victims families.&#13;
&#13;
And I applaud coach Frank Beamer for his cancellation of the traditional Maroon and White Football game. He is a class act, emphasizing the need to heal before you hooray -- and I guarantee you this fall when the first few cords of Enter Sandman blare throughout Lane Stadium for the opening home game of the season, those tears you see will once again be for joy.&#13;
&#13;
But for now we work to dry the tears of sorrow, knowing that Virginia Tech and its local and extended community will never be the same. This could have happened to anyone, in any town, at any school, at any time -- but it happened at my school, where not so long ago I was the one walking across campus to Norris Hall for class. And while I did not personally know any of the victims, the entire Hokie Nation has been victimized.&#13;
&#13;
And now, as the entire world watches, the international community is realizing that Hokie resolve is as strong as the stone that bares its name -- stone that has been used for more than 130 years to build the campus and community.&#13;
&#13;
The memories and images of this tragic event will forever scar, and we will never forget, but my personal resolve to one day have my children stand on those same steps outside Burress Hall as I did has not wavered.&#13;
&#13;
We are Virginia Tech.&#13;
&#13;
Elliott Gordon graduated Virginia Tech in 1994. He was NASCAR.COM&amp;#39;s Director of Programming from 2001-2006. &#13;
&#13;
--&#13;
&#13;
As posted on NASCAR.COM on April 20th, 2007: &#13;
&lt;a href="http://www.nascar.com/2007/news/opinion/04/20/guest.column.virginia.tech/story_single.html"&gt;http://www.nascar.com/2007/news/opinion/04/20/guest.column.virginia.tech/story_single.html&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9414">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12880">
                <text>Sports world reaches out, helps Virginia Tech cope</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="84">
        <name>alumni</name>
      </tag>
      <tag tagId="441">
        <name>collegiate times</name>
      </tag>
      <tag tagId="440">
        <name>nascar</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="699" public="1" featured="0">
    <fileContainer>
      <file fileId="410">
        <src>https://www.april16.vtlibraries.net/files/original/IMG_5947_f1fb1be678.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="14798">
                    <text>2007-07-11</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15918">
                    <text>2007-07-11 15:40:26</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2021">
                <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="3912">
                <text>Jarrod Miller</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="5890">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7768">
                <text>Squires Student Center is filled with posters, message boards, flowers, and other items that universities, businesses, and other places around the country have sent to Virginia Tech.&#13;
&#13;
Orginial Source: &lt;a href=" http://www.flickr.com/photos/soilrocks/468955846/in/photostream/"&gt;http://www.flickr.com/photos/soilrocks/468955846/in/photostream/&lt;/a&gt;&#13;
&#13;
Photo courtesy of Jarrod Miller&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9739">
                <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="11721">
                <text>Permission:&#13;
Jarrod Miller&#13;
Jarrod@uky.edu</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13166">
                <text>Squires Hall</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="429">
        <name>message boards</name>
      </tag>
      <tag tagId="113">
        <name>messages</name>
      </tag>
      <tag tagId="430">
        <name>squires student center</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="337" public="1" featured="0">
    <fileContainer>
      <file fileId="231">
        <src>https://www.april16.vtlibraries.net/files/original/VT Remembers 138_cb00021e8e.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="14628">
                    <text>2007-06-01</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="15748">
                    <text>2007-06-01 11:14: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="1686">
                <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="3577">
                <text>Frank Eak</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="5555">
                <text>2007-06-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7433">
                <text>Squires Student Center is filled with posters, message boards, flowers, and other items that universities, businesses, and other places around the country have sent to Virginia Tech.&#13;
&#13;
Original source: &lt;ahref=" http://www.imagestation.com/album/pictures.html?id=2093007661"&gt; http://www.imagestation.com/album/pictures.html?id=2093007661&lt;/a&gt;&#13;
&#13;
Photo Courtesy of Frank Eak&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9404">
                <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="11405">
                <text>Permission:&#13;
Frank Eak&#13;
feak@va.metrocast.net</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12871">
                <text>Squires Student Center</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="117">
        <name>squires</name>
      </tag>
      <tag tagId="430">
        <name>squires student center</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="338" public="1" featured="0">
    <fileContainer>
      <file fileId="232">
        <src>https://www.april16.vtlibraries.net/files/original/VT Remembers 149_fbcdbcf0d1.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="14629">
                    <text>2007-06-01</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="15749">
                    <text>2007-06-01 11:17:41</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="1687">
                <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="3578">
                <text>Frank Eak</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="5556">
                <text>2007-06-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7434">
                <text>Squires Student Center is filled with posters, message boards, flowers, and other items that universities, businesses, and other places around the country have sent to Virginia Tech.&#13;
&#13;
Original source: &lt;ahref=" http://www.imagestation.com/album/pictures.html?id=2093007661"&gt; http://www.imagestation.com/album/pictures.html?id=2093007661&lt;/a&gt;&#13;
&#13;
Photo courtesy of Frank Eak&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9405">
                <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="11406">
                <text>Permission:&#13;
Photo courtesy of Frank Eak&#13;
http://www.imagestation.com/album/pictures.html?id=2093007661&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12872">
                <text>Squires Student Center</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="431">
        <name>sacramento state</name>
      </tag>
      <tag tagId="117">
        <name>squires</name>
      </tag>
      <tag tagId="430">
        <name>squires student center</name>
      </tag>
      <tag tagId="383">
        <name>university memorial</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="552" public="1" featured="0">
    <fileContainer>
      <file fileId="348">
        <src>https://www.april16.vtlibraries.net/files/original/P1000815_204fe3eda0.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="14741">
                    <text>2007-06-17</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="15861">
                    <text>2007-06-17 20:32:52</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="1881">
                <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="3772">
                <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="5750">
                <text>2007-06-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7628">
                <text>Ryan "Stack" Clark&amp;#39;s Hokie Stone memorial on the drillfield. The victim memorials continue to evolve, with new items, tributes, and flowers being added all the time. Photo taken Thursday, June 14.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9599">
                <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="11587">
                <text>Creative Commons Attribution-NonCommercial-ShareAlike 3.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13043">
                <text>Stack&amp;#39;s Stone</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="426">
        <name>clark</name>
      </tag>
      <tag tagId="372">
        <name>Hokie stone</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="367">
        <name>ryan clark</name>
      </tag>
      <tag tagId="668">
        <name>stack</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1680" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  Note that facsimiles or images of texts are still of the genre text.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2822">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4713">
                <text>Editorial Staff</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6691">
                <text>2008-02-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8569">
                <text>By&#13;
PUBLISHED APRIL 17, 2007&#13;
&#13;
On Monday morning, 32 students at Virginia Tech were killed and about 30 others injured by a shooting at the hands of a fellow student. This tragedy raises questions about the nature of events like this and what Columbia might do in a similar situation. Yet the administration was slow in publicly responding to the event, and when it did, it failed to address the crucial question about what the University&amp;#39;s response plan would be. The University should have expressed its sympathy, explained the counseling options available to students, and addressed safety concerns on Monday when the shootings occurred.&#13;
&#13;
The tragedy hit especially close to home on campus-first, because the victims were fellow students, and second, because many students here have friends and acquaintances at Virginia Tech. The University&amp;#39;s immediate response should have been to give some notification telling students where they could go for counseling if desired. Tonight a candlelight vigil will be held on Low Steps for the victims, and the Counseling and Psychological Services office will be open until 11 p.m. for students who need its services. This is a good step on the University&amp;#39;s part, but it should have made those resources available more quickly and opened CPS for extended hours.&#13;
&#13;
Questions have also been asked about how effective Virginia Tech officials were in securing the campus after the first round of shooting. Naturally, these questions raise concerns about Columbia&amp;#39;s own emergency management plan and the safety and security of its campus. University of Pennsylvania President Amy Gutmann and Dartmouth College President James Wright have released statements offering condolences to the Virginia Tech community and providing information about the security of their respective campuses, as well as publicizing the counseling services that they have available. University President Lee Bollinger should follow suit and send an e-mail to the entire University explaining the details of its response plan.&#13;
&#13;
Obviously, students do not need the University to hold their hands. But the University does have the responsibility to help them get through tragedies such as this and to encourage them to seek help if needed. Merely informing students more quickly of what counseling options were available would have been of significant help to students, as would have information about what the University would do if a similar crisis occurred here. Tonight at the candle light vigil, Columbia students will come together in solidarity. The University must do the same, providing students help and support.&#13;
&#13;
--&#13;
&#13;
Originial Source: Columbia Spectator&#13;
&lt;a href="http://www.columbiaspectator.com/node/24900"&gt;http://www.columbiaspectator.com/node/24900&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10540">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12181">
                <text>Tom Faure (tomfaure@gmail.com)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13886">
                <text>STAFF EDITORIAL: Providing Comfort</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1922">
        <name>columbia</name>
      </tag>
      <tag tagId="1552">
        <name>counseling</name>
      </tag>
      <tag tagId="1924">
        <name>emergency management plan</name>
      </tag>
      <tag tagId="1923">
        <name>univeristy response</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1265" 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="2534">
                <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="4425">
                <text>Editorial Board</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="6403">
                <text>2007-09-03</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8281">
                <text>By:Editorial Staff&#13;
Posted: 8/29/07&#13;
&#13;
This summer, University Police, in cooperation with Information Services and University Communications, implemented a new software system called UNLAlert, most likely in response to the April shootings at Virginia Tech.&#13;
&#13;
The software, which students can download and install on their computers, communicates with UNL servers to provide alerts and updates in emergency situations. The thinking is that during an emergency, better communication and dissemination of information leads to a safer campus.&#13;
&#13;
We applaud the continuing effort of the university to keep students safe, but the software is by no means an all-inclusive safety net.&#13;
&#13;
Far from it, in fact.&#13;
&#13;
The software isn&amp;#39;t much of an application at all. It&amp;#39;s essentially a stand-alone Flash file - University Police are harnessing the same technology used to bring you online Su-Do-Ku puzzles and amusing "Pac-Man" imitation games.&#13;
&#13;
And it&amp;#39;s big. Really big, actually. Its executable image, the program&amp;#39;s memory footprint, is about 16 megabytes - bigger than AOL Instant Messenger and Mozilla Firefox, both of which are full-fledged desktop applications.&#13;
&#13;
It should come as no surprise, then, that it constantly consumed almost 10 percent of the processing resources on one of our brand new 2.2-gigahertz design computers.&#13;
&#13;
To put that in perspective: Adobe Photoshop, Apple iTunes, and Mozilla Firefox together use less than 3 percent while idle. UNLAlert is no little program that runs in the background.&#13;
&#13;
It&amp;#39;s not a big deal, though, right? Who cares if it slows down your machine a bit - this application could save your life.&#13;
&#13;
Right?&#13;
&#13;
Assuming the two servers that are responsible for handling all the emergency alert requests for the entire campus - alert1 and alert2 - stay online, then yes, it could save your life.&#13;
&#13;
But, after reverse-engineering and analyzing the software, we&amp;#39;re not only disappointed with its performance, we&amp;#39;re disappointed with the way information is being distributed to computers.&#13;
&#13;
Instead of using industry-standard TCP/IP multicast, which allows data to be distributed to all "subscribers" simultaneously, instantly and efficiently, Information Services is using a simple Web server to distribute information.&#13;
&#13;
In an emergency situation, this could lead to heavy network congestion, which could then slow all of our Internet connections on campus to a stand-still.&#13;
&#13;
A slow, unresponsive network probably won&amp;#39;t help emergency responders, university officials, students or staff.&#13;
&#13;
UNLAlert is a great idea that&amp;#39;s been poorly executed.&#13;
&#13;
With a software rewrite and more robust network design, UNLAlert would prove to be a valuable tool. Until then, it might cause more problems than it solves.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailynebraskan.com/media/storage/paper857/news/2007/08/29/Opinion/Staff.Editorial.Unlalert.A.Great.Idea.But.Needs.Some.Work-2941116.shtml&gt;Daily Nebraskan - August 29, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10252">
                <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="11236">
                <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="12086">
                <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="13651">
                <text>STAFF EDITORIAL: UNLAlert a great idea, but needs some work</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1669">
        <name>university of nebraska </name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="498" public="1" featured="0">
    <fileContainer>
      <file fileId="324">
        <src>https://www.april16.vtlibraries.net/files/original/Yale Daily News - Stage weapons ban reversed_ba4df98ee9.pdf</src>
        <authentication>null</authentication>
        <elementSetContainer>
          <elementSet elementSetId="1">
            <name>Dublin Core</name>
            <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
            <elementContainer>
              <element elementId="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14718">
                    <text>2007-06-11</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15838">
                    <text>2007-06-11 23:59:41</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1831">
                <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="3722">
                <text>Sara  Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5700">
                <text>2007-06-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7578">
                <text>Published: Wednesday, April 25, 2007&#13;
&#13;
&#13;
Tyler Hill&#13;
Staff Reporter&#13;
&#13;
After a weekend of national media coverage and student outcry, administrators decided Monday to rescind the ban on stage weapons that was enacted in the wake of the Virginia Tech massacre.&#13;
&#13;
Last week, Dean of Student Affairs Betty Trachtenberg told several students that realistic-looking stage weapons would no longer be permitted in Yale theatrical productions. Amid concerns that the restriction was inhibiting free speech, a group of administrators decided Monday to overturn the policy, Yale spokeswoman Helaine Klasky said. In the future, Yale will require that audiences be warned before performances that include scenes with fake weapons, she said.&#13;
&#13;
Trachtenberg had originally intended to ban all stage weapons, but was persuaded that obviously fake weapons should be permitted, Sarah Holdren &amp;#39;08 told the News last Thursday. Holdren directed this weekend&amp;#39;s production of "Red Noses," which was forced to use wooden swords instead of more realistic props. The restriction also affected the opera "Orpheus in the Underworld," which used balloon swords in place of its real-looking stage weapons.&#13;
&#13;
News of the University&amp;#39;s reversal was only released when a reporter from the Associated Press called Klasky on Monday evening to ask about the original restriction. Students have not yet been officially informed of the change in policy, Klasky said.&#13;
&#13;
Administrators, including Yale President Richard Levin, weighed in on the decision to overturn the ban after it became apparent that it concerned issues of free speech, Levin said. Although the administration will not censor future shows, he said, the Dean of Student Affairs still has the authority to regulate student productions.&#13;
&#13;
"The fundamental consideration was trading off artistic freedom of expression against concern about the potential emotional precariousness of audiences during the week of a mass murder," he said. "There was a different approach which hadn&amp;#39;t been considered at the time, and the approach would be not to censor the show but warn the audience."&#13;
&#13;
But Holdren said she asked Trachtenberg on Thursday to consider allowing the use of realistic-looking weapons if the staff included a warning before each show. At the time, Trachtenberg found that alternative unacceptable, Holdren said. She said that although the change comes too late to affect her show, which ended its run on Saturday, she is glad the administration has considered the issue more carefully.&#13;
&#13;
"Obviously professional theater companies do shows with weapons all of the time and it&amp;#39;s up to the audience&amp;#39;s discretion whether or not to watch," she said.&#13;
&#13;
Trachtenberg declined to comment Tuesday night about the reversal of her decision, but over the weekend she told the News that student criticism of the stage weapons ban had been exaggerated.&#13;
&#13;
"I think people should start thinking about other people rather than trying to feel sorry for themselves and thinking that the administration is trying to thwart their creativity," Trachtenberg said. "They&amp;#39;re not using their own intelligence. ... We have to think of the people who might be affected by seeing real-life weapons."&#13;
&#13;
Dustin Cho &amp;#39;08, chair of the Yale chapter of the American Civil Liberties Union, said "knee jerk" reactions are common after national tragedies, but that such limitations on free speech inhibit any meaningful dialogue. Generally Yale is very good at protecting free speech, he said.&#13;
&#13;
"It&amp;#39;s quite a stretch to say that substituting realistic-looking prop swords with wooden ones showed more sensitivity to the shooting victims," he said. "This was a grave mistake, but I&amp;#39;m glad they took care of it immediately."&#13;
&#13;
Trachtenberg, who has served as Dean of Student Affairs for 20 years, announced in November that she is stepping down at the end of the academic year.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.yaledailynews.com/articles/view/20927"&gt; Yale Daily News - 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="9549">
                <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="11541">
                <text>Editor-in-Chief, Yale Daily News - Sarah Mishkin &lt;sarah.mishkin@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12993">
                <text>Stage weapons ban reversed</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="318">
        <name>guns</name>
      </tag>
      <tag tagId="583">
        <name>theater</name>
      </tag>
      <tag tagId="582">
        <name>university response</name>
      </tag>
      <tag tagId="580">
        <name>yale</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="749" 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="2068">
                <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="3959">
                <text>David Reynolds</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="5937">
                <text>2007-07-16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7815">
                <text>&lt;b&gt;Will examine campus security&lt;/b&gt;&#13;
&#13;
By: David Reynolds, Staff Writer&#13;
Posted: 4/20/07&#13;
&#13;
In the aftermath of the Virginia Tech tragedy, school systems across the country are discussing new security measures to ensure that such a harrowing event never could be duplicated.&#13;
&#13;
Virginia Gov. Tim Kaine announced Thursday that an independent review panel has been formed to analyze the circumstances surrounding Monday&amp;#39;s shooting.&#13;
&#13;
Retired Virginia State police Superintendent Col. Gerald Massengill will be the head of the panel, which also will include Tom Ridge, the former U.S. secretary of homeland security.&#13;
&#13;
N.C. Attorney General Roy Cooper also has called for a special task force in conjunction with the State Bureau of Investigation, the UNC system, the N.C. Community College System and the N.C. Independent Colleges and Universities to look for improvements in campus emergency plans.&#13;
&#13;
"We&amp;#39;ll be looking at issues such as guidelines for when to declare a campus lockdown, how to better communicate with students and faculty in a crisis and more ways to identify a potential shooter, along with many others," he said in a Wednesday press conference.&#13;
&#13;
Hope Williams, president of N.C. Independent Colleges and Universities, said school administrators will choose a task force during the next 10 days. She said this task force will release a report within six months containing suggestions for the 2007 fall semester.&#13;
&#13;
The task force will not mandate changes, Williams said, because a one-size plan cannot fit different universities&amp;#39; needs.&#13;
&#13;
"I think the major question is one of modifying and adjusting existing emergency response plans as institutions feel it is necessary."&#13;
&#13;
Jeff Davies, the chief of staff for UNC-system President Erskine Bowles, said discussions already had begun concerning improvements in security before the Va. Tech incident, but the event has added impetus to the debate.&#13;
&#13;
"The decisions have been made to ensure that all residence halls will have card access, alarms and cameras," he said. "We are trying to wrap our arms around a very big issue in a very short amount of time."&#13;
&#13;
Davies said the UNC system likely will ask for state funding for the changes.&#13;
&#13;
And like many other schools nationwide, UNC-Chapel Hill has looked critically at its security measures.&#13;
&#13;
UNC-CH officials said their campus police have completed annual active shooter training and will work with local law enforcement in the case of an emergency.&#13;
&#13;
UNC-CH has the ability to contact students through radio broadcast, housing fliers and campuswide informational e-mails.&#13;
&#13;
E-mails sent to the University community take roughly two hours to reach all intended recipients.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailytarheel.com/media/storage/paper885/news/2007/04/20/StateNational/State.Looks.To.Review-2870573.shtml&gt; The Daily Tar Heel - 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="9786">
                <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="11111">
                <text>The Daily Tar Heel</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11766">
                <text>Kevin Schwartz &lt;kschwartz@unc.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13209">
                <text>State looks to review</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="866">
        <name>state safety review</name>
      </tag>
      <tag tagId="857">
        <name>unc</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1411" 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="2661">
                <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="4552">
                <text>Jacob Lutz</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="6530">
                <text>2007-09-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8408">
                <text>By &lt;a href="unirel@vt.edu"&gt;Jacob Lutz&lt;/a&gt;&#13;
&#13;
BLACKSBURG, Va., September 23, 2007 -- Following the release of the Report of the Virginia Tech Review Panel on August 30, 2007 and three separate internal review reports, Virginia Tech President Charles Steger and senior administrators have led an effort to examine the recommendations contained in these reports with the goal of meshing them and adopting best practices and procedures for all relevant areas on a forward-looking basis.&#13;
&#13;
The Board believes that goal was accomplished in the development of the Virginia Tech Action Plan presented today at a special meeting of the Board of Visitors.&#13;
&#13;
The Virginia Tech Action Plan sets forth the process of tracking all recommendations made from these reports and determining priorities, internal responsibility, procedures for evaluation, alternative solutions, action timelines, and financial analysis. The recommendations included in the Virginia Tech Action Plan are extensive and implementation will require substantial effort and expense.&#13;
&#13;
Virginia Tech has already taken action on a number of items with an immediate priority, some of which were discussed at today&amp;#39;s Board of Visitors meeting. Examples include: multiple redundant notification systems for students, faculty, and staff; additional security devices and measures; additional counseling resources; and many other steps to improve the safety, security, and well-being of the Virginia Tech community.&#13;
&#13;
The Board of Visitors commends President Charles Steger in the adoption of the Virginia Tech Action Plan and for his leadership in these most difficult times. The Board of Visitors would also like to thank the students, staff, faculty and administrators of Virginia Tech for their outstanding service and commitment in responding to the events of April 16, 2007. Their leadership, devotion, and cooperative spirit have been instrumental in moving Virginia Tech forward.&#13;
&#13;
The Board of Visitors also extends its wishes for ongoing recovery to the families of the deceased and the survivors, their families and all of those affected by the terrible events of April 16, 2007. The magnitude of losses and injuries suffered by these victims, their families, the Virginia Tech community, and our Commonwealth is immeasurable. By adopting the Virginia Tech Action Plan with the goal of implementing changes that will reduce the risks of future violence and promote the well-being of our students, faculty, and staff, we are honoring the lives and sacrifices of all who have suffered and advancing the notion of service that is fundamental to Virginia Tech&amp;#39;s mission.&#13;
&#13;
Contact Jacob Lutz at &lt;a href="mailto:unirel@vt.edu"&gt;unirel@vt.edu&lt;/a&gt; or 540-231-5396.&#13;
&#13;
--&#13;
&#13;
Original Source: Virginia Tech News&#13;
&lt;a href="http://www.vtnews.vt.edu/story.php?relyear=2007&amp;itemno=554"&gt;http://www.vtnews.vt.edu/story.php?relyear=2007&amp;itemno=554&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10379">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13729">
                <text>Statement by Virginia Tech Board of Visitors regarding the Virginia Tech Action Plan</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1777">
        <name>action plan</name>
      </tag>
      <tag tagId="1774">
        <name>board of visitors</name>
      </tag>
      <tag tagId="1775">
        <name>bov</name>
      </tag>
      <tag tagId="1637">
        <name>recommendations</name>
      </tag>
      <tag tagId="1641">
        <name>reports</name>
      </tag>
      <tag tagId="248">
        <name>review panel</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
