<?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://april16archive.org/items/browse/tag/+media?output=omeka-xml" accessDate="2026-06-09T08:16:23+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>1</pageNumber>
      <perPage>20</perPage>
      <totalResults>60</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="2800" public="1" featured="0">
    <fileContainer>
      <file fileId="1307">
        <src>https://april16archive.org/files/original/no_media_sign_6cf3c5b53b.jpg</src>
        <authentication>40d3456f8cbd28c6357ae73015d7f8a1</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="75">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17908">
                    <text>492</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="76">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17926">
                    <text>382</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="77">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17944">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="78">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="17962">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="82">
                <name>IPTC Array</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="18014">
                    <text>a:0:{}</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="8">
        <name>Contribution Form</name>
        <description>The set of elements containing metadata from the Contribution form.</description>
        <elementContainer>
          <element elementId="39">
            <name>Submission Consent</name>
            <description>Indicates whether or not the contributor of this Item has given permission to submit this to the archive. (Yes/No)</description>
            <elementTextContainer>
              <elementText elementTextId="1083">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Posting Consent</name>
            <description>Indicates whether or not the contributor of this Item has given permission to post this to the archive. (Yes/No)</description>
            <elementTextContainer>
              <elementText elementTextId="1084">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Online Submission</name>
            <description>Indicates whether or not this Item has been contributed from a front-end contribution form.</description>
            <elementTextContainer>
              <elementText elementTextId="1085">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="89">
            <name>Contributor is Creator</name>
            <description>Indicates whether or not the contributor of the Item is responsible for its creation.</description>
            <elementTextContainer>
              <elementText elementTextId="18026">
                <text>Yes</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
      <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="3259">
                <text>Megan Minter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5237">
                <text>Megan Minter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9089">
                <text>One of the signs that went up on the buildings around campus shortly after Apr 16 directing the media to stay out of the campus buildings</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12571">
                <text>	You are contributing your stories and/or files to The April 16 Archive, which is developing a permanent digital record of the events surrounding the tragedy on the Virginia Tech campus on April 16, 2007. Your participation in this project will allow future researchers, and people such as yourself, to gain a greater understanding of these events and the responses to them.&#13;
		&#13;
	You must be 13 years of age or older to submit material to us. Your submission of material constitutes your permission for, and consent to, its dissemination and use in connection with The April 16 Archive in all media in perpetuity. If you have so indicated on the form, your material will be published on The April 16 Archive web site (with or without your name, depending on what you have indicated). Otherwise, your submitted materials will only be available to approved researchers using The April 16 Archive. The material you submit must have been created by you, wholly original, and shall not be copied from or based, in whole or in part, upon any other photographic, literary, or other material, except to the extent that such material is in the public domain. Further, submitted material must not violate any confidentiality, privacy, security or other laws.&#13;
&#13;
	By submitting material to The April 16 Archive you release, discharge, and agree to hold harmless The April 16 Archive and persons acting under its permission or authority, including a public library or archive to which the collection might be donated for purposes of long-term preservation, from any claims or liability arising out the The April 16 Archive's use of the material, including, without limitation, claims for violation of privacy, defamation, or misrepresentation.&#13;
&#13;
	The April 16 Archive has no obligation to use your material.&#13;
&#13;
	You will be sent via email a confirmation of your contribution to The April 16 Archive. We cannot return any material you submit to us so be sure to keep a copy. The April 16 Archive will not share your email address or any other information with commercial vendors.&#13;
	</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14396">
                <text>No More Media</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="424">
        <name>campus</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2033" public="1" featured="0">
    <fileContainer>
      <file fileId="932">
        <src>https://april16archive.org/files/original/467337804_04bd281805_b_849d0e4593.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="15289">
                    <text>2008-04-06</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16409">
                    <text>2008-04-06 15:19: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="2972">
                <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="4863">
                <text>Roger Gupta</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="6841">
                <text>2008-04-06</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8719">
                <text>A student is interviewed by the media. Burruss Hall in background.&#13;
&#13;
Photo by Roger Gupta.&#13;
&#13;
--&#13;
&#13;
Original Source:&#13;
&lt;a href="http://www.flickr.com/photos/spector1/467337804/in/set-72157600104116028/"&gt;http://www.flickr.com/photos/spector1/467337804/in/set-72157600104116028/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10690">
                <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="12315">
                <text>"Gupta, Roger" &lt;ragupta@vt.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14034">
                <text>Under the glare</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="773">
        <name>burruss hall</name>
      </tag>
      <tag tagId="775">
        <name>interviews</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="2099">
        <name>news cameras</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1927" 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="2944">
                <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="4835">
                <text>Lawrence G. Hincker</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6813">
                <text>2008-03-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8691">
                <text>Date:  	Sun, 23 Mar 2008 15:05:04 -0400&#13;
From: 	Unirel@vt.edu&#13;
To: 	Multiple recipients &lt;LISTSERV@LISTSERV.VT.EDU&gt;&#13;
Subject: 	Preparing for Media on April 16&#13;
&#13;
&#13;
March 2008&#13;
&#13;
To the Students, Faculty, and Staff of Virginia Tech&#13;
 &#13;
