<?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?output=omeka-xml&amp;page=27&amp;sort_field=Dublin+Core%2CCreator" accessDate="2026-04-04T11:23:43+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>27</pageNumber>
      <perPage>20</perPage>
      <totalResults>1884</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="283" 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="1636">
                <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="3527">
                <text>Cyndy Aleo-Carreira</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="5505">
                <text>2007-05-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7384">
                <text>Posted by &lt;a href="http://www.profy.com/profile/cyndy-aleo-carreira/"&gt;Cyndy Aleo-Carreira&lt;/a&gt; on April 17th, 2007&#13;
&#13;
I know that I speak for everyone here at Profy when I say that our thoughts are with the family and friends of the victims of yesterday&amp;#39;s events at &lt;a href="http://www.vt.edu/"&gt;Virginia Tech&lt;/a&gt;.&#13;
&#13;
The horror of yesterday will live in the hearts and minds of the Virginia Tech community, the United States, and much of the world for some time to come, but what moved me the most was the way in which what would have been a local, and somewhat national, event even a few years ago moved worldwide due to a global online community. &#13;
&#13;
The first reports of what was happening on the VT campus came from students sending reports via their cell phones. Today, the grief of the VT community has moved online.&#13;
&#13;
On the University&amp;#39;s own &lt;a href="http://www.vt.edu/tragedy/"&gt;website on the tragedy&lt;/a&gt;, updates are presented in blog format, the Convocation held today was streamed live, and is available to students, faculty, and families as a podcast, as it contains information on resources available for counseling and information.&#13;
&#13;
On &lt;a href="http://www.livejournal.com"&gt;LiveJournal&lt;/a&gt;, a professor shares his grief online, giving us a mere glimpse of the person (and student) that &lt;a href="http://tekmagika.livejournal.com/672246.html"&gt;Reema Samaha&lt;/a&gt; was. &#13;
&#13;
On &lt;a href="http://www.facebook.com"&gt;Facebook&lt;/a&gt;, comments have been left on the pages of victims from friends as well as students at rival schools, and sorority sisters and fraternity brothers from other chapters.&#13;
&lt;a href="http://www.myspace.com"&gt;MySpace&lt;/a&gt; includes an &amp;quot;official&amp;quot; &lt;a href="http://profile.myspace.com/index.cfm?fuseaction=user.viewprofile&amp;amp;friendid=42548491"&gt;VT page&lt;/a&gt;&amp;nbsp;called HokieNation which has been updated with a VT emblem with wings and a cartoon showing anthropomorphic characters of other universities gathered around the VT character with the caption &amp;quot;Today we are all Hokies.&amp;quot; Many user icons of VT alums and students as well as people affiliated with the university, like radio stations that broadcast VT games have changed their avatars to a black ribbon with the VT emblem.&#13;
&#13;
And comments have been left on articles ranging from blogs to news sites. &#13;
&#13;
Twenty years ago, we&amp;#39;d have seen this as a tragedy, watched the footage on CNN, and that would have been the end of it. In the age of Web 2.0, anyone with enough inclination and five minutes of time can reach out to those most closely affected by events and let them know how many people are thinking of them. Over 650 comments have been left on the HokieNation MySpace page alone in the past two days.&#13;
&#13;
If Web 2.0 is remembered for nothing else, it will be remembered for giving us this ability to quickly connect with people. In this instance, it gives a personal insight into the lives of the victims that makes them much more than simply a name in a newcast. &#13;
&#13;
Additional information: &lt;a href="http://www.people.com"&gt;People&lt;/a&gt;&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.profy.com/2007/04/17/virginia-tech-grieves-online/"&gt;http://www.profy.com/2007/04/17/virginia-tech-grieves-online/&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/publicdomain/"&gt;Creative Commons Public Domain Dedication&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9354">
                <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="11358">
                <text>Creative Commons Public Domain Dedication</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12827">
                <text>Virginia Tech Grieves Online</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="83">
        <name>blog</name>
      </tag>
      <tag tagId="240">
        <name>commentary</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="379">
        <name>online</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1103" public="1" featured="0">
    <fileContainer>
      <file fileId="560">
        <src>https://april16archive.org/files/original/F200704180757522799116952_7661f71670.jpg</src>
        <authentication>null</authentication>
        <elementSetContainer>
          <elementSet elementSetId="1">
            <name>Dublin Core</name>
            <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
            <elementContainer>
              <element elementId="43">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="14943">
                    <text>2007-08-15</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16063">
                    <text>2007-08-15 17:00:04</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2403">
                <text>Na Mi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4294">
                <text>çŽ¯çƒåœ¨çº¿</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6272">
                <text>2007-08-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8150">
                <text>People mourned for the victims on the drillfield.  Vigil on April 17&#13;
&#13;
Original Source:hqchinadaily.cn&#13;
&#13;
&lt;a href="http://egsky.cn/default.asp?distype=normal&amp;tag=%E7%BE%8E%E5%9B%BD"&gt;http://egsky.cn/default.asp?distype=normal&amp;tag=%E7%BE%8E%E5%9B%BD&lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10121">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13521">
                <text>Sorrowful moment</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
      <tag tagId="14">
        <name>virginia tech</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="253" 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="1607">
                <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="3498">
                <text>D. Grant Haynes</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="5476">
                <text>2007-05-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7355">
                <text>by D. Grant Haynes &lt;i&gt;Thursday, Apr. 19, 2007 at 2:10 PM&lt;/i&gt;&#13;
