<?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=61&amp;sort_field=Dublin+Core%2CCreator" accessDate="2026-04-12T23:18:04+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>61</pageNumber>
      <perPage>20</perPage>
      <totalResults>1884</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="646" public="1" featured="0">
    <fileContainer>
      <file fileId="383">
        <src>https://www.april16.vtlibraries.net/files/original/ribbon_9ef8a28d38.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="14774">
                    <text>2007-07-02</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15894">
                    <text>2007-07-02 11:28:49</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="1973">
                <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="3864">
                <text>Kristina Cummins</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="5842">
                <text>2007-07-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7720">
                <text>A large tree on the Virginia Tech campus has a simple orange ribbon tied around it. &#13;
&#13;
Original source: &lt;ahref=" http://www.deviantart.com/deviation/53546156/"&gt; http://www.deviantart.com/deviation/53546156/&lt;/a&gt;&#13;
&#13;
Photo Courtesy of Kristina Cummins&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9691">
                <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="11675">
                <text>Permission:&#13;
Kristina Cummins&#13;
cumminsk@vt.edu</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13123">
                <text>Today we are all Hokies</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="774">
        <name>orange ribbon</name>
      </tag>
      <tag tagId="46">
        <name>ribbon</name>
      </tag>
      <tag tagId="138">
        <name>tree</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="647" public="1" featured="0">
    <fileContainer>
      <file fileId="384">
        <src>https://www.april16.vtlibraries.net/files/original/message board_6bebb5b9f5.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="14775">
                    <text>2007-07-02</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15895">
                    <text>2007-07-02 11:32:58</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="1974">
                <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="3865">
                <text>Kristina Cummins</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="5843">
                <text>2007-07-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7721">
                <text>Message boards filled with comments are stationed on the drill field.&#13;
&#13;
Original source: &lt;ahref=" http://www.deviantart.com/deviation/53546019/"&gt; http://www.deviantart.com/deviation/53546019/&lt;/a&gt;&#13;
&#13;
Photo Courtesy of Kristina Cummins&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9692">
                <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="11676">
                <text>Permission:&#13;
Kristina Cummins&#13;
cumminsk@vt.edu</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13124">
                <text>We are Virginia Tech</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="341">
        <name>signed boards</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="648" public="1" featured="0">
    <fileContainer>
      <file fileId="385">
        <src>https://www.april16.vtlibraries.net/files/original/ribbon II_f016017428.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="14776">
                    <text>2007-07-02</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15896">
                    <text>2007-07-02 11:37:05</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="1975">
                <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="3866">
                <text>Kristina Cummins</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="5844">
                <text>2007-07-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7722">
                <text>A large tree on the Virginia Tech campus has several ribbons tied around it. &#13;
&#13;
Original source: &lt;ahref=" http://www.deviantart.com/deviation/53545565/ "&gt; http://www.deviantart.com/deviation/53545565/ &lt;/a&gt;&#13;
&#13;
Photo Courtesy of Kristina Cummins&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9693">
                <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="11677">
                <text>Permission:&#13;
Kristina Cummins&#13;
cumminsk@vt.edu</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13125">
                <text>Hokies United </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="46">
        <name>ribbon</name>
      </tag>
      <tag tagId="138">
        <name>tree</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1042" 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="2343">
                <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="4234">
                <text>Kyle Cheney</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="6212">
                <text>2007-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8090">
                <text>By:Kyle Cheney&#13;
Posted: 4/19/07&#13;
&#13;
Adan Berkowitz&amp;#39;s disdain for the very media that gives him a voice is an alarmingly narrow-minded generalization. ("A campus in grief distracted by media attack," April 18, p. 9). While sensationalism is all too prevalent in certain segments of the press, to ignore examples of remarkable, in-depth coverage of the Virginia Tech massacre is equally egregious.&#13;
&#13;
Tragedies such as this are the rare moments in U.S. history when the country collectively holds its breath, anxiously waiting for the newest fact or detail to emerge. In these cases, we rely on reporters on the ground to ask tough questions and capture the horror and pain that sent shock waves around the world.&#13;
&#13;
It surprises me that amid the supposed "swarm" of reporters marauding like vultures on the Virginia Tech campus, Berkowitz failed to notice the intrepid coverage by the Roanoke Times, a local outlet that has the most comprehensive, to-the-minute coverage and became a virtual bible for out-of-town reporters. The paper currently features a moving tribute to the victims on its main web page.&#13;
&#13;
Berkowitz also curiously missed the fantastic USA Today coverage, and even his hometown Boston Globe made a fine showing.&#13;
&#13;
To be sure, the Talking Heads do have a way of obscuring issues and turning them into partisan talking points, and they certainly make a lot of noise. But they are hardly representative of the media as a whole, which, at least on this story, performed masterfully.&#13;
&#13;
Kyle Cheney&#13;
COM &amp;#39;06&#13;
Former editor-in-chief of The Daily Free Press &#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailyfreepress.com/media/storage/paper87/news/2007/04/19/Opinion/Letter.Good.Coverage.Is.Worthwhile-2853056.shtml&gt;The Daily Free Press - April 19, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10061">
                <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="11169">
                <text>The Daily Free Press</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11962">
                <text>Matt Negrin &lt;editor@dailyfreepress.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13462">
                <text>LETTER: Good coverage is worthwhile</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1457">
        <name> media coverage</name>
      </tag>
      <tag tagId="1458">
        <name> news</name>
      </tag>
      <tag tagId="1459">
        <name> sensationalism</name>
      </tag>
      <tag tagId="895">
        <name>boston university</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1224" 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="2507">
                <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="4398">
                <text>Kyle Thomas</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="6376">
                <text>2007-08-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8254">
                <text>By: Kyle Thomas&#13;
Posted: 4/24/07&#13;
The terrible tragedy which took place last week at Virginia Tech has stunned the nation. The day a tormented madman decided to take the lives of 32 innocent individuals was horrid, disgusting, gut wrenching and a host of other words, which escape my mind right now.&#13;
&#13;
But in the midst of such a horrendous event, - one in which pure evil was on display - this nation was introduced to a slew of new heroes. All too often in out commercial society, we choose to worship the wrong type of hero. Most of us at one time or another have aspired to be a famous athlete or actor, and maybe we&amp;#39;ve even called them "heroes." But every time a tragedy of this magnitude occurs, one really has to stop and think about how silly - or how downright stupid it is - to refer to these commercial icons as heroes.&#13;
&#13;
Liviu Librescu, a 76-year-old professor, was killed last Monday. By all accounts, Professor Librescu saved the lives of many of the students in his classroom when he, in reckless disregard for his own life, barricaded the door to his classroom with his own body. As a direct result of his actions, only two of his students were injured. No one in the classroom was killed - except Professor Librescu.&#13;
&#13;
Librescu, a Romanian-born Holocaust survivor, never had an easy life. Yet despite all of the challenges he faced, he still managed to receive advanced degrees in engineering. He was an internationally-known leader in the field of aeronautical engineering. He was also the son of two.&#13;
&#13;
It is a shame that true heroes like Librescu will never get the recognition they deserve. Certainly he will be forever memorialized on the campus of Virginia Tech. They will build him a stature, or name a building after him. But only a few months from now, we&amp;#39;ll all go back to calling those silly athletes heroes - and so life will go on.&#13;
&#13;
Now that this country is an established institution, it seems like there is nary a chance for true national heroes to emerge. There are no more British soldiers to defeat and no one else can be the first man on the moon. The only thing really left is responding to tragedy.&#13;
&#13;
Think back to the days, weeks and months that followed Sept. 11. Our television screens were plastered with pictures and family videos of firemen and policemen who ran 80 flights of stairs while bystanders and innocent people were running down. How many of those heroes can you name?&#13;
&#13;
When Timothy McVeigh bombed the Alfred P. Murrah Federal Building in Oklahoma City in 1995, all of us again were bombarded with tales of heroic acts. Yet, the only names we remember 12 years later are that of McVeigh and his accomplice, Terry Nichols.&#13;
&#13;
Years from now - or maybe just days from now - some other tragic event that we cant yet imagine will occur. We wont remember those heroes either.&#13;
&#13;
Most people want to be famous - so how can someone who attains fame be a hero? I know of no one who dreams of dying in a classroom so that others can live. Can a hero really be someone that does something we&amp;#39;d all love to do? A hero should be someone that does something that none of us would ever want to do.&#13;
&#13;
Random House Dictionary lists the definition of hero as "a person who, in the opinion of others, has heroic qualities or has performed a heroic act and is regarded as a model or ideal." That definition is not specific enough. There is an immeasurable leap between a role model and a hero. Older brothers are models to their younger brothers. Teachers are models for their students. But no matter how great their contributions are, they don&amp;#39;t deserve the "hero" moniker.&#13;
&#13;
When professional sports franchises win their respective championships, entire cities come out for a parade. When the city has been without a championship title for a long time, the team is referred to in the media as heroes. The 2004 Red Sox were heroes.&#13;
&#13;
Only, they weren&amp;#39;t. They didn&amp;#39;t risk their lives to win that championship. Never did they face tremendous adversity to attain their goal.&#13;
&#13;
Professor Librescu gave his life so that every student who was in his classroom could live. A gunman shot him to death through a door that only he was keeping closed. Librescu is a hero, and to demerit the term by using it so often is to do a disservice to his memory.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailycampus.com/media/storage/paper340/news/2007/04/24/Commentary/Stop-To.Remember.Our.True.Heroes-2876952.shtml&gt;The Daily Campus - April 24, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10225">
                <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="11229">
                <text>The Daily Campus</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12076">
                <text>Melissa Bruen &lt;eic@dailycampus.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13625">
                <text>Stop To Remember Our True Heroes</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1618">
        <name>university of connecticut</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="769" 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="2087">
                <text>Elva Orozco</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3978">
                <text>La bloguera </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="5956">
                <text>2007-07-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7834">
                <text>Publicado por La bloguera en Mayo 2, 2007 04:24 PM &#13;
