<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://www.april16.vtlibraries.net/items?output=omeka-xml&amp;page=53&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-12T15:21:32+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>53</pageNumber>
      <perPage>20</perPage>
      <totalResults>1884</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="808" 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="2123">
                <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="4014">
                <text>Judy Polumbaum</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="5992">
                <text>2007-07-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7870">
                <text>By Judy Polumbaum&#13;
Updated: 2007-04-19 07:10&#13;
&#13;
Details of the shootings on the Virginia Tech campus on Monday have unfolded to confirm that the gunman was a US resident originally from South Korea. He is Cho Seung-hui, who killed 32 people and then himself in the worst campus carnage in US history.&#13;
&#13;
Cho, a senior English major at the university who had come to the US at the age of 8, went about his murders methodically. Doors of one building where he opened fire on classes had been chained from the inside.&#13;
&#13;
Two hours earlier, a young woman and a resident hall assistant had been shot at a dormitory, a presumably related incident that police at first interpreted as a domestic dispute. Their assumption led to the calamitous delay in alerting the campus and community to the threat.&#13;
&#13;
The Virginia shooting inevitably brings back memories of a gunman&amp;#39;s rampage one drizzly November afternoon more than 15 years ago on the campus of the University of Iowa, where I teach. The killer at Iowa was Lu Gang, a Chinese doctoral student in physics and astronomy.&#13;
&#13;
On November 1, 1991, just up the hill from my office, Lu shot to death one fellow Chinese, three professors and an administrator, and critically wounded an undergraduate student, leaving her a paraplegic, before killing himself.&#13;
&#13;
Undoubtedly, as more becomes known about the Virginia Tech shooter and his circumstances, people will reflect on what produced the sort of nihilistic rage that could lead someone to commit mass murder.&#13;
&#13;
Such rumination, among both Americans and Chinese, ensued after the Lu Gang shootings. Most of us on the Iowa campus, and US observers generally, viewed Lu Gang&amp;#39;s crimes primarily as the actions of a deranged individual. In China, by contrast, people sought broader social explanations.&#13;
&#13;
A prolonged discussion carried out in the pages of the Beijing Youth News raised a variety of notions, including that Lu Gang&amp;#39;s generation lacked good values due to defective early schooling during the "cultural revolution". A minority of readers suggested that the unfair pressure and discrimination that Chinese students suffered abroad was the root cause.&#13;
&#13;
Such analyses were contradicted, of course, by the story of the young Chinese colleague among Lu&amp;#39;s victims. Shan Linhua, brilliant, outgoing, well liked, the son of poor peasants from Zhejiang Province, had flourished at Iowa, winning a prestigious dissertation award and a research job on campus after his graduation.&#13;
&#13;
Among the factors once again under discussion in the wake of the Virginia tragedy are an American "culture of violence" celebrated in mass media, a prevalence of "narcissism" among young people who lash back when they feel slighted, and shortcomings in provision of psychological counseling for troubled students.&#13;
&#13;
Ultimately, however, what enabled both campus killers to cut down other human beings was the easy accessibility of guns in the United States.&#13;
&#13;
After the Iowa shootings, Lu Gang was found to have purchased guns and practiced his markmanship at a local shooting range. Similarly, Cho Seung-hui wrought bloody mayhem with two guns and ample ammunition in hand. Reports say that five weeks earlier, wielding merely a credit card, he had paid $500 for a gun.&#13;
&#13;
Weapons fanciers among US bloggers and commentators are raising a hue and cry against using the Virginia episode as another argument for gun control.&#13;
&#13;
The zealots claim the mantle of the US Constitution, specifically, the Second Amendment. They selectively stress the phrase "the right of the people to keep and bear arms" while conveniently ignoring the larger context, which is to support society&amp;#39;s ability to maintain a "well-regulated militia" for its security.&#13;
&#13;
Nothing could be less secure than a nation awash in guns. We speak of "random" violence in connection with these campus shootings, but such incidents are not random. They&amp;#39;re a logical result of the doctrine that gun ownership is an unassailable personal right, along with the blithe attitude that trade in guns is simply another unexceptional form of commerce.&#13;
&#13;
Even in US states with stricter regulation, any lunatic who wants to buy a gun can find a way. The fact that both Iowa and Virginia shooters were of Asian heritage is mere coincidence. Their shared instruments of choice are not.&#13;
&#13;
Judy Polumbaum is professor of journalism at The University of Iowa &#13;
&#13;
--&#13;
Original Source:ChinaDaily&#13;
&#13;
&lt;a href="http://www.chinadaily.com.cn/cndy/2007-04/19/content_853892.htm"&gt;http://www.chinadaily.com.cn/cndy/2007-04/19/content_853892.htm&lt;a/&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9841">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13260">
                <text>One more rampage, same weapon of choice</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="87">
        <name>gun control</name>
      </tag>
      <tag tagId="1222">
        <name>psychological counseling</name>
      </tag>
      <tag tagId="1224">
        <name>rampage</name>
      </tag>
      <tag tagId="1223">
        <name>troubled students</name>
      </tag>
      <tag tagId="1229">
        <name>weapon of choice</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="73" public="1" featured="0">
    <fileContainer>
      <file fileId="56">
        <src>https://www.april16.vtlibraries.net/files/original/a day of mourning_e285692467.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="14476">
                    <text>2007-05-01</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15596">
                    <text>2007-05-01 23:29:19</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="1444">
                <text>Melissa Helms</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3335">
                <text>Melissa Helms</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="5313">
                <text>2007-05-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7194">
                <text>one of the many trees around the drillfield</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9162">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12659">
                <text>One Tree</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="33">
        <name>Drillfield</name>
      </tag>
      <tag tagId="46">
        <name>ribbon</name>
      </tag>
      <tag tagId="138">
        <name>tree</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1678" 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="2821">
                <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="4712">
                <text>Charles W. Steger</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="6690">
                <text>2008-02-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8568">
                <text>Date:  	Fri, 15 Feb 2008 18:17:17 -0500&#13;
From: 	Virginia.Tech.news@vt.edu&#13;
To: 	Multiple recipients &lt;LISTSERV@LISTSERV.VT.EDU&gt;&#13;
Subject: 	Ongoing support for Northern Illinois University, Virginia Tech&#13;
&#13;
Friday, February 15, 2008&#13;
&#13;
The Virginia Tech community continues to reach out to those at Northern Illinois University.&#13;
&#13;
Throughout today, numerous university administrators, faculty and students have been in contact with counterparts at NIU to offer assistance, advice, and support. The university will continue to lend support as long as it is needed.&#13;
&#13;
Cook Counseling Center will be open Saturday, Feb. 16 and Sunday, Feb. 17 from noon to 5 p.m. Walk-in appointments are welcome to students who may wish to seek support should difficult memories of last year&amp;#39;s event resurface. The center can be reached at 231-6557 24 hours a day, seven days a week.&#13;
&#13;
Employees seeking assistance can call 866-725-0602 anytime 24 hours a day.&#13;
&#13;
Hokies United is planning a candlelight vigil Monday night on Alumni Mall, near Torgersen Bridge. The event will be at dusk, approximately 6:30 p.m. Everyone in the Blacksburg and Virginia Tech communities are welcome.&#13;
&#13;
Hokies United is also asking everyone to wear red and black on Monday to show solidarity and support for the Northern Illinois University community.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10539">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13885">
                <text>Ongoing support for Northern Illinois University, Virginia Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1552">
        <name>counseling</name>
      </tag>
      <tag tagId="1911">
        <name>niu</name>
      </tag>
      <tag tagId="1909">
        <name>northern illinois university</name>
      </tag>
      <tag tagId="133">
        <name>steger</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="514" 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="1846">
                <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="3737">
                <text>Lisette Rimer</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="5715">
                <text>2007-06-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7593">
                <text>May 14, 2007&#13;