As you can imagine, there remains significant ongoing media interest in Virginia Tech in light of the tragedy that occurred on our campus last April 16.  As is customary for an event of this magnitude - one that gripped not only reporters, but the entire world -  there will be anniversary coverage on or around April 16, 2008.&#13;
&#13;
We expect again to have many, many reporters, broadcasters, and cameras on campus during that week and/or at the remembrances planned for that day.&#13;
&#13;
As I did last year, let me again apprise you of our policy and the law. Our university is public property. Roads are public thoroughfares.  We cannot bar the media, although many have suggested it.  We will be working to provide appropriate but limited access to the campus.  I believe that most were respectful of you and the circumstances of our healing last year.&#13;
&#13;
Reporters (or other visitors) are never allowed in classrooms without the faculty member&amp;#39;s permission.  This is a moot point, since classes are cancelled on April 16.  Still, we are apprising the media to refrain from entering academic buildings before or after April 16.  Residence halls are always off limits to any visitor unless approved by a resident or a member of the student affairs&amp;#39; leadership.  Spaces like offices and labs are always controlled by the occupants. Certain university buildings have nominal public access and you may bump into a reporter.  If a building is open to the public, it is open to all members of the public.&#13;
&#13;
What should you do if a member of the news media approaches you for an interview either on that day or before?  You are never REQUIRED to speak to a reporter.  Politely telling a reporter &amp;#39;no thank you&amp;#39; will suffice.  If a reporter is particularly insistent, just walk away and do not feel guilty about doing so. We have posted media guidelines at www.remembrance.vt.edu.&#13;
&#13;
However, we have a powerful story to tell. We have prevailed and we are healing.  The Hokie Nation is strong. You have represented us well during some very trying times.  You have shown the world the special nature of Hokie Spirit and our sense of community.   The close-knit nature of this academic community was readily apparent throughout the days and months after April&amp;#39;s tragedy and continues.&#13;
&#13;
If interviewed, I would expect a reporter to ask you about April 16.   Go only as far as you feel comfortable.  You control the discussion. Students and professors with whom I&amp;#39;ve discussed this possibility are in different places emotionally.  Many are ready to move on and speak to the now or the future.  Frankly, I like to focus on what we were before April 16 and what we remain today - one of America&amp;#39;s leading universities focused on learning, discovery, and engagement.  You help invent the future.&#13;
&#13;
Virginia Tech&amp;#39;s reputation and legacy are founded on the quality of its people.  I have great confidence in the university community and the institution as we continue on the road to recovery.&#13;
&#13;
If you have any concerns, please do not hesitate to contact our office at unirel@vt.edu or 231-5396.&#13;
&#13;
Sincerely yours,&#13;
 &#13;
Lawrence G. Hincker&#13;
Associate Vice President&#13;
University Relations</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10662">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14007">
                <text>Preparing for Media on April 16</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1989">
        <name>anniversary</name>
      </tag>
      <tag tagId="1363">
        <name>hincker</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="115">
        <name>university relations</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1787" 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="2908">
                <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="4799">
                <text>James Dechant</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="6777">
                <text>2008-02-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8655">
                <text>Observer Viewpoint&#13;
Issue date: 4/19/07 Section: Viewpoint&#13;
&#13;
Anyone old enough to speak coherently at the time still remembers the moment, over forty years ago, when they heard about JFK&amp;#39;s assassination. Our grandparents can tell us how they listened to the radio accounts of Pearl Harbor on a December day, more than six decades gone. Every single one of us here at Notre Dame can recall where we were on the day of Sept. 11, 2001 - what we were doing, how the horribly tragic events of that morning unfolded for us and our personal feelings on the matter. Any time someone shares a personal story of That Day, I&amp;#39;m always amazed at the details people recall.&#13;
&#13;
I remember listening to Paul Harvey&amp;#39;s show on my AM radio while driving to school when he announced the first plane crash. I remember talking about it with my friend before the start of first-hour Biology, and I remember the girl who came in and told us the other tower had been hit. I remember conversations I had that day, things different teachers said and talking with my grandparents in the evening. That was my experience, half a country away, without a personal connection to anyone involved. The mass media of the past century gave rise to a new, shared cultural experience, a common reference point that breaches distance and background: the generation-defining event.&#13;
&#13;
When we hear 9/11 described this way, it is absolutely on-target.&#13;
&#13;
This week, we have another national tragedy. News of the massacre at Virginia Tech on Monday spread like wildfire throughout both national and international outlets, even reaching most of us studying abroad in Europe within the hour. We learned of the catastrophe over television stations, through quickly formed Facebook groups, on Internet news sites and during instant messaging conversations. Solid facts came slowly, but no report could sanitize away the fear, confusion, anger, torrential grief and host of other emotions that assault us all in such times.&#13;
&#13;
This is the great curse of our generation&amp;#39;s hyper-awareness and the awesome power of modern media. We cannot escape the sentiments swirling around the tragedies, and they cannot remain anonymous or distant to us. It is hard to ignore the images of grown men and women crying as dead college students are carried away, the surreal sounds of gunshots being fired on a peaceful college campus or the first-hand accounts of courage and action during the Virginia shootings. I hesitate to compare this with 9/11; the numbers, circumstances, impact, source, scope and means are worlds apart. Yet both incidents serve to painfully remind us that these events always seem to be associated with sorrow, tragedy and death.&#13;
&#13;
 The events of Monday, though still fresh in my mind, will probably not stick with me as do those of 9/11. Sadly, the thousands of students and faculty and staff connected with the university, the thousands of parents worrying at home and the thousands of residents in the surrounding community don&amp;#39;t have that luxury of separation. For them, this will become a "where were you when..." event. Monday will haunt their minds and stay with them for the duration of their lives. Healing can take place, and God willing, can come soon, but memories of all the little details from Monday will stick. Meanwhile, the rest of us are stuck asking ourselves: How many more of these "defining" events can we plan on seeing in the coming years and decades? And when can we expect one judged not by the body count or human toll, but by the rewards and human joy brought about?&#13;