&#13;
La peor masacre escolar en la historia de Estados Unidos, que dejÃ³ un saldo de 33 muertos en la Universidad de Virginia Tech, ha generado mÃ¡s interrogantes que respuestas, y mientras la naciÃ³n estÃ¡ de luto muchos se preguntan cÃ³mo afectarÃ¡ Ã©sta tragedia la imagen del inmigrante en este paÃ­s.&#13;
&#13;
La prensa repite constantemente que el asesino, Cho Seung-Hui, emigrÃ³ de Corea a los 8 aÃ±os.&#13;
&#13;
Antes de sus escalofriantes actos, la historia del joven es similar a la de muchas familias inmigrantes.&#13;
&#13;
Sus padres que emigraron buscando un futuro mejor, durante aÃ±os trabajaron en una lavanderÃ­a, y seguramente estaban orgullosos que sus hijos fueran a la universidad. &#13;
&#13;
Inicialmente, Cho Seung-Hui, fue blanco de las burlas por no saber inglÃ©s, pero eventualmente aprendiÃ³ el idioma, y se podrÃ­a decir que incluso absorbiÃ³ los aspectos mÃ¡s violentos de esta sociedad, donde los tiroteos en las escuelas parecen repetirse sin sentido.&#13;
&#13;
Ahora sus padres viven "una horrible pesadilla" segÃºn un comunicado de la familia que agrega que nunca se imaginaron la capacidad de violencia de su hijo quien "ha puesto a llorar al mundo". &#13;
&#13;
Pero esta masacre tambiÃ©n tiene otra cara inmigrante que no ha recibido tanta atenciÃ³n de los medios.&#13;
&#13;
Las vÃ­ctimas, los hÃ©roes y los dolientes de esta tragedia, tambiÃ©n tienen rostro inmigrante y desde PerÃº, Puerto Rico, Indonesia, India, LÃ­bano, Polonia, Vietnam, CanadÃ¡ y los Emiratos Arabes Unidos, llegaron para cumplir su sueÃ±o americano estudiando o enseÃ±ando en Virginia Tech.&#13;
&#13;
El profesor Liviu Librescu, nacido en Polonia, se interpuso ante las balas tratando de salvar la vida de sus estudiantes. El maestro bloqueÃ³ la puerta del salÃ³n, mientras le urgÃ­a a sus estudiantes que se tiraran al piso.&#13;
&#13;
El estudiante peruano, Daniel PÃ©rez Cueva de 21 aÃ±os, tambiÃ©n muriÃ³ en el tiroteo.&#13;
&#13;
Su madre Betty Cueva lo recuerda como un joven alegre, que sin embargo asumiÃ³ grandes responsabilidades familiares tras la deportaciÃ³n de su padre a PerÃº y se pagaba sus estudios para no incomodar a su familia. &#13;
&#13;
Juan RamÃ³n Ortiz de Puerto Rico, tambiÃ©n fue vÃ­ctima de la masacre. &#13;
&#13;
Su padre, al ser entrevistado desde Puerto Rico, dio un ejemplo de compasiÃ³n al mundo, al decir entre lÃ¡grimas, que tambiÃ©n habÃ­a que orar por la familia del asesino.&#13;
&#13;
Al igual que ese fatÃ­dico 11 de septiembre, con la masacre en Virginia Tech, los inmigrantes sufren en carne propia las tragedias nacionales, pero a la vez son una parte integral y necesaria para cicatrizar estas heridas y luchar por un mejor paÃ­s.&#13;
&#13;
--&#13;
&#13;
Fuente Original: Los Blogueros - Washington, DC.&#13;
&lt;a href="http://www.losblogueros.net/mt-weblog/2007/05/las_caras_inmigrantes_de_la_ma.html"&gt;http://www.losblogueros.net/mt-weblog/2007/05/las_caras_inmigrantes_de_la_ma.html&lt;/a&gt;&#13;
&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9805">
                <text>spa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11785">
                <text>Nick, or Dabloguiman</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13225">
                <text>Las caras inmigrantes de la masacre de Virginia Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="897">
        <name>emigracion</name>
      </tag>
      <tag tagId="898">
        <name>inmigrante</name>
      </tag>
      <tag tagId="435">
        <name>librescu</name>
      </tag>
      <tag tagId="896">
        <name>ortiz</name>
      </tag>
      <tag tagId="105">
        <name>perez</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1013" 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="2315">
                <text>Elva Orozco</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4206">
                <text>La Raza Newspaper</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="6184">
                <text>2007-08-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8062">
                <text>Publicado por La Raza Newspaper&#13;
06-14-2007 &#13;
&#13;
Washington, D.C. (EFE).â€” Un comitÃ© creado por el presidente de Estados Unidos, George W. Bush, para estudiar la matanza en la Universidad virginia tech recomendÃ³ ayer controlar mejor a las "personas peligrosas", pero no pidiÃ³ endurecer las leyes para restringir el acceso a las armas. &#13;
&#13;
El informe dice que todos los estados deberÃ­an enviar los datos de personas que no pueden poseer armas por problemas mentales a una lista nacional de la Oficina Federal de Investigaciones (FBI) denominada Sistema de ComprobaciÃ³n Inmediata de Antecedentes Penales (NICS). &#13;
&#13;
Actualmente, sÃ³lo 23 de los 50 estados del paÃ­s envÃ­an esa informaciÃ³n. &#13;
&#13;
El estado de Virginia no enviÃ³ al NICS los datos de Cho Seung-Hui, un estudiante coreano de 23 aÃ±os que habÃ­a sido sometido a tratamiento psiquiÃ¡trico. &#13;
&#13;
Sus problemas mentales deberÃ­an haberle impedido comprar las dos armas que usÃ³ para matar en abril a 32 estudiantes y profesores en la Universidad PolitÃ©cnica, pero Cho pudo adquirirlas legalmente porque su nombre no estaba en esa lista nacional. &#13;
&#13;
La CÃ¡mara de Representantes de EU aprobÃ³ ayer un proyecto de ley que obligarÃ­a a los estados a pasar al FBI de forma automÃ¡tica los nombres de personas como Cho. &#13;
&#13;
El informe, elaborado por los secretarios de Salud, Michael Leavitt, y EducaciÃ³n, Margaret Spellings, asÃ­ como el fiscal general, Alberto Gonzales, tambiÃ©n seÃ±ala que existe "confusiÃ³n sobre las leyes que regulan el intercambio de informaciÃ³n" respecto de personas que pueden ser un peligro. &#13;
&#13;
El comitÃ© concluye que profesores, administraciones e instituciones no tienen claro cuÃ¡ndo pueden o deben alertar a las autoridades sobre estas personas para impedir que tengan acceso a armas. &#13;
&#13;
"Este miedo y malos entendidos probablemente limitan la transferencia de informaciÃ³n", se explica en el documento. &#13;
&#13;
Asimismo, el comitÃ© recomienda poner en marcha programas para instruir a padres, alumnos y profesores sobre los signos de que una persona sufre desequilibrios mentales que le pueden llevar a la violencia. &#13;
&#13;
AdemÃ¡s, insta a mejorar los servicios mÃ©dicos para estudiantes que padecen enfermedades mentales. &#13;
&#13;
Por Ãºltimo, plantea que los planes para responder a emergencias a nivel local y estatal tengan en cuenta las necesidades de los centros educativos, y que los cuerpos de seguridad de las escuelas colaboren de forma mÃ¡s estrecha con la policÃ­a. &#13;
&#13;
El informe no habla en ningÃºn momento, sin embargo, de la necesidad de endurecer las leyes para restringir el acceso a las armas en general, en un paÃ­s donde sus ciudadanos poseen mÃ¡s de 200 millones de armas de fuego. &#13;
&#13;
En Virginia, por ejemplo, cualquier persona que no tenga un historial criminal puede comprar legalmente un arma por mes. &#13;
&#13;
Otras matanzas han sido cometidas por personas que no habÃ­an sido tratadas por problemas mentales, como por ejemplo la ocurrida en 1999 en la escuela secundaria de Columbine, en la que murieron 14 estudiantes y un profesor.&#13;
&#13;
--&#13;
Fuente Original: Diario La Raza - Chicago&#13;
&lt;a href="http://www.laraza.com/news.php?nid=44534&amp;clave=a%3A1%3A%7Bi%3A0%3Bs%3A13%3A%22virginia+tech%22%3B%7D"&gt;http://www.laraza.com/news.php?nid=44534&amp;clave=a%3A1%3A%7Bi%3A0%3Bs%3A13%3A%22virginia+tech%22%3B%7D&lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10033">
                <text>spa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11939">
                <text>Jorge Mederos&#13;
Executive Editor&#13;
La Raza Chicago Inc.&#13;
jorge.mederos@laraza.com&#13;
August, 13 2007</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13434">
                <text>Legisladores sÃ³lo piden mayor control sobre las â€˜personas peligrosasâ€™ en EE.UU.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="949">
        <name>armas</name>
      </tag>
      <tag tagId="891">
        <name>fbi</name>
      </tag>
      <tag tagId="628">
        <name>gonzales</name>
      </tag>
      <tag tagId="626">
        <name>leavitt</name>
      </tag>
      <tag tagId="1354">
        <name>nics</name>
      </tag>
      <tag tagId="1353">
        <name>problemas mentales</name>
      </tag>
      <tag tagId="627">
        <name>spellings</name>
      </tag>
      <tag tagId="234">
        <name>virginia</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1063" 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="2363">
                <text>Elva Orozco</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4254">
                <text>La Raza Newspaper</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="6232">
                <text>2007-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8110">
                <text>Identifican al agresor como un estudiante de Corea del Sur.&#13;