By Lisette Rimer&#13;
&#13;
Dear Dr. Hennessy,&#13;
&#13;
Thank you for your op-ed piece May 4th on preventing future tragedies such as Virginia Tech. It was forwarded to me byone of your students who suffered the loss of a friend, my son Patrick Wood. Patrick graduated from Stanford in 2005 with distinction in math. He loved the school, had many friends there, and was even treated for depression there. In January before he graduated, he was hospitalized for, as he explained to me, "having thoughts of suicide." He was committed to the Stanford hospital for five days, but proclaimed that he was OK, mostly bored, and didn&amp;#39;t belong there. The psychiatrist in charge at the hospital agreed that Pat was OK and should be permitted to return to school as long as he continued therapy. He saw a therapist and a psychiatrist on campus and renewed his medication. His mood was up and down, but he continued an active social life and good communication with us. He was excited about an internship at Siemens in Berlin, Germany, which he began after graduation. He had applied for the internship through the Stanford Center in Berlin. He suspended his therapy for the summer with plans to return in September for the computer science co-term program, but he loved Berlin too much to leave just yet. Another friend from Stanford was arriving to work in the American Embassy there, and so Patrick obtained a leave of absence and continued to work at Siemens through the fall.&#13;
&#13;
All the while, he made many friends, spoke and wrote fluent German, went to concerts with colleagues at Siemens, and maintained close contact with the Stanford Center. He could often be heard playing the piano there just as he had done at Haus Mitt. He wrote about a "mini-depression" before he came home to Connecticut for Christmas vacation. We thought a medication refill would be the answer. His twin sister and older brother were home, along with cousins, aunts, and uncles. It was the usual busy but fun time. Pat later told friends it was "relaxing" and that it was good to get away from the city for a while. On December 27th, he went to New York City to see another good friend from Stanford. He returned to Berlin on the 28th. In January he wrote about a "mini-breakdown." We had many emails. I called, but could not contact him by telephone. His last email to me was on January 26th. Humboldt University had requested additional information on his application as a grad student there. He took it as rejection, told me he might be returning to Stanford, and asked me to wish him luck. He answered no more emails after that. He saw friends on the weekend of the 28th and 29th. He did not return phone calls after Tuesday the 31st. His friend, who worked at the American Embassy and who lived a block away, became worried. He called and went to Pat&amp;#39;s apartment several times the following weekend. He called the Stanford Center on Monday morning. They called the police to break into the apartment. By that evening, the police found Pat. He had died of carbon monoxide poisoning on Tuesday, January 31st.&#13;
&#13;
Patrick was one of many graduates that June. He was one of many more who were going on to graduate school. The school cannot be responsible for every student on campus or every new graduate. I am under no illusions about who was responsible for his treatment and for what he did. It was Patrick alone who decided to stay in Germany, who decided to suspend treatment, and ultimately who decided that suicide would relieve his depression. I have tried to retrace his steps continuously in my mind ever since we were notified on February 6, 2006. On that day, his friend and others from the Stanford Center identified him. They called a Stanford residential housing director in Palo Alto, and he called us. Both the Stanford School in Berlin and Palo Alto had memorial services for him in February and March of last year. As you can see, the school was very much involved in both the life and in the death of my son.&#13;
&#13;
Please do not mistake my comments for blame. Maybe no one could have prevented his loss, but I have learned that it is the very nature of his disease, and of Cho&amp;#39;s at Virginia Tech, that should cause us to be hyper-vigilant. Students who are depressed, even brilliant and loving students like Pat, cannot function reliably because the source of their decision-making process is under attack. They are making flawed decisions because the very same mechanism used to make these decisions is malfunctioning. There is an anatomical difference between a healthy brain and a depressed brain. It is a detectable, visible difference, and yet it is only a part of the brain, for many decisions appear "normal." It is those normalities which lulled me into thinking that Pat would get help, that he would take care of himself, that he would certainly see how magnificent he was, that he had just graduated from Stanford with a 3.9 average and a major in math, that his friends loved him, that he had had the best childhood we could provide, that he had the brightest future of anyone. How could he not be happy? The answer is because depression does not operate on the same assumptions.&#13;
&#13;
I have had to change my own notions of well-being because they failed Pat. He did not get help in Germany because he could not. The decisions he needed to make were not possible with the oppression and pain he was feeling. Although he was physically able to get to a doctor or call a therapist, just as he had done at Stanford, those functions needed motivation, and it was his motivation which had been destroyed. All the drive, the talent, the brilliance that had won him a full scholarship to Pomfret School, that had gotten him perfect SAT&amp;#39;s, that had made him a valedictorian, that had made him a merit scholar, that had gotten him into Stanford, that won him a scholarship there, that had gotten him into the Krupp Internship program in Germany and then into Siemensâ€”all the motivation he needed to achieve academic and social success was no match for this disease. He had sought treatment, and it had not worked, so he turned inward until he isolated his thoughts, his wants, and his pain, until he was feeling nothing but the sense of control which suicide brings.&#13;
&#13;
I think your comments about psychological services are a welcome response. Pat&amp;#39;s life was saved the first time he had major depression and was hospitalized by one of the counselors on campus, and I am deeply grateful. But I would hope, in the wake of Pat&amp;#39;s agonizing loss and the frightening possibility of another Virginia Tech, that we come away with a few additional realizations. I have spent every day trying to do the same thing.&#13;
&#13;
Mainly I hope that we understand that suicide victims are not insane. They function as well as they need to function. Almost everything about Pat was normal on the outside, even the relationship problem that preceded his death.&#13;
&#13;
A truth I have learned too late is that we have to go to them. Pat needed someone to take him for help. Just because he did it the first time didn&amp;#39;t mean he would do it again. As a matter of fact, there was less chance he would get help because he was weakened from the first depressive episode.&#13;
&#13;
Because I have learned that depression is a terminal illness, I would hope that we could change the meaning of the term from a saddened state of mind, to the dangerous, insidious threat that it is. Most people who commit suicide have been depressed and have attempted it beforehand. As I think Patrick and the Virginia Tech incident made abundantly clear, we are ill-equipped to detect the severity of the disease and, therefore, the likelihood that these victims will complete a suicide. Anatomical detection would give us empirical data that we need to make a more accurate diagnosis, certainly more accurate than relying on a patient to rate himself on a depression scale as is now commonly the case. How many other diseases have to be self-diagnosed when a patient is least able?&#13;
&#13;
And finally, a thought about treatment. A newspaper article last year pointed out that patients who were "cured" had to endure an average of four combinations of medication and therapy before finding one that succeeded. That means a great deal of trial and error at a time when any failure can be misconstrued as a reason for hopelessness and self-harm.&#13;
&#13;
The implications for a university are complex. How much do you reach out, especially if the patient does not seek treatment? How do you know the severity of the depression? If we are relying on averagely intelligent people to pick up on the cues, we will never succeed. I know because I am one of those failures. I will hate myself forever for what I did not know about depression, for what I missed, for what I did not do for my son, but I also know that there are a lot of people saying the same thing about Cho. They are all blaming themselves, just as I am, because what passes for non-threatening behavior before suicide becomes pockmarked with danger signs afterward. I should have gone to Berlin. I should have called his friends. I should have done a lot of things and so should they who knew Cho. But we don&amp;#39;t because we don&amp;#39;t know they are necessary. We don&amp;#39;t know they mean life or death, and we will not know until we have reliable detection.&#13;
&#13;
Maybe the lesson that arises from Patrick, a favorite son of Stanford, is that students within Stanford programs should be better monitored no matter where they are. Whether they are in Palo Alto or Germany, follow-up and care (and this is most important) should be initiated by the school. Why? Because seriously depressed students are less likely to seek treatment. They consider themselves to be defective instead of legitimately sick because that&amp;#39;s what depression does. It convinces them that there is no hope, and therefore no cure, but that is really depression talking. We have to break through that. We have to go to them, physically and mentally. If you go to the website for The American Federation for Suicide Prevention, you will see their advice for preventing suicide. The suicidal person cannot be expected to independently seek treatment. Somebody must take them.&#13;
&#13;
If we can come away with any insight from Patrick and Cho, it is that follow-up was woefully lacking. I shudder to mention their names in the same sentence, but similar questions in their aftermaths compel me. Why didn&amp;#39;t the school follow up on Pat&amp;#39;s treatment in Germany even though he was in a Stanford internship program? The answer: Stanford was relying on Pat, and so was I. That cannot continue. When students become patients, the school must monitor them as long as they are connected to the school and wherever they are connected. Depressed students â€” even the best, like Pat â€” are simply not capable. Depressed students don&amp;#39;t seek treatment because they are, not surprisingly, depressed. This is how depression kills, and in the process, it robs functioning until there is very little on which to rely. How do we know when that functioning is gone? We don&amp;#39;t, and that is why it is up to us to know more. It is simply in our own best interest to detect and treat more actively and accurately. If I have come away with anything from the loss of my beautiful son it is this: Depression will kill anybody, but the burden is on usto know whom.&#13;
&#13;
When Pat graduated in 2005, our whole family came to Stanford to wish him well: my husband and I from Connecticut, his older brother Colin and Colin&amp;#39;s friend Julie from Washington State, his twin sister Libby from Vermont, and his grandparents Dr and Mrs. David Rimer from Los Angeles. We all came to congratulate him, and we were impressed with the beautiful ceremonies and meaningful events, but as I read your op-ed piece, the memory of meeting you at graduation stood out the most. You seemed like a caring person, even during the brief moments in which we had our photograph taken with you. We commented afterward how welcoming you and your wife had been, even though you were probably exhausted from shaking hands and posing for several hours. And now I write to ask you to bring that caring sensibility to the forefront of this issue. Suicide is the second leading cause of death for college students. It weakens parents&amp;#39; confidence in the safety of their children on campus â€” parents, who, by the way, are already feeling excluded from the well-beings of their children because of confidentiality. We cannot see grades, get psychiatric records, get tuition bills directly, or intervene on students&amp;#39; behalf. Everything is left up to the student, and, as we have seen with Patrick and Cho, we risk too much isolation.&#13;
&#13;
Again, thank you for your interest in this issue, and thank you for promoting the psychological well-being of your students. I appreciate your focusing Stanford&amp;#39;s public attention on these avoidable catastrophes. Patrick loved Stanford dearly. He was grateful for the services you did provide, and now, in his stead, we are grateful for your continuing efforts to protect our children.&#13;
&#13;
I invite you to visit the memorial blog set up for Patrick by his Stanford friends at: http://patrickwood.blogspot.com/&#13;
&#13;
Sincerely,&#13;
&#13;
Lisette Rimer, Pat&amp;#39;s mom&#13;
Pomfret Center, Connnecticut&#13;
&#13;
&lt;b&gt;Comment on this article &lt;/b&gt;&#13;
&#13;
&lt;b&gt;Jon Bell&lt;/b&gt; - 5/14/07&#13;
&#13;
Ten day ago, a newly-admitted Freshman to Stanford went on yet another in a long-time-series of verbal abuse tirades against all the people who loved her; wished that they were all dead; that she hated all people, especially the rich--and that after Stanford she wanted a career in public relations. This person is now getting help--if she allows it. The University has been informed and has been fabulous.&#13;
&#13;
&lt;b&gt; Ted Rudow III,MA &lt;/b&gt;- 5/14/07&#13;
There is no reason to doubt the generous impulse behind the work of professional psychologists and social scientists. Most of the experts who guide the psychological society have good intentions.&#13;
&#13;
But there may be reasons to doubt the competence of psychological helpers. A willingness to help does not guarantee a helpful result. Sometimes, as Thoreau wryly observed, the result is the opposite: "If I knew for a certainty that a man was coming to my house with the conscious design of doing me good, I should run for my life."&#13;
&#13;
The fact that psychologists are trying to help people often keeps us from asking whether they know how to help. We think it&amp;#39;s bad manners to ask a man who is trying to help us if he really knows what he&amp;#39;s doing. Of course, it&amp;#39;s not just manners that prevent us from questioning psychology. It&amp;#39;s also faith--the kind of faith that makes us believe that school teachers are doing what is best for our children. Or the kind of faith that tells you that the man in the clerical collar won&amp;#39;t knock you down and steal your wallet. Just the same, we ought to be asking if psychologists really do know how to help. A good deal of research suggests that psychology is ineffective. And there is evidence pointing to the conclusion that psychology is actually harmful.&#13;
The first indication that psychology might be ineffective came in 1952 when Hans Eysenck of the Institute of Psychiatry, University of London, discovered that neurotic people who do not receive therapy are as likely to recover as those who do. Psychotherapy, he found, was not any more effective than the simple passage of time. Additional studies by other researchers showed similar results. Then Dr. Eugene Levitt of the Indiana University School of Medicine found that disturbed children who were not treated recovered at the same rate as disturbed children who were. A further indication of the problem was revealed in the results of the extensive Cambridge-Somerville Youth Study. The researchers found that uncounseled juvenile delinquents had a lower rate of further trouble than counseled ones. Other studies have shown that untrained lay people do as well as psychiatrists or clinical psychologists in treating patients. And the Rosenham studies indicated that mental hospital staff could not even tell normal people from genuinely disturbed ones. It is possible to go on with the list. It is quite a long one. But I hope this is sufficient to make the point that when psychologists rush in to help, they are not particularly successful.&#13;
&#13;
&lt;b&gt; Ted Rudow III, Scientologist &lt;/b&gt; - 5/14/07&#13;
Hey Ted, what exactly do you mean by, "psychology is actually harmful." That&amp;#39;s a pretty nice blanket statement there. What you&amp;#39;re meaning to say is, clinical psychology isn&amp;#39;t always effective. The studies you list aren&amp;#39;t indictments of psychology as a discipline, but specific methods of treatment. And none of them conclude, "Therefore, nobody should trust any psychologists, because of what we have tried to show." Seriously. Neurosis is not as widespread or specific as depression. Psychotherapy was always hackery and has little to do with modern-day depression treatment methods. Children&amp;#39;s developmental processes are also moot in this discussion, be they abnormal or normal or whatnot. There are lots of studies showing a lot of things. You have to look at the whole body of the discipline and then inform yourself, not take the good and pointed studies relating to specific areas and discount the entire field.&#13;
&#13;
&lt;b&gt;Why did you even give her space?&lt;/b&gt; - 5/14/07&#13;
At some point, you just have to let go, lady. Get a grip. Stop projecting your woulda-coulda-shoulda parental replays to compensate for everything you didn&amp;#39;t do, just to make yourself feel better and ignore what really did happen, most of which probably wouldn&amp;#39;t have changed even with all the nannying you suggest.&#13;
&#13;
&lt;b&gt; The Real BadgerNation &lt;/b&gt; - 5/14/07&#13;
I agree...&#13;
and President Hannessy&amp;#39;s fake smile and politically correct image are a clear sign that he cares. Same way G.W.&amp;#39;s visits to Iraq and shaking of those people&amp;#39;s hands, taking pictures and putting up a big baboon smile show that he also cares... about sending America&amp;#39;s sons to die.&#13;
&#13;
&lt;b&gt; Why is this letter in the Daily? &lt;/b&gt;- 5/15/07&#13;
I agree with WDYEGHS - it&amp;#39;s not very helpful to expect that CAPS could be able to &amp;#39;follow-up&amp;#39; on GRADUATES (who aren&amp;#39;t eligible for their services any more, anyway...*ahem*), not to mention when they are 9 time zones away. Aside from the logistical (think personnel, funding, time and money spent tracking down Stanford students abroad) impossibility of this operation, how would that be funded? A third of Stanford undergrads go to CAPS at some time in their career here - keeping tabs on them to follow up is just not feasible with the way the service is set up at the moment.&#13;
Also, when would treatment end? If we were to promote a regime of following up on everybody after every psychological event had been resolved (something that closely resembles nannying...which health services can&amp;#39;t do to people once they are of age without their consent) then it risks wasting the time of professionals who are already over-stretched and underpaid.&#13;
Finally, CAPS psychologists are not permitted to practice in Germany because they are licensed in the state of California. This guy&amp;#39;s story is really tragic and it makes me really sad to have read this piece, but the answer, if there was one, would not have lay at Stanford no matter what obligations the mother wants to impose on the university.&#13;
&#13;
&lt;b&gt;A more sympathetic response...&lt;/b&gt; - 5/15/07&#13;
I think the three posts above me are not giving this well thought out article enough credit. I don&amp;#39;t think she&amp;#39;s advocating for a CAPS conselour to commute to Germany to make sure a graduate is doing ok, but some sort of follow up with the family or student to make sure they are getting some sort of help. Yes, a third of the student body may go to CAPS, but a much smaller fraction of the student body would require this follow up - - those who attempted suicide, were committed to the hospital against their will, etc.&#13;
&#13;
While this article does suggest that Stanford should have remained involved in Pat&amp;#39;s mental rehabilitation, I think the more important thing to take away is the author&amp;#39;s useful view into the life of a mentally depressed student, and hopefully raises awareness of what our peers are going through - peers who you see next to you at dinner, walk by in white plaza, sit next to in class. while pat did not take his life while at stanford, many others have, and that fact needs a lot more attention from ALL OF US at stanford.&#13;
&#13;
&lt;b&gt; Alyssa O&amp;#39;Brien, PWR Instructor&lt;/b&gt; - 5/16/07&#13;
As a Stanford instructor who knew Pat as a student years ago in PWR "Comic Rhetoric," I am deeply saddened to hear of his death. My heart goes out to Lisette and to all Pat&amp;#39;s friends and family members. I still remember his gentle smile and quick wit. I hope anyone reading this realizes that suicide is a lonely and terrible solution -- there are people who will grieve and miss you with a deep ache. May 17 is the first annual Stanford Wellness day. Make a pact on this day to reach out to others and not give in or give up.&#13;
&#13;
&lt;b&gt; Grateful&lt;/b&gt; - 5/17/07&#13;
Thank you for sharing your painful and most personal experience. Your letter points out the difference between sadness and depression. Don&amp;#39;t ever let go of your search for meaning and your determination to help others. Even if some miss the point (as evidenced by a few of the responses), to me and to others your words are precious. No man is an island. Thank you.&#13;
&#13;
&lt;b&gt; Lisette Rimer&lt;/b&gt; - 5/20/07&#13;
&#13;
Dear Mr. Hohmann,&#13;
&#13;
Thank you for being so generous with space in the Daily for Pat&amp;#39;s picture and story. You gave prominence to an issue which has apparently troubled Stanford both on and off campus and, judging by the responses to Pat&amp;#39;s story, drawn the full range of reaction. I found it interesting that I shared all views at different times in my life. Before Pat died, I agreed completely that schools cannot be traipsing all over the globe to protect students from themselves, that we could not make students live if they didn&amp;#39;t want to. As a matter of fact, it is probably that kind of thinking that put me in this situation today.&#13;
&#13;
Now that he&amp;#39;s gone, I can only say from experience that the nature of the disease demands more from us. There is no better proof than Pat that depression is a terminal disease and that it operates outside the realm of logic. How do we know when a student has crossed that line? We don&amp;#39;t, and so it stands to reason that we should take a conservative approach. As my doctor has told me many times since Pat&amp;#39;s death, depression is like cancer, only worse in the sense that it attacks the very decision-making ability that students need to seek help. If you can&amp;#39;t depend on the students, and the parents are three thousand miles away and getting the "I&amp;#39;m OK" side of the story, who is left? It is only the professionals who know that depression does not "heal" after the first "episode" Even on medication, it takes longer to recover with each setback. Severely depressed patients do not "learn" from past failures. They get worse. They become more vulnerable. They are chronically ill, and even if they sought hospitalization once, as Pat did, they may be less likely to do it again because they will think they are beyond hope. My therapist tells me we can assume one thing about suicide: the person is in so much pain that death is a mandate. It&amp;#39;s not like they went to a psychological shopping mall and unexplainably picked that choice. I have learned that it is a severe, agonizing, psychological torture, which constricts them internally but allows enough external composure to carry out their plan. Pick up any book on the subject and then think about it as I have done every day for fifteen months. If the school is sincere in improving its psychological services, follow-up after hospitalization is essential. Nobody else is equipped to do it, and the consequences may be fatal.&#13;
&#13;
I am not removing blame from myself or from Pat, and I appreciate those who wrote and understood that. My letter is not about finding fault. It is simply stating a fact: the school must be proactive. The psychiatric services are excellent on campus. As a friend once told Pat, "Stanford is one of the best places to have a breakdown." Extending those services is simply a matter of a phone call, in Pat&amp;#39;s case, to the Stanford Center in Berlin.&#13;
&#13;
Most importantly, thank you to "A more sympathetic response," "Alyssa O&amp;#39;Brien," and "Grateful." You knew Pat (Was it you, Mrs. O&amp;#39;Brien, who nominated him for a writing prize for his paper on Juvenal? He was touched that you liked it.), and you knew how depression works. It&amp;#39;s a thief, and it robs you blind. You cannot see your prospects unless professionals pry your eyes open. Thank you, Stanford, for the wonderful care you did give, and thank you again for continually working to improve those resources.&#13;
&#13;
Lisette Rimer, Pat&amp;#39;s mom&#13;
Pomfret Center, CT 06259&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://daily.stanford.edu/article/2007/5/14/opedAnOpenLetterToPresidentHennessy"&gt; Stanford Daily - May 14, 2007&lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9564">
                <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="11069">
                <text>Stanford Daily</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11555">
                <text>Permissions granted by&#13;
James Hohmann&#13;
Editor-in-Chief&#13;
The Stanford Daily&#13;
&lt;jhohmann@stanford.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13008">
                <text>Op-Ed: An open letter to President Hennessy</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="482">
        <name>mental illness</name>
      </tag>
      <tag tagId="591">
        <name>stanford</name>
      </tag>
      <tag tagId="603">
        <name>suicide</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="513" 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="1845">
                <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="3736">
                <text>John Hennessy</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="5714">
                <text>2007-06-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7592">
                <text>May 4, 2007&#13;
By JOHN HENNESSY&#13;
&#13;
On April 16, 2007, our country suffered a terrible tragedy when a troubled student killed 32 members of the Virginia Tech community.&#13;
&#13;
Such tragedies are unfathomable. Words, as eloquent and sincere as they may be, fail to convey the shock and sadness we all felt upon hearing that news.&#13;
&#13;
At Stanford, I was struck by the deep and sincere evidence of sympathy and concern throughout campus, from the moments of silence at many meetings to the cards signed in dining halls to the moving ceremony at Memorial Church. Today, Stanford&amp;#39;s condolences stand among those of more than 300 other colleges and universities on the Virginia Tech website. Ours is a caring community, and that fact was never so clear as it was on April 16 and the days immediately thereafter.&#13;
&#13;
Not surprisingly, I have been asked about emergency protocols here at Stanford. I want you to know that in the wake of the Virginia Tech tragedy, a group has been convened by Vice President Randy Livingston to review all of our emergency protocols, as well as our methods of communication. Stanford has had an emergency management program in place for many years. The emergency plan has evolved from one primarily focused on earthquake preparation and response and now includes an "all hazards" approach. We practice annually for all types of emergencies, including intentional acts. In addition, we have various methods available through which to communicate with the entire campus, but we are seeking to improve the speed and efficiency with which we can do so. Our emergency protocols are good, but the realities of today&amp;#39;s society demand that they be even better.&#13;
&#13;
As important as they are, emergency protocols are unfortunately after-event procedures, and therefore only part of a necessary dialogue. As has been made very clear in the days following the tragedy at Virgina Tech, the challenge of how society addresses mental health issues is serious and complicated. We pray that what happened at Virginia Tech was a horrible aberration that will not be repeated anywhere. We know in retrospect that more must be done to recognize the warning signs of mental distress, including its potential for violence. We know we must learn more about how and when to intervene appropriately.&#13;
&#13;
The deaths at Virginia Tech are a tragedy of national proportions, but college campuses are experiencing smaller, quieter, yet profoundly distressing tragedies every day â€” young people who have chosen to take their own lives. The Stanford community has been no exception in this regard. Since the beginning of the academic year, we have lost several Stanford students. As we think through the maze of mental health challenges, we must also confront the problem of suicide â€” openly, constructively and with determination.&#13;
&#13;
For many, the imponderability of suicide may make us feel powerless to know where to begin in addressing such a painfully personal issue. So perhaps the place to start is in the recognition that we all do indeed have a role to play. A university is a deeply intimate community â€” what touches one, truly touches all. That means that as a community we have a set of responsibilities to each other. We have the responsibility to understand, to comfort, to reach out and, in some cases, to act.&#13;
&#13;
Mental and emotional distress know no bounds of gender, background or color. I am hopeful for a day when the stigma associated with depression and other mental health problems â€” whether imposed by others or one&amp;#39;s self â€” dissipates and goes the way of other misplaced fears and biases. Helping each other overcome that stigma is an important first step.&#13;
&#13;
This stigma, which often results in a reluctance to seek help, implies an additional responsibility: We must share a commitment to be compassionate, to not turn away from seeing and acknowledging a difficult circumstance, and then take the opportunity to reach out to help â€” or even seek help ourselves.&#13;
&#13;
There are many resources available at Stanford, including Counseling and Psychological Services (CAPS) at Vaden Health Center, the Bridge Peer Counseling Center, the Office for Religious Life, the community centers and residence staff, among others. But these resources can only be brought to bear if they are engaged.&#13;
&#13;
Last fall, Provost John Etchemendy appointed a group to examine issues around the psychological well being of our students and assess the services we offer in this area. Other colleges and universities are taking similar measures in the face of an increasing demand for mental health and well being services. Some of you will be asked to participate in focus groups this spring or to take an online survey, and I hope you will choose to participate.&#13;
&#13;
It goes without saying that one suicide is too many, and we must look within ourselves to be certain that we are doing everything we can to prevent such tragedies. I have been gratified by the strength and compassion of students, faculty and staff in the last few weeks. I hope and believe we can build on that to create an even healthier, safer and more caring community.&#13;
&#13;
John Hennessy is the president of Stanford University.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://daily.stanford.edu/article/2007/5/4/opedHennessyReflectsOnTragedy"&gt; Stanford Daily - May 4, 2007 &lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9563">
                <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="11554">
                <text>Permissions granted by&#13;
James Hohmann&#13;
Editor-in-Chief&#13;
The Stanford Daily&#13;
&lt;jhohmann@stanford.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13007">
                <text>Op-Ed: Hennessy reflects on tragedy</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="611">
        <name>emergency protocols</name>
      </tag>
      <tag tagId="591">
        <name>stanford</name>
      </tag>
      <tag tagId="610">
        <name>university president comments</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1956" public="1" featured="0">
    <fileContainer>
      <file fileId="926">
        <src>https://www.april16.vtlibraries.net/files/original/opening ceremony_3de9f9f50f.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="15284">
                    <text>2008-03-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="16404">
                    <text>2008-03-27 17:36:02</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="2964">
                <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="4855">
                <text>tarish.rm</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="6833">
                <text>2008-03-27</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8711">
                <text>Teams line up at the opening ceremony before the balloons are released. &#13;
&#13;
Photo by Tarish Smith. &#13;
&#13;
--&#13;
&#13;
Original Source:&#13;
&lt;a href="http://www.flickr.com/photos/tarish/2344459376/"&gt;http://www.flickr.com/photos/tarish/2344459376/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10682">
                <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="12309">
                <text>"Tarish Smith" &lt;tarish@rocketmail.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14027">
                <text>Opening Ceremony</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="378">
        <name>balloons</name>
      </tag>
      <tag tagId="2065">
        <name>baseball game</name>
      </tag>
      <tag tagId="2094">
        <name>opening ceremony</name>
      </tag>
      <tag tagId="2064">
        <name>yankees</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1485" public="1" featured="0">
    <fileContainer>
      <file fileId="752">
        <src>https://www.april16.vtlibraries.net/files/original/1484015158_0f12cd8075_o_2bfecd5cb3.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="15116">
                    <text>2007-10-25</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16236">
                    <text>2007-10-25 23:05:59</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="2716">
                <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="4607">
                <text>Christopher Bowns</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6585">
                <text>2007-10-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8463">
                <text>Orange and maroon balloons released at a Hokies United drillfield memorial service on the morning of Monday, April 23, 2007.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href="http://www.flickr.com/photos/cipherswarm/1484015158/"&gt;http://www.flickr.com/photos/cipherswarm/1484015158/&lt;/a&gt;&#13;
&#13;
Licensed under &lt;a href="http://creativecommons.org/licenses/by-sa/2.0/deed.en-us"&gt;Creative Commons Attribution-Share Alike 2.0 Generic&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10434">
                <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="12150">
                <text>Creative Commons Attribution-Share Alike 2.0 Generic</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13784">
                <text>Orange and Maroon</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="376">
        <name>april 23</name>
      </tag>
      <tag tagId="378">
        <name>balloons</name>
      </tag>
      <tag tagId="377">
        <name>hokies united</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2322" public="1" featured="0">
    <fileContainer>
      <file fileId="1146">
        <src>https://www.april16.vtlibraries.net/files/original/100_0399_76fb431073.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="15498">
                    <text>2008-05-09</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16618">
                    <text>2008-05-09 14:34: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="3197">
                <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="5088">
                <text>Kacey Beddoes</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="7066">
                <text>2008-05-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8944">
                <text>One of the items on display at the Alumni Center Art Exhibit. On 4/16/08, as part of the Day of Remembrance observance, the Holtzman Alumni Center Museum displayed examples of art, crafts, quilts, and other memorabilia contributed since April 16, 2007. This is one of over 60,000 items that will eventually go to Special Collections at Newman Library.&#13;
&#13;
A letter accompanying this doll said:&#13;
&#13;
"Dear Sir,&#13;
My name is Linda Woodward and I have been making dolls for a while.  I heard about the tragedy that happen last week.  I am so deeply sorry about it.  So I would like to send you a VT doll that I made with tears and sadness.  There is a bow for every soul that died. Thirty three in all, all little bows.&#13;
&#13;
I am sorry again,&#13;
Linda Woodward"&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10915">
                <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="12518">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14259">
                <text>Orange and Maroon doll</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1651">
        <name>alumni center</name>
      </tag>
      <tag tagId="1989">
        <name>anniversary</name>
      </tag>
      <tag tagId="2233">
        <name>doll</name>
      </tag>
      <tag tagId="2226">
        <name>exhibit</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2312" public="1" featured="0">
    <fileContainer>
      <file fileId="1136">
        <src>https://www.april16.vtlibraries.net/files/original/100_0342_849f9ba5c3.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="15488">
                    <text>2008-05-09</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16608">
                    <text>2008-05-09 12:41:08</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3187">
                <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="5078">
                <text>Kacey Beddoes</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="7056">
                <text>2008-05-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8934">
                <text>One of the items on display at the Alumni Center Art Exhibit. On 4/16/08, as part of the Day of Remembrance observance, the Holtzman Alumni Center Museum displayed examples of art, crafts, quilts, and other memorabilia contributed since April 16, 2007. This is one of over 60,000 items that will eventually go to Special Collections at Newman Library.&#13;
&#13;
&#13;
A quilt accompanied by a letter that said:&#13;
&#13;
"My name is Jackie Wake.  When the shootings happened in April my heart fell to my gut.  This is what I do (make afgans) and the Lord laid in on my heart to do this for VT.  Please lay it out and stand back so you can read all the names.  We decided to take a trip to bring it down.  We hope you can find a use for it.&#13;
&#13;
Jackie Wake&#13;
106 Macomber Ave.&#13;
Auburn, MI 48611&#13;
989-662-7725"</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10905">
                <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="12508">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14249">
                <text>Orange and Maroon Quilt</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1651">
        <name>alumni center</name>
      </tag>
      <tag tagId="1989">
        <name>anniversary</name>
      </tag>
      <tag tagId="2226">
        <name>exhibit</name>
      </tag>
      <tag tagId="2124">
        <name>quilt</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2100" public="1" featured="0">
    <fileContainer>
      <file fileId="980">
        <src>https://www.april16.vtlibraries.net/files/original/100_0252_64993e1edf.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="15337">
                    <text>2008-04-10</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="16457">
                    <text>2008-04-10 11:18:23</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3022">
                <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="4913">
                <text>Kacey Beddoes</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="6891">
                <text>2008-04-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8769">
                <text>This hand crafted glass bowl was made by Gene Messick of Restoration Glass.  He sent it to President Steger to thank him for his leadership during the crisis.  </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10740">
                <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="12362">
                <text>Kacey Beddoes (kbeddoes@vt.edu)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14084">
                <text>Orange glass bowl</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="2150">
        <name>glass bowl</name>
      </tag>
      <tag tagId="2151">
        <name>messick</name>
      </tag>
      <tag tagId="2107">
        <name>perspective gallery</name>
      </tag>
      <tag tagId="117">
        <name>squires</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2253" public="1" featured="0">
    <fileContainer>
      <file fileId="1088">
        <src>https://www.april16.vtlibraries.net/files/original/2419985200_3cebca5562_b_d81114c5d2.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="15440">
                    <text>2008-05-02</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="16560">
                    <text>2008-05-02 16:00:10</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3139">
                <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="5030">
                <text>Brian Sewell</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7008">
                <text>2008-05-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8886">
                <text>Memorial stone of Juan Ramon Ortiz-Ortiz on 4/16/08.&#13;
&#13;
Photo by Brian Sewell.&#13;
&#13;
--&#13;
&#13;
Original Source:&#13;
&lt;a href="http://flickr.com/photos/briansewell/2419985200/in/set-72157604577382666/"&gt;http://flickr.com/photos/briansewell/2419985200/in/set-72157604577382666/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10857">
                <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="12461">
                <text>Brian Sewell &lt;bwsewell@vt.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14201">
                <text>Ortiz-Ortiz memorial</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1989">
        <name>anniversary</name>
      </tag>
      <tag tagId="32">
        <name>memorial</name>
      </tag>
      <tag tagId="2186">
        <name>ortiz-ortiz</name>
      </tag>
      <tag tagId="373">
        <name>stone</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1277" 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="2543">
                <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="4434">
                <text> Andy Boyle</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="6412">
                <text>2007-09-03</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8290">
                <text>By: Andy Boyle&#13;
Posted: 4/23/07&#13;
An unknown man called in a false bomb threat to Othmer Hall around noon Friday.&#13;
&#13;
The engineering building was closed for about two hours to students, faculty and staff members while authorities searched for explosives.&#13;
&#13;
Kelly Bartling, a spokeswoman for the University of Nebraska-Lincoln, said on Friday a man called Dean of Engineering David Allen&amp;#39;s office and told an assistant, "I planted a bomb in the building, you bitch."&#13;
&#13;
The secretary called University Police, who advised her to leave the building and pull the fire alarm.&#13;
&#13;
Garret Schram, a junior civil engineering major, was in the building "30 seconds after the call."&#13;
&#13;
People were crowded around a desk talking quietly, he said.&#13;
&#13;
Schram was in the office getting lunch tickets for an E-week event that college was hosting. E-week is an annual celebration put on by the engineering college.&#13;
&#13;
Schram then ran out of the building with everyone else.&#13;
&#13;
The college&amp;#39;s E-week included an open house meant for recruiting, displaying presentations, checking out labs and meeting with businesses that came for recruitment, said Joey Schaefer, a junior mechanical engineering major.&#13;
&#13;
At a press conference Friday, UNL Chancellor Harvey Perlman said the bomb threat wasn&amp;#39;t real and other campuses across the country have had similar threats over the week.&#13;
&#13;
"Unfortunately, these are to be expected when we had a major event like we had at Virginia Tech," he said.&#13;
&#13;
Othmer Hall contains the Biological Process Development Facility, which researches vaccines for biological warfare agents, according to the facility&amp;#39;s Web site, www.bpdf.unl.edu.&#13;
&#13;
John Ballard, the associate dean of the engineering college, said he didn&amp;#39;t know if there was a hazard involved because of the facility&amp;#39;s research in biological warfare.&#13;
&#13;
Othmer Hall was the first building evacuated, said University Police Chief Owen Yardley. Connecting buildings Nebraska Hall and the Walter Scott Engineering Center were evacuated about 20 minutes later.&#13;
&#13;
The last previous bomb threat called in to the university occurred in late September when a man approached a group of sorority members at the parking garage at 17th and R and claimed to have a bomb.&#13;
&#13;
Yardley couldn&amp;#39;t comment on how the search of Othmer was conducted.&#13;
&#13;
He also would not confirm that the caller was a man. Earlier, Bartling told the Daily Nebraskan the caller was a man.&#13;
&#13;
"We know it was a phone call that was received by somebody in the department," Yardley said.&#13;
&#13;
Police procedure is to attempt traces on the phone call and investigate who is involved, Yardley said. He said a bomb threat is be a felony charge.&#13;
&#13;
Perlman said if a student were involved, he would like them to be punished as seriously as the university allows.&#13;
&#13;
"I would hope that the campus community would take this seriously," he said, "and if anybody hears or sees anything that would help in this investigation, they would notify campus police or Crime Stoppers or provide us with information."&#13;
&#13;
University Police can be reached at 472-3555. The Crime Stoppers&amp;#39; phone number is 475-3600.&#13;
&#13;
-Daily Nebraskan senior reporter Johnny Perez contributed to this story&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailynebraskan.com/media/storage/paper857/news/2007/04/23/News/Othmer.Bomb.Threat.Perpetrator.Still.Unknown-2873794.shtml&gt; Daily Nebraskan - April 23, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10261">
                <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="11243">
                <text>Daily Nebraskan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12095">
                <text>Josh Swartzlander &lt;jdwriter19@yahoo.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13660">
                <text>Othmer bomb threat perpetrator still unknown</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1669">
        <name>university of nebraska </name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="888" 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="2197">
                <text>Elva Orozco</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4088">
                <text>Carlos Alberto Montaner</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="6066">
                <text>2007-08-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7944">
                <text>Por Carlos Alberto Montaner&#13;
1 de mayo de 2007&#13;
&#13;
Cuando Seung-Hui Cho fue a entrar pistola en mano en la clase de aeronÃ¡utica para asesinar a sus condiscÃ­pulos en Virginia Tech, el profesor Liviu Librescu, un anciano de 76 aÃ±os, menudo de cuerpo pero dotado de un carÃ¡cter firme, se lo impidiÃ³ durante unos minutos mientras sus estudiantes huÃ­an por las ventanas. Finalmente, el joven asesino hiriÃ³ de muerte a Librescu y siguiÃ³ su recorrido en busca de nuevas vÃ­ctimas. Librescu era el scholar con mÃ¡s publicaciones de toda la universidad. Un verdadero sabio en su campo de investigaciones.&#13;
&#13;
Esto sucediÃ³ el 16 de abril, precisamente en Yom Hashosha, el dÃ­a en que se conmemora el Holocausto que arrasÃ³ sin piedad con seis millones de judÃ­os europeos entre 1935, cuando Hitler promulgÃ³ &amp;#39;&amp;#39;las leyes de Nuremberg&amp;#39;&amp;#39;, con las que despojÃ³ de derechos a las personas de esta etnia o religiÃ³n, hasta 1945, cuando los aliados entraron en los campos de exterminio y, horrorizados, encontraron a un puÃ±ado de despojos humanos que habÃ­an logrado sobrevivir milagrosamente.&#13;
&#13;
Uno de esos sobrevivientes del Holocausto habÃ­a sido Librescu, entonces un adolescente en su RumanÃ­a natal, a quien el destino todavÃ­a le depararÃ­a otra experiencia monstruosa: el establecimiento de la dictadura comunista en RumanÃ­a, tambiÃ©n teÃ±ida por el antisemitismo, la irracionalidad y la barbarie. A fines de los setenta, afortunadamente, por una gestiÃ³n de Menajem Begin, consiguiÃ³ emigrar a Israel y, unos aÃ±os mÃ¡s tarde, desembarcÃ³ en Estados Unidos donde acaba de morir heroica e inesperadamente a manos de un muchacho enloquecido.&#13;
&#13;
Traigo a cuento la historia triste y gloriosa de Librescu porque llega en medio de un debate mundial: Â¿quÃ© hacer con los canallas que niegan la existencia del Holocausto? En CanadÃ¡ y en algunos paÃ­ses de Europa los parlamentos han aprobado leyes por las que sancionan a quienes niegan el exterminio masivo de judÃ­os, alegando que esa falsedad estimula el odio racial, mientras en Estados Unidos la Primera Enmienda les permite difundir sus envenenadas informaciones porque el Estado no puede legislar en materia de libertad de prensa.&#13;
&#13;
Creo que hay dos buenos argumentos para asumir la posiciÃ³n norteamericana. El primero, es que en una democracia libre les corresponde a los ciudadanos y no al gobierno decidir lo que quieren leer y creer. Si cuatro imbÃ©ciles racistas, pese a las toneladas de pruebas y testimonios, se dedican a negar la existencia del Holocausto o de la esclavitud de los negros, hay que confiar en el sentido comÃºn de la sociedad y no en el de los censores oficiales, gente que acaba por ser muy daÃ±ina.&#13;
&#13;
Por otra parte, vivir en libertad exige aprender a tolerar la existencia de creencias y actitudes repugnantes. Las dictaduras comunistas, por ejemplo, le costaron a la humanidad cien millones de muertos a lo largo del siglo XX, pero en todas las sociedades libres hay tipos que todavÃ­a veneran a Lenin, Stalin, Mao o Fidel Castro, y no queda mÃ¡s remedio que coincidir con ellos pacÃ­ficamente en el ascensor o en la cafeterÃ­a.&#13;
&#13;
Pero tal vez existe un argumento tÃ¡ctico para oponerse a las leyes contra la negaciÃ³n del Holocausto. Cada vez que uno de estos racistas abre la boca para mentir y difundir falsedades crea una oportunidad perfecta para recordarle al mundo que el antisemitismo estÃ¡ vivo y coleando y que no desapareciÃ³ en la CancillerÃ­a junto a los huesos quemados de Hitler. Todos los sÃ­ntomas seÃ±alan que hay un peligroso repunte del odio a Israel y a los judÃ­os en diversas partes del mundo. Todo lo que se haga por denunciarlo y detenerlo es una forma de preservar la paz en el mundo.&#13;
&#13;
--&#13;
Fuente Original: El Instituto Independiente&#13;
&lt;a href="http://independent.typepad.com/elindependent/2007/05/otra_vez_el_hol.html"&gt;http://independent.typepad.com/elindependent/2007/05/otra_vez_el_hol.html&lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9915">
                <text>spa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11842">
                <text>Gabriel Gasave&#13;
Reasearch Analyst&#13;
Center On Global Prosperity&#13;
The Independent Institute&#13;
ggasave@independent.org&#13;
August 01, 2007</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13332">
                <text>Otra vez el holocausto</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1001">
        <name>hitler</name>
      </tag>
      <tag tagId="1000">
        <name>holocausto</name>
      </tag>
      <tag tagId="435">
        <name>librescu</name>
      </tag>
      <tag tagId="1003">
        <name>odio racial</name>
      </tag>
      <tag tagId="1002">
        <name>rumana</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1698" 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="2839">
                <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="4730">
                <text>Editorial Staff</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6708">
                <text>2008-02-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8586">
                <text>ssue Date:Tuesday April 17, 2007   &#13;
Section: Editorial Section&#13;
&#13;
By Monday afternoon, the nation was shocked by the tragedy that occurred at Virginia Tech.&#13;
&#13;
At least 32 people were killed and more than 20 were left wounded in the nation&amp;#39;s most violent school shooting ever.&#13;
&#13;
Though the campus of West Virginia University did not directly experience the tragedy, Mountaineer students found themselves anxious and alarmed as the news spread across the country. Some were distracted from their studies, while others waited with bated breath to hear word from their Hokie friends.&#13;
&#13;
Every student on every college campus is affected when an event like this occurs.&#13;
&#13;
As Virginia Tech mourns the loss of its students in the coming days, and some continue to mourn for many years to come, the staff of The Daily Athenaeum sends out our thoughts and sympathy to those who lost loved ones in Monday&amp;#39;s shooting.&#13;
&#13;
When an event like this occurs, no matter what college campus you call home, you are taken out of your comfort zone. It&amp;#39;s hard to fathom what Virginia Tech students, staff, faculty and families are going through.&#13;
&#13;
As a peer institution and ultimately a friend of Virginia Tech, we hope that they will be able to mend after such a horrifying occurrence.&#13;
&#13;
As the end of the semester draws near, it is hard enough to deal with the stress of classes, projects and final exams. Now, Virginia Tech students will be faced with even bigger obstacles.&#13;
&#13;
While we go through the next few weeks, take the time to remember those who were lost in this unspeakable tragedy. Enjoy every day, and take time to tell your friends and family that you care about them.&#13;
&#13;
It&amp;#39;s unfortunate, but sometimes we are so wrapped up with our daily lives that it takes an event like this to bring us back to reality and remind us to be thankful.&#13;
&#13;
Again, our hearts and thoughts go out to those affected by the shooting. We will continue to think about you as we undergo the mourning process alongside college students across the nation.&#13;
&#13;
--&#13;
&#13;
Original Source: The Daily Athenaeum&#13;
&lt;a href="http://www.da.wvu.edu/show_article.php?&amp;story_id=27549"&gt;http://www.da.wvu.edu/show_article.php?&amp;story_id=27549&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10557">
                <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="12197">
                <text>Leann Ray &lt;Leann.Ray@mail.wvu.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13903">
                <text>Our hearts go out to those at VT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="747">
        <name>student reactions</name>
      </tag>
      <tag tagId="157">
        <name>sympathy</name>
      </tag>
      <tag tagId="1952">
        <name>wvu</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="688" 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="2012">
                <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="3903">
                <text>Editorial Staff</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5881">
                <text>2007-07-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7759">
                <text>&lt;strong&gt;Emory&amp;#39;s Campus No Place For Guns&lt;/strong&gt;&lt;br /&gt;&#13;
Issue date: 5/1/07&lt;br /&gt;&#13;
Section: Editorials&#13;
&#13;
The recent controversy concerning funding for a College Republicans&amp;#39; trip to a shooting range has brought the issues of gun control and campus safety to the forefront of the Emory discourse.&#13;
&#13;
Last Wednesday, College Council denied the College Republicans funding to help pay for a trip to a local shooting range. The College Republicans said they hoped the trip would promote safe and responsible gun handling and ownership. College Council legislators say they withheld the funds due to safety concerns, even going so far as to propose an amendment to the organization&amp;#39;s monetary code prohibiting the use of College Council funds to purchase or rent firearms and ammunition.&#13;
&#13;
Generally speaking, we believe College Council should be able to fund activities like a trip to the shooting range. Shooting is a sport recognized by the NCAA, and shooting range sessions monitored by professionals are exceedingly safe. Amending the monetary code to prevent such trips is unwarranted.&#13;
&#13;
It&amp;#39;s unfortunate that the shootings at Virginia Tech took place just weeks before the scheduled date for the trip, but given that the College Republicans had been planning this event for quite some time, we don&amp;#39;t believe the shootings are an adequate reason for the trip to be cancelled. Although some could perceive the trip as insensitive, there is still an immense difference between safely firing a gun at a target and using a gun to commit mass murder. If the College Republicans want to take a trip to the shooting range, then they should receive the same support given to any other group.&#13;
&#13;
What we cannot condone is the College Republicans&amp;#39; plan to request permission from University President James W. Wagner to carry concealed weapons on campus. This idea was proposed by nationally syndicated radio host Lars Larson on whose show Tittsworth appeared to discuss the Council&amp;#39;s decision to deny funding.&#13;
&#13;
Under current Georgia law, it is illegal for a civilian to carry any sort of weapon or explosive compound while on school property. There&amp;#39;s a reason such a law was passed. We understand the need for protection and the value of feeling safe at school, but we do not believe that allowing more guns on campus will help foster the open learning environment we want at the University.&#13;
&#13;
Allowing guns on campus would propagate an atmosphere tinged with the spectre of possible violence. This would make us less safe, rather than moreso. The only people who should be allowed guns on campus are those who have gone through rigorous training to become certified in their use and have taken an oath to protect the citizenry - in this case, the Emory Police Department.&#13;
&#13;
The College Republicans should realize that by tying the issue of funding from College Council to the ludicrous question of concealed weapons on campus, they are only hurting their prospects of getting that money in the future. Who would want to give money for a shooting range trip to a group that has expressed its desire to carry concealed weapons on campus?&#13;
&#13;
As the Second Amendment states, there is a place for guns in our society. The shooting range is one of those places - Emory&amp;#39;s campus is not.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href= http://media.www.emorywheel.com/media/storage/paper919/news/2007/05/01/Editorials/Our-Opinion.Gun.Control-2889391.shtml&gt; Emory Wheel - May 1, 2007&lt;/a&gt;&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9730">
                <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="11712">
                <text>"Christopher H. Megerian" &lt;cmegeri@LearnLink.Emory.Edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13157">
                <text>Our Opinion: Gun Control</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="813">
        <name>emory</name>
      </tag>
      <tag tagId="87">
        <name>gun control</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1287" 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="2553">
                <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="4444">
                <text>Anonymous</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="6422">
                <text>2007-09-03</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8300">
                <text>&#13;
We cannot begin to imagine what the community is going through, but we do know they stood strong in the face of terrible acts of violence.&#13;
&#13;
We would like to specifically recognize the Collegiate Times, the student newspaper at Virginia Tech, for its excellent news coverage as the rest of the University faced crisis.&#13;
&#13;
While the entire school was in a state of shock, the newspaper&amp;#39;s staff managed to provide up-to-date information on the paper&amp;#39;s Web site, and we want the paper to know their efforts did not go unnoticed.&#13;
&#13;
As student journalists, we can understand the horror of working through the greatest school tragedy in history.&#13;
&#13;
Many members of The Plainsman staff referenced that site throughout the day to get the latest information, and we are proud of these strong students.&#13;
&#13;
As the details of the tragedy continue to be released, we have confidence the newspaper will continue its excellence in reporting.&#13;
&#13;
While we watched in shock as the tragedy unfolded, we began to wonder what we would do if something like this happened at Auburn.&#13;
&#13;
We discussed the safety measures at Auburn, and we began to realize that is is almost impossible to prepare for an emergency situation of this magnitude.&#13;
&#13;
It is the kind of situation that takes one by surprise in the worst way imaginable, and we feel no amount of preparation could have completely prevented the events at Virginia Tech Monday.&#13;
&#13;
We commend everyone involved in the tragedy for the efforts they put forth to help the Virginia Tech community.&#13;
&#13;
Again, we offer our deepest sympathies to everyone affected by the events on Virginia Tech&amp;#39;s campus, and you will remain in our thoughts.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.theplainsman.com/node/2418&gt; Auburn Plainsman - April 18, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10271">
                <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="11252">
                <text>Auburn Plainsman</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12105">
                <text>David Ingram &lt;ingradc@auburn.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13670">
                <text>Our View: Tragedy strikes Virginia Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="328">
        <name>auburn university</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="152" 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="1520">
                <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="3411">
                <text>Zach Sims</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="5389">
                <text>2007-05-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7269">
                <text>The shooting at Virginia Tech is undeniably one of the worst tragedies American students have ever faced.  Stories of heroism make their way out of the situation, but the media is focused on the death and destruction caused on the campus of Virginia Tech University.  One thing, however, should give Virginia Tech students, and Americans throughout the country, something to be proud of.  In the absence of professional newsmen, students took control of the media, showing an unprecedented ability to shape the coverage regarding their event.&#13;
&#13;
In the wake of the worst campus massacre ever in the United States, dozens of news organizations flocked to Virginia to cover the tragedy.  Before they arrived, however, the mainstream media relied on reports from those already on the ground: the college students themselves.  Armed with the video and still cameras on their mobile phones, dozens of students set out to create their own coverage of an incident that was very much their own.  The first audio and video accounts of the incident aired by CNN came from &lt;a onclick="javascript:urchinTracker (&amp;#39;/outgoing/www.cnn.com/exchange/&amp;#39;);"  href="http://www.cnn.com/exchange/" title="iReport"&gt;iReport&lt;/a&gt;, their citizen journalism program.  The video, shot on a Nokia smartphone, made its way around the networks, all courtsey of a Virginia Tech student named &lt;a onclick="javascript:urchinTracker (&amp;#39;/outgoing/www.cnn.com/2007/US/04/16/vtech.witness/index.html?eref=rss_topstories&amp;#39;);"  href="http://www.cnn.com/2007/US/04/16/vtech.witness/index.html?eref=rss_topstories" title="Jamal Albarghouti"&gt;Jamal Albarghouti&lt;/a&gt;.&lt;/p&gt;&#13;
&lt;p&gt;Dozens of similar stories are to be told.  In the hours preceding the arrival of professional reporters, Virginia Tech students had, unfortunately, the opportunity to shape the world&amp;#8217;s news.  Their coverage helped to show the world how terrible the massacre was and helped to qualm some fears about students that were safe.  &lt;a onclick="javascript:urchinTracker (&amp;#39;/outgoing/www.twitter.com&amp;#39;);"  href="http://www.twitter.com"&gt;Twitter&lt;/a&gt;, a &amp;#8220;stream of consciousness&amp;#8221; blogging tool by &lt;a onclick="javascript:urchinTracker (&amp;#39;/outgoing/obvious.com/&amp;#39;);"  href="http://obvious.com/"&gt;Obvious Corp&lt;/a&gt; (utilized mostly by web celebrities such as &lt;a onclick="javascript:urchinTracker (&amp;#39;/outgoing/www.twitter.com/scobleizer&amp;#39;);"  href="http://www.twitter.com/scobleizer"&gt;Robert Scoble&lt;/a&gt; and &lt;a onclick="javascript:urchinTracker (&amp;#39;/outgoing/www.twitter.com/thomashawk&amp;#39;);"  href="http://www.twitter.com/thomashawk"&gt;Thomas Hawk&lt;/a&gt;), served constant updates to the internet, courtesy of a user named &lt;a onclick="javascript:urchinTracker (&amp;#39;/outgoing/twitter.com/tmarkiewicz&amp;#39;);"  href="http://twitter.com/tmarkiewicz"&gt;Tom Markiewicz&lt;/a&gt;.  &lt;a onclick="javascript:urchinTracker (&amp;#39;/outgoing/www.twitter.com/chrispirillo&amp;#39;);"  href="http://www.twitter.com/chrispirillo" title="Chris Pirillo"&gt;Chris Pirillo&lt;/a&gt;, a web celebrity in his own right, helped to stream live coverage with a tool called &lt;a onclick="javascript:urchinTracker (&amp;#39;/outgoing/www.ustream.tv&amp;#39;);"  href="http://www.ustream.tv"&gt;UStream.tv&lt;/a&gt;.   His &lt;a onclick="javascript:urchinTracker (&amp;#39;/outgoing/ustream.tv/chrispirillo/videos/bhi33KQS7tCNS,Bbhi,w1w&amp;#39;);"  href="http://ustream.tv/chrispirillo/videos/bhi33KQS7tCNS,Bbhi,w1w"&gt;conversation with Planet Blacksburg,&lt;/a&gt; a new student-run publication from Virginia Tech, captured nationwide attention as sections were &lt;a onclick="javascript:urchinTracker (&amp;#39;/outgoing/www.youtube.com/watch?v=s8_X5PaDRhE&amp;#39;);"  href="http://www.youtube.com/watch?v=s8_X5PaDRhE"&gt;aired on various evening news programs&lt;/a&gt;.&#13;
&#13;
What most surprised me, however, was the caliber and tenacity of the coverage coming from the students themselves at Virginia Tech.  Via the aforementioned &lt;a onclick="javascript:urchinTracker (&amp;#39;/outgoing/www.planetblacksburg.com/&amp;#39;);"  href="http://www.planetblacksburg.com/"&gt;Planet Blackburg&lt;/a&gt;, they helped to broadcast news of the tragedy throughout the world, becoming the go-to site for immediate updates.  The Web2.0 movement, which many experts see as a bubble ready to burst, finally showcased its effectiveness yesterday. YouTube has showed its staying power by drawing users in to watch videos on their website.  The entire citizen journalism movement, however, displayed its prominence yesterday with the Virginia Tech shooting.  Never, in years past, would internet surfers be granted the same hard-hitting coverage as Planet Blacksburg provided yesterday.&#13;
&#13;
In this day and age, everyone is a reporter.  Yesterday, as CNN broadcast video from a student&amp;#8217;s cellphone video, and as Planet Blacksburg updated faster than the almighty network news, it became apparent.  The &amp;#8220;new media&amp;#8221; is here to stay, and, from the looks of it, it&amp;#8217;s ready to provide better coverage than had ever been imagined.  The shooting at Virginia Tech has caused incredible sadness and grief.  It has, however, caused something else: the birth of a new generation of reporters.&#13;
&#13;
&lt;em&gt;News of the incident continues to stun the staff here at New School Politics.  In the coming days, we&amp;#8217;ll be doing everything we can to help, but for the moment, the best we can do is to give our condolences to those involved in the tragedy at Virginia Tech.  On April 30th, we&amp;#8217;ll be participating in &lt;a onclick="javascript:urchinTracker (&amp;#39;/outgoing/www.onedayblogsilence.com&amp;#39;);"  href="http://www.onedayblogsilence.com" title="One Day Blog Silence"&gt;One Day Blog Silence&lt;/a&gt;, a day of quiet on the blogosphere dedicated to the memory of those who lost their lives in this terrible tragedy.&lt;/em&gt;&#13;
&#13;
Date : 19 April 2007&#13;
Categories : Liberal Content, media, culture, education, tragedy, web2.0, Virginia Tech&#13;
&#13;
--&#13;
&#13;
Originally posted by Zach Sims on the New School Politics blog:&#13;
&lt;a href="http://www.newschoolpolitics.com/liberal-content/out-of-darkness-comes-light/"&gt;http://www.newschoolpolitics.com/liberal-content/out-of-darkness-comes-light/&lt;/a&gt;&#13;
&#13;
Licensed under a &lt;a href="http://creativecommons.org/licenses/by-nc-nd/3.0/us/"&gt;Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9238">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12725">
                <text>Out of Darkness Comes Light</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="242">
        <name>commentary blog</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1236" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  Note that facsimiles or images of texts are still of the genre text.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2518">
                <text>Brent Jesiek</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4409">
                <text>Larry Hincker</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6387">
                <text>2007-08-26</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8265">
                <text>&lt;p&gt;By &lt;a href="mailto:hincker@vt.edu"&gt;Larry Hincker&lt;/a&gt;&#13;
&#13;
BLACKSBURG, Va., August 22, 2007 -- On May 9, 2007, Virginia Tech President Charles Steger directed three internal reviews in the wake of the April 16 tragedy on the Virginia Tech campus. He directed the chairs "to look at strengths and weaknesses of our existing systems/infrastructure and how they may be improved or augmented to address emergency situations that might arise in the future."&#13;
&#13;
These reviews are internal in structure and focus and not intended to be forensic in nature. Says Steger, "I asked for the creation of two different, but concurrent review processes. The external review commissioned by Governor Kaine is essentially investigatory in nature, while ours is a forward looking review of university policy, resources, and infrastructure through the prism of April 16."&#13;
&#13;
&lt;b&gt;The Security Infrastructure Group&lt;/b&gt; was charged with examining the university&amp;#39;s existing security systems and recommending changes that would enhance the university&amp;#39;s ability to respond quickly and effectively in situations where the safety of the campus community is jeopardized. This group was also directed to identify strategies that might decrease the probability of such situations occurring, looking at both technological and behavioral aspects.&#13;
&#13;
&lt;b&gt;The Information and Communications Infrastructure Group&lt;/b&gt; analyzed and inventoried the communication infrastructure and information systems used during the crisis period, evaluated their performance, and identifies tactics and strategies for improvements.&#13;
&#13;
&lt;b&gt;The Interface Group&lt;/b&gt; evaluated the relationships between the university&amp;#39;s student counseling services, academic affairs, judicial affairs, and the legal system. It was charged with examining the existing systems and the interface between them and determining what constraints, legal or otherwise, hamper effective interactions in order to respond to and support at-risk students.&#13;
&#13;
&lt;b&gt;Security Infrastructure Group&lt;/b&gt;&#13;
&#13;
Among its findings the security infrastructure group found good cooperation and sound agreements between Virginia Tech and local police, fire, and EMS jurisdictions including ongoing training exercises; sound emergency communications; robust communications infrastructure; a sound emergency preparedness plan; engagement of the leadership in campus emergencies; and a nationally accredited campus police department.&#13;
&#13;
The security group recommends enhancements in physical infrastructure, emergency communications, emergency preparedness, and selected protocols.&#13;
&#13;
Infrastructure recommendations include modification of building door hardware, installation of locks on general assignment classrooms, evaluating the utility of centrally controlled electronic key card access to key academic and administrative facilities (such as the system currently in place on all residence halls), constructing a public safety building combining the university police and rescue squad, and evaluating installation of centrally monitored video surveillance cameras.&#13;
&#13;
Communications recommendations include mass notification techniques within classrooms and other locations, message board in key or high profile public areas and along major vehicular thoroughfares, a people locator system, and further articulation of the recently adopted VT Alerts notification system.&#13;
&#13;
Emergency preparedness recommendations include updating the emergency preparedness plan, more frequent emergency exercises or drills, creation of building coordinators for emergencies, and identification of backups for the policy committee (university leadership with oversight of an emergency).&#13;
&#13;
Protocols include increased education of the university community about appropriate emergency response actions and creation of a comprehensive security master plan and campus security committee.&#13;
&#13;
&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_security_infrastructure.pdf"&gt;Read the full Security Infrastructure Group report&lt;/a&gt; (PDF) â€ºâ€º&#13;
&#13;
&lt;b&gt;Information and Communications Infrastructure Group&lt;/b&gt;&#13;
&#13;
Broadly defined, telecommunications comprises the university&amp;#39;s data network, telephone systems (university and/or vendor owned), cable TV, educational systems, and centralized information services. They were dramatically stressed but performed adequately during the crisis. The university on-campus phone system was not degraded but was affected by external problems. External cellular telephone systems and the Public Switched Telephone Network (hardwire telephone systems off campus) experienced huge demand increases and experienced some blocking of calls during the initial periods of the crisis on April 16.&#13;
&#13;
Other university systems experienced some loading, which were quickly identified and rectified, and performed well with no significant problems. For example, the university website www.vt.edu saw a 3,000 percent increase in traffic on April 16, Virginia Tech Police dispatch experienced 450 percent increase, and the university switchboard experienced a 300 percent increase in calls.&#13;
&#13;
Emergency Responder Radio Communication continues to suffer nationally and locally from "interoperability" issues because they use a variety of radio systems and frequencies. Radio systems typically do not support mobile data, encryption, GIS, or other advanced capabilities. Indicative of relatively common signal penetration problems in large buildings, emergency responders reported that radios did not work in some areas of Norris Hall.&#13;
&#13;
This group provides a series of strategic and tactical recommendations. The full report details more than 120 tactical recommendations. Two major strategies emerge:&#13;
&#13;
1) &lt;i&gt;Installation of a new fully integrated digital campus architecture for all telecommunications functions based on Internet Protocol (IP).&lt;/i&gt; The new system, based on a diverse optical core and including wireless and wired access, would fully integrate all telecommunications functions including voice, video, data, entertainment, and educational systems. This system could remediate every problem and enable every innovation identified by the study committee.&#13;
&#13;
2) &lt;i&gt;Make selected research and administrative IT capabilities available to local first responders to improve radio communications capabilities.&lt;/i&gt; In addition to improving interoperability problems, the new systems would be integrated with IP based information architecture allowing new applications such as GIS, identity management, sensor networks, location awareness, high-speed links to criminal information databases.&#13;
&#13;
&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_communications_infrastructure.pdf"&gt;Read the full Information and Communications Infrastructure Group report&lt;/a&gt; (PDF) â€ºâ€º&#13;
&#13;
&lt;b&gt;Interface Group&lt;/b&gt;&#13;
&#13;
The Interface Group looked at policies, procedures, capabilities and interdepartmental relationships and communications for the selected areas related to identifying and supporting at-risk students. By its nature the system was found to be logically connected and responsive. The Division of Student Affairs is at the core and supported by and interacting with law enforcement, the academic enterprise, and other university resources offices.&#13;
&#13;
Consistent with the national findings of the federal report commissioned by President Bush, the Interface Group found some confusion about applicability and interpretation of privacy laws among some offices or faculty. To some extent, this created internal silos and feedback problems preventing some offices from having salient information on students at risk. The "system may not be robust enough to provide the kind of analysis that is warranted by more complex, high risk cases... with need for significant mental health services."&#13;
&#13;
The committee makes a series of recommendations under three broad themes:&#13;
&#13;
&lt;b&gt;1. Expanding Capacity in the System&lt;/b&gt;&lt;/p&gt;&#13;
&lt;p&gt;&lt;ul&gt;&lt;li&gt;Refining and expanding the Care Team, a key SA group that identifies and responds to students at risk (among other responsibilities), including addition of VTPD to standing membership and connecting academic personnel to deliberations where appropriate.&lt;/li&gt;&#13;
&lt;li&gt;Creating a Threat Assessment Team charged with examining the most complex cases of distressed students and empowering it to act quickly, when necessary.&lt;/li&gt;&#13;
&lt;li&gt;Expanding Case Management Capacity by adding case managers to the Dean of Students office and Cook Counseling Center to improve follow-up with students and to improve information flow through appropriate units about students at risk.&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;2. Improving Communications in the System&lt;/b&gt;&lt;/p&gt;&#13;
&lt;p&gt;&lt;ul&gt;&lt;li&gt;Improve Communications in the Systems with particular emphasis on privacy law education throughout the university, clarifying policies for communications with external agencies, establishing a central university contact with a clear picture of distressed students.&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p id ="nq"&gt;&lt;b&gt;3. Connecting Strategies for Identifying and Supporting at Risk Students to the Broader University Plan for Campus Safety&lt;/b&gt;&lt;/p&gt;&#13;
&lt;p&gt;&lt;ul&gt;&lt;li&gt;Expanding Training of Administrators, Faculty, and Staff in Violence Prevention recognizing the campus safety is the province of all university employees to some extent.&lt;/li&gt;&#13;
&lt;li&gt;Extending the University-wide Violence Prevention Policy to integrate the numerous university-wide efforts to enhance campus safety.&lt;/li&gt;&#13;
&lt;li&gt;Building Community to Promote Individual and Community Well Being Virginia Tech has a strong, supportive, and vibrant community which is essential in creating a safe campus environment with very good policies and support systems. However, it is recommended that a more systematic approach be instituted with campus well-being as a goal.&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_internal_communications.pdf"&gt;Read the full Interface Group report&lt;/a&gt; (PDF) â€ºâ€º&lt;/p&gt;&#13;
&lt;p&gt;&lt;hr size="1" width="50%" align="left" /&gt;&lt;/p&gt;&#13;
&lt;p&gt;&lt;b&gt;Read and/or listen to formal statements regarding the reports:&lt;/b&gt;&lt;/p&gt;&lt;p&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_steger.doc" target="new"&gt;Charles W. Steger, president&lt;/a&gt; (MS Word) | &lt;em&gt;&lt;a href="http://www.podcasts.vt.edu/internal-steger.mp3"&gt;Listen&lt;/a&gt;&lt;/em&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_hyatt.doc" target="new"&gt;James A. Hyatt, executive vice president and chief operating officer&lt;/a&gt; (MS Word) | &lt;em&gt;&lt;a href="http://www.podcasts.vt.edu/internal-hyatt.mp3"&gt;Listen&lt;/a&gt;&lt;/em&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_blythe.doc" target="new"&gt;Earving L. Blythe, vice president for information technology&lt;/a&gt; (MS Word) | &lt;em&gt;&lt;a href="http://www.podcasts.vt.edu/internal-blythe.mp3"&gt;Listen&lt;/a&gt;&lt;/em&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.vtnews.vt.edu/documents/2007-08-22_niles.doc" target="new"&gt;Jerry Niles, retired dean, College of Liberal Arts &amp; Human Sciences&lt;/a&gt; (MS Word) | &lt;em&gt;&lt;a href="http://www.podcasts.vt.edu/internal-niles.mp3"&gt;Listen&lt;/a&gt;&lt;/em&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;Contact  Larry Hincker at &lt;a href="mailto:hincker@vt.edu"&gt;hincker@vt.edu&lt;/a&gt; or (540) 231-5396.&#13;
&#13;
##07433##&#13;
&#13;
--&#13;
&#13;
Original Source: Virginia Tech News&lt;br /&gt;&#13;
&lt;a href="http://www.vtnews.vt.edu/story.php?relyear=2007&amp;itemno=459"&gt;http://www.vtnews.vt.edu/story.php?relyear=2007&amp;itemno=459&lt;/a&gt;&lt;/p&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10236">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13636">
                <text>Overview of the findings and recommendations of the April 16 tragedy internal review committees</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1636">
        <name>findings</name>
      </tag>
      <tag tagId="1639">
        <name>information and communications infrastructure</name>
      </tag>
      <tag tagId="1638">
        <name>internal review committees</name>
      </tag>
      <tag tagId="1637">
        <name>recommendations</name>
      </tag>
      <tag tagId="1641">
        <name>reports</name>
      </tag>
      <tag tagId="1640">
        <name>security intrastructure</name>
      </tag>
      <tag tagId="1642">
        <name>statements</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="532" public="1" featured="0">
    <fileContainer>
      <file fileId="334">
        <src>https://www.april16.vtlibraries.net/files/original/pidradio070422_57b3bfc294.mp3</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="14727">
                    <text>2007-06-16</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="15847">
                    <text>2007-06-16 14:21:56</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="5">
      <name>Sound</name>
      <description>A resource whose content is primarily intended to be rendered as audio.</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="1861">
                <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="3752">
                <text>P.I.D. Radio</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="5730">
                <text>2007-06-16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7608">
                <text>16 kpbs MP3 6.9 MB&#13;