&#13;
&lt;i&gt;The senseless murder of 32 people at Virginia Tech underlines once again the necessity for stricter gun control laws in the United States.&lt;/i&gt;&#13;
&#13;
Americans are busily soul searching one more time after another mass killing at an educational institution.&#13;
&#13;
This time the setting was a university rather than a secondary school.&#13;
&#13;
But the ghastly spectacle that unfolded at Virginia Polytechnic University in Blacksburg, Virginia, on April 16 when a disaffected student--Cho Seung-Hui, 23--systematically executed 32 innocent students and faculty members was fully as terrible as other such recent massacres in America--only worse.&#13;
&#13;
More were killed at Virginia Tech than at Columbine High School in Colorado eight years ago. And the killer&amp;#39;s cold-blooded and methodical resolve, as well as an inexplicable lack of appropriate and timely responses from police officers on the scene, will put the Virginia Tech massacre in a class apart always.&#13;
&#13;
Media pundits, politicians, university administrators, psychologists, clergymen and others talk endlessly now about what lessons might be learned from Virginia Tech.&#13;
&#13;
The university should have had a better evacuation or lock down protocol in place.&#13;
&#13;
University and other police officers should have been more diligent in protecting students from Cho Seung-Hui&amp;#39;s rage after his first shooting spree in which he killed two individuals more than two hours before he reappeared on campus to kill 30 more students.&#13;
&#13;
The mental health community should have done a better job of intervention when Cho Seung-Hui had, over several years&amp;#39; time, displayed symptoms of mental illness.&#13;
&#13;
There is ample blame to go around in this botched and bungled phantasmagoric mess that, seemingly, could not have been handled in a worse way than it was handled.&#13;
&#13;
But in all of the hand-wringing 24-hour non-stop media reportage and speculation about Blacksburg, few professionals and fewer politicians with their fingers to the wind and their campaign coffers chock full of National Rifle Association dollars in some cases, have been willing to state the obvious.&#13;
&#13;
Cho Seung-Hui could not have murdered 32 people so efficiently in Blacksburg, Virginia, on April 16 without access to two pistols and endless rounds of ammunition for them.&#13;
&#13;
Cho was a brooding youth. One of his teachers had identified him as deeply troubled because of the excessively violent nature of his fictionalized scenarios. She had even referred him for counseling.&#13;
&#13;
He had had encounters with the university police over allegations of stalking others.&#13;
&#13;
He had been described as a potential menace to himself and others by a mental health professional.&#13;
&#13;
Should not these facts alone have been a red flag sufficient to dictate a more than perfunctory look at him when he sought to acquire death-dealing hand guns?&#13;
&#13;
That should have been the case and would have been in a more sensible culture.&#13;
&#13;
Had minimally effective gun control laws been in place in Virginia when Cho sought to purchase his pistols and cartridges, he would have been denied a permit and 32 dead Virginia Tech students and faculty members would be alive today.&#13;
&#13;
For all practical purposes, anyone in this nation can obtain a firearm, regardless of his or her emotional stability, maturity, or legitimate need for the weapon.&#13;
&#13;
This is wrong and is cause for people in more sane societies to fear for their very lives when contemplating a trip to America. This writer knows whereof he speaks because he lived in Great Britain for a time and was asked often about the danger of being gunned down in America.&#13;
&#13;
What must they all think today?&#13;
&#13;
More stringent gun control is the only answer to the madness of disaffected youths and others who, repeatedly, have walked into schools and work places and murdered innocent people.&#13;
&#13;
But cowardly Democrats who should be at the forefront of gun control legislation are already distancing themselves from calls for tougher gun laws in the wake of the Virginia Tech tragedy.&#13;
&#13;
Congressional Democrats fear the wrath of the National Rifle Association and that organization&amp;#39;s clout with a certain segment of American voters too much to do what they know is both right and desperately needed.&#13;
&#13;
Senate majority leader, Harry Reid (D-NV) squelched serious talk of more rigid gun controls following the Virginia Tech shootings. The Associated Press reported Reid&amp;#39;s lackluster and cowardly response to questions of stricter gun control as blood was being mopped at Virginia Tech.&#13;
&#13;
"After the worst mass shooting in U.S. history, Senate Majority Leader Harry Reid cautioned Tuesday against a &amp;#39;rush to judgment&amp;#39; on stricter gun control....&#13;
&#13;
"I think we ought to be thinking about the families and the victims and not speculate about future legislative battles that might lie ahead," said Reid... ."&#13;
&#13;
And you should also be thinking about the families and the victims of the next such massacre, Senator Reid.&#13;
&#13;
A ban on the sale of assault rifles in the United States--one that was in place from 1994 until 2004 when a Republican Congress permitted it to expire--should be reinstated as soon as possible.&#13;
&#13;
And hand gun acquisition requirements should also be made more restrictive as soon as possible.&#13;
&#13;
The American with a legitimate need for a personal hand gun--certainly and especially a license to carry such a weapon on his person--should become a rare exception rather than the rule.&#13;
&#13;
The Cho Seung-Hui&amp;#39;s of this nation should never be permitted to purchase a handgun or an assault rifle. Background checks prior to the sale of a pistol should be infinitely more thorough--modeled, perhaps after the British system.&#13;
&#13;
The only viable solution to the epidemic of mass killings at American educational institutions and work places is to drastically reduce the number of guns in the hands of Americans.&#13;
&#13;
This can be done and should be done.&#13;
&#13;
And to those who would at this point trot out the tired old bromide, "when guns are outlawed, only outlaws will have guns", one can only observe that we must start somewhere and at some point in time.&#13;
&#13;
The process may take decades, but if assault rifle acquisitions are stanched altogether and hand guns are made infinitely more difficult to obtain, there will be ever fewer of each in circulation over time.&#13;
&#13;
That would represent a move in the right direction and would be a fitting memorial to those who gave their lives at Virginia Tech because Virginia&amp;#39;s gun laws had permitted a psychologically impaired youth to acquire the instruments to murder 32 people on a morning that will live in infamy throughout American history.&#13;
&#13;
How many more Virginia Techs must occur before our elected representatives muster the courage to confront the gun lobby and do what must be done?&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://la.indymedia.org/news/2007/04/197101.php"&gt;http://la.indymedia.org/news/2007/04/197101.php&lt;/a&gt;&#13;
&#13;
(c) Los Angeles Independent Media Center. Unless otherwise stated by the author, all content is free for non-commercial reuse, reprint, and rebroadcast, on the net and elsewhere. Opinions are those of the contributors and are not necessarily endorsed by the Los Angeles Independent Media Center.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9325">
                <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="11335">
                <text>(c) Los Angeles Independent Media Center. Unless otherwise stated by the author, all content is free for non-commercial reuse, reprint, and rebroadcast, on the net and elsewhere. Opinions are those of the contributors and are not necessarily endorsed by the Los Angeles Independent Media Center.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12802">
                <text>It's time to confront the gun lobby</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="240">
        <name>commentary</name>
      </tag>
      <tag tagId="87">
        <name>gun control</name>
      </tag>
      <tag tagId="352">
        <name>laws</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1223" 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="2506">
                <text>Sara AA Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4397">
                <text>Daily Campus Editorial Board</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6375">
                <text>2007-08-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8253">
                <text>By: Daily Campus Editorial Board&#13;
Posted: 4/24/07&#13;
The tragic shootings at Virginia Tech have provoked much discussion regarding measures to avoid future heartbreak. Perhaps the events in Blacksburg hit close to home in Storrs because of the similarities of the size and nature of the communities. Numerous measures have already been called for, some of which would entail strict regulation of the movement of people over campuses, including sign-in sheets and metal detectors. College campuses are open areas, and to restrict the movement of students over such a large area is both improbable and impractical. While the issue obviously needs to be addressed, any response must be reasonable, practical and not overbearing.&#13;
&#13;
Thankfully, events like this are rare. Due to this, it is impossible to detect when or where an individual may be driven to commit such an atrocity. It is equally impossible to plan for every eventuality. Regardless of the number of safeguards that may be enacted, it is impractical to expect to prevent something like this from happening again.&#13;
&#13;
Some hold counselors culpable for not taking appropriate action. It is extremely unfair to expect anyone to preempt this sort of tragedy by identifying and deterring those who may be likely to commit acts of violence. Even if violence were prevented, there would be no way to prove it was and anyone who took action would be open to liability imposed by our litigious culture. This threat of repercussion understandably causes most to pursue self-preservation rather than taking risks that may or may not save lives.&#13;
&#13;
Despite the inability to prevent, there may be more passive measures to keep people out of harm&amp;#39;s way if such an incident does occur. Some deaths may have been prevented by a campus-wide notification system. Much of the campus was not aware that a shooting was ongoing. UConn currently has a call box system, the blue light emergency phones around campus, in place to allow distressed individuals to contact the UConn Police Department. This system could be programmed to put out audible and visual alerts there was a public danger. Another possibility is for universities to text message subscribers to an emergency alert program. Cell phone numbers could easily be taken during the beginning of semester registration. This way the message could be dispersed quickly and efficiently to the majority of those who carry phones. An attractive point of both measures is that they would remain inconspicuous until utilized. While safety is paramount, it is important to enable the living to continue living freely, and overt security measures would do nothing but remind students to live in fear.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.dailycampus.com/user/index.cfm?event=displayregistrationprompt&amp;requiredregistration=1&amp;thereferer=http%3A//media.www.dailycampus.com/media/storage/paper340/news/2007/04/24/Commentary/Campus.Saftey.Measures.Must.Be.Sensible-2876947.shtml&gt;The Daily Campus - April 24, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10224">
                <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="11228">
                <text>The Daily Campus</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12075">
                <text>Melissa Bruen &lt;eic@dailycampus.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13624">
                <text>Campus Saftey Measures Must Be Sensible</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1618">
        <name>university of connecticut</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="530" 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="1860">
                <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="3751">
                <text>Dale Peskin</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="5729">
                <text>2007-06-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7607">
                <text>Posted by &lt;a href="http://ifocos.org/author/dale-peskin/"&gt;Dale Peskin&lt;/a&gt; | April 23rd, 2007&#13;