&#13;
&#13;
Publicado por Diario la Raza&#13;
04-18-2007&#13;
&#13;
&#13;
Washington, D.C. â€” La policÃ­a de EE.UU. identificÃ³ como el autor de la matanza en la universidad &lt;b&gt;virginia tech&lt;/b&gt; al estudiante surcoreano Cho Seung Hui, de 23 aÃ±os, un joven descrito como "solitario" y cuyos escritos habÃ­an suscitado preocupaciÃ³n entre sus profesores. &#13;
&#13;
Hasta el momento se desconocen los motivos que llevaron a Cho, quien vivÃ­a en EU desde los 8 aÃ±os y estudiaba filologÃ­a inglesa, a matar a 32 personas, entre profesores y estudiantes â€”al menos dos latinoamericanosâ€” y suicidarse. &#13;
&#13;
Una de sus profesoras recordaba ayer a la prensa el tono perturbador de algunos de sus ejercicios literarios, hasta el punto de que sus instructores le aconsejaron recibir ayuda psicolÃ³gica. &#13;
&#13;
SegÃºn el diario Chicago Tribune, el asesino dejÃ³ una nota en su habitaciÃ³n en la que clamaba contra los "niÃ±os ricos", "la decadencia" y los "embusteros charlatanes" en el campus y asegura: "Me obligaste a hacerlo". &#13;
&#13;
Al parecer, segÃºn la cadena CNN, Cho comprÃ³ una pistola Glock el mes pasado en una tienda de Roanoke, una ciudad vecina, y pagÃ³ por ella 571 dÃ³lares con un cheque. &#13;
&#13;
La matanza se produjo en dos fases: en un primer tiroteo murieron dos personas, un hombre y una mujer, en una residencia de estudiantes; y el segundo, en el que muriÃ³ el resto, tuvo lugar dos horas mÃ¡s tarde, en las aulas de la Facultad de IngenierÃ­a. &#13;
&#13;
Las autoridades han confirmado que las armas empleadas en la matanza fueron al menos dos pistolas y que una de ellas se usÃ³ en los dos tiroteos. &#13;
&#13;
"La evidencia no nos ha conducido a decir categÃ³ricamente que el mismo autor estuvo implicado en los dos tiroteos", pero "es ciertamente razonable suponer que Cho fue el autor en los dos incidentes", indicÃ³ el superintendente de la PolicÃ­a de Virginia, Steven Flaherty. &#13;
&#13;
Entre los fallecidos se encuentran profesores y estudiantes. La lista completa no se ha dado a conocer pero sÃ­ han salido a la luz los nombres de un grupo de vÃ­ctimas. &#13;
&#13;
Entre ellos se encuentra el peruano Daniel PÃ©rez Cuevas, muerto mientras asistÃ­a a una clase de francÃ©s y quien habÃ­a iniciado sus estudios universitarios en Miami pero se cambiÃ³ a &lt;b&gt;virginia tech&lt;/b&gt;, por su mayor prestigio acadÃ©mico. &#13;
&#13;
TambiÃ©n estÃ¡ el puertorriqueÃ±o Juan RamÃ³n Ortiz, de 26 aÃ±os, y que cursaba su primer aÃ±o de maestrÃ­a en la universidad, donde se habÃ­a matriculado junto a su esposa, Liselle Vega, con quien llevaba casado un aÃ±o. &#13;
&#13;
El gobierno de EU afirmÃ³ ayer que estÃ¡ dispuesto a ofrecer la ayuda que sea necesaria para los extranjeros que hayan sido vÃ­ctimas de la masacre en la Universidad PolitÃ©cnica de Virginia el lunes. &#13;
&#13;
SegÃºn han contado los supervivientes, el asesino cerrÃ³ varias salidas del edificio con cadenas y candados, y despuÃ©s fue vaciando sus cargadores, aula por aula. &#13;
&#13;
La primera clase, y donde al parecer se han registrado mÃ¡s vÃ­ctimas, fue una de alemÃ¡n, en la que el asesino disparÃ³ a la cabeza del profesor Chris Bishop antes de abrir fuego sobre los alumnos. &#13;
&#13;
En otras aulas algunos alumnos huyeron por las ventanas. Otros intentaron bloquear las puertas con sus cuerpos, en algunos casos con resultado fatal. &#13;
&#13;
Ese fue el caso del profesor Liviu Librescu, que fue alcanzado por disparos a travÃ©s de la puerta mientras impedÃ­a el paso al agresor y lograba asÃ­ salvar a sus alumnos. &#13;
&#13;
Doce estudiantes de la universidad se recuperan de sus heridas y permanecen estables en distintos hospitales de la zona de Blackburg, donde se encuentra el centro docente. &#13;
&#13;
La matanza ha conmovido a todo el paÃ­s y ha suscitado reacciones de condolencia en todo el mundo. &#13;
&#13;
El presidente de EU, George W. Bush, asegurÃ³ ayer que se trata de un "dÃ­a de tristeza para todo el paÃ­s" e instÃ³ a los estudiantes a no dejarse llevar por la ira, en un acto de homenaje a las vÃ­ctimas en el polideportivo de la universidad. &#13;
&#13;
Bush ordenÃ³ que las banderas estadounidenses ondeen a media asta en seÃ±al de duelo hasta el domingo. &#13;
&#13;
El incidente ha comenzado a suscitar ya las primeras crÃ­ticas sobre la reacciÃ³n de las autoridades tanto policiales como universitarias. &#13;
&#13;
Muchos estudiantes han censurado que, tras el primer incidente, no se suspendieran las clases ni se diera un aviso de peligro hasta dos horas despuÃ©s, y eso sÃ³lo a travÃ©s de un correo electrÃ³nico. &#13;
&#13;
La matanza ha vuelto a reabrir el debate sobre la regulaciÃ³n de la tenencia de armas en Estados Unidos, un paÃ­s en el que las leyes sobre el control de armas de fuego son muy laxas. EFE &#13;
&#13;
&#13;
--&#13;
Fuente Original: Diario La Raza - Chicago&#13;
&lt;a href="http://www.laraza.com/news.php?nid=43338&amp;clave=a%3A1%3A%7Bi%3A0%3Bs%3A13%3A%22virginia+tech%22%3B%7D"&gt;http://www.laraza.com/news.php?nid=43338&amp;clave=a%3A1%3A%7Bi%3A0%3Bs%3A13%3A%22virginia+tech%22%3B%7D&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10081">
                <text>spa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11980">
                <text>Jorge Mederos&#13;
Executive Editor&#13;
La Raza Chicago Inc.&#13;
jorge.mederos@laraza.com&#13;
August 13, 2007</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13482">
                <text>Luto en el paÃ­s por matanza en Virginia</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="227">
        <name>bishop</name>
      </tag>
      <tag tagId="125">
        <name>bush</name>
      </tag>
      <tag tagId="323">
        <name>cho</name>
      </tag>
      <tag tagId="1500">
        <name>flaherty</name>
      </tag>
      <tag tagId="435">
        <name>librescu</name>
      </tag>
      <tag tagId="896">
        <name>ortiz</name>
      </tag>
      <tag tagId="1501">
        <name>pÃ©rez</name>
      </tag>
      <tag tagId="946">
        <name>vega</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1732" 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="2868">
                <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="4759">
                <text>Lach R. Liwer</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="6737">
                <text>2008-02-19</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8615">
                <text>Guest commentary&#13;
By: Lach R. Liwer |&#13;
Issue date: 4/23/07 Section: Commentary&#13;
&#13;
This week we witnessed a brutal act of violence directed randomly at unsuspecting students of Virginia Tech University. Seung-Hui Cho, a VT student, shot nearly 45 students and faculty at the school, killing 32 including himself.&#13;
&#13;
Much has been said about the magnitude of this tragedy, and the nature of the mental disturbance that could have allowed Cho to conceive of and carry out his heinous crime.&#13;
&#13;
What we gravely need to discuss, however, is how it was possible that a lone gunman could, over the course of 35 minutes, stalk through a building with over 300 people locked inside and then systematically shoot more than 45 people, the whole time remaining effectively unopposed.&#13;
&#13;
On September 11, 2001, the famed flight 93 crashed into the fields of Somerset County, taking far fewer lives than the terrorists who hijacked it had intended. Had the passengers of this flight not given their lives to take back the plane, countless more innocents would have perished.&#13;
&#13;
I did not know any of the victims of the April 16 massacre, but I assume that they were not that different from my University classmates who graduated three years ago. Thinking about that group, I feel very confident that fewer than 1 in 10 of us had ever faced real violence, whether in sports, fistfights, or military combat. This became increasingly evident a year after my graduation when I became an Army infantryman. While training at Fort Benning, we participated in rigorous aggression training like hand-to-hand combat and tactical field problems to elevate our comfort with aggression and teach us to think rationally in the face of violence and fear. It quickly became apparent that many of us displayed little physical aggression or the ability to act violently and deliberately. But as we watched each other and experienced this sensation for the first time, along with the taste of our own blood and the fear and excitement of fighting, we learned to control, to harness our aggression and put it to use in defending ourselves.&#13;
&#13;
There is no way to know whether the tragedy of April 16 could have been avoided or diminished under different circumstances. But it seems to me, in light of the utter failure of our security and police forces to protect those students, that we have grown too comfortable with the illusion of our own safety. We must ask whether the instructions we give our children - namely, to run and hide in the face of violent threats - is the best answer in all circumstances. It seems likely that had a group of students decided to put an end to the killing, and harnessed their own aggression en masse to defend themselves, that the outcome could hardly have been worse. We must learn a lesson from the 30 innocent dead of April 16 and the 2973 killed by the September 11 hijackers. The lesson is that ultimately we cannot maintain the safety of our communities by teaching that the best answer we have for those who would take everything from us is to remain docile. Rather, we must learn the realities of the world; there are violent people who wish to do us harm, and though there is never complete safety, we can be less vulnerable by learning to defend ourselves and those we love. By understanding and controlling the aggressive nature that mankind is so tragically capable of instead of fearing it we may diminish the likelihood that a single aggressor can destroy so many lives so easily.&#13;
&#13;
Lach R. Liwer is a University alum and an infantryman in the United States Army&#13;
&#13;
--&#13;
&#13;
Original Source: Daily Emerald&#13;
&lt;a href="http://media.www.dailyemerald.com/media/storage/paper859/news/2007/04/23/Commentary/SelfDefense.A.Necessary.Skill.To.Know.During.Times.Of.Danger-2874218.shtml"&gt;http://media.www.dailyemerald.com/media/storage/paper859/news/2007/04/23/Commentary/SelfDefense.A.Necessary.Skill.To.Know.During.Times.Of.Danger-2874218.shtml&lt;/a&gt;&#13;
&lt;a href="http://media.www.dailyemerald.com/media/storage/paper859/news/2007/04/23/Commentary/SelfDefense.A.Necessary.Skill.To.Know.During.Times.Of.Danger-2874218-page2.shtml"&gt;http://media.www.dailyemerald.com/media/storage/paper859/news/2007/04/23/Commentary/SelfDefense.A.Necessary.Skill.To.Know.During.Times.Of.Danger-2874218-page2.shtml&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10586">
                <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="12226">
                <text>Judy Riedl &lt;jriedl@uoregon.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13932">
                <text>Self-defense a necessary skill to know during times of danger</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1937">
        <name>self-defense</name>
      </tag>
      <tag tagId="1979">
        <name>university of oregon</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="350" 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="1694">
                <text>Landon Owen</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3585">
                <text>Landon Owen</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="5563">
                <text>2007-06-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7441">
                <text>Waco, TX.  Oklahoma City, OK. Columbine, CO.  Blacksburg, VA.&#13;
