<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://april16archive.org/items?output=omeka-xml&amp;page=22&amp;sort_field=added" accessDate="2026-04-03T20:02:01+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>22</pageNumber>
      <perPage>20</perPage>
      <totalResults>1884</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="584" 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="1913">
                <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="3804">
                <text>Doug Eshleman</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="5782">
                <text>2007-06-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7660">
                <text>&lt;b&gt;Comments to Manna adviser offer first glimpse of Cho family reaction&lt;/b&gt;&#13;
&#13;
By Doug Eshleman&#13;
Princetonian Staff Writer&#13;
&#13;
    While family members of the Virginia Tech gunman have secluded themselves during the last three days to avoid media attention, his older sister, Sun-Kyung Cho &amp;#39;04, reached out to a close friend and spiritual adviser from her Princeton days yesterday, offering the first glimpse of how the shooter&amp;#39;s closest relatives are reacting to Monday&amp;#39;s killings.&#13;
&#13;
    At a discussion forum organized yesterday by the Korean American Students Association (KASA) to help students cope with the shootings, Manna Christian Fellowship director Rev. David Kim told the group that Cho â€” a member of Manna while at the University â€” called and talked to him over the phone yesterday morning.&#13;
&#13;
    Some of Cho&amp;#39;s conversation with Kim focused on the guilt he said she&amp;#39;s feeling in the aftermath of her brother&amp;#39;s actions. Kim said that Cho apologized for any negative repercussions Koreans on campus may have experienced after Monday&amp;#39;s shooting.&#13;
&#13;
    The 23-year-old Cho Seung-Hui â€” who shot himself after taking the lives of 32 people Monday on the Virginia Tech campus â€” immigrated to the United States in 1992 from South Korea, along with Sun-Kyung and their parents.&#13;
&#13;
    "When she called, one of the first things she did was she apologized because she felt so bad for the Koreans on campus," Kim said. Several Korean students and alumni have expressed anxiety regarding a possible nationwide backlash against their community following the Virginia shootings.&#13;
&#13;
    Kim added that in the next few days, Cho would release a public statement on behalf of her family, since her parents do not speak English. Cho has taken a leave of absence from her job with a State Department contractor, ABC News reported yesterday, and her parents left their Centreville, Va. house Monday before media members swarmed the location.&#13;
&#13;
    Cho could not be reached yesterday. She declined to comment when contacted on her cellphone Tuesday.&#13;
&#13;
    In an interview after the forum, Kim said that Cho is "doing okay and [that] she appreciates the support of the Manna community that she knows." He added that he wanted to respect Cho&amp;#39;s privacy by restricting his public comments about her, emphasizing his desire not to "compromise [his] ability to support her as a friend."&#13;
&#13;
    Manna, a Christian undergraduate group, has historically had heavily Asian-American membership though its website emphasizes that it seeks diverse student involvement. Cho was involved with the group during her time at the University, but it remains unclear whether her affiliation with Manna reflected her family&amp;#39;s religious beliefs or convictions she developed on her own.&#13;
&#13;
    Cho was an economics major who interned at the U.S. Embassy in Bangkok during the summer after her junior year. She also wrote briefly for The Daily Princetonian. Kim said he had known Cho when she was an undergraduate at the University and described her as "one of the sweetest people."&#13;
&#13;
    He also said that though her family was in great need of support, Cho told him that rumors and media reports that her parents had attempted suicide were untrue.&#13;
&#13;
    During the discussion last night, some Korean students said they could not help feeling somehow connected to Cho Seung-Hui. "I can&amp;#39;t help feeling a relation to him," Jin-Hee Kim &amp;#39;07 said. "I feel connected to him even though there is no pressure from others." She explained that, like Cho Seung-Hui, she has two foreign-born Asian parents.&#13;
&#13;
    "We feel embarrassed because we associate him as one of our own," Jae Han &amp;#39;09 said.&#13;
&#13;
    Andrew Kim &amp;#39;10 said he felt differently about the situation. "I think the feelings that we have are a manifestation of what the media is putting into us," he said. He added that he believes the media tends to emphasize Cho&amp;#39;s ethnicity unnecessarily. "I feel that it is important to not become part of that." But, he emphasized, as a Korean, he does not feel threatened or uncomfortable on campus.&#13;
&#13;
    Juyoung Chung &amp;#39;10 said he, too, hopes that the tragedy at Virginia Tech will not become too closely tied to the Korean ethnicity. "Even though Koreans can feel associated, I hope people recognize that this was an isolated event," he said.&#13;
&#13;
--  &#13;
&#13;
Original Source: &lt;a href=http://www.dailyprincetonian.com/archives/2007/04/19/news/18166.shtml&gt; Daily Princetonian - April 19, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9631">
                <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="11616">
                <text>Kavita Saini &lt;ksaini@Princeton.EDU&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13075">
                <text>Cho &amp;#39;04 calls campus friend</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="719">
        <name>cho family response</name>
      </tag>
      <tag tagId="711">
        <name>princeton</name>
      </tag>
      <tag tagId="714">
        <name>sunkyung cho</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="585" 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="1914">
                <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="3805">
                <text> Owen Fletcher</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="5783">
                <text>2007-06-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7661">
                <text>By Owen Fletcher&#13;
Princetonian Staff Writer&#13;
&#13;
    About a week before last week&amp;#39;s shootings at Virginia Tech, the University made the prescient purchase of a mass alert system to notify students of campus security crises.&#13;
&#13;
    The University&amp;#39;s system, which messages students&amp;#39; cell phones or other portable devices, has not yet been fully implemented, but it signals a heightened concern about campus security that existed even before the shootings.&#13;
&#13;
    But the shootings have ignited a national debate on methods to prevent and effectively respond to crises and have led to questions about campus security procedures.&#13;
&#13;
    Some Virginia Tech students have criticized campus safety officials for their slow response to gunman Cho Seung-Hui&amp;#39;s murder of two students. Campus police notified students by email about two hours after the incident, but by then, Cho had begun his second round of shooting, taking 30 more lives and his own.&#13;
&#13;
    Crises like last week&amp;#39;s shooting are difficult to predict, Public Safety Deputy Director Charles Davall said. "You can never totally be prepared for something like this," he said. "It could happen anywhere."&#13;
&#13;
    At a Senate hearing yesterday on campus security, Public Safety Director Steven Healy recommended that more universities adopt "mass notification systems that are capable of reaching community members."&#13;
&#13;
    Getting students to provide their portable contact information for this system, however, could be difficult, Healy testified. "Even if you have a system that can reach a person&amp;#39;s cell phone" or other portable device, he said, "they still have to be willing to give you those numbers."&#13;
&#13;
    Healy, who is also president of the International Association of Campus Law Enforcement Administrators, said there is room for nationwide improvement on campus security.&#13;
&#13;
    "[M]ost colleges and universities have plans" to respond to crises, he said, but "we&amp;#39;re a long way from being able to say ... that all institutions know how those plans will play."&#13;
&#13;
    Since last week&amp;#39;s shootings, Public Safety has begun a review of campus security plans. Davall said that the department tentatively has arranged for Mercer County officials to train its officers.&#13;
&#13;
    In the event of a crisis, Davall said, Public Safety would respond by securing the area and calling local armed police, since campus police do not carry weapons. They would then notify all University members by email. But one problem with this method is that "students have to be looking at [a computer] to get the email," he said.&#13;
&#13;
    Healy also advocated "community policing" in his testimony. As part of Public Safety&amp;#39;s policy, officers are required to patrol campus by foot for at least two hours a day so that students and faculty feel comfortable approaching them, officer Jim Lanzi said.&#13;
&#13;
    The department&amp;#39;s efforts to engage the community can make people more comfortable in reporting suspicious activity, Lanzi said, but they are also meant to educate the community since students sometimes have a "false sense of security" on campus.&#13;
&#13;
    While these initiatives would not directly prevent an event like the Virginia Tech shooting, Lanzi said, the atmospheric difference they make could help increase the efficacy of a response.&#13;
&#13;
    Princeton "is generally a safe area ... but [students] always need to be aware of their surroundings," Davall said.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://www.dailyprincetonian.com/archives/2007/04/24/news/18230.shtml&gt; Daily Princetonian - April 24, 2007&lt;/a&gt; </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9632">
                <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="11073">
                <text>Daily Princetonian </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11617">
                <text>Kavita Saini &lt;ksaini@Princeton.EDU&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13076">
                <text>Would Public Safety be able to prevent a shooting?</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="721">
        <name>campus safety</name>
      </tag>
      <tag tagId="711">
        <name>princeton</name>
      </tag>
      <tag tagId="720">
        <name>warning systems</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="586" 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="1915">
                <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="3806">
                <text>Uwe E. Reinhardt</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="5784">
                <text>2007-06-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7662">
                <text>By Uwe E. Reinhardt&#13;
Princetonian Columnist&#13;
&#13;
    Students gathered in Richardson Auditorium last night for a service in memory of the victims of Monday&amp;#39;s shooting at Virginia Tech," reported The Daily Princetonian on April 18. A day earlier, President Tilghman stated that "my reaction was horror at the loss of so many innocent young lives," a sentiment echoed by President Bush when he remarked that "those whose lives were taken did nothing to deserve their fate. They leave behind grieving families and grieving classmates and a grieving nation." Congress openly prayed for the victims and their loves ones. Flags flew at half-mast across the nation.&#13;
&#13;
    It was good. Solidarity with stricken fellow human beings forges a group of people sharing a geography into a "community" or "nation." As Associate Dean of Religious Life Deborah Blanks put it so eloquently during the memorial: "We dare to affirm that there is strength in community."&#13;