&#13;
Unaware of a shooting in a dormitory that left two people dead, Virginia Tech graduate student Jamal al Barghouti headed across campus to meet with his advisor. Nearing Norris Hall he ran into police, guns drawn, rushing inside. As al Barghouti took cover, he pulled out his Nokia camera-phone and started recording. Then came the haunting sound of 26 gunshots. As the volley increased in intensity he unexpectedly recorded his own startled voice: "Wow," he said.&#13;
&#13;
Across campus, freshman Bryce Carter was hiding in his dorm room. When word reached him that fellow students had been shot, he went online. After assuring friends that he was alive, he wrote these works on Bryce&amp;#39;s Journal, his blog: "My friends could be dead." &#13;
&#13;
Over at the business school, computer science-business technology major Kevin Cupp was locked down, distanced from the computer servers he manages as webmaster of Planet Blacksburg. So he sent an instant message on his cell phone to Twitter, the new digital network where people describe what they are doing at the moment. His first of many posts that day:  "Trapped inside of Pamplin, shooter on campus, they won&amp;#39;t let us leave. &#13;
&#13;
What we experienced about the horrific events on a black day in Blacksburg owes to a savvy, social generation connected emotionally and technologically to its media. Their eyewitness descriptions, photos, video and reporting from a remote, rural Virignia town - one of the world&amp;#39;s first connected communities â€” made a story visceral to the world. &#13;
&#13;
The ability to instantly capture and disseminate information at a time when it was most needed, as well as to communicate with each other across time and geography, has not only helped unite a community but has become a real-time example of how personal media empowers and defines communication in today&amp;#39;s connected society. &#13;
&#13;
Watching events unfold, the shift in the power of media was perceptible. Traditional broadcasters and publishers competently covered the tragic events in Blacksburg. But the story belongs to Virginia Tech students. They were at once reporters, witnesses and subjects of the deadliest shooting in U.S. history. It was like watching a new kind of reality show where the stars used their devices, their social networks, and their wits to survive and to cope. &#13;
&#13;
News organizations responded by plundering material posted on the web and pumping their own content into the online ether. The Internet encouraged a collective expression of emotion that was faithfully reported by traditional media outlets. As if the world outside newsrooms didn&amp;#39;t already know, CBS News ran this story a day after the shootings: &lt;a href="http://www.cbsnews.com/stories/2007/04/17/the_skinny/main2693331.shtml"&gt;Students turn to web in time of tragedy&lt;/a&gt;. The Los Angeles Times went with: &lt;a href="http://www.latimes.com/technology/la-fi-web17apr17,0,5808497.story?coll=la-home-headlines"&gt;Students Trace a Tragedy Online&lt;/a&gt;.&#13;
&#13;
So, too, did adults. While social networking sites such as Facebook and My Space became an integral part of the story, millions turned to the sites produced by mainstream news outlets for the latest from Blacksburg.  But the Internet had done more than create a distribution center for news and information; it became a place for news to happen. An online community emerged around the story. The immediacy of the medium helped to relay both the scope of news as well as the full emotion of the event. Once again, citizen journalists armed with mobile phones supplied invaluable material, including pictures and video footage of the shootings, to established news organizations. &#13;
&#13;
Newspapers lost more hallowed ground in the media war for immediate attention and influence. An editor for The Washington Post lamented the "dead-tree" limitations of covering a breaking story that made newspaper editions the harbingers of yesterday&amp;#39;s news tomorrow. A day late and many breaking developments short, the mighty Post was relegated to this headline on Tuesday, April 17, a full day after the shootings:  "&lt;a href="http://www.washingtonpost.com/wp-dyn/content/article/2007/04/16/AR2007041600533.html"&gt;Gunman Kills 32 at Virginia Tech In Deadliest Shooting in U.S. History&lt;/a&gt;."&#13;
&#13;
There can be no denying now that We Media - the ecosystem in which everyone is media - is the dominant force of communication in our culture. The digital network has changed the way we create, access and distribute news and information.&#13;
&#13;
Virginia Tech&amp;#39;s students shined even as it they were portrayed as victims. One articulate student-witness set the record straight while being interviewed by a testy CNN reporter.  "Don&amp;#39;t you get it?" he asked the reporter. "Its our story, not yours."&#13;
&#13;
As the student went off to awaiting cameras for a series of interviews and special reports with the other television networks, a CNN producer channeled the network&amp;#39;s coverage to a report on counseling services on campus.&#13;
&#13;
The TV moment recalled the recent complaint by NBC Nightly News anchor Brian Williams that the had spent a career as a journalist only to compete now with "some guy named Vinny."&#13;
&#13;
But it was not Vinny with whom Williams had to compete in Blacksburg. It was Jamal, Bryce and Kevin. They are, for the moment, the celebrated journalists of their generation, embedded correspondents reporting from a war zone with all the courage and authenticity that radio reporter Edward R. Murrow famously exhibited covering the bombing of London during World War II. &#13;
&#13;
Undeniably less sophisticated than Morrow&amp;#39;s reporting, their citizen journalism is shown, replayed, recast, remixed and referenced over-and-over again on the Internet as well as on traditional newscasts. The unfettered, unfiltered coverage of the shootings is accepted for what it is, unapologetic for its lack of cohesiveness or for its personal perspective. The audience understands the story is personal and incomplete, a work in progress that continues long after the network camera crews and out-of-town reporters leave Blacksburg. Suddenly, the Internet looks less like a threat to &amp;#39;old media&amp;#39;, and more like a resource it can easily exploit.&#13;
&#13;
The We Media Generation now looks to pick up the pieces, to remember their friends, their community, and to share their stories of survival with the rest of the world. It is the informing story of their lives. No wonder they asked NBC and the outside media to leave for violating their fragile community by repeatedly overplaying, then replaying over and over, the grotesque rants of a killer, once a disturbed fellow student.&#13;
&#13;
The story of a generation turned quickly to coping with unimaginable tragedy, a cruel and unforeseen twist for college students living in the sanctuary of a college campus. Amid tragedy there was pathos and authenticity in the way they mourned, grieved and supported one another through public acts of catharsis. &#13;
&#13;
At the Tuesday night vigil for their slain comrades Virginia Tech students lit "The Drill" with candles and the glow of screens on their cell phones. Virtual vigils emerged across the web. Happy Slip, a vlogger in New York City, posted a photo sent via a cell phone from the vigil. These words accompanied the photo: "Know that a community here in New York was on their knees praying for you tonight." Thousands of bloggers shared similar sentiments. Technorati, a web site that indexes blogs, tracked nearly 30,000 posts about Virginia Tech the following day.&#13;
&#13;
As expressions of sorrow and support, memorials proliferated on the web. West Virginia Blogger collected links to the personal web sites of victims, many on My Space or Facebook, as a way of paying tribute. "It&amp;#39;s one thing to hear a list of names on TV, or read them online," she wrote, "but if you take a second to view a bit of the person&amp;#39;s personal life it will give you a deeper understanding of that person." &#13;
&#13;
Forums were established on sites such as VTtragedy.com and VTincident.com for students to express their condolences and grief. The creators of OneDayBlogSilence.com proposed a day of silence in the blogosphere to pay tribute to the victims. Citizens of the virtual world Second Life established a memorial for visitors to leave virtual notes and flowers.&#13;
&#13;
The big news organizations did their best to compete with the raw elegance of user-generated tributes, but their stories seemed trite amid the outpouring of personal expression.&#13;
&#13;
As the world tries to understand what happened in Blacksburg, the conversation should once and for all dispel the "derivative myth" spun by newspapers and news broadcasters. The myth holds that most news of value is created and owned by the newspapers who publish it or by the broadcasters who air it. While there is no denying that news organizations may add value to news by employing large numbers of specialists to gather, create, edit, produce and distribute it, the notion that they either "own&amp;#39; the news or that they are the original source for it becomes irrelevant, if not absurd, when everyone is media.&#13;
&#13;
Today&amp;#39;s news tumbles through a connected society, spiraling through media, changing as it goes, an organic story with no beginning, middle or end. What seems chaotic is actually a story arc that assumes clarity, context and meaning as it unfolds through a proliferation of sources, many accessible to anyone. The days of once-a-day publishing cycles and scheduled news broadcasts are mere supplements to a continuous stream of news and information available any time through a variety of sources and ubiquitous devices.&#13;
&#13;
With their cell phones, networks and knowledge of place, Virginia Tech students were better prepared to report the events overtaking them than the swarm of professional reporters who descended upon Blacksburg following the shootings. On camera the students appeared more composed, informed and sure-footed than the confused reporters from the big cities.&#13;
&#13;
Community - a word that is now used to describe the digital connections among people, as well as the social and emotional ones  - was the word heard time-and-time again from Blacksburg. Extended by personal media, the Blacksburg community quickly expanded to include students on campuses everywhere, as well as a diverse, caring generation connected to each other through digital media.&#13;
&#13;
"Today we are all Hokies," student leaders proclaimed when asked by reporters how the tragic events would impact Virginia Tech. In a show of support, fellow students at universities across the U.S. created video tributes and memorials on You Tube, some remixing an audio track of Avril Lavigne&amp;#39;s "Keep Holding On" with slideshows of photos grabbed from Flickr. Many of the videos ended with a slide displaying the logo of their universities next to the words "today we are all Hokies."&#13;
&#13;
Powerful forces were in play in Blacksburg that week. One was the invisible infrastructure of digital networks, wired and wireless, connecting a geographically isolated community to itself and to the world. Another was the connected culture of young adults, savvy content creators and communicators who instinctively use social media as integral parts of their life. When shots rang out, the story unfolded through their devices and their networks.&#13;
&#13;
A new generation of media experts provided an indelible record of what happened on a terrible day in Blacksburg. They have created a lasting tribute to and by its community. The way we are informed will never be the same.&#13;
&#13;
--&#13;
&#13;
Original Source: ifocos - institute for the connected society&#13;
&lt;a href="http://ifocos.org/2007/04/23/connected-to-the-news-by-a-generation-of-wired-witnesses/"&gt;http://ifocos.org/2007/04/23/connected-to-the-news-by-a-generation-of-wired-witnesses/&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc-sa/2.5/"&gt;Creative Commons Attribution-NonCommercial-ShareAlike 2.5&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9578">
                <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="11568">
                <text>Creative Commons Attribution-NonCommercial-ShareAlike 2.5</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13022">
                <text>Connected to the news by a generation of wired witnesses</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="589">
        <name>citizen journalism</name>
      </tag>
      <tag tagId="640">
        <name>common good</name>
      </tag>
      <tag tagId="639">
        <name>community</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="836" 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="2147">
                <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="4038">
                <text>Damon Wilson</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="6016">
                <text>2007-07-27</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7894">
                <text>TO THE EDITOR:&#13;