&#13;
Fifteen years ago, a person could have looked at those four cities and wondered why they have been grouped together.  None of these places had anything in common.  Most people might not even have heard of three of those cities, save for people that live in those states.  &#13;
&#13;
April 19, 1993.  April 19, 1995.  April 20, 1999.  April 16, 2007.&#13;
&#13;
Fifteen years ago, a person could have looked at those four dates and wondered why they have been grouped together.  None of these dates could have possibly had any future significance, save for the fact that they would all occur within the same calendar week.&#13;
&#13;
Fifteen years.  Such a small window in the grand scheme of things we call time.&#13;
&#13;
Julius Caesar was told by the Soothsayer to "Beware the Ides of March."  Perhaps the third week in this month should be called the "Ides of April."  All four tragedies have occurred within the same calendar week, the third week of April. &#13;
&#13;
These events helped shape - or scar - today&amp;#39;s society.  To be sitting here, writing about the worst shooting in United States history, is almost surreal.  It goes along with events like the Kennedy assassination, the Challenger space shuttle, and September 11th.  People will ask you years from now, "Where were you that day?"  Almost regrettably, my answer will be, "Across the street from West AJ."    &#13;
&#13;
I remember sitting in my dorm room my senior year in college, waking up to see that the World Trade Center had fallen and the Pentagon had been stuck by terrorists.  I recall the sense of anger, so much so that my hands were shaking.  A sense of utter disbelief ran wild through my head for days as I sat glued to the television newscasts.  I felt a need for vengeance, a need for retribution.  Our troops took care of that for us, and are still fighting nearly six years later. &#13;
&#13;
As I sat through today&amp;#39;s event in Blacksburg, all I could think of was that this is how the story ends.  There will be no revenge, no retribution, no release from our anger.  All that is left after today is the memory of 32 of Virginia Tech&amp;#39;s finest students, staff, and faculty that came to class today to find a way to make tomorrow better.  Instead, tomorrow we will grieve their loss and ask the Lord to help guide them to their final resting place in Hokie Heaven.&#13;
&#13;
It&amp;#39;s hard to put arms around the situation, almost impossible to feel the gravity of the situation at the time being.  As time passes, wounds will get worse before they get better. Pain will work its way deep into our hearts before it can be lifted.  The Virginia Tech motto, Ut Prosim, translates to, "That I may serve."  May we all serve the families that have suffered such a great loss by keeping them in our hearts, our minds, and our prayers.&#13;
&#13;
God Bless&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9412">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12878">
                <text>The Ides of April</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="439">
        <name>april</name>
      </tag>
      <tag tagId="438">
        <name>ides</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="716" 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="2038">
                <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="3929">
                <text>Lara Loewenstein</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="5907">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7785">
                <text>&lt;b&gt;Although meditation can help ease stress, it won&amp;#39;t cure what really ails students, society&lt;/b&gt;&#13;
&#13;
By Lara Loewenstein&#13;
Thursday, May 3, 2007&#13;
&#13;
Film director David Lynch has the answer to the itching question of how to stop school shootings forever - he&amp;#39;s going to teach 1 million students transcendental meditation. I&amp;#39;m almost waiting for Tom Cruise to announce his plan to convert a second million to Scientology.&#13;
&#13;
Transcendental meditation is a practice in which participants sit comfortably with their eyes closed and recite a mantra for 20 minutes, twice a day. Unlike other forms of meditation, TM is not meant to involve any form of concentration or effort other than finding the time to practice it. Courses to learn TM cost about $2,500.&#13;
&#13;
It almost sounds like nap time. Expensive nap time. But the David Lynch Foundation wants to teach us. For free.&#13;
&#13;
Or rather, they want to fund UCLA to teach us - he&amp;#39;s providing the funds for schools that want to include TM in their curriculum in order to end school violence. All the schools have to do is contact him. Unfortunately, I don&amp;#39;t think UCLA is going to take up the offer.&#13;
&#13;
Unfortunate because TM does have some proven benefits - namely, reducing blood pressure and stress.&#13;
&#13;
But TM is not proven to stop violence. And honestly, I don&amp;#39;t know what problems Lynch thinks people have that can all be eased with TM. Maybe all his frustrations with film directing can be fixed. But TM isn&amp;#39;t going to put an end to concrete problems college students face such as paying school loans.&#13;
&#13;
And it certainly isn&amp;#39;t going to solve mental instability, seemingly the cause of the recent Virginia Tech shooting.&#13;
&#13;
But even with all the things TM won&amp;#39;t do, during the Web cast on Tuesday, Lynch, so-called quantum physicist John Hagelin and singer-song writer Donovan gave me an idea of what TM would do.&#13;
&#13;
After telling their personal stories about discovering TM, Hagelin described specifically how TM works. According to him, meditation allows the mind to settle inward, causing the brain to be more coherent before finally coming to a sense of unity where you realize we are all part of the same entity. He even provided useful charts - to aid those who aren&amp;#39;t scientifically minded - that detailed how the state of unity in TM is the same as the "unified field of natural laws of nature."&#13;
&#13;
My, that&amp;#39;s an eloquent phrase.&#13;
&#13;
But besides not knowing exactly what a quantum physicist is, I also don&amp;#39;t know what this unified field has anything to do with any sense of unity I might achieve through meditation.&#13;
&#13;
But I&amp;#39;ll give Hagelin points for creativity. After all, he has a Ph.D. from Harvard.&#13;
&#13;
According to Hagelin, Lynch and Donovan, it&amp;#39;s this sense of unity that people achieve via TM that will bring about world peace and consequently end school violence.&#13;
&#13;
They even stressed how by using their technique we won&amp;#39;t need to debate gun control anymore. Because once everyone knows TM, nobody will want to use a gun even if they have access to one. They&amp;#39;re going to be too busy enjoying their higher consciousness.&#13;
&#13;
I love it; it&amp;#39;s so simple and free of politics. And totally fantastical.&#13;
&#13;
Not only is TM not going to cure all ills that cause violence, I don&amp;#39;t understand where Lynch, Hagelin and Donovan expect people who are, say, in the process of applying to Harvard to find time to meditate for 40 minutes a day.&#13;
&#13;
Still, methods to reduce stress and blood pressure and increase happiness should be studied.&#13;
&#13;
But considering how much trouble I have sitting still, I&amp;#39;d like to see some non-pseudo, and unbiasedly authored, studies comparing happiness and stress release related to smoking pot on a daily basis, swing dancing or getting laid.&#13;
&#13;
But even with my attention issues, I still want to learn TM. I&amp;#39;m just not paying $2,500.&#13;
&#13;
I quickly sent an e-mail to the David Lynch Foundation on Tuesday requesting to be taught.&#13;
&#13;
He hasn&amp;#39;t responded yet. I doubt people requesting to learn TM are the ones at risk for becoming gunmen.&#13;
&#13;
So I started by teaching myself.&#13;
&#13;
But the "how to" for TM is pretty secretive. I suppose they really want that $2,500. I had to settle for plain meditation with a non-unique mantra - "hamsa."&#13;
&#13;
So I sat down in a comfortable position and tried it, saying "ham" when I breathed in and "sa" when I breathed out.&#13;
&#13;
Hammmm ... saa.&#13;
&#13;
I fell asleep after five minutes.&#13;
&#13;
And now I don&amp;#39;t have time to do my problem set. Thanks, David.&#13;
&#13;
I&amp;#39;m sure meditation works for some people, but I&amp;#39;m going to go back to my nap.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.dailybruin.ucla.edu/news/2007/may/03/mantras_miracles/&gt;The Daily Bruin - May 3, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9756">
                <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="11736">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13179">
                <text>Mantras can&amp;#39;t make miracles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="839">
        <name>meditation</name>
      </tag>
      <tag tagId="838">
        <name>stress management</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="734" 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="2054">
                <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="3945">
                <text>Lara Loewenstein</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="5923">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7801">
                <text>&lt;b&gt;UCLA, other schools should take time now to improve their emergency alert systems&lt;/b&gt;&#13;