&#13;
    It takes nothing away from the grief we share with Virginia Tech&amp;#39;s community to let the mind wander from that tragedy to another one, the daily toll of fellow human beings grotesquely destroyed or maimed in Iraq, among them many American men and women just as young and innocent as those killed at Virginia Tech. As Keith Olbermann of MSNBC&amp;#39;s "Countdown," standing out from the herd politically correct journalists, asked boldly on April 17: "In just the last 10 days, 32 American troops, many the same age as the Virginia Tech students, have died. While one may take issue with the comparison, one cannot ignore the similarities ... It seems fair to ask the question, if the violent deaths in Virginia send the nation into shock and expressions of concern and anxiety, why is not the continuous flow of blood in Iraq creating a similar reaction? Why isn&amp;#39;t our flag permanently at half staff?"&#13;
&#13;
    Olbermann has a point. In just the two days following the shooting at Virginia Tech, close to 400 Iraqis were brutally blown to shreds and hundreds more seriously wounded, along with the usual daily toll of U.S. military personnel. Stories on their fate were pushed way down the list of reports on TV or in the daily press. Did Congress pray for them? Are these human beings part of Dean Blanks&amp;#39; "community"?&#13;
&#13;
    It appears that the daily slaughter of people in Iraq has become so routine now that reports on it must compete for America&amp;#39;s attention with updates on Wall Street, sport scores and the Anna Nicole Smith story. On our campus, the indifference may be amplified by what USG president Rob Biederman &amp;#39;08 called at the memorial the "Orange Bubble," namely, the fact that "every college should be a place apart," presumably from the outside world. The tragedy at Virginia Tech seems to have penetrated that Bubble only because of what Biederman called "the similarity of all students&amp;#39; campus experiences."&#13;
&#13;
    Military service for one&amp;#39;s country and the horrors of war are as far removed from the campus experience as one could imagine. To illustrate, in early October of 2005 I wrote to the then editor-in-chief of the Daily Princetonian: "I would like to make a suggestion that would add grace to the &amp;#39;Prince.&amp;#39; Show every day, on the front page of the paper, the names of American troops who have been killed in Afghanistan and Iraq. The idea would be to remind young Princetonians, many of whom aspire to be future leaders, that there is a war going on and that they have contemporaries who are willing to stand tall for their country and to pay the ultimate price for it."&#13;
&#13;
    In a courteous email, the editor replied that she understood and agreed with my sentiment, but that "The Daily Princetonian has a defined scope as a newspaper: We cover events and people affiliated with the University Community." She pointed out that the national newspapers are to keep us abreast of other events. Alas, who among college students these days actually reads these dailies?&#13;
&#13;
    In fairness to the &amp;#39;Prince,&amp;#39; not all dailies report on the blood cost of the war either. For example, I had earlier asked The Wall Street Journal, a major cheerleader for the invasion of Iraq, to honor on its front page the names of the fallen warriors. That request did not even warrant an answer, presumably because the Journal does not want to highlight that war has its costs.&#13;
&#13;
    As a member of the University community, I can well understand the comfort the stricken Virginia Tech community may find in Princeton&amp;#39;s and the nation&amp;#39;s vigils for them and the sentiment that begot the vigils. But as the parent of a Marine who narrowly escaped death on the battlefield in 2005 and may yet have to serve a fourth tour of duty (because too few career-minded inhabitants of the College Bubble are willing to take over from him), I also share the loneliness that all military families feel in a nation that seems preoccupied with things other than the human toll in Iraq.&#13;
&#13;
&lt;i&gt;Uwe E. Reinhardt is the James Madison Professor of Political Economy and a professor in the Wilson School. He can be reached at reinhard@princeton.edu.&lt;/i&gt;&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://www.dailyprincetonian.com/archives/2007/04/23/opinion/18202.shtml&gt; Daily Princetonian - 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="9633">
                <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="11618">
                <text>Kavita Saini &lt;ksaini@Princeton.EDU&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13077">
                <text>The narrow reach of &amp;#39;community&amp;#39;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="639">
        <name>community</name>
      </tag>
      <tag tagId="711">
        <name>princeton</name>
      </tag>
      <tag tagId="722">
        <name>response</name>
      </tag>
      <tag tagId="17">
        <name>tragedy</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="587" 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="1916">
                <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="3807">
                <text>Anonoymous </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="5785">
                <text>2007-06-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7663">
                <text>By Anonymous &#13;
&#13;
    The shooting at Virginia Tech serves as a tragic reminder of the importance of a strong campus community, one in which people know and look out for each other. In the wake of this event, it is important that we make sure that all students feel comfortable in our campus community. This opportunity should be seized to reflect on how to foster a greater sense of community, especially in upperclass dorms.&#13;
&#13;
    There seems to be a presumption that, once out of their residential colleges, upperclassmen are sufficiently acclimatized to college life. While colleges provide students with RCAs who organize study breaks and generally foster a sense of commnity within dorms, upperclassmen are left to their own devices. Though eating clubs provide some measure of support for upperclassmen, nothing exists to promote socialization in upperclass dorms or among the many students who do not choose to join clubs or remain in the residential colleges. Independent work, which puts increased pressure on upperclassmen and often requires them to spend significant time alone, means that community feeling outside of eating clubs often suffers. Some students go through an entire year without meeting all their neighbors.&#13;
&#13;
    Though social dynamics among students is, in the end, the result of our own behavior, there is room for the administration to provide a helping hand. While the University provides mental health services for those in need, having intermediaries step, similar to RCAs, would greatly stimulate social interactions in upperclass dorms and encourage students with psychological issues not to isolate themselves. This could easily be achieved by expanding the mission â€” and budget â€” of dormitory assistants, whose current responsibilities are focused on questions of maintenance and living conditions.&#13;
&#13;
    These measures are not intended to prevent tragic instances such as those at Virginia Tech. They would, however, encourage interaction in upperclass dorms and foster a greater sense of community. It would encourage people to meet and take an interest in their neighbors, reducing the risk that students who are depressed, or feel particularly lonely, slip through the cracks unnoticed. We share the pain of the Virginia Tech community and hope that from this tragedy, we can all realize the vital role of looking out for the wellbeing of our classmates.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://www.dailyprincetonian.com/archives/2007/04/20/opinion/18175.shtml&gt; Daily Princetonian - April 20, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9634">
                <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="11074">
                <text>Daily Princetonian</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11619">
                <text>Kavita Saini &lt;ksaini@Princeton.EDU&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13078">
                <text>A call for community</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="639">
        <name>community</name>
      </tag>
      <tag tagId="723">
        <name>outreach</name>
      </tag>
      <tag tagId="711">
        <name>princeton</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="588" 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="1917">
                <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="3808">
                <text> Sam Fox Krauss</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="5786">
                <text>2007-06-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7664">
                <text>By Sam Fox Krauss&#13;
Princetonian Staff Writer&#13;
&#13;
    Students who kill their classmates are motivated by a desire to change their reputation, Wilson School professor Katherine Newman and politics professor Keith Whittington told about 50 students and community members last night at a talk on the Virginia Tech shootings.&#13;
&#13;
    Newman discussed the social experience of school shooters and the unpredictability of such tragedies, while Whittington related the killings at Virginia Tech to gun control regulation and discussed the potential for changes to concealed weapons permits.&#13;
&#13;
&lt;b&gt;The sociology of school shootings&lt;/b&gt;&#13;
&#13;
    Major American school shootings have mostly occurred in obscure rural neighborhoods, Newman said. She likened the school massacres in small towns to the "endemic" violence in big cities.&#13;
&#13;
    Newman went on to discuss Virginia Tech shooter Cho Seung-Hui in the context of three case studies she has done of school shootings since the 1999 shooting at Columbine High School in Littleton, Colo.&#13;
&#13;
    "What all three of these boys were trying to do was changing their image in the eyes of their peers," Newman said.&#13;
&#13;
    In rural towns, the school is an easy place to make a violent statement, Newman said. She contrasted this with the situation in cities, where young men are more likely to commit violent crimes on the street.&#13;
&#13;
    Newman found that school gunmen in recent years have professed a desire to surpass the death toll of the Columbine shootings. The same mentality, she said, seems to be true for Cho.&#13;
&#13;
    Newman discussed several cases of school shootings, all committed by students much younger than Cho. She said that if the children been older, their mental diseases would have been more readily apparent.&#13;
&#13;
    "There isn&amp;#39;t a single rampage incident that wasn&amp;#39;t preceded by a string of signals," Newman said.&#13;
&#13;
    But the signals that future shooters send out are often ambiguous and under the radar of adults, which is why the signs are rarely reported, she said.&#13;
&#13;
    Classmates of the shooters often do not convey their suspicions to authority figures because they fear being labeled a "rat," Newman said.&#13;
&#13;
    She described the sense of community in small towns that can lead to reluctance to come forward with damaging information regarding a child. In one example, a neighbor saw a child killing cats in his backyard but did not tell the child&amp;#39;s parents. The child went on to kill several students at his middle school.&#13;
&#13;
    Neighbors may also be suspicious of the motives of the people who come forward with information about their children.&#13;
&#13;
    Newman noted that the Virginia Tech shootings were different from other school shootings because classmates and professors did come forward with information, and Cho did receive treatment.&#13;
&#13;
&lt;b&gt;School shootings and gun control&lt;/b&gt;&#13;
&#13;
    Whittington discussed the Brady Handgun Violence Prevention Act of 1993, which requires federally licensed handgun dealers to run background checks on customers.&#13;