&#13;
I am a Hokie.&#13;
&#13;
I finished my degree work at Virginia Tech in 1974, and in all these years, I have never regretted my choice to go to Blacksburg. I became the man that I am there.&#13;
&#13;
To have this ugly nightmare play out in my emotional home, is a desecration of my special place. The hurt, the disgust, is beyond my ability to express.&#13;
&#13;
We are Virginia Tech.&#13;
&#13;
I could not be more proud of the current generation of Hokies living and learning at Virginia Tech than I am today. The clarity of thought and action, the selflessness, the love for one another, the support, the unanimity of the University in the face of this "monumental horror," helps me and all VT grads everywhere. I can see where this current generation of Hokies is growing up at Tech.&#13;
&#13;
We are the Hokie Nation.&#13;
&#13;
When we celebrate, we do it together. When we cry, we cry together. When we need to, we close ranks, hunker down, and face our problems together. And we help each other to keep on going. But as we do just that, we also wonder: Does anyone else even understand what is happening to us?&#13;
&#13;
My son is growing to manhood at UNC and has kept me informed of activities there. I have heard of the ribbons being worn, in maroon and orange. I have heard of the message posters being signed by so many of you, expressing support and love. And I have heard of your candlelight service, in memorial to those whose lives were snuffed out before being able to live our motto: "That I May Serve."&#13;
&#13;
I have passed news of this to my Hokie colleagues, and the effect on us is profound. You have touched where we live. You understand what is happening to us.&#13;
&#13;
We welcome our Carolina cousins into our family, into our nation, with open arms - and great thanks. We are the Hokie Nation. You are the Hokie Nation. For today, we are ALL Hokies.&#13;
&#13;
&#13;
&#13;
Damon Wilson&#13;
Virginia Tech Class of 1974&#13;
&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9865">
                <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="11811">
                <text>Kevin Schwartz &lt;kschwartz@unc.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13283">
                <text>Virginia Tech appreciates support from UNC friends</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="954">
        <name>letter to the editor</name>
      </tag>
      <tag tagId="3">
        <name>support</name>
      </tag>
      <tag tagId="955">
        <name>thanks</name>
      </tag>
      <tag tagId="857">
        <name>unc</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1718" 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="2856">
                <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="4747">
                <text>Dan Anderson</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="6725">
                <text>2008-02-19</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8603">
                <text>By: Guest Commentary |&#13;