&#13;
By Lara Loewenstein&#13;
Thursday, April 19, 2007&#13;
&#13;
There are a few questions that have been circulating with regard to the Virginia Tech shootings. How many lives could have been saved if the administration had reacted differently? How would UCLA respond if such an event happened?&#13;
&#13;
It&amp;#39;s pretty obvious that the administration of Virginia Tech could have responded differently. But what&amp;#39;s more important than the mistakes the administration at Virginia Tech made is how Virginia Tech and other universities can learn from these mistakes.&#13;
&#13;
In response to the shooting, Interim Chancellor Norman Abrams released a statement on Monday. It began with information that should go without saying - student and faculty safety is a top priority - and then went on to say that UCPD officers are trained to handle shooting scenarios.&#13;
&#13;
But that doesn&amp;#39;t answer my questions because that isn&amp;#39;t the issue. The issue was that students weren&amp;#39;t and couldn&amp;#39;t have been notified of the earlier shooting - when the gunman killed two people in the dormitories - in enough time to allow them to make an informed choice to not go to campus. There wasn&amp;#39;t even a system in place to contact students if the administration at Virginia Tech had decided to close the campus.&#13;
&#13;
Sure, the police officers thought it was a domestic violence issue and that the suspect had left campus, but now that the administration at Virginia Tech knows better, it should be apologizing for the wrong choices it made and its lack of an emergency plan. Instead, it&amp;#39;s just making excuses.&#13;
&#13;
One of the excuses Virginia Tech President Charles W. Steger gave for not closing down the campus and canceling classes was that he didn&amp;#39;t know what the alternative to students coming to class would be.&#13;
&#13;
One has to ask, shouldn&amp;#39;t such an alternative be included in an emergency plan in case of such an incident? Shouldn&amp;#39;t the alternative have been known, available and rehearsed? After all, student and faculty safety is a top priority, is it not?&#13;
&#13;
And does UCLA have such a plan?&#13;
&#13;
Abrams&amp;#39; statement went on to say, "UCLA has an emergency response team and protocols in place to notify the campus community in the event of any circumstances requiring emergency action, such as the closing of the campus."&#13;
&#13;
This gives me the impression that UCLA has such a plan in place. However, what that plan actually is befuddles me because what exactly would UCLA have been able to do differently?&#13;
&#13;
They could have sent the warning e-mail out earlier, sure. But I don&amp;#39;t usually wake up in the morning with the thought of checking my e-mail to see if there&amp;#39;s a gunman on campus.&#13;
&#13;
And as for students whose Internet was down, or don&amp;#39;t have home access, they wouldn&amp;#39;t have received the message at all.&#13;
&#13;
I suppose they could start calling people, but it seems a little unrealistic to call more than 40,000 students and faculty. Besides, I don&amp;#39;t think UCLA even has my cell phone number.&#13;
&#13;
In that case, they wouldn&amp;#39;t even reach me - they&amp;#39;d reach my parents&amp;#39; house, and it&amp;#39;s likely they wouldn&amp;#39;t even be home.&#13;
&#13;
There are concerns that if universities went overboard with safety regulation then students and faculty would have to compromise certain freedoms. But there are plans that wouldn&amp;#39;t impede everyday life that would be more effective than contacting students by e-mail.&#13;
&#13;
According to the Washington Post, a campus spokesperson said that earlier in the semester, Virginia Tech had been working with a company with which they could contact students via text message in case of an emergency. Students would be required to submit their cell phone numbers when they registered for classes.&#13;
&#13;
Whether this plan is going to be carried through wasn&amp;#39;t said.&#13;
&#13;
Considering the number of people who own cell phones, and how often we check them for messages or otherwise, this could reach more people than an e-mail message would.&#13;
&#13;
I don&amp;#39;t know what plan Abrams was referring to in his statement, but I hope it&amp;#39;s better than the one Virginia Tech had in place. And if it isn&amp;#39;t, I hope this so-called plan is reworked - maybe to include a text message notification system or otherwise.&#13;
&#13;
In fact, the president of the University of California, Robert C. Dynes, said in his statement about the shootings that all UC campuses would be reviewing their security policies. He mentioned to the Daily Bruin that this system might incorporate emergency text messages.&#13;
&#13;
This provides some comfort - as long as it happens soon. The next biggest shooting in modern American history could happen anytime, and it could happen on this campus. I want to know that we&amp;#39;re ready for it.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.dailybruin.ucla.edu/news/2007/apr/19/emuniversities_must_learn_handling_shootingem/&gt;The Daily Bruin - April 19, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9772">
                <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="11752">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13195">
                <text>Universities must learn from handling of shooting</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="606">
        <name>crisis response</name>
      </tag>
      <tag tagId="852">
        <name>security concerns</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
      <tag tagId="582">
        <name>university response</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="155" 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="1523">
                <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="3414">
                <text>Larry Hincker</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5392">
                <text>2007-05-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7272">
                <text>By &lt;a href="hincker@vt.edu"&gt;Larry Hincker&lt;/a&gt;&#13;
&#13;
BLACKSBURG, Va., May 10, 2007 -- Virginia Tech President Charles W. Steger addressed the Virginia Tech Review Panel here Thursday. These were his comments.&#13;
&#13;
Governor Kaine, Colonel Massengill, and members of the commission.&#13;
&#13;
Normally, I would address a commission by saying that I am happy to have the opportunity to appear before you. We know that is not true. Each of us appears here today with heavy heart, a most profound sense of sorrow...and yes, still to this day...disbelief.&#13;
&#13;
A terribly deranged young man....one of our own students...visited unimaginable horror upon our university, our bright young minds, our rising stars, and our caring and learned faculty.&#13;
&#13;
He took 32 precious lives and then his own. He wounded 25 more. In the process, he seriously injured an entire nation.&#13;
&#13;
As we have noted many times throughout this terrible ordeal, the families of those who lost their lives and the injured have remained our highest priority, followed by the needs of our greater university community. We will do everything possible to assist with their recovery.&#13;
&#13;
I have said time and again, that Virginia Tech, our commonwealth, all of higher education, and indeed, the world must learn from this tragedy. I personally asked the governor for your work.&#13;
&#13;
We have been and will continue to cooperate fully with your review and findings. I have appointed a lead individual, a retired university executive with experience in many sectors including audit, to assist you with your data gathering and be your liaison with any office on campus.&#13;
&#13;
Each one of us and each sector of our society that has been touched by this tragedy must welcome the inspection, introspection, and the scrutiny of a thorough analysis.&#13;
&#13;
In our own case we have underway after-action reviews, which can inform your data gathering. In addition to understanding the incidents, we will be looking at three broad areas: telecommunications infrastructure, the physical infrastructure as it relates to safety and security, and most importantly, the internal protocols for information exchange. I am particularly interested in those intersections between the academic enterprise, counseling, our disciplinary system, the legal system, and the police.&#13;
&#13;
Our preliminary schedule calls for those reviews to be complete by late August, which I understand is within your study time-frame to be of use to you.&#13;
&#13;
In addition to our incident response, I know that you will be looking at the broad spectrum of issues including policies, protocols, and the law.&#13;
&#13;
I have read and heard other university presidents and pundits say that this tragedy could have happened on any campus in America. We draw no solace from such observations.&#13;
&#13;
My hope is that we - and every campus throughout the nation - can learn in the months ahead what happened and why...to the extent that rational conclusions can be drawn from irrational violence. We will learn and the world will learn from this.&#13;
&#13;
There already is a vigorous national discourse underway on many issues - mental health, the interplay between the rights of individuals and the rights of societies and communities, the interaction between gun laws and privacy, campus security and the underlying physical infrastructure, and much more.&#13;
&#13;
We need to know how well our mental health system is performing. Is this country devoting the time, resources, and energy to helping those in need?&#13;
&#13;
We need to know if privacy laws can or should change so that school administrators, court officials, or the mental health profession itself, has the information it needs to treat and handle those with mental illnesses on college campuses.&#13;
&#13;
Certainly, you will bump into the nexus of individual rights and privacy laws versus the rights of a society, a community, or a university to protect itself against possible harm from the mentally ill...or anyone else, for that matter.&#13;
&#13;
We need to know if the university reacted in accordance with accepted procedure in its response to the murders within our residence hall. Our university police and rescue squad responded within three minutes of a report that someone fell from a bed within a residence hall. Within minutes thereafter, the police, then knowing of a gunshot fatality and injury, secured the residence hall, began investigating, and within one hour had a "person of interest." Your analysis of this and the terrible events following is of crucial importance.&#13;
&#13;
My campus has 19 miles of public roads on its 2,600 acres and 153 mostly accessible buildings. On any given day, we have about 35,000 people coming and going. How does an organization secure a university campus during an emergency? Or for that matter, what levels of security are appropriate for normal operations?&#13;
&#13;
We need to know about the preparedness - to the degree that any institution can prepare for horrible and irrational mass violence - of my university and other schools like ours for violence or other mass events that require an institutional response to protect the health, safety, and welfare of a campus community.&#13;
&#13;
We have multiple methods of emergency communications and have in the works implementation plans for more. We all need to know whether universities such as our can do more to protect and inform its populations and multiple audiences in emergencies.&#13;
&#13;
Tomorrow, Virginia Tech will celebrate its annual spring commencement. This is our time for celebration. Commencement, of course, means "the beginning." For our graduates, it is and will be the beginning of the next phases of their lives. We know that they will carry with them not only those treasured memories unique to the college experience, but also the searing memory of the tragic events of April 16.&#13;
&#13;
We owe it to them, we owe it to the injured, we owe it the families of the fallen... indeed, we owe it to all other schools and campuses in this country to examine all these issues in their totality....and find ways of preventing anything like this ever again.&#13;
&#13;
Contact Larry Hincker at hincker@vt.edu or (540) 231-5396.&#13;
&#13;
##07265##&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.vtnews.vt.edu/story.php?relyear=2007&amp;itemno=285"&gt;http://www.vtnews.vt.edu/story.php?relyear=2007&amp;itemno=285&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9241">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12728">
                <text>President Steger addresses Virginia Tech Review Panel</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="37">
        <name>address</name>
      </tag>
      <tag tagId="249">
        <name>may 10</name>
      </tag>
      <tag tagId="248">
        <name>review panel</name>
      </tag>
      <tag tagId="133">
        <name>steger</name>
      </tag>
      <tag tagId="250">
        <name>vtreviewpanelorg</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1236" 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="2518">
                <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="4409">
                <text>Larry Hincker</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6387">
                <text>2007-08-26</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8265">
                <text>&lt;p&gt;By &lt;a href="mailto:hincker@vt.edu"&gt;Larry Hincker&lt;/a&gt;&#13;