&#13;
    Cho went through a background check when he purchased a gun from a licensed dealer. Unfortunately, Cho was not in the federal background check system, though a Virginia judge had ruled him to be a danger to himself.&#13;
&#13;
    "[Cho] should have been included in the database, and [it] should have excluded him," Whittington said.&#13;
&#13;
    "[Gun control is] not a sufficiently high priority in the state or federal budget," Whittington said. He also noted many problems with background checks, including the high cost of constantly updating databases and difficulties in maintaining consistency across databases.&#13;
&#13;
    "It&amp;#39;s unlikely to thrust forward a major movement ... for rethinking gun control more broadly," Whittington said. He does not foresee a major shift in gun control, but he predicts a debate about concealed weapons permits.&#13;
&#13;
    The argument for concealed weapons permits is that students may have been able to stop Cho during the shootings.&#13;
&#13;
    The lecture was organized as a response to the Virginia Tech shootings by the Office of the Dean of Undergraduate Students and the USG.&#13;
&#13;
-- &#13;
&#13;
Original Source: &lt;a href= http://www.dailyprincetonian.com/archives/2007/04/24/news/18229.shtml&gt; Daily Princetonian - April 24, 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="9635">
                <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="11075">
                <text>Daily Princetonian</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11620">
                <text>Kavita Saini &lt;ksaini@Princeton.EDU&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13079">
                <text>Prof. Newman: Self-image drove Va. Tech shooter</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="711">
        <name>princeton</name>
      </tag>
      <tag tagId="725">
        <name>psychology of school shootings</name>
      </tag>
      <tag tagId="724">
        <name>self image</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="589" public="1" featured="0">
    <fileContainer>
      <file fileId="353">
        <src>https://april16archive.org/files/original/expansion_008954_fc936f3a35.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="14746">
                    <text>2007-06-22</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="15866">
                    <text>2007-06-22 16:52:44</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="1918">
                <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="3809">
                <text>Cornelia Hall</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="5787">
                <text>2007-06-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7665">
                <text>&lt;b&gt;Campus comes together to mourn victims of shooting&lt;/b&gt;&#13;
&#13;
By Cornelia Hall&#13;
Princetonian Staff Writer&#13;
&#13;
Photo by Gabriela Aoun&#13;
&#13;
    Students gathered in Richardson Auditorium last night for a service in memory of the victims of Monday&amp;#39;s shootings at Virginia Tech. With solemn faces, some stained with tears, they listened to musical performances, prayers and speeches.&#13;
&#13;
    Associate Dean of Religion Life Deborah Blanks took the podium first, addressing the assembled students with deliberate, heartfelt remarks. She emphasized the renewed interconnectedness of the student body, calling the Princeton community "united in heart, spirit and solidarity."&#13;
&#13;
    "We dare to affirm that there is strength in community," she said.&#13;
&#13;
    In addition to the sense of unity on Princeton&amp;#39;s campus, Blanks spoke of its tie to all academic institutions. "When tragedy touches one life, its universal reach reminds us of the fragility and the vulnerability of all life," she noted. She closed her remarks with a prayer.&#13;
&#13;
    USG president Rob Biederman &amp;#39;08 also stressed the transcendence of the college experience, bringing the events at Virginia Tech closer to the Princeton campus. He spoke solemnly as the audience kept their gazes fixed on the podium.&#13;
&#13;
    "Every college campus should be a place apart; I imagine Princeton and Virginia Tech are no different in this regard," he told the gathering. "Here at Princeton, some casually refer to this as the Orange Bubble. At Virginia Tech yesterday, the bubble was ruptured, and we felt the shocks of that rupture here."&#13;
&#13;
    Monday&amp;#39;s gunshots reverberated across the country, with President Bush seeking to console an appalled America and Speaker of the House Nancy Pelosi (D-Calif.) offering a moment of silence on the House floor.&#13;
&#13;
    "Those whose lives were taken did nothing to deserve their fate," Bush said at a memorial held at the Virginia Tech campus yesterday. "They were simply in the wrong place at the wrong time. Now they&amp;#39;re gone, and they leave behind grieving families and grieving classmates and a grieving nation."&#13;
&#13;
    One reason why Princeton felt the repercussions of the tragedy, Biederman said, is the similarity of all students&amp;#39; campus experiences. "As college students, we can feel for their tragedy because we too know the sense of safety and security they felt that morning. We must give our thoughts and prayers to them because we are the same."&#13;
&#13;
    For some, the tragedy hit especially close to home. Misan Ikomi &amp;#39;08, from Leesburg, Va., said about a third of her high school class attends Virginia Tech. After Monday&amp;#39;s violence, she contacted a close friend to check in on her and was assured of her safety. "She said it&amp;#39;s been pure chaos, like being in a movie and not really understanding what&amp;#39;s happened," Ikomi said.&#13;
&#13;
    Jeff Hall &amp;#39;08 has a brother who attends Virginia Tech. Hall reflected on the conversation he had after calling to make sure his brother was okay. "He didn&amp;#39;t really talk about it too much," Hall said. "He was in a building nearby when it happened, and he saw people running out the door when it happened. I didn&amp;#39;t really get much of a reaction from him."&#13;
&#13;
    "Even for those of us without friends or relatives in Blacksburg," Biederman said, "it&amp;#39;s nearly impossible to feel unaffected by what has transpired," he said.&#13;
&#13;
    Students clapped sporadically during the service, seemingly unsure of the appropriate response to the speeches. Applause was subdued and brief.&#13;
&#13;
    The speakers also offered a sense of optimism, encouraging students to look toward the future in evaluating how they go about their daily lives.&#13;
&#13;
    President Tilghman was traveling and could not attend the service, but Vice President for Campus Life Janet Dickerson, Provost Christopher Eisgruber &amp;#39;83 and several officials from Public Safety were in attendance.&#13;
&#13;
    At an Episcopalian memorial service in the University Chapel earlier yesterday afternoon, Princeton community members remembered the victims of Monday&amp;#39;s attacks while searching for higher meaning through religion.&#13;
&#13;
    "I would hope that this would be an opportunity to develop habits of prayer and ongoing awareness of the transient nature of life and what that means for us in terms of our relationships, with one another and with God," Rev. Stephen White, an Episcopal chaplain, said after the service.&#13;
&#13;
    Eisgruber offered similar advice at the memorial. "Take the time to honor and value your own life and the lives of the people around you," he said.&#13;
&#13;
    Biederman suggested the University community address the issue of personal safety not with increased security but with increased trust.&#13;
&#13;
    "We should work daily to deepen and strengthen the bonds that make the college experience so special," Biederman told the gathering. "We need to look out for each other." &#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href= http://www.dailyprincetonian.com/archives/2007/04/18/news/18128.shtml&gt; Daily Princetonian - 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="9636">
                <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="11621">
                <text>Kavita Saini &lt;ksaini@Princeton.EDU&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13080">
                <text>Tragedy hits close to home</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="592">
        <name>memorial service</name>
      </tag>
      <tag tagId="711">
        <name>princeton</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="590" 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="1919">
                <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="3810">
                <text>Sean Moroney</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="5788">
                <text>2007-06-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7666">
                <text>By: Sean Moroney&#13;
Posted: 5/17/07&#13;
&#13;
Other than being two of the most-read playwrights in history, Sophocles and Shakespeare share another common thread-a knack for writing gruesome but also unforgettable scenes.&#13;
&#13;
Likewise, Cho Seung-Hui, the Virginia Tech shooter who was a senior majoring in English, graphically described murder and violence in two plays he wrote for a class in the fall of his senior year.&#13;
&#13;
One difference between the well-known playwrights and Cho, however, was that their words stayed on the stage and Cho&amp;#39;s played out in real life.&#13;
&#13;
Since the Virginia Tech massacre April 16, critics have questioned whether university administrators and professors could have taken further steps to prevent the shooting. Specifically, they have focused on Cho&amp;#39;s two plays-"Mr. Brownstone" and "Richard McBeef," in which a 13-year-old threatens to kill his stepfather.&#13;
&#13;
"There is that understood latitude in creative writing," Duke English Professor Deborah Pope wrote in an e-mail. "There has to be that room to reach deeply. Not least of all because some of the greatest writers we know have written about quite disturbing events and characters. Many of the Greek plays and Shakespeare, as just two examples, are full of gore."&#13;
&#13;
In the English department at Duke, students can take a number of courses that either integrate creative writing into the curriculum or focus solely on it. Pope, who teaches creative writing, said she is not aware of an official policy on regulating a student&amp;#39;s creative writing.&#13;
&#13;
"I don&amp;#39;t know how there could be," Pope said. "It must rest with a teacher&amp;#39;s individual judgment."&#13;
&#13;
Creative writing in college is a delicate issue because professors oftentimes encourage students to express themselves freely in their writing but at the same time must recognize when highly imaginative writing signals problems in the personal lives of the student.&#13;
&#13;
"I read both of [Cho&amp;#39;s] short plays. I was pretty horrified and disgusted because I hate violence," said senior and English major Stephen Lee. "I haven&amp;#39;t written anything equally violent or disturbing."&#13;
&#13;
Lee said he sometimes feels self-conscious about sharing his writing that is particularly grotesque due to fear of how other students might react. He added, however, that his creative writing professors have never censored a student&amp;#39;s work just because it was violent or disturbing.&#13;
&#13;
"At Duke, I have read some disturbing stories written by fellow students, but I&amp;#39;ve never felt remotely endangered because the author has always been able to explain and defend his or her creative choices," Lee wrote in an e-mail.&#13;
&#13;
A senior in Cho&amp;#39;s playwrighting class, Steven Davis, told The New York Times that after reading Cho&amp;#39;s play "Richard McBeef" one night, he turned to his roommate and said, "This is the kind of guy who is going to walk into a classroom and start shooting people."&#13;
&#13;
After noticing a pattern of odd behavior from Cho-which included taking pictures of women with his cell phone camera in a poetry class in his junior year and a taciturn personality, Lucinda Roy, chair of the English department and co-director of the creative writing program at Virginia Tech, began to tutor Cho privately.&#13;
&#13;
Roy and other professors took further steps to ensure that counseling was sought for Cho, who was ordered to attend a psychiatric facility in late 2005. But their actions were not enough to prevent the shooting.&#13;
&#13;
"Fortunately, I have never had to deal with writing that struck me as truly psychotic or sadistic," Pope said. "When I heard that the Virginia Tech&amp;#39;s writing teacher, of all people, had raised red flags, my first reaction was, &amp;#39;My god, it must have been something really, really, unsettling-it must have just been completely over the edge.&amp;#39;"&#13;
&#13;
English major Melanie Garcia, Trinity &amp;#39;07, said the way she approaches writing is to write about things that mean a lot to her.&#13;
&#13;
"By writing things down that are personal, I make them permanent-they become something outside of me," she said. "If it were a painful memory, it would not be as painful."&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dukechronicle.com/media/storage/paper884/news/2007/05/17/News/After.Vatech.Violent.Creative.Writing.Raises.Concerns.On.Campuses-2904875.shtml&gt; Duke Chronicle - May 17, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9637">
                <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="11076">
                <text>Duke Chronicle </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11622">
                <text>David Graham &lt;david.graham@duke.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13081">
                <text>After VaTech, violent creative writing raises concerns on campuses</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="726">
        <name>duke</name>
      </tag>
      <tag tagId="44">
        <name>teaching</name>
      </tag>
      <tag tagId="326">
        <name>violence</name>
      </tag>
      <tag tagId="727">
        <name>writing</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="591" 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="1920">
                <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="3811">
                <text>Danny Mistarz</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="5789">
                <text>2007-06-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7667">
                <text>By: Danny Mistarz&#13;