Issue date: 5/1/07 Section: Commentary&#13;
&#13;
We must not let those who abuse our rights forsake our national belief in freedom above all else. If we do, then the victims of these shooters, these evil young men who have turned classrooms into firing ranges, will not only be those innocents slain in Blacksburg, Va. and other places where massacres have happened, but all who believe in American self-determination.&#13;
&#13;
An editorial in The New York Times concluded that, "What is needed, urgently, is stronger controls over the lethal weapons that cause such wasteful carnage and such unbearable loss."&#13;
&#13;
But blaming guns is too easy.&#13;
&#13;
This shooting was an act of insanity and we must treat it as such. The shooter&amp;#39;s actions should not be given the power and legitimacy to change our laws governing civil liberties. That is government by martyrdom.&#13;
&#13;
My belief, that guns and violence enjoy a marriage of convenience, was reaffirmed by news that the mayor of Nagasaki, Japan had been assassinated this week by a man with a handgun. He was shot point-blank in the back because of an unresolved dispute with a gangster over damage done to the gangster&amp;#39;s car. Japan is a country where handguns are outlawed.&#13;
&#13;
"But," a child in Nagasaki might ask, "if handguns are forbidden, then how could my mayor be killed by one?" I would tell that child that it is impossible to ban handguns; that it is impossible to ban anything.&#13;
&#13;
Japan also knows that people die by means other than guns.&#13;
&#13;
Multiple leaders have been stabbed to death in Japan - one was even killed by a man with a samurai sword. Atomic bombs have killed thousands there, too.&#13;
&#13;
Hopefully, the Japanese do not decide to increase the scope of their bans, just as we should be hopeful that the United States does not increase the scope of its gun bans.&#13;
&#13;
Because if we were to enact stricter gun laws, it would be an admittance of our uneasiness with the freedom we have been given. And then, before we know it, we are a fearful and retreating democracy called to action by hateful men wielding 9mm and .22-caliber pistols on college campuses.&#13;
&#13;
So then what do we do when we are shocked and hurt by events such as those that occurred at Virginia Tech?&#13;
&#13;
Let&amp;#39;s try collectively standing up to hate and violence with our countrymen, becoming a people holding one another so tightly and with such conviction that we are as impenetrable as a great seawall. Let&amp;#39;s disarm hateful and violent people before they arm themselves, by recognizing and resolving their personal crises.&#13;
&#13;
But that is difficult and abstract.&#13;
&#13;
We have yet to mourn and come to terms with our grief.&#13;
&#13;
Perhaps we should not rush to judgment until our tempers have cooled and loved ones have had the opportunity to tell us about the people who found themselves in the shooter&amp;#39;s path in Blacksburg, but not in the path of most of our lives.&#13;
&#13;
Perhaps we should try to remember them completely.&#13;
&#13;
And then? What do we do with those memories?&#13;
&#13;
We never forget, that&amp;#39;s what.&#13;
&#13;
And we look to the people who we share this free and open country with and decide whether we will be the ones who let the self-righteous and insane run things or if we will be the ones who are brave, once the pain has subsided, and become that impenetrable seawall so that we may protect our right to self-determination and tranquility wherever we are.&#13;
&#13;
It is not the guns of the world that should worry us, it is the shooters.&#13;
&#13;
Dan Anderson is a University graduate student&#13;
&#13;
--&#13;
&#13;
Original Source: Daily Emerald&#13;
&lt;a href="http://media.www.dailyemerald.com/media/storage/paper859/news/2007/05/01/Commentary/Government.By.Martyrdom.Is.Not.The.Way.It.Should.Work-2889799.shtml"&gt;http://media.www.dailyemerald.com/media/storage/paper859/news/2007/05/01/Commentary/Government.By.Martyrdom.Is.Not.The.Way.It.Should.Work-2889799.shtml&lt;/a&gt;&#13;
&lt;a href="http://media.www.dailyemerald.com/media/storage/paper859/news/2007/05/01/Commentary/Government.By.Martyrdom.Is.Not.The.Way.It.Should.Work-2889799-page2.shtml"&gt;http://media.www.dailyemerald.com/media/storage/paper859/news/2007/05/01/Commentary/Government.By.Martyrdom.Is.Not.The.Way.It.Should.Work-2889799-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="10574">
                <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="12214">
                <text>Judy Riedl &lt;jriedl@uoregon.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13920">
                <text>Government by martyrdom is not the way it should work</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1237">
        <name>civil liberties</name>
      </tag>
      <tag tagId="558">
        <name>freedom</name>
      </tag>
      <tag tagId="87">
        <name>gun control</name>
      </tag>
      <tag tagId="1979">
        <name>university of oregon</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="198" 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="1560">
                <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="3451">
                <text>Dan Brekke</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="5429">
                <text>2007-05-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7308">
                <text>Monday, April 16, 2007&#13;
&#13;
I broke down and turned on CNN to check out coverage of the Virginia Tech shooting. I see there and elsewhere, without really knowing the details from this morning&amp;#39;s mayhem, that the media are turning to the question of what it all means. With the help of sociologists, CNN bloviator in chief Lou Dobbs is going to scrutinize school shootings.&#13;
&#13;
It&amp;#39;s an unspeakable tragedy, of course, and what will come to distinguish it will be the awful, heartbreaking details to be revealed over the hours and days to come. But really: does this tell us anything about any aspect of our society that we didn&amp;#39;t know before this morning? Or before Columbine? Or the Killeen, Texas, massacre? Or Oliver James Huberty&amp;#39;s slaughter of the innocents at the San Ysidro McDonald&amp;#39;s. Go ahead and jump in -- you can all think of an incident that fits.&#13;
&#13;
I&amp;#39;m not sure what any of these killings says, by the way, beyond the obvious: how violent the society is, how efficient firearms are at doing what they&amp;#39;re designed to do. But regardless of the meaning, to me, these have come part of the landscape we live in, a little like earthquakes in California. You know they&amp;#39;re coming; you know they could be devastating; but you never know when it&amp;#39;s going to happen.&#13;
&#13;
Of course, unlike earthquakes, in theory, at least, there&amp;#39;s the hope we might be able to do something to stop random massacres. After every one, there&amp;#39;s lots and lots of talk; Lou Dobbs and his sociologists. Then -- then we move on, till the next time.&#13;
&#13;
Posted by Dan Brekke at 03:15 PM &#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://infospigot.typepad.com/infospigot_the_chronicles/2007/04/force_of_nature.html"&gt;http://infospigot.typepad.com/infospigot_the_chronicles/2007/04/force_of_nature.html&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc/2.0/"&gt;Creative Commons Attribution-NonCommercial 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="9278">
                <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="11290">
                <text>Creative Commons Attribution-NonCommercial 2.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12755">
                <text>Force of Nature</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="83">
        <name>blog</name>
      </tag>
      <tag tagId="240">
        <name>commentary</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="501" 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="1834">
                <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="3725">
                <text>Dan Gillmor</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="5703">
                <text>2007-06-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7581">
                <text>April 17th, 2007 by Dan Gillmor&#13;
&#13;
&lt;i&gt;(Note: This will appear tomorrow as an op-ed piece in the &lt;a href="http://www.examiner.com/"&gt;Washington Examiner&lt;/a&gt; newspaper.)&lt;/i&gt;&#13;
&#13;
Once again, horror has given us a glimpse of our media future: simultaneously conversational and distributed, mass and personal.&#13;
&#13;
The killings Monday at Virginia Tech brought to the forefront the remarkable evolution in media over the past few years. And as we move into a time in which we will be saturated with data, we need to be clear on some of the implications of democratized media.&#13;
&#13;
We&amp;#39;ve had any number of glimpses already in this new century. On Sept. 11, 2001, we read blog postings and watched citizen videos of planes smashing into the World Trade Center towers. During the Asian tsunami, tourist videos showed waves smashing onto shores. A man in the London underground, wielding a mobile phone camera, took the image we all remember best from that day.&#13;
&#13;
The scope of the media shift was clearer again on Monday. Some of the most widely viewed images came from a mobile phone camera aimed at the police response by a student, Jamal Albaughouti. His video made its way to CNN and other media, and was seen by millions.&#13;
&#13;
But others on and off the Blacksburg, Va., campus were also using conversational media in highly visible ways. Social network communications, blog postings, email and a host of other technologies were brought to bear by people who were directly and indirectly part of this huge event.&#13;
&#13;
The students&amp;#39; words were achingly poignant. They were straight from the source, not pushed through a traditional-media funnel as they&amp;#39;d have been in the not-so-distant past.&#13;
&#13;
They brought to mind a blog post I spotted after the Sept. 11 terrorist attacks by a young man in Brooklyn, N.Y., across the river from the World Trade Center. He wrote, "Now I know what a burning city smells like."&#13;
&#13;
The democratization of media is not just about creation, though that has been the most notable aspect so far. Putting the tools into everyone&amp;#39;s hands has produced an explosion of media creation, as blogs and sharing sites such as YouTube and Flickr show us.&#13;
&#13;
Traditional media think of distribution: making journalism or movies or programs and sending them out to consumers. This is inverted in a democratized media world, where we all have access to what we want, as well as when and where.&#13;
&#13;
I didn&amp;#39;t turn on my TV yesterday except in the evening, to watch a national network&amp;#39;s news report. I wanted to see a summary of what a serious journalism organization had to say about what it knew so far.&#13;
&#13;
Instead, during the day, I used the online media â€” including the major news sites â€” to get the latest information, sifting it, making judgments about credibility and reliability as I read and watched and listened. That, too, is the future in many cases.&#13;
&#13;
It&amp;#39;s also worth noting that the citizen media component of this terrible event is not a new to the digital era. When President John F. Kennedy was gunned down in Dallas back in 1963, Abraham Zapruder caught the gruesome killing on a home movie camera â€” footage that became an essential part of the historical record. But the difference between then and tomorrow is this:&#13;
&#13;
In 1963, one man with a camera captured the event on film. In a very few years, a similar situation would be captured by thousands of people â€” all holding high-resolution video cameras â€” and all of those cameras would be connected to high-speed digital networks.&#13;
&#13;
That is different.&#13;
&#13;
Remember, too, that the passengers aboard the airplanes on Sept. 11, 2001, were making voice calls to loved ones and colleagues with mobile phones. What if they&amp;#39;d been sending videos to the world of what was happening inside those doomed aircraft?&#13;
&#13;
We will still need journalists to help sort things out. But the "burning city" words from 2001 revealed something.&#13;
&#13;
We used to say that journalists write the first draft of history. Not so, not any longer. The people on the ground at these events write the first draft. This is not a worrisome change, not if we are appropriately skeptical and to find sources we trust. We will need to retool media literacy for the new age, too.&#13;
&#13;
 This entry was posted on April 17th, 2007 at 1:12 pm and is filed under &lt;a href="http://citmedia.org/blog/category/citizen-journalism-general/"&gt;Citizen Journalism -- General&lt;/a&gt;, &lt;a href="http://citmedia.org/blog/category/news/"&gt;News&lt;/a&gt;.&#13;