&#13;
BLACKSBURG, Va., August 22, 2007 -- On May 9, 2007, Virginia Tech President Charles Steger directed three internal reviews in the wake of the April 16 tragedy on the Virginia Tech campus. He directed the chairs "to look at strengths and weaknesses of our existing systems/infrastructure and how they may be improved or augmented to address emergency situations that might arise in the future."&#13;
&#13;
These reviews are internal in structure and focus and not intended to be forensic in nature. Says Steger, "I asked for the creation of two different, but concurrent review processes. The external review commissioned by Governor Kaine is essentially investigatory in nature, while ours is a forward looking review of university policy, resources, and infrastructure through the prism of April 16."&#13;
&#13;
&lt;b&gt;The Security Infrastructure Group&lt;/b&gt; was charged with examining the university&amp;#39;s existing security systems and recommending changes that would enhance the university&amp;#39;s ability to respond quickly and effectively in situations where the safety of the campus community is jeopardized. This group was also directed to identify strategies that might decrease the probability of such situations occurring, looking at both technological and behavioral aspects.&#13;
&#13;
&lt;b&gt;The Information and Communications Infrastructure Group&lt;/b&gt; analyzed and inventoried the communication infrastructure and information systems used during the crisis period, evaluated their performance, and identifies tactics and strategies for improvements.&#13;
&#13;
&lt;b&gt;The Interface Group&lt;/b&gt; evaluated the relationships between the university&amp;#39;s student counseling services, academic affairs, judicial affairs, and the legal system. It was charged with examining the existing systems and the interface between them and determining what constraints, legal or otherwise, hamper effective interactions in order to respond to and support at-risk students.&#13;
&#13;
&lt;b&gt;Security Infrastructure Group&lt;/b&gt;&#13;
&#13;
Among its findings the security infrastructure group found good cooperation and sound agreements between Virginia Tech and local police, fire, and EMS jurisdictions including ongoing training exercises; sound emergency communications; robust communications infrastructure; a sound emergency preparedness plan; engagement of the leadership in campus emergencies; and a nationally accredited campus police department.&#13;
&#13;
The security group recommends enhancements in physical infrastructure, emergency communications, emergency preparedness, and selected protocols.&#13;
&#13;
Infrastructure recommendations include modification of building door hardware, installation of locks on general assignment classrooms, evaluating the utility of centrally controlled electronic key card access to key academic and administrative facilities (such as the system currently in place on all residence halls), constructing a public safety building combining the university police and rescue squad, and evaluating installation of centrally monitored video surveillance cameras.&#13;
&#13;
Communications recommendations include mass notification techniques within classrooms and other locations, message board in key or high profile public areas and along major vehicular thoroughfares, a people locator system, and further articulation of the recently adopted VT Alerts notification system.&#13;
&#13;
Emergency preparedness recommendations include updating the emergency preparedness plan, more frequent emergency exercises or drills, creation of building coordinators for emergencies, and identification of backups for the policy committee (university leadership with oversight of an emergency).&#13;
&#13;
Protocols include increased education of the university community about appropriate emergency response actions and creation of a comprehensive security master plan and campus security committee.&#13;
&#13;
&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_security_infrastructure.pdf"&gt;Read the full Security Infrastructure Group report&lt;/a&gt; (PDF) â€ºâ€º&#13;
&#13;
&lt;b&gt;Information and Communications Infrastructure Group&lt;/b&gt;&#13;
&#13;
Broadly defined, telecommunications comprises the university&amp;#39;s data network, telephone systems (university and/or vendor owned), cable TV, educational systems, and centralized information services. They were dramatically stressed but performed adequately during the crisis. The university on-campus phone system was not degraded but was affected by external problems. External cellular telephone systems and the Public Switched Telephone Network (hardwire telephone systems off campus) experienced huge demand increases and experienced some blocking of calls during the initial periods of the crisis on April 16.&#13;
&#13;
Other university systems experienced some loading, which were quickly identified and rectified, and performed well with no significant problems. For example, the university website www.vt.edu saw a 3,000 percent increase in traffic on April 16, Virginia Tech Police dispatch experienced 450 percent increase, and the university switchboard experienced a 300 percent increase in calls.&#13;
&#13;
Emergency Responder Radio Communication continues to suffer nationally and locally from "interoperability" issues because they use a variety of radio systems and frequencies. Radio systems typically do not support mobile data, encryption, GIS, or other advanced capabilities. Indicative of relatively common signal penetration problems in large buildings, emergency responders reported that radios did not work in some areas of Norris Hall.&#13;
&#13;
This group provides a series of strategic and tactical recommendations. The full report details more than 120 tactical recommendations. Two major strategies emerge:&#13;
&#13;
1) &lt;i&gt;Installation of a new fully integrated digital campus architecture for all telecommunications functions based on Internet Protocol (IP).&lt;/i&gt; The new system, based on a diverse optical core and including wireless and wired access, would fully integrate all telecommunications functions including voice, video, data, entertainment, and educational systems. This system could remediate every problem and enable every innovation identified by the study committee.&#13;
&#13;
2) &lt;i&gt;Make selected research and administrative IT capabilities available to local first responders to improve radio communications capabilities.&lt;/i&gt; In addition to improving interoperability problems, the new systems would be integrated with IP based information architecture allowing new applications such as GIS, identity management, sensor networks, location awareness, high-speed links to criminal information databases.&#13;
&#13;
&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_communications_infrastructure.pdf"&gt;Read the full Information and Communications Infrastructure Group report&lt;/a&gt; (PDF) â€ºâ€º&#13;
&#13;
&lt;b&gt;Interface Group&lt;/b&gt;&#13;
&#13;
The Interface Group looked at policies, procedures, capabilities and interdepartmental relationships and communications for the selected areas related to identifying and supporting at-risk students. By its nature the system was found to be logically connected and responsive. The Division of Student Affairs is at the core and supported by and interacting with law enforcement, the academic enterprise, and other university resources offices.&#13;
&#13;
Consistent with the national findings of the federal report commissioned by President Bush, the Interface Group found some confusion about applicability and interpretation of privacy laws among some offices or faculty. To some extent, this created internal silos and feedback problems preventing some offices from having salient information on students at risk. The "system may not be robust enough to provide the kind of analysis that is warranted by more complex, high risk cases... with need for significant mental health services."&#13;
&#13;
The committee makes a series of recommendations under three broad themes:&#13;
&#13;
&lt;b&gt;1. Expanding Capacity in the System&lt;/b&gt;&lt;/p&gt;&#13;
&lt;p&gt;&lt;ul&gt;&lt;li&gt;Refining and expanding the Care Team, a key SA group that identifies and responds to students at risk (among other responsibilities), including addition of VTPD to standing membership and connecting academic personnel to deliberations where appropriate.&lt;/li&gt;&#13;
&lt;li&gt;Creating a Threat Assessment Team charged with examining the most complex cases of distressed students and empowering it to act quickly, when necessary.&lt;/li&gt;&#13;
&lt;li&gt;Expanding Case Management Capacity by adding case managers to the Dean of Students office and Cook Counseling Center to improve follow-up with students and to improve information flow through appropriate units about students at risk.&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;2. Improving Communications in the System&lt;/b&gt;&lt;/p&gt;&#13;
&lt;p&gt;&lt;ul&gt;&lt;li&gt;Improve Communications in the Systems with particular emphasis on privacy law education throughout the university, clarifying policies for communications with external agencies, establishing a central university contact with a clear picture of distressed students.&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p id ="nq"&gt;&lt;b&gt;3. Connecting Strategies for Identifying and Supporting at Risk Students to the Broader University Plan for Campus Safety&lt;/b&gt;&lt;/p&gt;&#13;
&lt;p&gt;&lt;ul&gt;&lt;li&gt;Expanding Training of Administrators, Faculty, and Staff in Violence Prevention recognizing the campus safety is the province of all university employees to some extent.&lt;/li&gt;&#13;
&lt;li&gt;Extending the University-wide Violence Prevention Policy to integrate the numerous university-wide efforts to enhance campus safety.&lt;/li&gt;&#13;
&lt;li&gt;Building Community to Promote Individual and Community Well Being Virginia Tech has a strong, supportive, and vibrant community which is essential in creating a safe campus environment with very good policies and support systems. However, it is recommended that a more systematic approach be instituted with campus well-being as a goal.&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_internal_communications.pdf"&gt;Read the full Interface Group report&lt;/a&gt; (PDF) â€ºâ€º&lt;/p&gt;&#13;
&lt;p&gt;&lt;hr size="1" width="50%" align="left" /&gt;&lt;/p&gt;&#13;
&lt;p&gt;&lt;b&gt;Read and/or listen to formal statements regarding the reports:&lt;/b&gt;&lt;/p&gt;&lt;p&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_steger.doc" target="new"&gt;Charles W. Steger, president&lt;/a&gt; (MS Word) | &lt;em&gt;&lt;a href="http://www.podcasts.vt.edu/internal-steger.mp3"&gt;Listen&lt;/a&gt;&lt;/em&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_hyatt.doc" target="new"&gt;James A. Hyatt, executive vice president and chief operating officer&lt;/a&gt; (MS Word) | &lt;em&gt;&lt;a href="http://www.podcasts.vt.edu/internal-hyatt.mp3"&gt;Listen&lt;/a&gt;&lt;/em&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_blythe.doc" target="new"&gt;Earving L. Blythe, vice president for information technology&lt;/a&gt; (MS Word) | &lt;em&gt;&lt;a href="http://www.podcasts.vt.edu/internal-blythe.mp3"&gt;Listen&lt;/a&gt;&lt;/em&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_niles.doc" target="new"&gt;Jerry Niles, retired dean, College of Liberal Arts &amp; Human Sciences&lt;/a&gt; (MS Word) | &lt;em&gt;&lt;a href="http://www.podcasts.vt.edu/internal-niles.mp3"&gt;Listen&lt;/a&gt;&lt;/em&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;Contact  Larry Hincker at &lt;a href="mailto:hincker@vt.edu"&gt;hincker@vt.edu&lt;/a&gt; or (540) 231-5396.&#13;
&#13;
##07433##&#13;
&#13;
--&#13;
&#13;
Original Source: Virginia Tech News&lt;br /&gt;&#13;
&lt;a href="http://www.vtnews.vt.edu/story.php?relyear=2007&amp;itemno=459"&gt;http://www.vtnews.vt.edu/story.php?relyear=2007&amp;itemno=459&lt;/a&gt;&lt;/p&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10236">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13636">
                <text>Overview of the findings and recommendations of the April 16 tragedy internal review committees</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1636">
        <name>findings</name>
      </tag>
      <tag tagId="1639">
        <name>information and communications infrastructure</name>
      </tag>
      <tag tagId="1638">
        <name>internal review committees</name>
      </tag>
      <tag tagId="1637">
        <name>recommendations</name>
      </tag>
      <tag tagId="1641">
        <name>reports</name>
      </tag>
      <tag tagId="1640">
        <name>security intrastructure</name>
      </tag>
      <tag tagId="1642">
        <name>statements</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1410" 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="2660">
                <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="4551">
                <text>Larry Hincker</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6529">
                <text>2007-09-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8407">
                <text>By &lt;a href="mailto:hincker@vt.edu"&gt;Larry Hincker&lt;/a&gt;&#13;