&#13;
April 22, 2007&#13;
&#13;
What more can be said about the shootings that left 33 dead at Virginia Tech last Monday? About 42 minutes&amp;#39; worth, apparently. We ask questions about a few details that bother us about the tragedy, which include a federal "stand down" order to local police and EMTs, the jamming of local cell phone service, and differing descriptions of the shooter.&#13;
&#13;
We also talk about Wednesday&amp;#39;s shooting on the streets of Columbia, less than a mile from the bunker. What all will come of this?&#13;
&#13;
Well, we expect to hear calls for tighter restrictions on handguns and mandatory mental health screening for elementary school students. Sounds good, but it ultimately means more government control over our lives and our children.&#13;
&#13;
Links:&#13;
&#13;
â€¢ &lt;a href="http://peeringintodarkness.com/ctd/?p=4920"&gt;Sources:  Feds ordered VA police to stand down&lt;/a&gt;&#13;
â€¢ &lt;a href="http://www.homelandsecurityus.com/WarlockBlue"&gt;Cell phones intentionally jammed at Virginia Tech by authorities&lt;/a&gt;&#13;
â€¢ &lt;a href="http://peeringintodarkness.com/ctd/?p=4908"&gt;Virginia Tech shooter was autistic:  Relative&lt;/a&gt;&#13;
â€¢ &lt;a href="http://www.cnn.com/CNN/Programs/anderson.cooper.360/blog/2007/04/plot-hatched-behind-cinder-block-walls.html"&gt;Karan Grewal tells CNN&amp;#39;s John King he and others were handcuffed&lt;/a&gt;&#13;
â€¢ &lt;a href="http://derekpgilbert.com/?p=2373"&gt;Differing descriptions of VT shooter&lt;/a&gt;&#13;
â€¢ &lt;a href="http://www.peeringintodarkness.com/forum/index.php?topic=4680.0"&gt;PID Forum:  Cho&amp;#39;s Sister an Intel Asset?&lt;/a&gt;&#13;
â€¢ &lt;a href="http://peeringintodarkness.com/ctd/?p=4825"&gt;Is this a picture of &amp;#39;Ismail-AX&amp;#39; (a.k.a. Cho Seung-Hui)?&lt;/a&gt;&#13;
&lt;i&gt;The original blog post and the photo at Flickr have since been deleted.  As far as we know,&lt;/i&gt; Connecting the Dots&lt;i&gt; is now the only place you&amp;#39;ll see this picture.&lt;/i&gt;&#13;
â€¢ &lt;a href="http://www.columbiatribune.com/2007/Apr/20070420News003.asp"&gt;Columbia shooting suspect had just left jail&lt;/a&gt;&#13;
â€¢ &lt;a href="http://peeringintodarkness.com/ctd/?p=4910"&gt;Gunman at NASA&lt;/a&gt;&#13;
â€¢ &lt;a href="http://peeringintodarkness.com/ctd/?p=4913"&gt;April:  The Cruelest Month?&lt;/a&gt;&#13;
â€¢ &lt;a href="http://peeringintodarkness.com/ctd/?p=4895"&gt;Gates says Washington to sell smart bombs to Saudi Arabia&lt;/a&gt;&#13;
â€¢ &lt;a href="http://www.military.com/NewsContent/0,13319,132397,00.html?ESRC=topstories.RSS"&gt;Air Force fills Army ranks&lt;/a&gt;&#13;
â€¢ &lt;a href="http://peeringintodarkness.com/ctd/?p=4871"&gt;Russia plans world&amp;#39;s longest tunnel to link to Alaska&lt;/a&gt;&#13;
â€¢ &lt;a href="http://www.escambray.cu/Eng/Special/Posada%20Carriles-Bush/Cprosecution070416839.htm"&gt;Cuba:  Posada prosecution in US or extradition to Venezuela&lt;/a&gt;&#13;
â€¢ &lt;a href="http://peeringintodarkness.com/ctd/?p=4924"&gt;Fallen Angel&lt;/a&gt;&#13;
â€¢ &lt;a href="http://peeringintodarkness.com/ctd/?p=4840"&gt;Pet food contamination:  Melamine now found in rice&lt;/a&gt;&#13;
â€¢ &lt;a href="http://peeringintodarkness.com/ctd/?p=4899"&gt;Australian officials puzzle over missing yacht crew&lt;/a&gt;&#13;
&#13;
--&#13;
&#13;
Original Source: P.I.D. Radio&#13;
&lt;a href="http://pidradio.com/?p=357"&gt;http://pidradio.com/?p=357&lt;/a&gt;&#13;
&#13;
This work is licensed under a &lt;a href="http://creativecommons.org/licenses/by-nc-nd/3.0/us/"&gt;Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9579">
                <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="11569">
                <text>Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13023">
                <text>P.I.D. Radio 4/22/07: 23, 33, 2121</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="323">
        <name>cho</name>
      </tag>
      <tag tagId="87">
        <name>gun control</name>
      </tag>
      <tag tagId="649">
        <name>podcast</name>
      </tag>
      <tag tagId="142">
        <name>radio</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="533" public="1" featured="0">
    <fileContainer>
      <file fileId="335">
        <src>https://www.april16.vtlibraries.net/files/original/pidradio070429_b9c20a003f.mp3</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="14728">
                    <text>2007-06-16</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="15848">
                    <text>2007-06-16 14:28:06</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="5">
      <name>Sound</name>
      <description>A resource whose content is primarily intended to be rendered as audio.</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="1862">
                <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="3753">
                <text>P.I.D. Radio</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="5731">
                <text>2007-06-16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7609">
                <text>16 kpbs MP3 6.9 MB&#13;