&#13;
--&#13;
&#13;
Original Source: Center for Citizen Media Blog&#13;
&lt;a href="http://citmedia.org/blog/2007/04/17/virginia-tech-how-media-are-evolving/"&gt;http://citmedia.org/blog/2007/04/17/virginia-tech-how-media-are-evolving/&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-nc-sa/3.0/"&gt;Creative Commons Attribution-Noncommercial-Share Alike 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="9552">
                <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="11543">
                <text>Creative Commons Attribution-Noncommercial-Share Alike 3.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12996">
                <text>Virginia Tech: How Media Are Evolving</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="589">
        <name>citizen journalism</name>
      </tag>
      <tag tagId="613">
        <name>democratization</name>
      </tag>
      <tag tagId="556">
        <name>editorial</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="971" 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="2273">
                <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="4164">
                <text>Dan Stein</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="6142">
                <text>2007-08-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8020">
                <text>By: Dan Stein // Contributing Sports Writer&#13;
Issue date: 4/20/07&#13;
&#13;
While the Miami Hurricane baseball team prepares for another tough weekend on the road in the ACC this weekend, one cannot help but notice a somewhat distracted mood in the dugout. Needless to say, the tragedy that took place on Monday at Virginia Tech, in which a student opened fire on classmates and professors, has left some players pondering things other than baseball.&#13;
&#13;
"Our prayers and thoughts are with them," first baseman Yonder Alonso said. "It is just so hard to believe. I am sure their guys are thinking about it today and will be for the rest of the year. It is one of the worst things that ever happened in the country, so it is hard to deal with."&#13;
&#13;
While the &amp;#39;Canes will travel to Blacksburg for a three game series this weekend, it is clear that the events have now become somber, and once again the role of sports as a healing power in America will be taken on.&#13;
&#13;
"It is hard for them to have to deal with it, but I feel like one of the best things is to play the game," Alonso said.&#13;
&#13;
The kinship felt between ballplayers at any two schools is generally strong, but this series is full of personal connections.&#13;
&#13;
Alonso said that he is good friends with the Hokies&amp;#39; catcher and sent him an email as soon as he heard what had happened. The situation also hit home for starting pitcher Enrique Garcia, who said that he has close friends at the school whom he was frightened for.&#13;
&#13;
However, Garcia seems to share Alonso&amp;#39;s opinion, which also seems to be the team consensus, that the series is a good thing.&#13;
&#13;
"I am excited for the series," Garcia said. "I think it will definitely help to play, not just for the players, but as a nice distraction for the whole community."&#13;
&#13;
Head Coach Jim Morris will present a signed banner and $10,000 check for the Hokie Spirit Memorial Fund. The team is also having special wristbands made for the series and will travel with extra security.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.thehurricaneonline.com/media/storage/paper479/news/2007/04/20/Sports/Players.Team.React.To.Tragedy-2871193.shtml&gt;The Miami Hurricane - April 20, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9991">
                <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="11145">
                <text>The Miami Hurricane</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11902">
                <text>Greg Linch &lt;greglinch@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13395">
                <text>Players, team react to tragedy</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1220">
        <name>baseball</name>
      </tag>
      <tag tagId="1219">
        <name>players react</name>
      </tag>
      <tag tagId="1100">
        <name>university of miami</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="649" public="1" featured="0">
    <fileContainer>
      <file fileId="386">
        <src>https://april16archive.org/files/original/flower_bcb335890f.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="14777">
                    <text>2007-07-02</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15897">
                    <text>2007-07-02 12:05:05</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1976">
                <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="3867">
                <text>Dana Burman</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="5845">
                <text>2007-07-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7723">
                <text>Message boards filled with comments are stationed on the drill field.&#13;
&#13;
Photo Courtesy of Dana Burman</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9694">
                <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="11678">
                <text>Permission:&#13;
Dana Burman&#13;
dana74@dwburman.com</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="342">
        <name>drill field</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="429">
        <name>message boards</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="650" public="1" featured="0">
    <fileContainer>
      <file fileId="387">
        <src>https://april16archive.org/files/original/Norris_00b725bd17.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="14778">
                    <text>2007-07-02</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15898">
                    <text>2007-07-02 12:09:51</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="1977">
                <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="3868">
                <text>Dana Burman</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="5846">
                <text>2007-07-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7724">
                <text>Norris Hall has been sealed off as the police conduct its investigation. &#13;
&#13;
Photo Courtesy of Dana Burman</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9695">
                <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="11679">
                <text>Permission:&#13;
Dana Burman&#13;
dana74@dwburman.com</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="337">
        <name>crime scene</name>
      </tag>
      <tag tagId="339">
        <name>norris hall</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="651" public="1" featured="0">
    <fileContainer>
      <file fileId="388">
        <src>https://april16archive.org/files/original/media_51ec4c1cff.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="14779">
                    <text>2007-07-02</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15899">
                    <text>2007-07-02 12:12:25</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="1978">
                <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="3869">
                <text>Dana Burman</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="5847">
                <text>2007-07-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7725">
                <text>Major media outlets interview students, faculty, and staff.&#13;
&#13;
Photo Courtesy of Dana Burman</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9696">
                <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="11680">
                <text>Permission:&#13;
Dana Burman&#13;
dana74@dwburman.com</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="775">
        <name>interviews</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
      <tag tagId="344">
        <name>reporter</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="652" public="1" featured="0">
    <fileContainer>
      <file fileId="389">
        <src>https://april16archive.org/files/original/memorial_52716ce21a.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="14780">
                    <text>2007-07-02</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15900">
                    <text>2007-07-02 12:16:39</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1979">
                <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="3870">
                <text>Dana Burman</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="5848">
                <text>2007-07-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7726">
                <text>The memorial at the Drill Field near Burress Hall and Norris Hall. &#13;