Posted: 4/24/07&#13;
After the tragic events that took place at Virginia Tech April 16, the anti-Second Amendment crowd has once again reared its ugly head. The usual claims of guns causing violence and the necessity to ban personal ownership have come out. But what if one person, a student, a professor, the RA in the dorm, had been carrying a gun? Would dozens of lives have been spared?&#13;
&#13;
The state of Virginia&amp;#39;s legislature had a bill proposed last year, HB 1572, proposing that handguns be permitted on college campuses for those persons with proper permits and certification. The bill was shot down in subcommittee, never making it to the house floor. At the time, it was celebrated by a VT spokesman as a stride toward continued public safety. Was the wrong decision was made? Guns are used 2.5 million times in self-defense annually, saving approximately 2,575 lives for each life lost annually according to the Second Amendment Foundation; could HB 1572 gave saved thirty-one lives on the morning of April 16, or even just one?&#13;
&#13;
Let&amp;#39;s assume that guns were permitted on campus at Virginia Tech, and that one student or one professor in the engineering building was carrying that day. This coward would never have been able to level a gun on hundreds of his classmates had he known there was the possibility of having to defend himself. What if a student on the hall of the dormitory had a gun, just in the room for protection? Certainly the first two gunshots, would have been heard and within a minute of the start of a rampage, 31 lives could have been saved. All it would take is one person, carrying one gun.&#13;
&#13;
No gun law could stop people who want to get guns from getting them any better than our current drug laws work. Perhaps the gun laws that need arguing against are the gun laws that limit us, not the laws that protect us.&#13;
&#13;
Danny Mistarz&#13;
&#13;
Pratt &amp;#39;09&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://www.dukechronicle.com/home/index.cfm?event=displayArticlePrinterFriendly&amp;uStory_id=8436d5a8-6250-459d-b726-78d5453835b3&gt; Duke Chronicle - April 24, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9638">
                <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="11077">
                <text>Duke Chronicle </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11623">
                <text>David Graham &lt;david.graham@duke.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13082">
                <text>Shooting points to need for less restrictive gun laws</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="726">
        <name>duke</name>
      </tag>
      <tag tagId="87">
        <name>gun control</name>
      </tag>
      <tag tagId="487">
        <name>law</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="592" 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="1921">
                <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="3812">
                <text>Zak Kazzaz</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="5790">
                <text>2007-06-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7668">
                <text>By: Zak Kazzaz&#13;
Posted: 4/23/07&#13;
Early Friday morning, Duke University Police Department received an anonymous bomb threat for Bell Tower Dormitory and another building, which does not exist.&#13;
&#13;
The threat-received through a telecommunications device for the deaf-was not found credible by the police, but they investigated the dorm to ensure there was no hazard, said Larry Moneta, vice president for student affairs.&#13;
&#13;
Bell Tower residents were not evacuated and received an e-mail about the threat several hours later.&#13;
&#13;
The incident added Duke to a list of schools and universities across the country that have received security threats since the Virginia Tech shootings a week ago.&#13;
&#13;
Although some universities have chosen to evacuate buildings and cancel classes in response to the threats, others have opted to continue normal activities.&#13;
&#13;
"Threats are made over the course of the year, and [the police] exercise a judgment," Moneta said. "They have expertise in determining that something&amp;#39;s credible or not."&#13;
&#13;
He added that DUPD is currently investigating who called in the threat.&#13;
&#13;
Some Bell Tower residents said they were wary of how the situation was handled.&#13;
&#13;
Freshman Jordan Rice said he saw a police officer searching the dormitory Friday.&#13;
&#13;
"We asked him if he needed any help, and he said no," Rice said. "He looked to be in no hurry."&#13;
&#13;
Rice added that he was unsure whether or not evacuation would have been necessary.&#13;
&#13;
"They deemed it was not credible," he said. "I trust that, but then again, you really don&amp;#39;t want to make the same mistake the Virginia Tech administrators made in not closing down classes or, in this case, evacuating a dorm."&#13;
&#13;
Joe Gonzalez, associate dean for residential life, wrote in the e-mail sent to the residents that there was no reason for students to feel unsafe.&#13;
&#13;
"We do not believe Bell Tower residents have any cause for concern at this time, but we wanted to make you aware of it and encourage extra vigilance on your part," he said.&#13;
&#13;
In addition to Gonzalez&amp;#39;s e-mail, Moneta sent out a message Friday to the entire undergraduate body, referencing the threat and encouraging students to remain safe and cautious.&#13;
&#13;
"Institutions across the nation and world, including Duke, begin hearing murmurs of violent acts to follow at home on one&amp;#39;s own campus," Moneta wrote in the e-mail. "While institutions must take such threats seriously and do their best to explore their veracity, this grim reality underscores our need to be extra vigilant in all that we do."&#13;
&#13;
Freshman Jon Silverman, a Bell Tower resident, said he preferred to remain unaware of threats unless the University chooses to take action.&#13;
&#13;
"I just don&amp;#39;t really want to know that they&amp;#39;re not going to do something," Silverman said. "It&amp;#39;s perceived risk versus actual risk."&#13;
&#13;
He added that, in this turbulent time, bomb threats have the potential to shut down universities and that Duke should only inform students of threats if they are concrete.&#13;
&#13;
"If they do start responding to every single bomb threat, we won&amp;#39;t have finals or classes," Silverman said. "If they just stop responding and don&amp;#39;t let all these copycats take it seriously, then hopefully it&amp;#39;ll die off." &#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://www.dukechronicle.com/home/index.cfm?event=displayArticlePrinterFriendly&amp;uStory_id=51338667-a7c8-461f-bf9e-7174632b4980&gt; Duke Chronicle - 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="9639">
                <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="11078">
                <text>Duke Chronicle </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11624">
                <text>David Graham &lt;david.graham@duke.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13083">
                <text>Bomb threat deemed no hazard</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="728">
        <name>bomb threat</name>
      </tag>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="726">
        <name>duke</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="593" 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="1922">
                <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="3813">
                <text>Eugene Wang</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="5791">
                <text>2007-06-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7669">
                <text>By: Eugene Wang&#13;