&#13;
April 29, 2007&#13;
&#13;
Today we feature audio from a radio interview Derek conducted Friday, April 27th with Peter Levenda, author of the excellent three-volume set Sinister Forces: A Grimoire of American Political Witchcraft.&#13;
&#13;
Simply put, Peter is as bothered by certain details of the Virginia Tech massacre as we are, and he&amp;#39;s concerned that the major media&amp;#39;s superficial analysis of the case is leading us to accept Cho Seung-Hui as nothing more than the latest in a long line of lone gunmen.&#13;
&#13;
Links:&#13;
&#13;
â€¢ &lt;a href="http://www.sinisterforces.info/"&gt;Peter Levenda&amp;#39;s website&lt;/a&gt;&#13;
â€¢ &lt;a href="http://www.sinisterforces.info/blog/index.php"&gt;Peter Levenda&amp;#39;s blog&lt;/a&gt;&#13;
â€¢ &lt;a href="http://www.sinisterforces.info/blog/index.php?/archives/38-Making-No-Sense-of-a-Massacre.html"&gt;"Making No Sense of a Massacre"&lt;/a&gt; by Peter Levenda&lt;/li&gt;&#13;
â€¢ &lt;a href="http://www.sinisterforces.info/blog/index.php?/archives/37-Tales-from-the-Darkside.html"&gt;"Tales From the Darkside"&lt;/a&gt; by Peter Levenda&#13;
&#13;
--&#13;
&#13;
Original Source: P.I.D. Radio&#13;
&lt;a href="http://pidradio.com/?p=358"&gt;http://pidradio.com/?p=358&lt;/a&gt;&#13;
&#13;
This work is licensed under a &lt;a href="http://creativecommons.org/licenses/by-nc-nd/3.0/us/"&gt;Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License&lt;/a&gt;.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9580">
                <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="11570">
                <text>Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13024">
                <text>P.I.D. Radio 4/29/07: Peter Levenda - What Made Cho a Killer?</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="323">
        <name>cho</name>
      </tag>
      <tag tagId="651">
        <name>levenda</name>
      </tag>
      <tag tagId="650">
        <name>peter levenda</name>
      </tag>
      <tag tagId="649">
        <name>podcast</name>
      </tag>
      <tag tagId="142">
        <name>radio</name>
      </tag>
      <tag tagId="652">
        <name>sinister forces</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