&#13;
Some may say any event that becomes constantly discussed, like 9/11, does not develop its crystalline clarity in the moments of its occurrence, but rather slowly cements itself during the constant regurgitation of facts and satellite details in the months and years following. Even if this were the case, we are still left empty-handed trying to think of a ubiquitous positive event. I firmly believe that such events, incredibly wonderful instead of shockingly horrific, are entirely possible. Unfortun-ately, we are still waiting to see what such an event would look like.&#13;
&#13;
The consistently negative nature of these events can be explained to some degree. "Good events," for one, rarely culminate in one triumphant moment. Tragedy, on the other hand, catches us unaware. In the shock, the horrific facts come slowly and there are a thousand unknowns. With triumphant accomplishments, the event is often merely symbolic and known well in advance. The closest models I can call to mind are the fall of the Berlin Wall - which I and most of my classmates were too young to remember - and the moon landing, decades before we were born.&#13;
&#13;
Our generation, already exposed to so much death and murder and war and evil, still waits for its anti-9/11. We have yet to gather around our televisions and computers to share joy instead of sorrow, fulfillment instead of shock, pleasure instead of anger. We are the waiting. But for the moment, in respect for the Virginia Tech community, let us remember that we are also among the mourning.&#13;
&#13;
James Dechant is a junior studying abroad in Rome this semester. Questions, complaints and rude remarks can be sent to jdechant@nd.edu&#13;
&#13;
The views expressed in this article are those of the author and not necessarily those of The Observer.&#13;
&#13;
--&#13;
&#13;
Original Source:&#13;
&lt;a href="http://media.www.ndsmcobserver.com/media/storage/paper660/news/2007/04/19/Viewpoint/Still.Waiting.For.Our.Victory-2852060.shtml"&gt;http://media.www.ndsmcobserver.com/media/storage/paper660/news/2007/04/19/Viewpoint/Still.Waiting.For.Our.Victory-2852060.shtml&lt;/a&gt;&#13;
&lt;a href="http://media.www.ndsmcobserver.com/media/storage/paper660/news/2007/04/19/Viewpoint/Still.Waiting.For.Our.Victory-2852060-page2.shtml"&gt;http://media.www.ndsmcobserver.com/media/storage/paper660/news/2007/04/19/Viewpoint/Still.Waiting.For.Our.Victory-2852060-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="10626">
                <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="12264">
                <text>Christopher Hine &lt;chine@nd.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13971">
                <text>Still waiting for our victory</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1977">
        <name>9/11</name>
      </tag>
      <tag tagId="172">
        <name>facebook</name>
      </tag>
      <tag tagId="2023">
        <name>jfk</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="2002">
        <name>notre dame</name>
      </tag>
      <tag tagId="1933">
        <name>students abroad</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1696" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  Note that facsimiles or images of texts are still of the genre text.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2837">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4728">
                <text>Ry Rivard</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6706">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8584">
                <text>Issue Date:Tuesday April 17, 2007   &#13;