Posted: 4/20/07&#13;
Executive Vice President Tallman Trask spoke about Duke&amp;#39;s emergency response system and Jo Rae Wright, dean of the Graduate School, reported on the future of the school at the Academic Council&amp;#39;s meeting Thursday.&#13;
&#13;
Paul Haagen, chair of the council and professor of law, said he asked Trask to speak about Duke&amp;#39;s preparation for "extraordinary safety-related events," in light of the massacre at Virginia Tech Monday.&#13;
&#13;
Duke has the plans, equipment and notification systems in place to respond to emergencies, Trask said. He added, however, that a response system alone may not have been able to prevent the tragedy.&#13;
&#13;
"In the current circumstances, I can assure you we have taken all prudent preparatory steps to deal with the circumstances," Trask said. He added it is impossible for the University to notify everyone instantly in the case of an emergency.&#13;
&#13;
"We don&amp;#39;t know of any communication systems that can get a message to 27,000 people in three minutes," Trask said.&#13;
&#13;
He also noted that although the electronic door locks can be instantly disabled, there is no way of instantaneously restricting entry to Duke&amp;#39;s campus.&#13;
&#13;
"We don&amp;#39;t even control access to our campus... there are almost 20 different roads anyone could ride down to get into Duke," Trask said.&#13;
&#13;
Some members asked why no mass message was sent to the students and their parents after the massacre at Virginia Tech.&#13;
&#13;
"We deliberately decided not to send a message to all parents... because none of us really know what to say, none of us know the facts," Trask said.&#13;
&#13;
Council members also discussed if Counseling and Psychological Services has the capacity and strategies to deal with students&amp;#39; mental health issues. "We need to be clearer in instructions about what faculty can and cannot do," Trask said.&#13;
&#13;
The council also listened to a presentation by Wright on the "strategic plan" for the Graduate School and the state of the school&amp;#39;s finances. She said her goals for the future are like a "three-legged stool"-to recruit, retain and train the "best and most successful students."&#13;
&#13;
She said the school must improve its financial support packages, including health insurance, stipends and summer research awards, if it hopes to attract talented graduate students. "Having outstanding graduate students is critical to getting outstanding faculty," Wright said. "If we aren&amp;#39;t willing to make that commitment as an institution, then we&amp;#39;re in the wrong business."&#13;
&#13;
She said her priorities for the Graduate School next year include recruiting underrepresented minorities, planning the Graduate Student Center and evaluating teaching assistant training programs. Wright added, however, that the funds to implement these priorities are still uncertain.&#13;
&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dukechronicle.com/media/storage/paper884/news/2007/04/20/News/Council.Hears.Duke.Safety.Plans-2871367.shtml&gt;Duke Chronicle - April 20, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9640">
                <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="11625">
                <text>David Graham &lt;david.graham@duke.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13084">
                <text>Council hears Duke safety plans</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="730">
        <name>community response</name>
      </tag>
      <tag tagId="726">
        <name>duke</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="594" 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="1923">
                <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="3814">
                <text>Anthony Galanos</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="5792">
                <text>2007-06-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7670">
                <text>By: Anthony Galanos&#13;
Posted: 4/20/07&#13;
&#13;
The media coverage of the tragedy at Virginia Tech is rewarding insanity and complicating grief. But there are 32 families, and an entire university who are grieving. Not sad, not upset, not disgruntled... but GRIEVING. And how we treat them in this critical period will determine how they cope now and what the legacy of this past week will be for them.&#13;
&#13;
Almost as sad as the loss of life is that this American culture acts like it knows not what grieving is. You want to see grieving, find any child 10 years of age or younger and watch them after their dog or cat dies. It is not a profound concept; it does not require a degree in philosophy or theological training. It is a natural process, common to all humanity. Why we ignore it or complicate it, I do not know, but to accent anything at this raw moment but the grief of the people involved is to confuse them-no, is to use them and to make their journey more complicated and more traumatic than it already is. If my 18-year-old daughter were shot and killed in her dorm, and the only way it was described by her college president was as a "domestic situation" because they thought she had dated the shooter, I would be outraged. I would wonder why this man or woman was on TV and not acknowledging my loss. I would wonder why a famous news anchor is blaming him for police matters (my assumption is that most college presidents know little, if anything, about police work) when I just lost my daughter. And, if the task of losing my child were not difficult enough, then I would have to cope with the media, stating without any evidence whatsoever, that perhaps my daughter&amp;#39;s life "could have been spared". Now, and forever, that "what if" question would dominate me. It was not random or the product of psychosis. It was someone&amp;#39;s fault, or so say the pundits. What would have been a normal grieving process, is now complicated. I was not afraid to grieve, but my grieving may have no end point.&#13;
&#13;
As a clinician, let me pronounce, just like the talking heads on TV, that you have no right to comment on my loss. Indeed, unless you have every fact available, know without doubt how and why it happened or I abdicate it to you... you have no right to judge or comment on my loss. That right does not belong to Matt Lauer or NBC or my priest. It belongs to me and my family. She was ours, not yours. Neither your camera, your microphone or your best intentions allow you to take this moment from us. We teach doctors in training how to deliver "bad news." We have learned that such moments belong to patients and families, not to us. And that our simple presence there, however silent, is more powerful than our explanations of physiology or what went wrong.&#13;
&#13;
Cannot we just say "let us let the grieving begin" and we can sort out the details when all of the data are in... and the facts are known? Can we not just let the students at Virginia Tech and the families, just tell us about the people they lost. Who were they? What were they like? How do you want us to remember them? This would be the line of questioning that would let any healing have any chance of taking hold. Can we not simply acknowledge that this moment is theirs, not ours or that of the media? Who was not touched by the dad being interviewed who said at the end of the segment that his daughter&amp;#39;s body had not yet been released to him or his family, and that they wanted to see her. The interviewer asked him what he would do if he could see his daughter, almost puzzled by why this guy was asking to "see my daughter." He responded, "so that I can kiss her face." Is that not grieving? Is that not how this man will cope and heal over time? Do we not instinctively know what he is saying? Of course we do, and parents all over America hugged and kissed their children this week. How many phone calls did Duke students receive from parents this week? For some reason, we often wait to express our feelings for one another at the end, on the "death bed," but this man&amp;#39;s open grief spurred us to action in the moment. Indeed, "why wait?"&#13;
&#13;
This should not just be the purview of doctors, chaplains and counselors. This belongs to all of us, all of humankind. Put grief on the front page, and let the culture of blame do its bidding on the back pages, whether it is Virginia Tech or Iraq. Wherever there is loss of life, particularly of the magnitude of this past Monday or every Monday in Iraq, let us learn how to grieve and how to allow the families involved to grieve. Do not ask me who is to blame, or whether my child could have been spared. Ask me who my child was and then just sit there and be quiet. I will share with you that I need to kiss my child one more time. I will grieve.&#13;
&#13;
Do not let the media, however well intentioned, teach you how not to grieve. You already know how.&#13;
&#13;
&lt;i&gt;Anthony Galanos, Trinity &amp;#39;75, works at Duke University Medical Center in the Department of Medicine and the Palliative Care Service.&lt;/i&gt;&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dukechronicle.com/media/storage/paper884/news/2007/04/20/Columns/Put-Grief.On.The.Front.Page-2871376.shtml&gt; Duke Chronicle - April 20, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9641">
                <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="11626">
                <text>David Graham &lt;david.graham@duke.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13085">
                <text>Put grief on the front page</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="726">
        <name>duke</name>
      </tag>
      <tag tagId="717">
        <name>grief</name>
      </tag>
      <tag tagId="39">
        <name>media</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="595" 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="1924">
                <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="3815">
                <text>Anna Lieth</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="5793">
                <text>2007-06-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7671">
                <text>By: Anna Lieth&#13;
Posted: 4/20/07&#13;
Days after the Virginia Tech shooter was identified as a Korean-American male by national media outlets, members of Duke&amp;#39;s Asian Students Association gathered Thursday night to discuss the possible backlashes the Asian-American community may endure as a result of the gunman&amp;#39;s actions.&#13;
&#13;
During the discussion, which was sponsored by Counseling and Psychological Services and ASA, students addressed concerns about how aspects of Asian-American culture may intensify frustrations and pressures with which many students struggle on a daily basis.&#13;
&#13;
Senior Kevin Fang, outgoing president of ASA, said the event was intended to give students on campus "an opportunity to process all that is going on."&#13;
&#13;
"A lot of Korean students at Virginia Tech have gone home," he said. "Although they know that the shooting had nothing to do with race, they feel that there might be some repercussions."&#13;
&#13;
The six students present also discussed the national media&amp;#39;s coverage of the incident, questioning their decision to identify the race of Cho Seung-Hui, the shooter, and debating the relevance of this information in attempting to understand the motive for his actions.&#13;
&#13;
They discussed whether or not the shooter&amp;#39;s actions could be explained through his cultural and social identity, and talked about how situations like the one Cho faced can be prevented.&#13;
&#13;
Some students shared experiences about other Asian-American students they knew who experienced pressures and feelings of cultural disconnect which led them to lives of isolation and depression.&#13;
&#13;
Gary Glass, senior coordinator for outreach and developmental programming for CAPS, said his objective in helping to organize the discussion was to "provide an arena for things to get voiced that aren&amp;#39;t often voiced-at least not in any formal capacity."&#13;
&#13;
He added that he saw a variety of reactions expressed during the discussion.&#13;
&#13;
"If there are voices that if they were more heard would further enrich the campus, then let&amp;#39;s create a space where they can be heard," Glass said.&#13;
&#13;
He said CAPS is devoted to supporting discourse with all different types of groups on campus, and that the Virginia Tech shooting presented a need for such discourse.&#13;
&#13;
The students, however, pointed to the social stigma many students associate with counseling that may discourage students in need from seeking help.&#13;
&#13;
The discussion was not limited to East-Asian students and included South-Asian students as well.&#13;
&#13;
Junior Shawn Kwatra, a South-Asian student and incoming co-president of external affairs for Duke Diya, said he felt the topic of the discussion was important not only for East Asians but for all Asians and for international students in general.&#13;
&#13;
Feelings of alienation are not only unique to Asian-American students alone but also affect foreign students of all backgrounds, Kwatra said.&#13;
&#13;
"There is a cultural difference, and that cultural difference is something that doesn&amp;#39;t have to be East Asian," he said.&#13;
&#13;
Kwatra added that he felt the forum was a first step on the way to finding solutions that could prevent students from taking a similar path to the one Cho took.&#13;
&#13;
"I think the biggest thing we need to do is raise awareness," Kwatra said. He added that it is important for peers to be able to recognize when others are suffering or isolated.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dukechronicle.com/media/storage/paper884/news/2007/04/20/News/Asians.Fear.Alienation.Scrutiny-2871400.shtml&gt; Duke Chronicle - April 20, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9642">
                <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="11079">
                <text>Duke Chronicle </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11627">
                <text>David Graham &lt;david.graham@duke.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13086">
                <text>Asians fear alienation, scrutiny</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="713">
        <name>backlash</name>
      </tag>
      <tag tagId="726">
        <name>duke</name>
      </tag>
      <tag tagId="731">
        <name>ethnic identity</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="596" 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="1925">
                <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="3816">
                <text>Sarah Ball</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="5794">
                <text>2007-06-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7672">
                <text>By: Sarah Ball&#13;