&#13;
BLACKSBURG, Va., September 25, 2007 -- The Virginia Tech Board of Visitors received a briefing at a special meeting September 23 on how the university plans to evaluate the hundreds of recommendations resulting from various reviews resulting from the Tragedy of April 16.&#13;
&#13;
"Reviewing, understanding, analyzing, prioritizing, and tracking the many recommendations represent a major project management task. We have created a blueprint for the next steps," said President Charles W. Steger.&#13;
&#13;
With 380 recommendations, large and small, ranging from whether to lock all academic and administrative buildings to whether to devote file servers to emergency activities, the recommendations are far reaching. "Some items are already implemented or underway. But others will require careful analysis, cost evaluation, and campus wide discussions," said Steger.&#13;
&#13;
A matrix developed by the Office of the Senior Fellow for Resource Development under former Executive Vice President Minnis Ridenour, links the various recommendations from the Virginia Tech Review Panel (the governor&amp;#39;s panel) and the three internal review committees on Security Infrastructure; Information and Communications Infrastructure; and the Interface between Counseling Services, Judicial Affairs, Academic Affairs, and Legal. It includes project management tools to appropriately task, evaluate, and act on the myriad recommendations.&#13;
&#13;
Each recommendation will be under the purview of a vice president or vice provost. "Although many recommendations are already in the process of implementation, we expect that analysis, evaluation, and identification of funding sources likely will require most of the academic year. And of course, many recommendations such as changes to state or federal codes rest outside the university&amp;#39;s purview but we will be tracking closely," said Steger.&#13;
&#13;
In order to ensure campus input where needed, President Steger is appointing two advisory groups composed of faculty, staff and students. The Committee on Human Dimensions will be chaired by Vice President for Student Affairs Zenobia Hikes, and the Committee on Security and Infrastructure will be chaired by Dean of the Pamplin College of Business Richard Sorenson.&#13;
&#13;
The Board also reviewed and approved an update to the six year plan as required under the Higher Education Restructuring Act. The law asks the university to develop six year plans to forecast enrollment, budget needs and tuition, and certain academic activities related to the Restructuring Act goals.&#13;
&#13;
&lt;a href="http://www.vtnews.vt.edu/story.php?relyear=2007&amp;itemno=554"&gt;Read a statement&lt;/a&gt; by Rector of the Board of Visitors, Jacob Lutz, regarding the Virginia Tech Action Plan.&#13;
&#13;
Contact Larry Hincker at &lt;a href="mailto:hincker@vt.edu"&gt;hincker@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=553"&gt;http://www.vtnews.vt.edu/story.php?relyear=2007&amp;itemno=553&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10378">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13728">
                <text>Board of Visitors reviews blueprint for analyzing April 16 recommendations</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <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="1776">
        <name>review committees</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1225" 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="2508">
                <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="4399">
                <text>Laura Alix</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="6377">
                <text>2007-08-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8255">
                <text>By: Laura Alix&#13;
Posted: 4/23/07&#13;
&#13;
So this is it - my final column for The Daily Campus. Over the past few weeks, I&amp;#39;ve been pondering whether I should write a more traditional "farewell" column or whether I should just do what I&amp;#39;ve been doing all along and simply give my opinion on some matter or another. Well, being the indecisive type that I do tend to be sometimes, I felt I should do a little bit of both. Bear with me, please.&#13;
&#13;
Rarely am I unsure of whether to laugh or be horrified, but then again, rarely do I check the news for updates on Fred Phelps and the Westboro Baptist Church, and rarely do I visit Phelps&amp;#39; Web site.&#13;
&#13;
For those of you who don&amp;#39;t know of the infamous Phelps, allow me to briefly fill you in. Phelps is the leader of the Westboro Baptist Church. He and his 71 followers - about 60 of whom are related to Phelps through either blood or marriage - are best known for protesting, well, just about everything. You may recall an uproar a little while back over some religious fanatics protesting the funerals of American soldiers killed in Iraq, claiming that the soldiers&amp;#39; deaths were God&amp;#39;s punishment for America&amp;#39;s tolerance of homosexuality. Those protestors were none other than Phelps and his Westboro Baptist Church. They have also protested the funeral of Matthew Shepard, productions of "The Laramie Project" - the play that details the death of Shepard - and various other political events. When criticized, Phelps simply invokes his First Amendment right to free speech.&#13;
&#13;
Phelps and the WBC have most recently made the news for their plans to protest the funerals of those killed in the Virginia Tech shootings. No, they really do not have any shame or sense of decency. Phelps has claimed that Cho Seung-Hui was hearing the voice of God and carrying out God&amp;#39;s orders, even though he is now in hell, too. The victims, according to Phelps, were punished for not being Christian enough.&#13;
&#13;
Although I consider myself non-religious, I have a hard time believing that any true Christian could believe the hateful nonsense that Phelps spews on a regular basis. His group has even made their own music videos, "God Hates the World" and "God Hates America," which is oh-so-cleverly set to the tune of "God Bless America." Ultimately, though, we really cannot take away Phelps&amp;#39; right to protest and free speech because it would be un-American to do so. The one consolation that I can offer to myself and others is we should just be grateful to live in a country so free that whackos like Phelps can enjoy the same rights as the rest of us.&#13;
&#13;
But it&amp;#39;s time to move on to the more everyday stuff. The past few weeks have been extremely hectic for me, and I&amp;#39;m sure they have been for other graduating seniors as well. I have too many projects and papers due and a serious desire to procrastinate. I&amp;#39;ve also been forgetting what day of the week it is on a pretty regular basis, waking up each morning and asking myself, "Do I go to work or class today?" I need a break by now - I think we all do.&#13;
&#13;
I&amp;#39;ve also had family members, co-workers and what feels like just about the rest of the world breathing down my neck and asking me what I&amp;#39;m going to do after graduation. This is tricky, see, because until about eight months ago, I talked about going to graduate school or law school, and when I suddenly just dropped the subjects, I guess they assumed that I still wanted to go. I really did think I would go to law school and become a lawyer when I chose political science as my major about three years ago. Honestly, it seemed like a fantastic idea until I woke up one morning and realized that I just really didn&amp;#39;t want to be a lawyer. Ditto on grad school - I just don&amp;#39;t want to pursue political science anymore, and I&amp;#39;d rather not waste the money unless I&amp;#39;m totally sure of what I want to do.&#13;
&#13;
But maybe that&amp;#39;s the whole problem to begin with. When we leave college, we are expected to know exactly what we want to do, as if this four or five year experience will help us to decide what the course of our entire lives will be. In middle school, we wondered what "the real world" would be like when we got to high school. In high school, we wondered the same thing about college. And now, well, I&amp;#39;m just not so sure that this proverbial real world is going to show its face in my presence. Much as I&amp;#39;m sure some of those in my life will be dismayed that I have not, in fact, charted the course of the rest of my life by now, I think that&amp;#39;s impossible for many people. Some people have a plan, and they stick to it from start to finish - I can admire that, but I just don&amp;#39;t think it&amp;#39;s possible for most of us. Things change.&#13;
&#13;
So what am I going to do after graduation? Right now, the post-graduation to-do list consists of the following: play some more guitar, read some more Bret Easton Ellis, quit wasting so much time on Facebook, quit buying so much junk on eBay and hopefully go to Europe - or at least Canada - at some point. Every person who has asked me, "What are you going to do with a degree in political science?" has received any one of the following smart-aleck answers: be president, be a vagabond, or be on TV. I&amp;#39;m probably going to end up going back to school again in the not-too-distant future, but right now, I need a break. Not a single one of my friends who has graduated so far has gone on to do exactly what he or she planned to do as a freshman in college - at least not yet anyway.&#13;
&#13;
I thought that upon graduating, that I would only miss The Daily Campus, but I&amp;#39;ve felt more and more lately like I just might be wrong about that. I don&amp;#39;t have the "Husky spirit," and I don&amp;#39;t like basketball or beer pong, but I&amp;#39;m still going to miss UConn somehow. My only parting advice to anybody reading this would be to make the best of these few years in any way that you can - and come write for Commentary. Goodbye everyone. Have a good life.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailycampus.com/media/storage/paper340/news/2007/04/23/Commentary/Fred-Phelps.And.A.Final.Farewell-2874465.shtml&gt;The Daily Campus - April 23, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10226">
                <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="11230">
                <text>The Daily Campus</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12077">
                <text>Melissa Bruen &lt;eic@dailycampus.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13626">
                <text>Fred Phelps And A Final Farewell</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1619">
        <name>university of connecticut&#13;
</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="425" public="1" featured="0">
    <fileContainer>
      <file fileId="281">
        <src>https://www.april16.vtlibraries.net/files/original/a_hug_for_Va_Tech_by_drainingraven_bff53b9c2a.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="14677">
                    <text>2007-06-07</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="15797">
                    <text>2007-06-07 11:45:10</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="1762">
                <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="3653">
                <text>Laura Aronson</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="5631">
                <text>2007-06-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7509">
                <text>&lt;b&gt;Artist&amp;#39;s Comments&lt;/b&gt;&#13;
&#13;
i took this at the covocation at virginia tech. there were thousands and thousands of people there--too many to fit in the castle where the speeches of important figures were live. the rest of us that couldn&amp;#39;t fit were detoured to the football stadium (where there would have been plenty of room for EVERYone)...We were forced to watch the speeches on the big screen. The audio was horrible, and many people left early. but it was nice to see all the unbroken spirit of the hokies and everyone support each other. i was very impressed with the number of people that came--not just students, but families and friends (like myself) and just anyone who wanted to show they cared.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.deviantart.com/deviation/53834709/"&gt;http://www.deviantart.com/deviation/53834709/&lt;/a&gt;&#13;
&#13;
Photo Courtesy of Laura Aronson</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9480">
                <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="11473">
                <text>Laura Aronson (drainingraven@hotmail.com)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12935">
                <text>a hug for Va Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="122">
        <name>april 17</name>
      </tag>
      <tag tagId="36">
        <name>convocation</name>
      </tag>
      <tag tagId="494">
        <name>hug</name>
      </tag>
      <tag tagId="124">
        <name>stadium</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1286" 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="2552">
                <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="4443">
                <text>Laura Chapman</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="6421">
                <text>2007-09-03</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8299">
                <text>By: Laura Chapman&#13;
Posted: 4/17/07&#13;
The university community was stunned Monday morning when a gunman killed more than 30 people, including students, at Virginia Tech University in Blacksburg, Va.&#13;
&#13;
Though more than 1,000 miles separate the University of Nebraska-Lincoln campus from Virginia Tech, UNL students and faculty members felt shock as well. University Police said they have made plans for a response to similar emergencies.&#13;
&#13;
David Solheim, the president of the Association of Students of the University of Nebraska, said the incident was almost surreal.&#13;
&#13;
"I couldn&amp;#39;t believe that something like this would happen on a college campus," said Solheim, a senior economics and international studies major. "It really makes you take your own daily life into perspective."&#13;
&#13;
Ali Moeller, the president of the Academic Senate, also expressed disbelief at the shootings in an e-mail interview.&#13;
&#13;
"It is difficult to find the words to describe such a monumental tragedy," she said.&#13;
&#13;
Moeller also said she was angry that laws allowed the shooter to have a weapon.&#13;
&#13;
"The lives of so many young men and women erased by the bullets of a madman is incomprehensible," she said.&#13;
&#13;
Capt. Carl Oestmann of University Police said the department is prepared for situations such as this.&#13;
&#13;
The preparation includes the ability to notify people of an emergency, plans to restrict access to academic and residence halls and investments in law enforcement equipment.&#13;
&#13;
Oestmann said University Police also has working relationships with other law enforcement agencies in the city, county and state.&#13;
&#13;
"It takes a combination of all of the systems to work together," he said.&#13;
&#13;
Solheim said Mobile Campus, a service ASUN has looked into investing in, could be a beneficial contact tool for the university in such emergency situations as the shootings at Virginia Tech. The service would allow UNL to send text messages to students.&#13;
&#13;
Though some might find the service expensive, it could be worth it, he said.&#13;
&#13;
"How much value do you put on a life?" Solheim said.&#13;
&#13;
Oestmann also offered his condolences to the Virginia Tech campus.&#13;
&#13;
In a late afternoon statement, Virginia Tech President Charles Steger said the university had already received condolences and messages of support from around the world. He said the well wishes were appreciated as the university worked to move forward in the next few days.&#13;
&#13;
"I cannot begin to convey my own personal sense of loss over the senselessness of such an incomprehensible and heinous act," he said.&#13;
&#13;
A convocation will be held on Virginia Tech&amp;#39;s campus today to help students and faculty members grieve.&#13;
&#13;
From her dorm room at Virginia Tech, Rachel Gicquelais, a freshman biology major, said she looks forward to attending.&#13;
&#13;
"I may not know anyone personally who died," Gicquelais said, "but I know all of us are going to be affected by the fact that part of our student body is gone."&#13;
&#13;
Gicquelais said she was in class when she found out about the first shooting, which took place in a residence hall around 7 a.m., leaving two dead. While the students in her class discussed the rumors behind that shooting, her building went into lockdown, she said.&#13;
&#13;
After waiting in the classroom for a couple hours, where her teaching assistant let the students go online to look for updates, Gicquelais was allowed to walk back to her dorm.&#13;
&#13;
Gicquelais had to take an alternative route back to her dorm, as the normal path would have taken her by Norris Hall, where 31 people were killed, including the gunman.&#13;
&#13;
Gicquelais said university officials kept students informed with frequent e-mails. Despite the shootings earlier in the day, she said the university did its best to ensure the safety of students.&#13;
&#13;
For the rest of the day, Gicquelais was glued to the television and Internet for updates. Watching the video footage of the campus has been strange for her, she said.&#13;
&#13;
"I know exactly where the videos are taken," she said. "I&amp;#39;ve walked where they are."&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailynebraskan.com/media/storage/paper857/news/2007/04/17/News/Virginia.Shooting.Shows.Need.For.Safety.Awareness.On.College.Campuses-2845122.shtml&gt; Daily Nebraskan - 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="10270">
                <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="11251">
                <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="12104">
                <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="13669">
                <text>Virginia shooting shows need for safety awareness on college campuses</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1669">
        <name>university of nebraska </name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="454" public="1" featured="0">
    <fileContainer>
      <file fileId="300">
        <src>https://www.april16.vtlibraries.net/files/original/IMG_9132_ee77e3c63c.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="14694">
                    <text>2007-06-08</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="15814">
                    <text>2007-06-08 14:57:00</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1788">
                <text>Adriana Seagle</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3679">
                <text>Laura Copcea</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="5657">
                <text>2007-06-08</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7535">
                <text>Moment de comemorare a studentilor de la universitatea Alexandru Ioan Cuza, Iasi pentru studentii de la Virginia Tech - vineri, 20 aprilie 2007&#13;
&#13;
Moment of commemoration from the students and faculty of Alexandru Ioan Cuza University, Iasi, Romania for Virginia Tech- Friday, April 20th, 2007. &#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
--&#13;
Sursa Originala: &lt;a href="&#13;
http://www.uaic.ro/uaic/bin/view/Photos/RememberVirginiaTech"&gt;http://www.uaic.ro/uaic/bin/view/Photos/RememberVirginiaTech&lt;/a&gt;&#13;
&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9506">
                <text>ron</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11498">
                <text>Laura Copcea (promovare@uaic.ro)</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="534">
        <name>alexandru ioan cuza</name>
      </tag>
      <tag tagId="435">
        <name>librescu</name>
      </tag>
      <tag tagId="529">
        <name>omagiu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="457" public="1" featured="0">
    <fileContainer>
      <file fileId="301">
        <src>https://www.april16.vtlibraries.net/files/original/IMG_9135_79d456a483.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="14695">
                    <text>2007-06-08</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="15815">
                    <text>2007-06-08 15:12:37</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1791">
                <text>Adriana Seagle</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3682">
                <text>Laura Copcea</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="5660">
                <text>2007-06-08</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7538">
                <text>Moment de comemorare a studentilor de la universitatea Alexandru Ioan Cuza, Iasi pentru studentii de la Virginia Tech - vineri, 20 aprilie 2007&#13;
&#13;
Moment of commemoration from the students and faculty of Alexandru Ioan Cuza University, Iasi, Romania for Virginia Tech- Friday, April 20th, 2007. &#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
&#13;
--&#13;
Sursa Originala: &lt;a href="&#13;
http://www.uaic.ro/uaic/bin/view/Photos/RememberVirginiaTech"&gt;http://www.uaic.ro/uaic/bin/view/Photos/RememberVirginiaTech&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9509">
                <text>ron</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11501">
                <text>Laura Copcea (promovare@uaic.ro)</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="534">
        <name>alexandru ioan cuza</name>
      </tag>
      <tag tagId="435">
        <name>librescu</name>
      </tag>
      <tag tagId="529">
        <name>omagiu</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