&#13;
Photo Courtesy of Dana Burman</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9697">
                <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="11681">
                <text>Permission:&#13;
Dana Burman&#13;
dana74@dwburman.com</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="362">
        <name>burress hall</name>
      </tag>
      <tag tagId="342">
        <name>drill field</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="869" 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="2178">
                <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="4069">
                <text>Daniel Colbert</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="6047">
                <text>2007-07-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7925">
                <text>&lt;b&gt;Experts in fields of security, law and mental health comprise panel; victims&amp;#39; families voice reactions&lt;/b&gt;&#13;
&#13;
Daniel Colbert, Cavalier Daily Senior Writer&#13;
&#13;
Thursday, April 19, while the nation was still coming to grips with the tragedy that had unfolded in Blacksburg three days earlier, Gov. Tim Kaine created an eight-member panel of experts in the fields of security, law and mental health to investigate fully what had gone wrong and what could be done to help prevent a similar incident in the future. Last Wednesday, the panel held what was to be its last public meeting -- it has since been announced that another will follow -- at the University. While the panel heard testimony on topics as wide-ranging as community mental health services and gun control laws, much of the discussion centered on the unique challenges faced in servicing and protecting a college population.&#13;
&#13;
Beyond "lockdown"&#13;
&#13;
As schools consider the most efficient and safe methods for responding to threats such as an active shooter on campus, lockdowns are a common solution. In fact, much of the panel&amp;#39;s discussion of security procedures focused on the appropriateness and plausibility of a campus-wide lockdown; however, all of the law enforcement experts who testified at the meeting in Charlottesville suggested that responding to such an event is not so simple.&#13;
&#13;
"I think we have this impression that we hit a switch and everything is locked and everything is secure, and that is not the case," said Don Challis, chief of police at the College of William &amp; Mary.&#13;
&#13;
Challis testified that a lockdown creates a "target-rich environment" in the academic buildings where students congregate. He instead recommended that colleges advise students to take refuge in their own rooms or other safe places. Challis emphasized that colleges need to make it clear in advance what would be expected of students in a crisis situation.&#13;
&#13;
"Hope is not a plan," Challis said. "We can&amp;#39;t hope that when something happens these people hang on our words and do what we say."&#13;
&#13;
Avoiding a tragedy&#13;
&#13;
Perhaps the most vexing question surrounding the Virginia Tech tragedy regards the various warning signs of the danger that shooter Seung-Hui Cho posed to others. The panel spent much of the morning hearing ways for universities to more readily identify a troubled student.&#13;
&#13;
Central to the goal of pre-emptive action are Threat Assessment Teams. These teams, present at many schools though not formally at the University, are made of up administrators, deans and law enforcement officers that meet to identify and evaluate potential threats posed by students, according to Challis&amp;#39;s testimony.&#13;
&#13;
Both Challis and Dr. James Madero, a professor at Alliant International University, testified that teams like these can be helpful in preventing school violence.&#13;
&#13;
"It needs to be a campus-wide group that includes ... people who have the most contact with students," Challis said. "If they see a flag, they can run that by others."&#13;
&#13;
The panel also heard testimony on the effectiveness of campus psychological services, primarily from Russell Federman, University director of counseling and psychological services.&#13;
&#13;
Federman pointed to the low suicide rate at the University-- three suicides in the last seven years, which is less than a third of the national average -- as evidence that CAPS is effective in dealing with high-risk individuals.&#13;
&#13;
Among the factors contributing to this success, he said, are frequent communication between the administration, faculty and CAPS to determine individuals who may pose threats and follow-up procedures for high-risk individuals who do not appear for counseling.&#13;
&#13;
"My hunch is that if Mr. Cho had been involuntarily hospitalized at U.Va. [as he was at Virginia Tech before the shootings occurred], CAPS staff would have become involved with him much earlier," Federman said.&#13;
&#13;
Not everyone was satisfied with Federman&amp;#39;s reasoning, however. Holly Sherman, whose daughter Leslie was a victim of the shootings, told reporters she thought the procedures Federman described were "very similar" to those in place at Virginia Tech before the shootings.&#13;
&#13;
Although he said he was confident that academic deans would have contacted CAPS about a student exhibiting the strange behaviors attributed to Cho, Federman said in a later interview he also could not say with certainty that CAPS would have prevented the shooting.&#13;
&#13;
"We can&amp;#39;t buy into the illusion that we can control the uncontrollable," Federman said. "The bottom line is if someone chooses to be violent, he or she can be without us being able to stop that."&#13;
&#13;
Issues of confidentiality&#13;
&#13;
One of the hotly debated issues of the day was the importance of students&amp;#39; rights, as adults, to privacy regarding their mental health records.&#13;
&#13;
Panelist Diane Strickland, Law School alumna and former dean of Student Legal Services, asked if CAPS had access to the mental health records of incoming first-year students while another panelist, Dr. Roger Depue, said he wondered if such information would prove to be helpful.&#13;
&#13;
Privacy concerns dictate that the University does not have such access, Federman answered, but that is not necessarily a problem for CAPS.&#13;
&#13;
Mandatory on-Grounds housing for first-year students ensures that mental health problems are observed quickly by Resident Staff or fellow students, Federman said. He added that even if mental health professionals had access to background information on a student, it would not always be necessary in deciding how to proceed with treatment.&#13;
&#13;
Several victims&amp;#39; parents expressed concern that privacy issues may hinder communication between administrators about students who present potential threats and may prevent mental health professionals from informing parents if their children seek psychological help.&#13;
&#13;
The experts testifying were divided over whether privacy laws make it difficult to share information among administrators. While Challis testified that privacy laws sometimes make it difficult to determine what information can be shared legally, other experts did not believe this to be the case.&#13;
&#13;
"I have been very alarmed by the perception that the law somehow impedes colleges and universities from doing what they think to be the right thing," University law Prof. Richard Bonnie said.&#13;
&#13;
Parental involvement does not always help mental health professionals treat students, Federman said, and it is rarely absolutely necessary. College represents a time of transition between dependency and autonomy for many students, and he said he believed, in most cases, automatically involving parents would undermine that transition.&#13;
&#13;
"That&amp;#39;s quite different from a very acute situation where we&amp;#39;re looking at issues of violence and danger to self and where we absolutely need the family involved to help us prevent a tragic outcome," Federman said.&#13;
&#13;
During the panel&amp;#39;s meeting, Federman resisted a call from Tom Ridge, former secretary of homeland security, to develop standardized guidelines for informing parents when their children seek psychological help, but assured the panel that mental health professionals would breach privacy laws if a situation demanded it.&#13;
&#13;
Several of the victims&amp;#39; parents present were unsatisfied with the explanations.&#13;
&#13;
"I worry about a society that places individual rights in such a high regard that it jeopardizes public safety," said Catherine Read, step-mother of victim Mary Read. &#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a&gt;http://www.cavalierdaily.com/CVArticle.asp?ID=30458&amp;pid=1596&gt;The Cavalier Daily - July 26, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9896">
                <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="11823">
                <text>Meggie Bonner &lt;meggiebonner@gmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13313">
                <text>Virginia Tech panel discusses prevention strategies</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="721">
        <name>campus safety</name>
      </tag>
      <tag tagId="975">
        <name>college population</name>
      </tag>
      <tag tagId="974">
        <name>investigation panel</name>
      </tag>
      <tag tagId="72">
        <name>uva</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="639" 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="1967">
                <text>Adriana Seagle</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3858">
                <text>Daniel E. Loeb / The Philadelphia Jewish Voice</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="5836">
                <text>2007-07-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7714">
                <text>The Jewish community mourns with Virginia Tech. &#13;