&#13;
&#13;
By now, there isn&amp;#39;t a soul in the United States who hasn&amp;#39;t seen the greasy, glinting forehead of Cho Seung-Hui, the gunman responsible for what broadcast news and the blogosphere are terming "the Virginia Tech Massacre." His grease and his glint are everywhere, above every fold, at the top of every segment of every news program on every channel. Every anchor and every rural Virginia stringer for every paper have started every story this week with that grease, and that man.&#13;
&#13;
Then, invariably, they turn it over to us-to the cell phone cameramen, the bloggers, the Facebook status changers.&#13;
&#13;
The era of the citizen journalist, age 19, has arrived.&#13;
&#13;
This week, in this new era, I watched major news programs become veritable footage Crazy Quilts, with those same borrowed phone shots and MySpace stills casually inter-cut with traditional anchor shots. In establishing a timeline on that fateful Monday, journalists did not simply seek help from the intrepid reporters at Tech&amp;#39;s paper, The Collegiate Times. They posted interview requests to message boards, requested footage to be e-mailed or uploaded to websites, scoured community sites like Facebook and MySpace for leads.&#13;
&#13;
Fox News, which has outdone itself with glossy infotainment segments and dirge-like piano soundtracks, ran an entirely viewer-constructed package called "You Report" on the day of the shooting. You Report was comprised of cell videos of police cars and evacuating students, as well as transcribed posts from sites like Fark.com and MySpace.&#13;
&#13;
When not plumbing the citizen journalist pool for pre-made reporting, Fox itself reported on other ways students were using Internet tech-kids notifying their families of their safety via Facebook, for example, when cell phone lines were clogged.&#13;
&#13;
In the absence of order, the cyber chaos both reported the news and was the news.&#13;
&#13;
All this is perhaps unremarkable, given the prevalence of digital communication in collegiate life, and the ways in which crisis tends to unify a body of people in whatever community, digital or physical, they may lie. Yet the transition from man-on-the-street interviewing and reporting in times of crisis to this mish-mashing of homemade footage nuggets can&amp;#39;t pass without examination.&#13;
&#13;
It&amp;#39;s not only a pretty new phenomenon for major network news stations to capitalize on these particular grassroots sources (Facebook? Really?), but it also actually alters the genre of what we&amp;#39;re seeing. Ostensibly, we&amp;#39;re watching news. But since when did news have weepy soundtracks, or gunman-style storyboard art, or dozens of non-journalist reporters? Is not a Fark post or personal blog entry the kissing cousin of a televised diary-room confession, that familiar feature of reality television that red flags what we&amp;#39;re watching as staged and fictional?&#13;
&#13;
Even secondary or tertiary differences, like the nauseating bobbing of handheld-cell phone footage, shows viewers a pure and unfiltered strain of raw emotion-a guttural-ness that we perhaps more closely associated with documentary film than with the six o&amp;#39;clock news.&#13;
&#13;
Hearing the personal thoughts of students is tremendously moving to me, and has no doubt left my fellow denizens of the beautiful Old Dominion close to breakdown as we wait to hear about friends and family. Yet each time I hear or read those unadulterated thoughts, or see that dizzying cell shot, I am not left with the impression that what I am consuming is news. I am still not sure what I can safely believe.&#13;
&#13;
Documentarian takes on soft news, in both conception and delivery phases, may peter out as a trend. We may lose our taste for the sensationalized, the citizen journalist and the unapologetic commodification of fact. At the bottom of a pack of Sour Patch Kids, your tongue eventually goes numb.&#13;
&#13;
But we could also adapt. We could learn to better process what hard news means for average citizens, as we see more confessionals, read more superlative language, hear more weepy piano. Emotive, homemade news could be the final frontier in mobilizing apathetic Americans.&#13;
&#13;
Or. Jack Shafer, editor-at-large of Slate.com, wrote Tuesday in defense of journalists that there is "no tougher assignment in journalism than knocking on the door of a mother who has lost her young daughter to a killer and asking, &amp;#39;How do you feel?&amp;#39;" Earnestness and an unshakeable "self-disgust" help reporters to cope and to get the mother on the record in these situations, he continues. Besides, if networks hadn&amp;#39;t gone to the wall on this one, chasing Facebook for sob stories, viewers would have been outraged.&#13;
&#13;
I&amp;#39;m not sure that I agree. Shafer says we&amp;#39;re narrowly avoiding outrageous sensationalism overall, but I&amp;#39;m not sure that it wouldn&amp;#39;t take much more than a boost in market competition among media outlets to finally reduce feature journalism to pulp. And if that happens-if rules bend to accommodate the effectively affecting, and if the untrained citizen reporter takes over-what mourning family would dignify that imposing knock with an open door and a somber quote?&#13;
&#13;
I know that I would not.&#13;
&#13;
&lt;i&gt;Sarah Ball is a Trinity junior and former editorial page editor of The Chronicle. She is a native of Virginia. Her column runs every Thursday.&lt;/i&gt;&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dukechronicle.com/media/storage/paper884/news/2007/04/19/Columns/Documentary.News-2853094.shtml&gt; Duke Chronicle - April 19, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9643">
                <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="11080">
                <text>Duke Chronicle </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11628">
                <text>David Graham &lt;david.graham@duke.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13087">
                <text>Documentary news?</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="726">
        <name>duke</name>
      </tag>
      <tag tagId="297">
        <name>media coverage</name>
      </tag>
      <tag tagId="535">
        <name>new media</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="598" 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="1927">
                <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="3818">
                <text>Sara  Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5796">
                <text>2007-06-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7674">
                <text>By: Zak Kazzaz&#13;
Posted: 4/18/07&#13;
Two days after the Monday massacre at Virginia Tech, students nationwide remained on edge Tuesday as more details of the tragedy emerged and additional security threats occurred on several other college campuses.&#13;
&#13;
A bomb threat at the University of Tennessee at Knoxville Monday, just hours after the Virginia Tech shootings, caused university officials to evacuate two buildings there. Another threat received Tuesday at St. Edward&amp;#39;s University in Austin, Texas, prompted the university to evacuate buildings and dormitories and cancel the entire day&amp;#39;s classes.&#13;
&#13;
Although many Duke students said they are not worried about a similar catastrophe in Durham, several said that there are safety concerns for which the University cannot account.&#13;
&#13;
"What terrifies me, and what I&amp;#39;m sure terrifies most people, is that it was random," freshman Kate Van Buskirk said. "He just went in and started killing people."&#13;
&#13;
Some parents of Duke students also said they have been gripped by fear and anxiety regarding the issue.&#13;
&#13;
"I don&amp;#39;t know what can happen or what can be done," said Ruth Azimi, parent of a Duke freshman and a Virginia resident. "On campus, everybody can get in, nobody asks for IDs, and now that&amp;#39;s kind of scary."&#13;
&#13;
John Burness, senior vice president for government affairs and public relations, said Duke is currently evaluating all of its security and response practices.&#13;
&#13;
He added that the University is considering a system that can send out a mass text message to all students in case of an emergency.&#13;
&#13;
"Let&amp;#39;s remind people what&amp;#39;s going on, and dust [the emergency systems] off, and make sure they still work," Burness said.&#13;
&#13;
Junior Paul Slattery, the incoming president of Duke Student Government, said that text messages, however, might not fully address the issue.&#13;
&#13;
"What if a student doesn&amp;#39;t have service or doesn&amp;#39;t have their cell phone?" Slattery said.&#13;
&#13;
The shooter&amp;#39;s student status at Virginia Tech makes such an incident very hard to predict since universities place trust in their students, Burness said.&#13;
&#13;
"Universities tend to be open places," he said. "With the tragedy at Virginia Tech, it wasn&amp;#39;t an individual from the outside, it was somebody from the inside. I think our folks have planned for the best they can, but you can never plan for everything."&#13;
&#13;
Students said the main concern raised by recent events is the communication between the administration and Duke community.&#13;
&#13;
Several students also said they had been unhappy with Duke&amp;#39;s lack of an immediate response to the situation.&#13;
&#13;
President Richard Brodhead released a response to The Chronicle Monday night but chose not to send an e-mail to the entire community, Burness said.&#13;
&#13;
Nearby ACC colleges, such as the University of North Carolina at Chapel Hill and Wake Forest University, placed their administrators&amp;#39; responses to the shooting on the homepages of their websites. Although Brodhead&amp;#39;s response was posted on Duke&amp;#39;s website, it was not displayed on the homepage.&#13;
&#13;
Burness said the statement was released late in the day Monday because the information about Tuesday&amp;#39;s vigil service had not yet been finalized. He added that the administration thought The Chronicle was the best outlet through which to reach students about the day&amp;#39;s tragedy.&#13;
&#13;
"I would have liked an e-mail to be sent out, given that we&amp;#39;re in such close proximity and there&amp;#39;s a lot of overlap of friends," Van Buskirk said. "People just had access to the news, and personally I had so much conflicting information."&#13;
&#13;
Some parents also said an e-mail should have been sent to both students and parents.&#13;
&#13;
"Right now, I think unity is very important," Azimi said. "We have to realize that being together in this moment means a lot to everyone. An expression extending that through to the parents would have been very nice."&#13;
&#13;
Brodhead&amp;#39;s statement said the Office of Student Affairs would contact students with connections to Virginia Tech. Burness added that Resident Assistants would contribute to this process, ensuring that students are aware of the counseling services available to them.&#13;
&#13;
The majority of students interviewed by The Chronicle, however, said neither group had contacted them.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dukechronicle.com/media/storage/paper884/news/2007/04/18/News/Security.Duke.Response.Raise.Some.Concerns-2849465.shtml&gt; Duke Chronicle - 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="9645">
                <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="11081">
                <text>Duke Chronicle </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11630">
                <text>David Graham &lt;david.graham@duke.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13089">
                <text>Security, Duke response raise some concerns</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="730">
        <name>community response</name>
      </tag>
      <tag tagId="726">
        <name>duke</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="599" 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="1928">
                <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="3819">
                <text>Kristen Davis</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="5797">
                <text>2007-06-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7675">
                <text>&lt;i&gt;2 days later, campus still rattled by tragedy&lt;/i&gt;&#13;