Section: Editorial Section&#13;
Ry Rivard, City Editor&#13;
&#13;
By the end of the Monday it was obvious that the media had begun selling the day&amp;#39;s horrors at Virginia Tech. No matter the gravity or magnitude of a tragedy, this country&amp;#39;s commentators veer from events as they are, in and of themselves horrible, to a decontextualized, surreal account of things so they can be sold to and consumed by us.&#13;
&#13;
The shooting - the deadliest shooting in American history - quickly became, for some people, another chance to make various political points. It became, by the time Wolf Blitzer&amp;#39;s show aired, a sort of tragic-porn, a way for the media to provoke rather than inform. Commentators tried to politicize it, politicians tried to comment on it, the news channels tried to heighten the drama with their usual parade of loud music and epic comparisons, "This is worse than ... " or "This is the biggest ... " Was what happened not enough in and of itself?&#13;
&#13;
Glenn Reynolds, law professor at University of Tennessee, quickly posted a 52-page paper on his popular Weblog arguing that the best way to prevent shootings like Monday&amp;#39;s is to permit concealed handguns. It was the day&amp;#39;s most academic approach to the event, but it was also one of the most callous.&#13;
&#13;
Written by two economists, the paper concluded that "the only policy factor to influence multiple victim public shootings is the passage of concealed handgun laws." Reynolds and several others who followed his lead took the deaths of 33 students to advance an agenda which, although done in an attempt to stop such events in the future, made them into a policy argument.&#13;
&#13;
Similarly, the Drudge Report, a conservative news site, dragged out a fourth-month old story from Roanoke Times about failed piece of legislation that would have permitted concealed handguns.&#13;
&#13;
It reported, "Virginia Tech spokesman Larry Hincker was happy to hear the bill was defeated. &amp;#39;I&amp;#39;m sure the university community is appreciative of the General Assembly&amp;#39;s actions because this will help parents, students, faculty and visitors feel safe on our campus.&amp;#39;"&#13;
&#13;
The point was: if students hadn&amp;#39;t had to wait for the police to arrive, Monday&amp;#39;s shootings would have been an incident and not a tragedy. The effect of their ill-made point was that gun control advocates were somehow responsible for the shooting.&#13;
&#13;
In response, the Huffington Post highlighted a story that the White House affirmed the "president believes that there is a right for people to bear arms." Their point: if only there had been a law against carrying weapons (and there is - VT&amp;#39;s handbook doesn&amp;#39;t permit guns on campus), this wouldn&amp;#39;t have happened. The effect of that point was that somehow the Second Amendment or the Bush Administration was responsible for the shooting.&#13;
&#13;
The politicians, meanwhile, all took care to come out and say how horrible the events were. Perhaps they thought if they didn&amp;#39;t grandstand on TV with their condolences, someone might mistake their silence for support?&#13;
&#13;
The news channels proved again that constant, breathless coverage undermines the fundamental tragedy, horror and fact of an event. CNN escalated its description of the shootings from "monumental" to a "rampage" to a "massacre," to a "bloodbath," as if their appellations signified anything but their desire to sell the story.&#13;
&#13;
By Monday evening, each station had begun saying as often as possible how tragic the obvious tragedy was, and how horrible the horror was - and at the same time they plugged their own brand: "Stay tuned to us for ... " For what? For whatever scarce news they could pry from any student on the VT campus they could pull aside and, occasionally, attempt to provoke into more tears with probing, useless questions.&#13;
&#13;
CNN kept mentioning their "I Reporters," which is their way of saying "people who sent us pictures from their cell phones."&#13;
&#13;
If the media&amp;#39;s reaction Monday was a sign of the American psyche, we are a country that cannot understand an event outside of a political framework, and we are a country that cannot understand an event as it is.&#13;
&#13;
There were two terrible but - compared to the media&amp;#39;s carnival barker commentary - honest accounts from Monday. The first was cell phone video footage taken outside the building of the shootings that captured the sounds of 27 shots being fired, presumably into somebody. It was replayed and replayed and, after a while, it became a selling point for CNN rather than a way to describe the day&amp;#39;s events.&#13;
&#13;
The second account, reminiscent of Sept. 11, came from a student who told ABC News, "Everyone started panicking and jumping out the window."&#13;
&#13;
But there is nothing anyone can say that makes it make sense, so, from Lord Byron:&#13;
&#13;
And thou art dead, as young and fair&#13;
&#13;
As aught of mortal birth;&#13;
&#13;
And form so soft, and charms so rare,&#13;
&#13;
Too soon return&amp;#39;d to Earth!&#13;
&#13;
Though Earth receiv&amp;#39;d them in her&#13;
&#13;
bed,&#13;
&#13;
And o&amp;#39;er the spot the crowd may&#13;
&#13;
tread&#13;
&#13;
In carelessness or mirth,&#13;
&#13;
There is an eye which could not brook&#13;
&#13;
A moment on that grave to look.&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27550"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27550&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10555">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12195">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13901">
                <text>When tragedy is for sale, it isnâ€™t tragic enough</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1964">
        <name>commentators</name>
      </tag>
      <tag tagId="1966">
        <name>concealed handgun laws</name>
      </tag>
      <tag tagId="1965">
        <name>drama</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="312">
        <name>politics</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1486" public="1" featured="0">
    <fileContainer>
      <file fileId="753">
        <src>https://april16archive.org/files/original/1483116677_7f9d73f7eb_o_84ff3e65db.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="15117">
                    <text>2007-10-25</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="16237">
                    <text>2007-10-25 23:26: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="2717">
                <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="4608">
                <text>Christopher Bowns</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="6586">
                <text>2007-10-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8464">
                <text>Photo taken April 18, 2007.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.flickr.com/photos/cipherswarm/1483116677/"&gt;http://www.flickr.com/photos/cipherswarm/1483116677/&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-sa/2.0/deed.en-us"&gt;Creative Commons Attribution-Share Alike 2.0 Generic&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10435">
                <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="12151">
                <text>Creative Commons Attribution-Share Alike 2.0 Generic</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13785">
                <text>Satellite Trucks at the Virginia Tech Inn</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1821">
        <name>april 18</name>
      </tag>
      <tag tagId="346">
        <name>inn</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="1822">
        <name>satellite trucks</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1331" public="1" featured="0">
    <fileContainer>
      <file fileId="665">
        <src>https://april16archive.org/files/original/1174168223_3f4a032ccd_o_42d1f9d169.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="15032">
                    <text>2007-09-09</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16152">
                    <text>2007-09-09 18:01:31</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2592">
                <text>Haeyong Chung</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4483">
                <text>null</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="6461">
                <text>2007-09-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8339">
                <text>Media coverage of the memorial dedication ceremony on August 19, 2007.&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-sa/2.0/"&gt;Creative Commons Attribution-NonCommercial-ShareAlike 2.0&lt;/a&gt;.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.flickr.com/photo_zoom.gne?id=1174168223&amp;context=set-72157601548585076&amp;size=o"&gt;http://www.flickr.com/photo_zoom.gne?id=1174168223&amp;context=set-72157601548585076&amp;size=o&lt;/a&gt;&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10310">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13709">
                <text>Dedication3</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1699">
        <name> august 19</name>
      </tag>
      <tag tagId="1697">
        <name> camera</name>
      </tag>
      <tag tagId="1698">
        <name>associated press</name>
      </tag>
      <tag tagId="1576">
        <name>dedication ceremony</name>
      </tag>
      <tag tagId="664">
        <name>intermediate memorial</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="1574">
        <name>memorial dedication</name>
      </tag>
      <tag tagId="454">
        <name>nbc</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1326" public="1" featured="0">
    <fileContainer>
      <file fileId="660">
        <src>https://april16archive.org/files/original/1175029020_9769e789f3_o_5e458110ec.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="15027">
                    <text>2007-09-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="16147">
                    <text>2007-09-08 22:27:22</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="2587">
                <text>Haeyong Chung</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4478">
                <text>null</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="6456">
                <text>2007-09-08</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8334">
                <text>Students carrying chairs at the memorial dedication ceremony on August 19, 2007.&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-sa/2.0/"&gt;Creative Commons Attribution-NonCommercial-ShareAlike 2.0&lt;/a&gt;.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.flickr.com/photo_zoom.gne?id=1175029020&amp;context=set-72157601548585076&amp;size=o"&gt;http://www.flickr.com/photo_zoom.gne?id=1175029020&amp;context=set-72157601548585076&amp;size=o&lt;/a&gt;&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10305">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13704">
                <text>Dedication9</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1575">
        <name>august 19</name>
      </tag>
      <tag tagId="1583">
        <name>crowd</name>
      </tag>
      <tag tagId="1576">
        <name>dedication ceremony</name>
      </tag>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="664">
        <name>intermediate memorial</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="1574">
        <name>memorial dedication</name>
      </tag>
      <tag tagId="54">
        <name>students</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1307" public="1" featured="0">
    <fileContainer>
      <file fileId="641">
        <src>https://april16archive.org/files/original/im_070417_april16_097_ff138b5e05.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="15009">
                    <text>2007-09-04</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16129">
                    <text>2007-09-04 21:09:24</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="2569">
                <text>Haeyong Chung</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4460">
                <text>Ivan V. Morozov</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6438">
                <text>2007-09-04</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8316">
                <text>2007.04.17.&#13;
A view of the crowd at the candlelight vigil on the Drill Field of the Virginia Tech campus.&#13;
&#13;
Photo courtesy of Ivan V. Morozov&#13;
 &#13;
 &#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10287">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13686">
                <text>At The Vigil </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="215">
        <name>candlelight vigil</name>
      </tag>
      <tag tagId="1583">
        <name>crowd</name>
      </tag>
      <tag tagId="342">
        <name>drill field</name>
      </tag>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1301" public="1" featured="0">
    <fileContainer>
      <file fileId="635">
        <src>https://april16archive.org/files/original/im_070417_april16_054_e3e9c90bc1.jpg</src>
        <authentication>null</authentication>
        <elementSetContainer>
          <elementSet elementSetId="1">
            <name>Dublin Core</name>
            <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
            <elementContainer>
              <element elementId="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="15005">
                    <text>2007-09-04</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16125">
                    <text>2007-09-04 20:52:46</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2565">
                <text>Haeyong Chung</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4456">
                <text>Ivan V. Morozov</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6434">
                <text>2007-09-04</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8312">
                <text>2007.04.17.&#13;
Ever present media is setting up to report from the Drill Field about the candlelight vigil.&#13;
&#13;
Photo courtesy of Ivan V. Morozov</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10283">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13682">
                <text>Media </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1672">
        <name>broadcast</name>
      </tag>
      <tag tagId="342">
        <name>drill field</name>
      </tag>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="344">
        <name>reporter</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1161" public="1" featured="0">
    <fileContainer>
      <file fileId="586">
        <src>https://april16archive.org/files/original/P1010506b_88afd05f0e.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="14968">
                    <text>2007-08-20</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="16088">
                    <text>2007-08-20 00:03:54</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="2456">
                <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="4347">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6325">
                <text>2007-08-20</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8203">
                <text>After the intermediate memorial dedication ceremony, interviews such as this one were commonplace. But while there was clearly a media presence at this event, it was subdued in comparison to the immediate aftermath of April 16.&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc-sa/3.0/"&gt;Creative Commons Attribution-NonCommercial-ShareAlike 3.0&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10174">
                <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="12029">
                <text>Creative Commons Attribution-NonCommercial-ShareAlike 3.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13574">
                <text>Post-Dedication Interview</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1576">
        <name>dedication ceremony</name>
      </tag>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="664">
        <name>intermediate memorial</name>
      </tag>
      <tag tagId="345">
        <name>interview</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="1574">
        <name>memorial dedication</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1142" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  Note that facsimiles or images of texts are still of the genre text.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2440">
                <text>Sara  Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4331">
                <text>Tammesia Green</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6309">
                <text>2007-08-19</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8187">
                <text>By Tammesia Green			&#13;
&#13;
Following the massacre that occurred at Virginia Tech University on April 16, many have come to question their own safety at universities across the country. The profile of a school shooter, once narrowed to a lonely white male high-school student with a fascination with and open access to guns, was quickly re-examined as we discovered the shooter to be 23-year-old Cho Seung-Hui. But before the news had been released that the shooter was Asian, the question on everyone&amp;#39;s mind was whether this catastrophe could have been prevented. This question is a good one, and should be debated, but reflecting on the length of time the press devoted to this subject was unsettling for me.&#13;
&#13;
&#13;
I remember going to class the morning of the shooting and hearing news reports that two people had been shot at a Virginia Tech dormitory. Upon my return five hours later I was shocked to see the death toll had escalated to 33. Immediately, I wanted to know what had happened and if the killer had been caught. Watching the news, all I could find were reporters asking questions like, "Why wasn&amp;#39;t the school placed on lockdown? What time was the first e-mail sent to students?  Why wasn&amp;#39;t more done to prevent this tragedy?"&#13;
&#13;
&#13;
It became clear that I would not learn anything about what actually took place on the campus that could account for the casualty numbers rising; I had to resort to the Internet to try to make sense of all that was happening. After getting a clear account, I was upset at the amount of time the network news channels devoted to placing blame on officials at Virginia Techâ€”only, the "placing blame" was not seen for what it was. Instead, it was promoted as good investigative journalism.&#13;
&#13;
&#13;
I understand that it is the job of a journalist to ask the hard questions and uphold a level of accountability toward officials. However, I found that the questions posed by reporters in press conferences regarding Virginia Tech were not necessarily out of line, but a result of constant criticism of their inability to question authority in high-stakes situations.&#13;
&#13;
&#13;
Past disasters such as Hurricane Katrina and the logic behind going to war with Iraq played their roles in the types of questions posed to Virginia Tech President Charles Steger. These questions were simply a ploy to preemptively avoid any backlash from the public for not addressing accountability. &#13;
&#13;
&#13;
Following the invasion of Iraq and never finding weapons of mass destruction, the public began to demand that journalists not be afraid to question authority and command answers from high-ranking officials. Hurricane Katrina allowed for reporters to regain some credibility by analyzing slow relief efforts and the lack of preparation from the government. It is no surprise that in order to keep credibility and uphold the public&amp;#39;s faith in reporters, journalists continued to grow a backbone and demanded answers from those in power. &#13;
&#13;
&#13;
The word "accountability" is ultimately what forced the media to focus on how administrators screwed up and not the shooter. But accountability is not to be placed on school administrators and campus police when the act was really the work of one man, and only he can be blamed. Real investigative journalism would have been to expose the motives of Cho, not debate whether an e-mail should have been sent earlier or been more detailed. Even as students from the Virginia Tech campus were being interviewed and asked if their administration at the university should have done more, the look of "Are you really asking me this now?" ran across most of their faces. They, like me, could not understand why their administrators were being harassed as if they made the events unfold, and not Cho.&#13;
&#13;
&#13;
There is no way administrators at Virginia Tech could have predicted that a domestic dispute incident would be cause for the closing of an entire university. Anyone who thinks they would have had the notion to suspend classes and not think of the first attack as an isolated incident is thinking in the context of hindsight. Colleges enroll large quantities of students, equivalent to the population of some U.S. cities. Just like a city, Virginia Tech did not shut down when evidence of a homicide was discovered. &#13;
&#13;
&#13;
It is nice to want to believe that our college campuses are the last step before entering the real world, and are therefore void of the many threats society holds. But evil does exist and it knows no bounds. This evil of one individual is the only factor that should matter in evaluating who is accountable for the Virginia Tech massacre.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.newuniversity.org/showArticle.php?id=5789&gt;New University - April 30, 2007&lt;/a&gt;&#13;
&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10158">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="11195">
                <text>New University</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12013">
                <text>Zachary Gale &lt;newueic@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13558">
                <text>Media Coverage of VT Tragedy Irresponsible</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1108">
        <name>criticism</name>
      </tag>
      <tag tagId="539">
        <name>journalism</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="297">
        <name>media coverage</name>
      </tag>
      <tag tagId="1563">
        <name>university of california - irvine</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1133" 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="2431">
                <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="4322">
                <text>STAFF EDITORIAL</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="6300">
                <text>2007-08-19</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8178">
                <text>By: STAFF EDITORIAL&#13;
Posted: 4/20/07&#13;
&#13;
Just days after the tragic shooting at Virginia Tech, NBC made the inappropriate decision to release videos of killer Cho Seung-Hui angrily ranting about the reasoning behind his crimes.&#13;
&#13;
Cho had sent a package that contained 43 photos, 28 video clips and a 23-page letter directly to NBC headquarters in New York during a break in his shooting spree on Monday. After NBC first released the shocking "multimedia manifesto" on the NBC Nightly News broadcast, 24-hour news networks quickly followed suit, constantly showing the disturbing video excerpts and photo clips.&#13;
&#13;
The media&amp;#39;s release of Cho&amp;#39;s photos and diatribe gave a deeper look into the mind and motivations of the killer, a decision that has had a great ripple affect across the country. While NBC stands by its decision to release the material, we believe the choice was made too hastily, without much thought or sensitivity for the families of the victims of the shooting, who have only had days to handle the emotional effects of losing their loved ones.&#13;
&#13;
Forensic psychiatrist and ABC News consultant Michael Welner appeared on "Good Morning America" yesterday to discuss the troublesome consequences. "This is a social catastrophe," Welner said. "This is perversion...[Cho] needs to create and produce his own picture in order to give himself a sense of power. Nobody saw him that way...that&amp;#39;s why he set this up and he did this to achieve immortality."&#13;
&#13;
Welner&amp;#39;s argument is logical. This footage does not present the public with any deeper knowledge about the crimes and, for that reason, it is not at all newsworthy. Instead, showing the video is a disrespectful and insensitive action toward the Blacksburg victims. Furthermore, the broadcast footage gives the fame-seeking Cho an audience and a stage where he can attempt to justify his crimes. In other words, it gives him exactly what he wanted.&#13;
&#13;
The problem is that 24-hour news networks have the unsettling habit of overeagerly reporting breaking news before having time to reflect upon the consequences of their coverage. NBC and other media outlets are pressured to constantly search for exciting and stimulating material to put on the air and as a result, they neglect to spend time on research and deliberation.&#13;
&#13;
That&amp;#39;s what went wrong here. Cho&amp;#39;s video collection was treated as news gold and was broadcasted without enough forethought. NBC and the other news networks had an obligation to act more responsibly. The videos and photos should have been carefully investigated before they were broadcast. Someone should have sat back and reflected upon the material and the negative repercussions that could follow.&#13;
&#13;
Unfortunately, our media tends to do this kind of thing all the time. As soon as we turn on our televisions, we are bombarded with news tickers, terror alerts and breaking stories that are blown up and emphasized to the extreme. Networks play on fear and paranoia to attract viewers, giving us shocking and reactive spurts of material that only serve to rouse our emotions.&#13;
&#13;
Instead of focusing on being the first to get the scoop, NBC and other media outlets should concentrate on thoughtfully investigating material before putting them on the air. &#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.pittnews.com/media/storage/paper879/news/2007/04/20/Opinion/Editorial.Media.Exploits.Killers.Manifesto-2870222.shtml&gt;The Pitt News - April 20, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10149">
                <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="11191">
                <text>The Pitt News</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12005">
                <text>Annie Tubbs &lt;annietubbs@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13549">
                <text>EDITORIAL - Media exploits killer&amp;#39;s manifesto</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="1562">
        <name>media criticism </name>
      </tag>
      <tag tagId="847">
        <name>media response</name>
      </tag>
      <tag tagId="1559">
        <name>pitt university</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1123" 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="2423">
                <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="4314">
                <text>Mark McNamee</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="6292">
                <text>2007-08-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8170">
                <text>Date: Fri, 17 Aug 2007 11:25:23 -0400&#13;
From: Provost@vt.edu&#13;
To: Multiple recipients &lt;LISTSERV@LISTSERV.VT.EDU&gt;&#13;
Subject: Provost Update August 17, 2007&#13;
&#13;
August 17, 2007&#13;
Dear Faculty and Staff Colleagues:&#13;
&#13;
You are probably noticing that the students are moving back to Blacksburg this week. (It is a good time to stay away from Washington Street.) The start of the fall semester is always an exciting time and we will be welcoming over 5,000 freshmen in the great new class of 2011. We will also be welcoming approximately 100 new faculty colleagues across all eight colleges. The first day of class will be a memorable adventure.&#13;
&#13;
Many departments and colleges have been busy this week with pre-semester retreats, planning sessions, and orientations. I realize that you are receiving multiple forms of communication about ongoing and new activities. I am going to highlight a few key issues and events recognizing that you have heard or will hear more about each of these items in different ways.&#13;
&#13;
1. The three internal reviews requested by President Steger will be presented soon. James Hyatt chaired the group looking at infrastructure and security; Erv Blythe chaired the group looking at networking; and Jerry Niles chaired the group looking at the relationships among the academic, judicial, counseling, and legal systems. Each group will provide an overview of existing structures and programs and will make recommendations for enhancements. Some of the relevant items have been or are being implemented already (such as VT Alerts), and a comprehensive summary and outline of additional security enhancements was prepared by Executive Vice President James Hyatt. A note of immediate relevance to faculty instructors: the general assignment classrooms are being fitted with hardware that will allow rooms to be locked from the inside with automatic unlocking features when exiting.&#13;
&#13;
2. The dedication ceremony of the memorial on the Drillfield will be held at noon on Sunday. All members of the university and extended community are invited. Faculty and student representatives will provide brief comments.&#13;
&#13;
3. Human Resources and the Cook Counseling Center are coordinating efforts to provide counseling support to faculty, staff, and students next week. There will be two primary sites staffed by trained professionals: a tent on the Drillfield and Squires Student Center. Counselors will be able to travel to other locations as needed. In addition, counselors will be specifically assigned to a few key locations (including Norris Hall). In April, faculty members implemented a plan to invite a faculty colleague to attend class on the first day. The colleague was available to provide collegial support and to be available, if needed, to help with any issues that came up.&#13;
&#13;
The college deans&amp;#39; offices are helping to promote and encourage a similar system next week. Last spring we relied on the good judgment of faculty members to decide how best to address and respond to the events of April 16. We will do so again. I anticipate that most students and faculty in the classroom will be eager to focus on what we do best: teaching and learning. CEUT held some sessions for faculty this week and will have follow-up sessions over the next few weeks. Your feedback about your experiences and the experiences of the students will be helpful.&#13;
&#13;
4. You have received advice about media attention early in the week. You are free to talk with the media, but you are under no obligation to do so. Also, you can decide what issues you want to discuss. You have control over who is admitted to your classrooms.&#13;
&#13;
5. The "Concert for Virginia Tech" on Thursday, September 6 is going to have an impact on classes that evening. As of now, we are planning to cancel classes beginning at 5 p.m. so that all faculty, staff, and students may attend the concert if they wish. Unlike the situation with football games, the parking lots are open to regular use and no one will be expected to vacate spaces in specific lots. As provost, I am never thrilled when the regular academic schedule is affected by non-academic events. We are going through an important phase of the healing process and I hope you will embrace the positive features of this unique contribution to the Virginia Tech community.&#13;
&#13;
6. One of the highlights of the academic year will be a special program that brings emphasis to our commitment to the unique responsibilities and opportunities that come from being Virginia&amp;#39;s senior land-grant university, as well as highlights the Student Engagement component of our Strategic Plan. The program, which we are calling VT-ENGAGE, is a university-wide initiative that reaffirms our motto, Ut Prosim, by facilitating and leading opportunities for students, faculty, staff, alumni, and community members to participate in community service, service learning, and volunteerism. During its inaugural year 2007-2008, VT-ENGAGE will honor the victims of the tragedy of April 16 and the commitment to service they demonstrated within their communities worldwide.&#13;
&#13;
A Steering Committee, which includes broad representation of faculty, staff, students, administrators, and community leaders, is working diligently on the planning for VT-ENGAGE. The committee has established a goal of at least 300,000 hours of service/service learning. Each member of the university community will be challenged to commit at least 10 hours during the academic year. We hope that each of you will choose to participate and that you will find creative ways to include the spirit of VT-ENGAGE in your teaching, research, and outreach.&#13;
&#13;
A major event will be held on the Drillfield the evening of October 16 to kick-off VT-ENGAGE. Community organizations are being invited to have displays and to sign-up volunteers. The event will be festive and feature stories of how Virginia Tech students, faculty, staff, students, and alumni make a difference in communities around the world. Much more to come.&#13;
&#13;
We believe VT-ENGAGE will send another positive message that Virginia Tech is a very special community with a spirit that does indeed prevail.&#13;
&#13;
Best wishes for a successful start to the new academic year.&#13;
&#13;
Mark McNamee&#13;
University Provost and Vice President for Academic Affairs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10141">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13541">
                <text>Provost Update August 17, 2007</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1554">
        <name>concert</name>
      </tag>
      <tag tagId="1553">
        <name>concert for virginia tech</name>
      </tag>
      <tag tagId="1552">
        <name>counseling</name>
      </tag>
      <tag tagId="664">
        <name>intermediate memorial</name>
      </tag>
      <tag tagId="1551">
        <name>internal reviews</name>
      </tag>
      <tag tagId="1549">
        <name>mcnamee</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="1550">
        <name>provost</name>
      </tag>
      <tag tagId="187">
        <name>security</name>
      </tag>
      <tag tagId="1555">
        <name>vt-engage</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1088" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  Note that facsimiles or images of texts are still of the genre text.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2388">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4279">
                <text>Lawrence G. Hincker</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6257">
                <text>2007-08-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8135">
                <text>Date: Tue, 14 Aug 2007 22:09:39 -0400&#13;
From: Virginia.Tech.news@vt.edu&#13;
To: Multiple recipients &lt;LISTSERV@LISTSERV.VT.EDU&gt;&#13;
Subject: Media and the return to school&#13;
&#13;
Wednesday, August 15, 2007&#13;
&#13;
TO: The students, faculty, and staff of Virginia Tech&#13;
 &#13;
RE: Media and the return to school&#13;
 &#13;
With the beginning of the fall 2007 semester, there will be intense media interest in the Virginia Tech community in light of the events of April 16. While some may prefer otherwise, there will again be many broadcasters, reporters, and cameras on the campus. Indeed, some already are on campus.&#13;
 &#13;
Our university is public property. Our roads are public thoroughfares. We cannot bar the media from campus. However, although our buildings are open to the public, residence halls, offices, and classrooms are restricted. Faculty members control entry to classrooms while teaching there. Labs are open only to those authorized. Offices are semi-private spaces open to anyone with a reason to be there. University residence halls are living quarters and open only to those living there and their guests.&#13;
 &#13;
What should you do if a member of the news media approaches you for an interview? You are never REQUIRED to speak to the media. Politely telling a reporter "no thank you" will suffice. If a reporter is particularly troublesome, just walk away and do not feel guilty about doing so.&#13;
 &#13;
However, I am proud -- very, very proud -- of our university community and how we have represented ourselves to the world through the media over the past several months. You have shown the world the special nature of Hokie Spirit. If you are comfortable, feel free to speak about yourselves, your involvement with the university, or your feelings about the future. I wouldn&amp;#39;t be surprised if reporters want to take you back to April 16. You control discussion and you talk about what you want to talk about. It&amp;#39;s your time.&#13;
 &#13;
Should you engage a reporter, take advantage of the opportunity to share some Hokie Spirit. The world mourned with us and maintains an interest in the collective health of our extended university community. I believe that most reporters share this concern and compassion. With so many reporters present, this is a unique opportunity to again convey the character of our community and tell a little about why Virginia Tech and Blacksburg are such very special places.&#13;
 &#13;
Sincerely yours,&#13;
Lawrence G. Hincker&#13;
Associate Vice President&#13;
University Relations</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10106">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13506">
                <text>Media and the return to school</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1363">
        <name>hincker</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="139">
        <name>reporters</name>
      </tag>
      <tag tagId="1522">
        <name>return to school</name>
      </tag>
      <tag tagId="115">
        <name>university relations</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="794" 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="2109">
                <text>Na Mi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4000">
                <text>Editor: Xiao Jie</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="5978">
                <text>2007-07-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7856">
                <text>www.chinaview.cn  2007-04-18 16:42:35&#13;
&#13;
 BEIJING, April 18 (Xinhua) -- Chinese Foreign Ministry spokesman Liu Jianchao Wednesday criticized some U.S. media&amp;#39;s irresponsible reports on the Virginia Tech shooting before finding out the truth, calling on relevant sides to eliminate baneful impact of the incident.&#13;
&#13;
    Following Monday&amp;#39;s shooting tragedy at Virginia Tech, some U.S. media reported the gunman was a Chinese student. Later, the U.S. police identified the gunman who killed 32 people as a student from the Republic of Korea, Cho Seung-Hui.&#13;
&#13;
    Calling the mass shooting a "very serious" incident, Liu said it was a terribly wrong move to give irresponsible reports before finding out the truth, which had violated the professional moral of the press.&#13;
&#13;
    The Chinese government and people are very concerned about this incident and lamented the deaths, the spokesman said, adding China expresses sincere sympathy and condolences to the families of the victims as well as the injured, hoping they will recover at an early date.&#13;
&#13;
    Foreign Minister Li Zhaoxing conveyed condolences to U.S. Secretary of State Condoleezza Rice over the shooting in a telegram Tuesday, expressing sincere concern to the U.S. government and those affected by the shooting.&#13;
&#13;
    Monday&amp;#39;s shooting rampage is the deadliest mass shooting in the U.S. history. Liu Jianchao said on Tuesday evening China is "shocked" by the tragedy and strongly condemns the violence. &#13;
&#13;
--&#13;
&#13;
Original Source: XINHUA Online, China&#13;
&lt;a href="http://news.xinhuanet.com/english/2007-04/18/content_5993865.htm"&gt;http://news.xinhuanet.com/english/2007-04/18/content_5993865.htm&lt;a/&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9827">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13246">
                <text>FM slashes U.S. untruthful reports on campus shooting</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1216">
        <name>china</name>
      </tag>
      <tag tagId="1123">
        <name>chinese foreign ministry</name>
      </tag>
      <tag tagId="903">
        <name>irresponsible reports</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="488" public="1" featured="0">
    <fileContainer>
      <file fileId="317">
        <src>https://april16archive.org/files/original/Media IV_f409dda5de.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="14711">
                    <text>2007-06-11</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15831">
                    <text>2007-06-11 15:44:13</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="1821">
                <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="3712">
                <text>Waldo Jaquith </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="5690">
                <text>2007-06-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7568">
                <text>There are always a trio of TVs running next to the information desk in Squires, tuned to three different news channels. All three were reporting on Virginia Tech.&#13;
&#13;
Original source: &lt;a href="http://www.flickr.com/photos/waldoj/463568953/in/set-72157600088262276/"&gt;http://www.flickr.com/photos/waldoj/463568953/in/set-72157600088262276/&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href=" http://creativecommons.org/licenses/by-sa/2.0/"&gt;Creative Commons Attribution-ShareAlike 2.0&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9539">
                <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="11531">
                <text>Permission:&#13;
Waldo Jaquith &#13;
http://www.flickr.com/photos/waldoj/463568953/in/set-72157600088262276/&#13;
Creative Commons Attribution-ShareAlike 2.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12983">
                <text>Wall-to-Wall VT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="573">
        <name>student squires center</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="418" public="1" featured="0">
    <fileContainer>
      <file fileId="274">
        <src>https://april16archive.org/files/original/Wolf_54e729787b.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="14670">
                    <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="15790">
                    <text>2007-06-07 10:37:08</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="1755">
                <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="3646">
                <text>Mark Ritchie</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="5624">
                <text>2007-06-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7502">
                <text>CNN&amp;#39;s anchor Wolf Blitzer reports from campus.&#13;
&#13;
Original source: &lt;a href="http://www.flickr.com/photos/wtrbyvt/464461991/in/set-72157600091484040/"&gt;http://www.flickr.com/photos/wtrbyvt/464461991/in/set-72157600091484040/&lt;/a&gt;&#13;
&#13;
Photo Courtesy of Mark Ritchie&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9473">
                <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="11466">
                <text>Permission:&#13;
Photo Courtesy of Mark Ritchie&#13;
http://www.flickr.com/photos/wtrbyvt/464461991/in/set-72157600091484040/&lt;/a&gt;&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12928">
                <text>Wolf</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="344">
        <name>reporter</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="417" public="1" featured="0">
    <fileContainer>
      <file fileId="273">
        <src>https://april16archive.org/files/original/Fox_ba4c1f4d14.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="14669">
                    <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="15789">
                    <text>2007-06-07 10:32:06</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="1754">
                <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="3645">
                <text>Mark Ritchie</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="5623">
                <text>2007-06-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7501">
                <text>Fox News&amp;#39; anchor Shepard Smith reports from campus.&#13;
&#13;
Original source: &lt;a href="http://www.flickr.com/photos/wtrbyvt/464462003/"&gt;http://www.flickr.com/photos/wtrbyvt/464462003/&lt;/a&gt;&#13;
&#13;
Photo Courtesy of Mark Ritchie&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9472">
                <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="11465">
                <text>Permission:&#13;
Photo Courtesy of Mark Ritchie&#13;
http://www.flickr.com/photos/wtrbyvt/464462003/&lt;/a&gt;&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12927">
                <text>That Fox Guy</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="344">
        <name>reporter</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="384" public="1" featured="0">
    <fileContainer>
      <file fileId="251">
        <src>https://april16archive.org/files/original/media III_e7283803b7.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="14648">
                    <text>2007-06-05</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="15768">
                    <text>2007-06-05 10:28:18</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="1726">
                <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="3617">
                <text>Daniel Lin </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="5595">
                <text>2007-06-05</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7473">
                <text>Matt Lauer and Meredith Vieria of the Today Show broadcast from the drill field.  &#13;
&#13;
Original source: &lt;a href=" http://www.flickr.com/photos/geeknerd99/464203561/in/photostream/"&gt; http://www.flickr.com/photos/geeknerd99/464203561/in/photostream/&lt;/a&gt;&#13;
&#13;
Photo Courtesy of Daniel Lin &#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9444">
                <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="11440">
                <text>Permission:&#13;
Photo Courtesy of Daniel Lin</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="344">
        <name>reporter</name>
      </tag>
      <tag tagId="468">
        <name>today show</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