&#13;
&lt;i&gt;-- Daniel Loeb&lt;/i&gt;&#13;
&#13;
The deadliest campus shooting in the history of the US occurred on Monday, April 16 at Virginia Tech. The tragic shootings at Virginia Tech happened on the day Jews all over the world observe Yom Hashoah, Holocaust Remembrance Day, and which is marked in Israel with two minutes of silence, prayer and reflection. &#13;
&#13;
The United States Congress has called for a minute of silence on Friday, April 20 at noon, to remember Monday&amp;#39;s victims, as well as the millions of other men and women around the world who have died at the hands of armed madmen and criminals. &#13;
&#13;
Seung-Hui Cho killed 32 people and injured 29 more before taking his own life.&#13;
&#13;
Ironically, one of the Virginia Tech victims, aeronautics professor Liviu Librescu, was a survivor of the Holocaust. He died while barricading his classroom against the gunman, saving the lives of several of his students through his sacrifice on Yom Hashoah.&#13;
&#13;
Librescu, born in 1930 in Ploiesti, Romania, survived the Holocaust in the ghetto of Focsani while his father was interned in the Transnistria labor camp. After the war, he studied Aerospace Engineering at the Polytechnic University of Bucharest and Fluid Mechanics at the Academia de Stiinte din Romania. &#13;
&#13;
He distinguished himself as a researcher at the Institute of Applied Mechanics, Institute of Fluid Mechanics and Institute of Fluid Mechanics and Aerospace Constructions of Academy of Science of Romania. However, then Romanian President Nicolae Ceausescu did not allow him to emigrate to Israel, however, until Israeli Prime Minister Menachem Begin personally intervened on Prof. Librescu&amp;#39;s behalf in 1978. &#13;
&#13;
After making aliyah, Librescu served as a Professor of Aeronautical and Mechanical Engineering at Tel-Aviv University. In 1985, he joined the faculty at Virginia Tech where he distinguished himself as the Virginia Tech professor with the greatest number of publications. &#13;
&#13;
At age 76, Professor Librescu held the door of his classroom shut so that Cho Seung-hui could not enter before his students escaped through the windows. Cho shot Liviu Librescu through the door mortally wounding this Professor considered a hero by his students. &#13;
&#13;
Professor Librescu was &lt;a href="http://www.pjvoice.com/v23/23001vatech.aspx"&gt;commended posthumously&lt;/a&gt; by the President of Romania with the Star of Romania Order in the grade of Great Cross, "as a token of high appreciation for the entire scientific and universitarian activity, as well as for his heroic acts during the tragic events of April 16th 2007 in the Virginia Polytechnic Institute and State University campus, when professor Librescu saved his students&amp;#39; lives at the cost of his own". &#13;
&#13;
Rabbi Yossel Kranz announced that the new Chabad House at Virginia Tech will be named for Professor Liviu Librescu. "Professor Librescu&amp;#39;s final act of heroism will be eternally memorialized in the life-affirming activities of the new center," said Rabbi Kranz. The professor&amp;#39;s widow Mrs. Marilena Librescu and their sons Ari and Joe shared with Rabbi Kranz their wishes that Librescu House serve as a home of healing, joy and spiritual fulfillment to Virginia Tech&amp;#39;s Jewish students.&#13;
&#13;
--&#13;
&#13;
Â© 2007. Permission is hereby granted to redistribute this issue of The Philadelphia Jewish Voice or (unless specified otherwise) any of the articles therein in their full original form provided these same rights are conveyed to the reader and subscription information to The Philadelphia Jewish Voice is provided. Subscribers should be directed to &lt;a href="http://www.pjvoice.com/Subscribe.htm"&gt;http://www.pjvoice.com/Subscribe.htm&lt;/a&gt;.&#13;
&#13;
Original Source: The Philadelphia Jewish Voice&#13;
&lt;a href="http://www.pjvoice.com/v23/23001vatech.aspx"&gt;http://www.pjvoice.com/v23/23001vatech.aspx&lt;/a&gt; </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9685">
                <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="11669">
                <text>Daniel E.Loeb (daniel.loeb@verizon.net)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13117">
                <text>Holocaust Survivor Slaughtered On Yom Hashoah </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="639">
        <name>community</name>
      </tag>
      <tag tagId="757">
        <name>jewish</name>
      </tag>
      <tag tagId="435">
        <name>librescu</name>
      </tag>
      <tag tagId="758">
        <name>mourns</name>
      </tag>
      <tag tagId="116">
        <name>prayer</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="267" public="1" featured="0">
    <fileContainer>
      <file fileId="179">
        <src>https://april16archive.org/files/original/16_1e4d9aefa8.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="14576">
                    <text>2007-05-27</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="15696">
                    <text>2007-05-27 16:21:33</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1620">
                <text>Daniel Lin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3511">
                <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="5489">
                <text>2007-05-27</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7368">
                <text>Man mourning near Burruss and Norris Halls.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9338">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="268" public="1" featured="0">
    <fileContainer>
      <file fileId="180">
        <src>https://april16archive.org/files/original/50_261e8a7882.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="14577">
                    <text>2007-05-27</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="15697">
                    <text>2007-05-27 16:25:20</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="1621">
                <text>Daniel Lin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3512">
                <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="5490">
                <text>2007-05-27</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7369">
                <text>Students stand during the playing of the Star Spangled Banner during the convocation on April 17, 2007.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9339">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="122">
        <name>april 17</name>
      </tag>
      <tag tagId="36">
        <name>convocation</name>
      </tag>
      <tag tagId="124">
        <name>stadium</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="379" public="1" featured="0">
    <fileContainer>
      <file fileId="246">
        <src>https://april16archive.org/files/original/mourning_306b734429.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="14643">
                    <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="15763">
                    <text>2007-06-05 10:12:17</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1721">
                <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="3612">
                <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="5590">
                <text>2007-06-05</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7468">
                <text>Individuals mourn as they attend the candlelight vigil at Virginia Tech.  &#13;
&#13;
Original source: &lt;a href="http://www.flickr.com/photos/geeknerd99/464196491/in/photostream/"&gt;http://www.flickr.com/photos/geeknerd99/464196491/in/photostream/&lt;/a&gt;&#13;
&#13;
Photo Courtesy of Daniel Lin </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9439">
                <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="11435">
                <text>Permission:&#13;
Daniel Lin&#13;
geeknerd99@gmail.com</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="215">
        <name>candlelight vigil</name>
      </tag>
      <tag tagId="390">
        <name>mourning</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
      <tag tagId="385">
        <name>virginia tech vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="380" public="1" featured="0">
    <fileContainer>
      <file fileId="247">
        <src>https://april16archive.org/files/original/Vigil III_00768dd2d7.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="14644">
                    <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="15764">
                    <text>2007-06-05 10:14:55</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="1722">
                <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="3613">
                <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="5591">
                <text>2007-06-05</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7469">
                <text>This photo was captured at the Virginia Tech candlelight vigil.&#13;
&#13;
Original source: &lt;a href=" http://www.flickr.com/photos/geeknerd99/464198355/"&gt; http://www.flickr.com/photos/geeknerd99/464198355/&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="9440">
                <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="11436">
                <text>Permission:&#13;
Photo Courtesy of Daniel Lin</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="215">
        <name>candlelight vigil</name>
      </tag>
      <tag tagId="390">
        <name>mourning</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
      <tag tagId="385">
        <name>virginia tech vigil</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