&#13;
By: Kristen Davis&#13;
Posted: 4/18/07&#13;
&#13;
More than a hundred students, faculty and administrators bowed their heads in silence at 2 p.m. Tuesday, as the Duke Chapel bell tolled 33 times-once for each casualty of the Virginia Tech shootings.&#13;
&#13;
The interfaith vigil-which was organized by Craig Kocher, assistant dean of the Chapel and director of religious life-was held at the same time as a memorial service in Blacksburg, Va., to display solidarity between Virginia Tech and Duke.&#13;
&#13;
In his reflection, Dean of the Chapel Samuel Wells spoke about the "fragile beauty" of human life and prayed for all those affected by the tragedy.&#13;
&#13;
A Buddhist chant of compassion was offered, and Carlisle Harvard, director of the International House, urged students to be sympathetic to Korean students&amp;#39; possible anxiety over the ethnicity of the shooter, who was identified Tuesday.&#13;
&#13;
Many Duke students-including some of the more than 500 undergraduates and graduates who call Virginia home-said that in the past two days they have felt the effects of the tragedy in a variety of ways.&#13;
&#13;
"Being at Duke, we usually don&amp;#39;t have time to deal with personal issues, so it was good to have time to release and vent and have a moment of silence," said Tiffany Scott, a senior from Virginia who added that she was relieved to learn that none of her friends at Virginia Tech had been hurt.&#13;
&#13;
Alan Combs, a third-year Divinity School student who is also from Virginia, said his brother-in-law, a freshman at Virginia Tech, used his cell phone to take one of the pictures that appeared on CNN.com.&#13;
&#13;
Combs&amp;#39; brother-in-law was not injured in the shootings, but at least one of his friends was killed.&#13;
&#13;
Combs, along with several other students, said the events encouraged deeper self-reflection.&#13;
&#13;
"[The massacre] reminds everyone of the contingency of our lives, which is not necessarily something to be fearful of, but more of a reminder that I don&amp;#39;t control my own life," Combs said.&#13;
&#13;
Many students also said that although they have made an effort to keep updated with news of the incident, they do not approve of the media&amp;#39;s coverage of it.&#13;
&#13;
"I tried to avoid watching the television because instead of acknowledging the tragedy, they spend time specifying motives and who&amp;#39;s to blame," Combs said.&#13;
&#13;
Students have used Internet technology, however, to broadcast their support for their fellow college students at Virginia Tech.&#13;
&#13;
The Facebook group "We Love You, Virginia Tech (Dukies in Support of Techies on a terrible day)" had 144 members as of Tuesday night, and many students have changed their Facebook profile pictures to a black ribbon with the maroon Virginia Tech insignia. "A lot of schools are creating their own logos [with their mascots] for support," junior Nick Pardo said. "&amp;#39;Today we are all Hokies.&amp;#39;"&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dukechronicle.com/media/storage/paper884/news/2007/04/18/News/Distraught.Duke.Asks.Questions-2849464.shtml&gt; Duke Chronicle - 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="9646">
                <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="11631">
                <text>David Graham &lt;david.graham@duke.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13090">
                <text>Distraught, Duke asks questions</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="730">
        <name>community response</name>
      </tag>
      <tag tagId="726">
        <name>duke</name>
      </tag>
      <tag tagId="717">
        <name>grief</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="600" 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="1929">
                <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="3820">
                <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="5798">
                <text>2007-06-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7676">
                <text>Editorial &#13;
Posted: 4/17/07&#13;
&#13;
Horrified silence saturated campuses across the country yesterday, as the death toll at Virginia Tech climbed to at least 32 fellow students. The deadliest mass shooting in United States history can be described only as a true tragedy.&#13;
&#13;
To begin, as members of the Duke community we express our sincerest condolences to families and friends of the deceased and wounded and to the entire Virginia Tech campus. Our hearts go out to all of those in the Virginia Tech community and all of the students here at Duke who have been touched by this shocking disaster in one way or another.&#13;
&#13;
A tragedy like this makes us pause to reflect upon our own mortality. Days like yesterday-filled with images of bloodied young bodies, terrified faces and drawn guns-bring violence and death close to home. As young men and women now in college, we can only hope (although likely and sadly in vain) to never see a day like this past Monday again.&#13;
&#13;
And during such times, there is a very human urge to point fingers-to place blame on administrators for not responding effectively or efficiently. But scenarios like those that played out yesterday are extremely hard to prepare for. Hindsight is 20/20, and we cannot judge the Virginia Tech administrators with the knowledge we now have. We trust they had students&amp;#39; best interests in mind and do so still as they seek to recover from the shock and horror of a day nobody can ever really anticipate.&#13;
&#13;
Monday&amp;#39;s tragedy does, however, provide an opportunity for Duke&amp;#39;s administrators to examine their own emergency response procedures. We depend on Duke administrators to keep us informed when urgent situations arise. Although mass e-mail lists serve great informative purposes, a faster mass communication system must be devised to alert students in times of emergency. Because many students come from differing parts of the country, Duke must also devise a plan to inform families quickly or to make themselves available for inquiries in situations of mass chaos.&#13;
&#13;
As members of a media publication, in the face of this tragedy we were dismayed to find that some media outlets displayed an almost-salacious interest in this story. The Washington Post ran an article titled "Virginia Tech&amp;#39;s Reputation Had Recently Been Soaring," which inappropriately dehumanized the catastrophe as something that could have an effect on image and ranking rather than something that did have a profound effect on human lives. Similarly, a reporter at a press conference asked what sort of effect this event will have on the school&amp;#39;s admissions. Such questions were both inappropriate and unanswerable. Subjects like Virginia Tech&amp;#39;s reputation can be addressed during another, more appropriate period.&#13;
&#13;
Although yesterday&amp;#39;s tragedy is in no way comparable to the Duke lacrosse case, the response of some reporters to the Virginia Tech shooting is yet another example of a fact we as Duke students know all too well-how shallow the media can be. The media must remember there is a human element to every event, particularly this tragic event, and they should not rush superficial sensationalism nor dehumanize questions of status.&#13;
&#13;
Even though the media has immense power in portraying events and situations, we must remember that a period of coverage does not characterize or define a school in its entirety. No matter how the media portrays a singular event, our schools are not defined by one moment. They are defined by their people, their resolve and their ability to overcome.&#13;
&#13;
Virginia Tech, Duke&amp;#39;s thoughts are with you. &#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dukechronicle.com/media/storage/paper884/news/2007/04/17/Editorial/Virginia.Tech.Our.Thoughts.Are.With.You-2846256.shtml&gt; Duke Chronicle - April 17, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9647">
                <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="11632">
                <text>David Graham &lt;david.graham@duke.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13091">
                <text>Virginia Tech, our thoughts are with you</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="726">
        <name>duke</name>
      </tag>
      <tag tagId="556">
        <name>editorial</name>
      </tag>
      <tag tagId="3">
        <name>support</name>
      </tag>
      <tag tagId="157">
        <name>sympathy</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="601" 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="1930">
                <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="3821">
                <text>Anna Lieth</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="5799">
                <text>2007-06-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7677">
                <text>&lt;i&gt;200 miles away, Duke students hold vigil, admins offer support&lt;/i&gt;&#13;
&#13;
By: Anna Lieth&#13;
Posted: 4/17/07&#13;
&#13;
After violent shootings shook students and administrators on Virginia Tech&amp;#39;s campus Monday, members of the Duke community gathered last night to mourn and come to terms with the tragic events of the day.&#13;
&#13;
Just 200 miles southeast of Virginia Tech&amp;#39;s home in Blacksburg, Va., Duke students said the news sent a shock wave through the campus. For some, the shock was followed by fear for friends and loved ones in Virginia, but for others fear was displaced by disbelief and worry that a similar event could take place at the campus they call home.&#13;
&#13;
And for one group of students, the natural response to the news was to pray. About 30 students gathered on the steps of the Duke Chapel for an emotional vigil and prayer session for the victims of the shooting, their respective families and the gunman Monday night.&#13;
&#13;
"[The vigil is] not just to console people, but also to know that there is a community that is here to support people and that as a community we need to act together," said sophomore Ashley Dunfee, who attended the event. "We have a root that we act from and that ultimately should be the source of what we do and where we&amp;#39;re going."&#13;
&#13;
President Richard Brodhead, in a statement released to The Chronicle, recognized the magnitude of the events at Virginia Tech and emphasized efforts the University is making to reach out to members of both the Virginia Tech and Duke communities who were affected by the tragedy.&#13;
&#13;
"This is the deadliest campus shooting in United States history and a profoundly sad day for everyone directly affected-and the nation as a whole," Brodhead said. "On behalf of the entire Duke community, I express my condolences to those who are grieving at Virginia Tech. They are enduring a time of unspeakable loss this evening."&#13;
&#13;
John Burness, senior vice president for government affairs and public relations, said Brodhead also reached out following news of the event to Charles Steger, Virginia Tech&amp;#39;s president, to offer his sympathies.&#13;
&#13;
Brodhead said the University is working to provide support for students on Duke&amp;#39;s campus who have been personally affected.&#13;
&#13;
"Student Affairs is in the process of trying to identify every Duke student with Virginia Tech connections and to make personal contact and to offer counseling," he said. "Our Religious Life staff is also available for counseling and the Duke Chapel will be open as always for those who wish to seek a quiet place to reflect."&#13;
&#13;
The Duke Chapel and the Duke Religious Life staff have organized an interfaith prayer vigil to be held on the Chapel steps at 2 p.m. today.&#13;
&#13;
"This vigil is a small gesture at being in solidarity with those in Blacksburg," Craig Kocher, assistant dean of the Chapel and director of religious life, wrote in an e-mail to the student body last night.&#13;
&#13;
Kocher said the vigil will include a time of silence followed by prayer and a bell toll for each person who died yesterday and will conclude with an open session for students to speak about the experience. Virginia Tech will be hosting a similar event on its campus simultaneously, Kocher said.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dukechronicle.com/media/storage/paper884/news/2007/04/17/News/32.Killed.In.Virginia.Tech.Massacre-2846222.shtml&gt; Duke Chronicle - April 17, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9648">
                <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="11082">
                <text>Duke Chronicle </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11633">
                <text>David Graham &lt;david.graham@duke.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13092">
                <text>32 killed in Virginia Tech massacre</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="730">
        <name>community response</name>
      </tag>
      <tag tagId="726">
        <name>duke</name>
      </tag>
      <tag tagId="582">
        <name>university response</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="597" 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="1926">
                <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="3817">
                <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="5795">
                <text>2007-06-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7673">
                <text>Editorial&#13;
Posted: 4/19/07&#13;
&#13;
When news of the Virginia Tech massacre broke Monday, to say that students across the country were on edge is an understatement. The horror and randomness of the event forced students to take a step back and examine their own campuses and ask, "Are we safe?"&#13;
&#13;
And members of the Duke community began to question what the safety and notification protocol would be if something of this magnitude occurred here. Many wondered what, if any, steps Duke was taking to tighten security Monday. Those with friends and family at Virginia Tech asked what resources were available for them here on campus. But answers to these queries were virtually impossible to discern.&#13;
&#13;
President Richard Brodhead released a statement to The Chronicle late Monday night, which was also published on the Duke News website. In the statement, Brodhead expressed his condolences to the Virginia Tech community and announced an interfaith vigil that would be held Tuesday at the Duke Chapel.&#13;
&#13;
But nowhere in the statement was there mention of Duke&amp;#39;s own security status. Moreover, while Brodhead said Student Affairs was trying to contact "every student with Virginia Tech connections," there is no way they could identify every student with a "connection." As such, those students with friends or acquaintances at Virginia Tech who the administration did not know about-as well as those simply overwhelmed by the tragedy-were told only that Religious Life staff and the Chapel were available for support. There was no mention of other, non-religious resources, such as augmented, emergency Counseling and Psychological Services, that could benefit all concerned students regardless of religious orientation.&#13;
&#13;
Most troubling, however, was the fact that Brodhead&amp;#39;s statement was not sent to the Duke community. It was published in The Chronicle, but no one could read it until Tuesday morning, nearly 24 hours after the massacre occurred. And while technically online, the statement was buried on the Duke News site, which is not a major source of information for most students.&#13;
&#13;
Many schools posted statements on their main websites. Still others, like The George Washington University, sent mass e-mails to students and their families discussing safety protocol.&#13;
&#13;
The Duke administration erred in its response. On a day when colleges and universities across the country stood still, shocked by how suddenly and violently an academic haven much like their own had been violated, Duke was silent. On a day when students and parents, faculty and staff wanted reassurance of their own safety and an assertion that the University stood in support of its ACC counterpart, Duke was largely absent.&#13;
&#13;
This is not to say there was no campus response. Religious organizations did an excellent job coordinating Tuesday&amp;#39;s interfaith vigil and several religious groups sent out e-mails to their members offering support. Such organizations, however, only touch a certain percentage of students; the Duke community as a whole was still left mostly in the dark about the University&amp;#39;s security and support responses.&#13;
&#13;
As Duke students, we wanted a prompter, more informative, more widely disseminated statement from the administration. In such situations, when our community is questioning its own well-being and mourning the damage done to another school&amp;#39;s sense of security and self, we want to hear Duke&amp;#39;s leadership loud and clear.&#13;
&#13;
We urge the administration to consider new and better ways to inform the community if it is threatened. And we appreciate Tuesday&amp;#39;s interfaith vigil and its visible community power. But we still missed and were puzzled by the lack of a simple, widely available statement of assurance and support.&#13;
&#13;
While we hope that such a statement will not be needed in the future, if it is needed, we look to the administration to stand as a stronger pillar of information, of comfort, and of guidance.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dukechronicle.com/media/storage/paper884/news/2007/04/19/Editorial/Dukes.Response.To.Vatech.Tragedy.Lacking-2853092.shtml&gt; Duke Chronicle - April 19, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9644">
                <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="11629">
                <text>David Graham &lt;david.graham@duke.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13088">
                <text>Duke&amp;#39;s response to VaTech tragedy lacking</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="618">
        <name>campus response</name>
      </tag>
      <tag tagId="726">
        <name>duke</name>
      </tag>
      <tag tagId="556">
        <name>editorial</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="604" 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="1933">
                <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="3824">
                <text>Shamus Williams</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="5802">
                <text>2007-06-26</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7680">
                <text>By: Shamus Williams&#13;
   &#13;
&#13;
(April 16) Well, I&amp;#39;m back safe and sound in my off-campus apartment. It has been a very scary and hectic past couple of hours to say the least.&#13;
&#13;
We were released at noon, but it was not an assisted evacuation as we were hearing that it would be. I was a little apprehensive that we were not assisted in leaving the campus, and I was constantly looking over my shoulder.&#13;
&#13;
I have never seen so many police officers in my life. There were police cars, ambulances, SWAT vehicles and other emergency vehicles lining every street possible that I could see. There were students running to their cars and it seemed every person was on their cell phone trying to call friends and family.&#13;
&#13;
It is definitely a scary time on campus. I am usually not one to worry about these things, but this has surpassed anything that the mind can even fathom. This is probably the most scared I have ever been in my life. The police made things seem somewhat safe, but I&amp;#39;m not sure all the police in the world could have made things seem perfectly safe.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://www.biglicku.com/blu/Stories/StoryDisplayPage.aspx?Title=Released%20from%20lockdown&amp;ID=186&gt;Big Lick U - April 16, 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="9651">
                <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="11636">
                <text>Chris Winston &lt;Chris.Winston@biglicku.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13095">
                <text>Released from lockdown</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="732">
        <name>big lick u</name>
      </tag>
      <tag tagId="733">
        <name>student response</name>
      </tag>
      <tag tagId="734">
        <name>vt campus</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="603" 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="1932">
                <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="3823">
                <text>Shamus Williams</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="5801">
                <text>2007-06-26</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7679">
                <text>By: Shamus Williams&#13;
&#13;
&#13;
(April 16 -- 11:55 a.m.) I am on campus as we speak and am under lockdown in Shanks Hall, which is located on the opposite side of campus from the shootings. But it is still too close for comfort.&#13;
&#13;
I was in class, working on a paper, when I got an e-mail saying that a shooting had occurred on campus. It was about 20 to 25 minutes later when we received word that the gunman was loose and we were on lockdown. It is a pretty scary thing, because of the recent bomb threats and the whole William Morva thing that happened earlier in the year.&#13;
&#13;
The students in my class have been pretty calm. Everybody is trying to reach friends and family and let them know that we are OK and that nothing has happened on this side of campus.  We have all been sending instant messages trying to find information, and there are plenty of rumors swirling. We are all trying to figure out what is real and what is not.&#13;
&#13;
There are plenty of different emotions flying around the room.  Some people are trying to make jokes to lighten the mood. Others are trying to scour the Web for information (I would fall into that category). Somehow, others are still trying to get their paper done. I&amp;#39;m definitely not trying to do anything associated with schoolwork with this thing going down.&#13;
&#13;
I really think that it will be a long time before we are let off campus, and the longer they keep us in here, the more worried we are all becoming.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://www.biglicku.com/blu/Stories/StoryDisplayPage.aspx?Title=In%20lockdown%20in%20Shanks%20Hall&amp;ID=185&gt; Big Lick U - April 16, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9650">
                <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="11635">
                <text>Chris Winston &lt;Chris.Winston@biglicku.com&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13094">
                <text>In lockdown in Shanks Hall</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="732">
        <name>big lick u</name>
      </tag>
      <tag tagId="733">
        <name>student response</name>
      </tag>
      <tag tagId="734">
        <name>vt campus</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
