<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://www.april16.vtlibraries.net/items?output=omeka-xml&amp;page=69" accessDate="2026-04-13T10:15:25+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>69</pageNumber>
      <perPage>20</perPage>
      <totalResults>1884</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="743" 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="2062">
                <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="3953">
                <text>Alexander Trowbridge</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="5931">
                <text>2007-07-16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7809">
                <text>By: Alexander Trowbridge, Staff Writer&#13;
Posted: 4/25/07&#13;
&#13;
The shooting at Virginia Tech last week put the gun control issue back in the national public forum.&#13;
&#13;
While Virginia Gov. Tim Kaine dismissed taking political advantage of the incident as deplorable, both pro-gun groups and those advocating gun control rallied for change.&#13;
&#13;
Barbara Hohlt, executive director of States United to Prevent Gun Violence, said stricter gun laws could have saved lives at Va. Tech.&#13;
&#13;
"We do a very poor job in this country at doing adequate background checks."&#13;
&#13;
Pro-gun advocates attacked gun-free safe zones such as the Va. Tech campus, which they claim prevented victims from protecting themselves.&#13;
&#13;
Carl Abbe, the owner and president of Calibers Indoor Gun Range in Greensboro, said gun-free zones let criminals know that no one is there to stop them.&#13;
&#13;
Abbe said Va. Tech should consider arming and training select members of the campus community to defend their fellow classmates.&#13;
&#13;
"If that one professor who blocked the door had had a handgun, he would have been able to do more than just block the door," Abbe said. "He would have been able to stop that man."&#13;
&#13;
The N.C. House passed a bill on Thursday that would allow judges to carry concealed weapons.&#13;
&#13;
Rep. Walter Church, D-Burke, sponsored the bill and said it was a response to the shooting of a judge in a courtroom in Atlanta last year.&#13;
&#13;
"The judges that I&amp;#39;ve talked to thought it was a good idea," Church said, adding that even those who don&amp;#39;t carry guns appreciate the attention to their security.&#13;
&#13;
The passage of the bill just days after the shooting at Va. Tech concerned some N.C. residents.&#13;
&#13;
Lisa Price, executive director of the North Carolinians Against Gun Violence Education Fund, said courtrooms already are protected.&#13;
&#13;
"In general, we dislike putting guns in more places," Price said.&#13;
&#13;
The issue of gun control is complex, and in North Carolina it is not always divided along party lines.&#13;
&#13;
Though Church sponsored the bill allowing judges to carry concealed weapons, he said he supports gun control and restrictions. He said the lack of a waiting period to purchase hand guns in Virginia is ridiculous.&#13;
&#13;
"I would support someone having a waiting period, especially those with mental cases."&#13;
&#13;
Rep. Verla Insko, D-Orange, voted against Church&amp;#39;s bill. However, she said she would oppose restricting everyone with a history of mental illness from purchasing a gun.&#13;
&#13;
"That is a very broad category of illnesses," she said, adding that while those at risk for violence should not be eligible to purchase handguns, not everyone with a mental illness is violent.&#13;
&#13;
-- &#13;
&#13;
Original Source:&lt;a href=ttp://media.www.dailytarheel.com/media/storage/paper885/news/2007/04/25/StateNational/Shooting.Amps.Up.Gun.Debate-2878831.shtml&gt;The Daily Tar Heel - April 25, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9780">
                <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="11760">
                <text>Kevin Schwartz &lt;kschwartz@unc.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13203">
                <text>Shooting amps up gun debate</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="87">
        <name>gun control</name>
      </tag>
      <tag tagId="857">
        <name>unc</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="742" 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="2061">
                <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="3952">
                <text>Kellen Moore</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="5930">
                <text>2007-07-16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7808">
                <text>By: Kellen Moore, Staff Writer&#13;
Posted: 4/25/07&#13;
&#13;
With last week&amp;#39;s Virginia Tech shootings still fresh in the minds of many, UNC officials are looking to evaluate residence hall safety as one area of emphasis.&#13;
&#13;
With about 7,700 students living on campus, resident advisers often are the first line of defense in emergencies.&#13;
&#13;
At Va. Tech, Ryan Clark, an RA in West Ambler Johnston Hall, was one of the first of 32 victims killed in last week&amp;#39;s shooting rampage. He was investigating a loud noise when he met the gunman in a hallway.&#13;
&#13;
Kyle Jordan, coordinator for student leadership and programming and a member of the committee responsible for training RAs to deal with emergencies, said that while the training RAs receive is extensive, it deals only with situations within the confines of everyday life.&#13;
&#13;
"We don&amp;#39;t train them to deal with any type of assailant that might have a weapon," Jordan said.&#13;
&#13;
At UNC, RAs are responsible for a section of a residence hall, and they are placed throughout 14 campus communities.&#13;
&#13;
Training is held two weeks before the semester starts, and it includes preparation for emergencies such as fires, medical accidents and sexual assault, among others.&#13;
&#13;
RAs also are instructed how to deal with roommate conflicts and how to approach students who they suspect might be experiencing emotional problems.&#13;
&#13;
"Really, it is a top-down process from the highest administrators living in a building down to the RAs," Jordan said.&#13;
&#13;
"Everybody is a part of crisis management, and we do it very well."&#13;
&#13;
But despite his confidence in those guidelines, Jordan said there has been talk about UNC reviewing safety procedures more.&#13;
&#13;
"There&amp;#39;s no time that we&amp;#39;re going to say our policies are 100 percent," Jordan said.&#13;
&#13;
Kareemah Lewis, a former RA in the Olde Campus Upper Quad Community, said the training she received came in handy.&#13;
&#13;
"We were prepared because we had specific training in that area, in dealing with a crisis - not specifically somebody coming to shoot, but students hurting themselves," she said.&#13;
&#13;
Lewis also said the training informed her of resources that most residents are not aware of, especially how to contact public safety officials directly. But she said there still is room to tweak the training.&#13;
&#13;
"I think we could improve on communication. ... Maybe creating new technology-savvy ways to communicate other than e-mail," she said.&#13;
&#13;
One focus of the training is explaining that RAs should be aware of their surroundings and report anything out of the ordinary.&#13;
&#13;
"I think Virginia Tech was a wake-up call to a lot of RAs that when we do see suspicious people ... to take it more seriously and that unexpected things can happen," said Laura Lilly, an RA in Kenan Community.&#13;
&#13;
Gay Perez, associate director of the Department of Housing and Residential Education, said methods used to respond to emergencies vary.&#13;
&#13;
"Sometimes you might stay in place; sometimes you might evacuate. Housing will take its cues from first responders, police or whoever is in charge," she said.&#13;
&#13;
"Everyone thinks they&amp;#39;re prepared until something like Virginia Tech happens. ... You can only plan so much."&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dailytarheel.com/media/storage/paper885/news/2007/04/25/University/Tragedy.May.Cause.Ra.Training.Review-2878794.shtml&gt; The Daily Tar Heel - April 25, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9779">
                <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="11107">
                <text>The Daily Tar Heel</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11759">
                <text>Kevin Schwartz &lt;kschwartz@unc.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13202">
                <text>Tragedy may cause RA training review</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="859">
        <name>ra training</name>
      </tag>
      <tag tagId="857">
        <name>unc</name>
      </tag>
      <tag tagId="860">
        <name>weapons in resident halls</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="741" 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="2060">
                <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="3951">
                <text>James F. Eby</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="5929">
                <text>2007-07-16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7807">
                <text>Posted: 4/26/07&#13;
&#13;
TO THE EDITOR:&#13;
&#13;
In the wake of the tragedy at Virginia Tech, we have the opportunity to reach out and touch the lives of the students affected by this tragedy. Eve Carson made the suggestion to find someone at Virginia Tech to "adopt".&#13;
&#13;
For student groups, search for a "sister organization." Student leaders, look up your counterparts in Blacksburg. Then, make some contact with them. Let them know they are in our thoughts. Need somewhere to get started? Get a shoe box, throw some candy and some pictures in it, and then write a letter. Be creative. Be genuine. Be yourself.&#13;
&#13;
If you need any help, we are personally available and extremely willing to do anything we can. We are not experts, but we will call upon what resources we have. We are available by e-mail, Facebook and phone. We also urge you to call upon your fellow students here in Chapel Hill and take advantage of this opportunity to grow closer to those in the UNC community as well.&#13;
&#13;
As the school year draws to a close, keep in mind that time is of the essence. This is a call to action. We know many people feel helpless, but this is simple, cheap and easy yet personal way to positively affect the Virginia Tech community.&#13;
&#13;
&#13;
James F. Eby&#13;
Carolina Advocacy, Executive Branch&#13;
&#13;
Logan Liles&#13;
Carolina Advocacy, Executive Branch&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://media.www.dailytarheel.com/media/storage/paper885/news/2007/04/26/LettersToTheEditor/Take-Time.To.Reach.Out.To.Someone.At.Virginia.Tech-2881893.shtml&gt;The Daily Tar Heel - April 26, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9778">
                <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="11106">
                <text>The Daily Tar Heel</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11758">
                <text>Kevin Schwartz &lt;kschwartz@unc.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13201">
                <text>Take time to reach out to someone at Virginia Tech</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="723">
        <name>outreach</name>
      </tag>
      <tag tagId="3">
        <name>support</name>
      </tag>
      <tag tagId="857">
        <name>unc</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="740" 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="2059">
                <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="3950">
                <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="5928">
                <text>2007-07-16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7806">
                <text>&lt;b&gt;Shooting sparks national debate&lt;/b&gt;&#13;
&#13;
By: Eric Johnson, Senior Writer&#13;
Posted: 5/24/07&#13;
&#13;
Congress is wading into the turbulent debate about campus safety in the aftermath of last month&amp;#39;s shootings at Virginia Tech and is considering possible changes to federal laws governing student privacy.&#13;
&#13;
A bill to loosen disclosure restrictions for campuses dealing with at-risk students is already attracting attention in the House, and similar measures are being drafted in the Senate.&#13;
&#13;
Meanwhile, the UNC-system will consider during the next few months whether to back any move to alter long-standing federal policy about the disclosure of student health records.&#13;
&#13;
"In Washington, there&amp;#39;s a lot of attention on this issue," said Kimrey Rhinehardt, UNC-system vice president for federal relations. "I think that certainly now, more than ever, the university is going to be a part of that discussion."&#13;
&#13;
The April 16 shooting of 32 students at Virginia Tech by a classmate with a documented history of mental instability has prompted colleges across the country to reevaluate their security procedures.&#13;
&#13;
It has also drawn national attention to the vague guidelines that govern when and how campuses can respond to threatening or self-destructive behavior by a student.&#13;
&#13;
Federal law prohibits universities from contacting a student&amp;#39;s parents unless the student presents an imminent danger to himself or others, a standard that is open to wide interpretation. In recent years, campuses have been sued for taking preemptive measures against troubled students in some instances and for failing to take preemptive action in others.&#13;
&#13;
As a result, most campus administrators have welcomed the opportunity to review the existing statutes.&#13;
&#13;
"I think there&amp;#39;s enough confusion now that most institutions would tell you that it could hardly get any worse," said Becky Timmons, assistant vice president for government relations at the American Council on Education.&#13;
&#13;
"Institutions may assume that scrutinizing this legislation would lend some greater clarity to the issue," she said. "There are some very legitimate reasons for the laws we have the on books, but they do create grey areas for campuses."&#13;
&#13;
The UNC-system has created a task force that will explore those grey areas, along with a whole host of other safety issues. The group will represent a variety of constituencies, from chancellors and legal counsel to students and staff members.&#13;
&#13;
Only after the task force has weighed in with recommendations - scheduled for sometime in September - will the system consider lobbying for any changes to federal law.&#13;
&#13;
"Because the issues of privacy and disclosure are so delicate, it&amp;#39;s going to take a lot of people thinking about this to come with the right balance," Rhinehardt said.&#13;
&#13;
In announcing the safety task force earlier this month, university officials stressed the need to avoid any hasty reactions.&#13;
&#13;
Noting that UNC campuses are statistically far safer than North Carolina as a whole, System President Erskine Bowles said the task force would proceed cautiously with any recommendations.&#13;
&#13;
"We have to really make sure we think through these issues and don&amp;#39;t just react," Bowles said. "We have to do things that make good common sense."&#13;
&#13;
It is unclear whether the task force will finish its work in time for UNC to weigh in effectively at the federal level. It will depend on how quickly Congress moves to revisit the privacy and disclosure issues.&#13;
&#13;
The state of Virginia has formed its own high-profile commission to study the shooting at Virginia Tech, and Timmons said that might prompt federal lawmakers to take a more deliberative approach.&#13;
&#13;
"I think there is a little bit of a sense of proceeding slowly out of a sense of respect for the Virginia Tech situation," she said.&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dailytarheel.com/media/storage/paper885/news/2007/05/24/StateNational/Student.Privacy.Under.Scrutiny-2907006.shtml&gt;The Daily Tar Heel - May 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="9777">
                <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="11757">
                <text>Kevin Schwartz &lt;kschwartz@unc.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13200">
                <text>Student privacy under scrutiny</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="465">
        <name>mental health</name>
      </tag>
      <tag tagId="464">
        <name>privacy</name>
      </tag>
      <tag tagId="857">
        <name>unc</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="739" 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="2058">
                <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="3949">
                <text>Elyse McCoy</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="5927">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7805">
                <text>By: Elyse McCoy, Staff Writer&#13;
Posted: 7/5/07&#13;
&#13;
The University is in the initial stages of development for the Public Information Emergency Response Communication Management System, or PIER, an Internet-based communication tool used to help relay emergency-related content and messages.&#13;
&#13;
Students, faculty and staff will be alerted in the event of a crime, unexpected weather emergency or other event that requires immediate warning through a secure Web page that will look like a regular UNC-Chapel Hill Web page. Using the PIER system, campus security officials can post key emergency materials; templates of information prepared in advance about certain scenarios; detailed information about how to reach the University&amp;#39;s key constituents, including students, faculty and staff; and background information about the campus, maps and emergency policies and procedures.&#13;
&#13;
PIER also provides the capability to track and respond to questions from key stakeholders or the general public.&#13;
&#13;
Following the Virginia Tech shootings, the University has strengthened its already extensive plans and procedures, but plans for developing a contract with the PIER vendor for the 16-campus UNC system have been in existence since the aftermath of Hurricane Katrina.&#13;
&#13;
UNC-Wilmington and UNC-Charlotte have been the most involved campuses to date, with Wilmington being designated the first campus to begin its PIER-related work and training several months ago.&#13;
&#13;
The PIER system&amp;#39;s clients include the U.S. Coast Guard - which used the system during Hurricane Katrina, the University of Houston, and several major corporations.&#13;
&#13;
UNC-Chapel Hill has just recently begun training a small group of key people most likely to be involved with using PIER as a communication tool in an emergency situation, including those involved in University relations, public safety and information technology departments.&#13;
&#13;
"We have started working on training issues as the spring semester was winding down and will continue over the summer," said Mike McFarland, the director of University communications.&#13;
&#13;
"We believe PIER can help complement resources the University already uses and are developing, such as a siren system and the Rave system to communicate quickly, accurately and effectively with students, faculty, staff and other University-related audiences or the general public," McFarland said. Unlike the PIER system, which is primarily focused around managing information in an emergency, the Rave system is part of a broader effort to extend the campus to mobile phones.&#13;
&#13;
"Rave has much more day-to-day impact on the lives of our students," said Brian Payst, the director of Technology &amp; Systems Support.&#13;
&#13;
"We certainly can, and will if needed, use Rave to send emergency broadcast messages, but it does much, much more than that for us."&#13;
&#13;
The Rave system is used to provide bus arrival times for all the Chapel Hill Transit routes and stops, the ability to read UNC e-mail, information from slice.unc.edu about student events, Blackboard alerts, Rave Guardian (an enhanced personal safety service), group messaging, polls and more on students&amp;#39; mobile phones. The University&amp;#39;s partnership with Rave Wireless also enables the University to offer a steeply discounted cell phone program to students living in residence halls on campus in order to allow access to these services at the lowest possible cost.&#13;
&#13;
The campus Emergency Notification committee has been coordinating efforts to integrate the PIER and Rave systems as much as possible to reduce duplication where it exists.&#13;
&#13;
"We plan to integrate the information coming from PIER into a spot in the UNC mobile phone interface so you can easily check for closings or other important announcements coming from PIER," Payst said.&#13;
&#13;
Payst does not think that the implementation of both the PIER system and the Rave system will be confusing to either students or their parents.&#13;
&#13;
"They do different things, so we do not think it will be all that confusing, and we will work hard to clearly communicate the distinctions where they arise."&#13;
&#13;
--&#13;
&#13;
Original Source: &lt;a href=http://media.www.dailytarheel.com/media/storage/paper885/news/2007/07/05/University/Emergency.Management.Comes.To.Unc-2921381.shtml&gt;The Daily Tar Heel - July 05, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9776">
                <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="11105">
                <text>The Daily Tar Heel</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11756">
                <text>&#13;
Kevin Schwartz &lt;kschwartz@unc.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13199">
                <text>Emergency management comes to UNC</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="858">
        <name>emergency response</name>
      </tag>
      <tag tagId="857">
        <name>unc</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="738" 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="2057">
                <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="3948">
                <text>Alex Fineman</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="5926">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7804">
                <text>Monday&amp;#39;s tragic shooting at Virginia Tech is the kind of event that provokes a nationwide outpouring of support, sympathy and questions - questions about the killer, his motives and what could have been done to prevent 33 students from needlessly dying.&#13;
&#13;
Campus security, in particular, has received a lot of scrutiny. Why were classes allowed to continue after shots were fired and students were killed early in the morning?&#13;
&#13;
The problem with such questions is that it is easy to ask them accusatorily in the wake of so many deaths. When nobody dies - when security clamps down on threatening behavior before it reaches such a drastic extreme - the questions asked are very different.&#13;
&#13;
In November, here at UCLA, there was another incident that received nationwide coverage - the use of a Taser gun on a student.&#13;
&#13;
Hundreds of people are in the campus library late at night, paying little attention to their surroundings. Per school policy, campus security officers perform student ID checks. One man refused to show his ID.&#13;
&#13;
Now stop and think: Is this man an unarmed student or an unstable psychotic with a cache of weapons in his backpack? At this point, you don&amp;#39;t know and neither do the police. The police only know that he is uncooperative and cannot prove that he has a right to be in the library. So they use their Taser guns.&#13;
&#13;
If the police had found weapons in the student&amp;#39;s backpack, they would have been hailed as heroes. Instead, they were vilified.&#13;
&#13;
We know the odds are against the student being a homicidal maniac, even if he is uncooperative with police. But should the police have taken a chance against an uncooperative individual?&#13;
&#13;
When a campus is open, like UCLA&amp;#39;s, anyone can walk onto school grounds armed to the teeth. The beeper may go off when you try to carry a book out of the building, but not if you walk in with a pair of handguns.&#13;
&#13;
The aphorism "better safe than sorry" exists for a reason.&#13;
&#13;
Alex Fineman&#13;
UCLA law student&#13;
&#13;
-- &#13;
&#13;
Original Source: &lt;a href=http://www.dailybruin.ucla.edu/news/2007/apr/23/letters_editor6/&gt;The Daily Bruin - 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="9775">
                <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="11104">
                <text>The Daily Bruin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11755">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13198">
                <text>Letters to the Editor - Shootings shed light on Taser incident</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
      <tag tagId="856">
        <name>weapons on campus</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="735" 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="2055">
                <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="3946">
                <text>Craig Chi</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="5924">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7802">
                <text>Wednesday, April 18, 2007&#13;
&#13;
The tragic event that took place at Virginia Tech on Monday raises many questions in students&amp;#39; minds: How safe are we? What measures are in place to keep us safe from harm while we&amp;#39;re in class, in our dorms, or walking across campus?&#13;
&#13;
Heaven forbid that a shooting should occur on our campus, but if it did, what would you do? What could you do? The truth is ... not much.&#13;
&#13;
Current law, as well as UC policy, prohibits you from providing yourself with a means of self-defense.&#13;
&#13;
UCLA&amp;#39;s weapons policy prohibits common defensive items. Like Virginia Tech, UCLA doesn&amp;#39;t allow firearms on campus even for law-abiding individuals trained and licensed to carry a concealed weapon.&#13;
&#13;
Even if UCLA did, California state law forbids it.&#13;
&#13;
As UC students, we&amp;#39;re forced to remain unarmed and defenseless.&#13;
&#13;
Because of this, we can only hope that suspension or expulsion will serve as a sufficient deterrent for those that mean to harm us. Forgive me if I&amp;#39;m less than confident.&#13;
&#13;
While you could always call the police if such a situation were to occur, their response times are measured in minutes.&#13;
&#13;
However, in life-threatening situations like the shooting at Virginia Tech, survival is measured in seconds.&#13;
&#13;
A single armed student or faculty member could have quickly ended - if not prevented - any and all school shootings.&#13;
&#13;
It&amp;#39;s time for change. It&amp;#39;s time to rethink the "feel-good" legislation that is leaving thousands of innocent people defenseless.&#13;
&#13;
It&amp;#39;s time to let our state and national representatives know that we want to be safe. It&amp;#39;s time that we let university students and public school teachers protect themselves and those in their care.&#13;
&#13;
I urge you to call, write a letter or send an e-mail to your representatives to ask them to make public schools and college campuses places where law-abiding citizens can defend themselves.&#13;
&#13;
Craig Chi&#13;
UCLA graduate student, Electrical Engineering&#13;
&#13;
-- &#13;
&#13;
Original Source: &lt;a href=http://www.dailybruin.ucla.edu/news/2007/apr/18/letters_editor8/&gt;The Daily Bruin - April 18, 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="9773">
                <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="11103">
                <text>The Daily Bruin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11753">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13196">
                <text>Letters to the Editor: Self-defense could stop violence</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="853">
        <name>selfdefense</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="734" public="1" featured="0">
    <itemType itemTypeId="1">
      <name>Document</name>
      <description>A resource containing textual data.  Note that facsimiles or images of texts are still of the genre text.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2054">
                <text>Sara  Hood</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3945">
                <text>Lara Loewenstein</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5923">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7801">
                <text>&lt;b&gt;UCLA, other schools should take time now to improve their emergency alert systems&lt;/b&gt;&#13;
&#13;
By Lara Loewenstein&#13;
Thursday, April 19, 2007&#13;
&#13;
There are a few questions that have been circulating with regard to the Virginia Tech shootings. How many lives could have been saved if the administration had reacted differently? How would UCLA respond if such an event happened?&#13;
&#13;
It&amp;#39;s pretty obvious that the administration of Virginia Tech could have responded differently. But what&amp;#39;s more important than the mistakes the administration at Virginia Tech made is how Virginia Tech and other universities can learn from these mistakes.&#13;
&#13;
In response to the shooting, Interim Chancellor Norman Abrams released a statement on Monday. It began with information that should go without saying - student and faculty safety is a top priority - and then went on to say that UCPD officers are trained to handle shooting scenarios.&#13;
&#13;
But that doesn&amp;#39;t answer my questions because that isn&amp;#39;t the issue. The issue was that students weren&amp;#39;t and couldn&amp;#39;t have been notified of the earlier shooting - when the gunman killed two people in the dormitories - in enough time to allow them to make an informed choice to not go to campus. There wasn&amp;#39;t even a system in place to contact students if the administration at Virginia Tech had decided to close the campus.&#13;
&#13;
Sure, the police officers thought it was a domestic violence issue and that the suspect had left campus, but now that the administration at Virginia Tech knows better, it should be apologizing for the wrong choices it made and its lack of an emergency plan. Instead, it&amp;#39;s just making excuses.&#13;
&#13;
One of the excuses Virginia Tech President Charles W. Steger gave for not closing down the campus and canceling classes was that he didn&amp;#39;t know what the alternative to students coming to class would be.&#13;
&#13;
One has to ask, shouldn&amp;#39;t such an alternative be included in an emergency plan in case of such an incident? Shouldn&amp;#39;t the alternative have been known, available and rehearsed? After all, student and faculty safety is a top priority, is it not?&#13;
&#13;
And does UCLA have such a plan?&#13;
&#13;
Abrams&amp;#39; statement went on to say, "UCLA has an emergency response team and protocols in place to notify the campus community in the event of any circumstances requiring emergency action, such as the closing of the campus."&#13;
&#13;
This gives me the impression that UCLA has such a plan in place. However, what that plan actually is befuddles me because what exactly would UCLA have been able to do differently?&#13;
&#13;
They could have sent the warning e-mail out earlier, sure. But I don&amp;#39;t usually wake up in the morning with the thought of checking my e-mail to see if there&amp;#39;s a gunman on campus.&#13;
&#13;
And as for students whose Internet was down, or don&amp;#39;t have home access, they wouldn&amp;#39;t have received the message at all.&#13;
&#13;
I suppose they could start calling people, but it seems a little unrealistic to call more than 40,000 students and faculty. Besides, I don&amp;#39;t think UCLA even has my cell phone number.&#13;
&#13;
In that case, they wouldn&amp;#39;t even reach me - they&amp;#39;d reach my parents&amp;#39; house, and it&amp;#39;s likely they wouldn&amp;#39;t even be home.&#13;
&#13;
There are concerns that if universities went overboard with safety regulation then students and faculty would have to compromise certain freedoms. But there are plans that wouldn&amp;#39;t impede everyday life that would be more effective than contacting students by e-mail.&#13;
&#13;
According to the Washington Post, a campus spokesperson said that earlier in the semester, Virginia Tech had been working with a company with which they could contact students via text message in case of an emergency. Students would be required to submit their cell phone numbers when they registered for classes.&#13;
&#13;
Whether this plan is going to be carried through wasn&amp;#39;t said.&#13;
&#13;
Considering the number of people who own cell phones, and how often we check them for messages or otherwise, this could reach more people than an e-mail message would.&#13;
&#13;
I don&amp;#39;t know what plan Abrams was referring to in his statement, but I hope it&amp;#39;s better than the one Virginia Tech had in place. And if it isn&amp;#39;t, I hope this so-called plan is reworked - maybe to include a text message notification system or otherwise.&#13;
&#13;
In fact, the president of the University of California, Robert C. Dynes, said in his statement about the shootings that all UC campuses would be reviewing their security policies. He mentioned to the Daily Bruin that this system might incorporate emergency text messages.&#13;
&#13;
This provides some comfort - as long as it happens soon. The next biggest shooting in modern American history could happen anytime, and it could happen on this campus. I want to know that we&amp;#39;re ready for it.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.dailybruin.ucla.edu/news/2007/apr/19/emuniversities_must_learn_handling_shootingem/&gt;The Daily Bruin - April 19, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9772">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11752">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13195">
                <text>Universities must learn from handling of shooting</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="606">
        <name>crisis response</name>
      </tag>
      <tag tagId="852">
        <name>security concerns</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
      <tag tagId="582">
        <name>university response</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="733" 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="2053">
                <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="3944">
                <text>Blair Socci  </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="5922">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7800">
                <text>By Blair Socci&#13;
Thursday, April 19, 2007&#13;
&#13;
In the aftermath of the shootings that occurred at Virginia Tech earlier this week, the University of California is now re-evaluating its own security policies.&#13;
&#13;
Authorities have been quick to assure the UCLA community that they are doing everything they can to assess current security measures, as well as to actively continue to seek out ways to improve safety.&#13;
&#13;
"What happened at Virginia Tech is a reminder that nobody is immune from violence and that we all need to remain vigilant in order to protect ourselves and our institution," UCLA spokesman Phil Hampton said.&#13;
&#13;
"In light of what has happened at Virginia Tech, this campus, as well as other UC campuses, will be solidifying (its) security policies."&#13;
&#13;
In the coming days and weeks, the university plans to review its policies and continue to examine new information that becomes available, UC President Robert Dynes said in a statement Monday.&#13;
&#13;
"As we learn more about the specific circumstances of the Virginia Tech shootings, we will apply those lessons as well," he said in the statement.&#13;
&#13;
At UCLA, authorities are currently devising new ways to improve mediums of response to emergencies and communication with the community, as well as providing care for people following any major incident.&#13;
&#13;
Some new methods being reviewed include notifying students personally on cell phones either by sending text messages or making phone calls, Hampton said.&#13;
&#13;
Another area that is being reviewed is the university&amp;#39;s psychological services.&#13;
&#13;
"We are also giving increased attention to student psychological support services and have begun phasing additional funding for these programs," Dynes said in his statement.&#13;
&#13;
But UCLA officials emphasized that the university already has various ways of dealing with an emergency.&#13;
&#13;
"The university has in place measures to guide us in case of an emergency," Hampton said.&#13;
&#13;
He said UCLA has regular training sessions in which they practice how to respond to and communicate during an emergency, as well as electronic means of notifying the community.&#13;
&#13;
"We have emergency mass e-mail, Web sites such as Gateway and MyUCLA that we can update, recorded telephone information and the campus radio station, which has recently been changed to 24-hour availability," Hampton said.&#13;
&#13;
University police also currently received training on how to respond to an emergency, said Nancy Greenstein, director of police community services for UCPD.&#13;
&#13;
"Our officers are highly trained individuals," she said.&#13;
&#13;
This training includes drills, special emergency-response shooter training and regular briefings educating officers on new security policies and discussion of current security methods.&#13;
&#13;
UCPD also uses a system called "active shooter training," which Greenstein said is based on real-life situations such as the shooting at Virginia Tech.&#13;
&#13;
"We want to be able to determine the cause and have an immediate response," she said.&#13;
&#13;
Greenstein said the state mandates law enforcement be involved in training every week and diligently prepare for all types of emergencies.&#13;
&#13;
She added that UCPD is hoping to learn from the Virginia Tech shooting, noting that as it is only a few days after the fact, changes will likely be made in the upcoming weeks when more information is available.&#13;
&#13;
A vigil co-sponsored by the Undergraduate Students Association Council Office of the President and the Office of Residential Life is planned for 8 p.m. in De Neve Plaza to give students an opportunity to express their condolences for the victims and their families, said Jesse Rogel, chief of staff at the USAC Office of the President.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.dailybruin.ucla.edu/news/2007/apr/19/shootings_spur_uc_assess_security_policies/&gt;The Daily Bruin - April 29, 2007&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9771">
                <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="11751">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13194">
                <text>Shootings spur UC to assess security policies</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="851">
        <name>security policies</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="732" public="1" featured="0">
    <fileContainer>
      <file fileId="431">
        <src>https://www.april16.vtlibraries.net/files/original/vp_aa087fac2f.ill.4_20tease_t135.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="14819">
                    <text>2007-07-15</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15939">
                    <text>2007-07-15 15:24:18</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2052">
                <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="3943">
                <text>Lina Chung  </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="5921">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7799">
                <text>&lt;b&gt;Feeling guilty for sharing the Virginia Tech gunman&amp;#39;s ethnicity will do more harm than good&lt;/b&gt;&#13;
&#13;
By Lina Chung&#13;
Friday, April 20, 2007&#13;
&#13;
After Monday&amp;#39;s Virginia Tech tragedy, shock reverberated among the Korean American community - the shooter, 23-year-old student Cho Seung-Hui, was a man of South Korean nationality.&#13;
&#13;
But, in an attempt to avert racial backlash, members of the community have only victimized themselves by allowing Cho&amp;#39;s nationality to spark a collective sense of guilt and responsibility.&#13;
&#13;
"All Koreans in South Korea - as well as here - must bow their heads and apologize to the people of America," said the Rev. Dong Sun Lim, founder of the Oriental Mission Church in Koreatown, according to the Los Angeles Times.&#13;
&#13;
As a Korean American student, I sensed my parents&amp;#39; fear of racial backlash when they called me Tuesday night. Worried about the media frenzy surrounding Monday&amp;#39;s tragedy, they suggested I come home for the week until the situation calmed down.&#13;
&#13;
I was initially baffled at my parents&amp;#39; concerns. But the following day, The New York Times and Los Angeles Times published articles reflecting this fear among South Korean parents across the U.S.&#13;
&#13;
And racial epithets against South Koreans were also flooding the Internet. Blog posts on sites such as Facebook and Sepia Mutiny (a blog site created by South Asians) attacked and pigeonholed South Koreans as violent, destructive people.&#13;
&#13;
"Koreans are the most hotheaded and macho of East Asians," said a Sepia Mutiny commentator.&#13;
&#13;
"Take that shit back to your own nation," said a Facebook user, according to an MSNBC article.&#13;
&#13;
Other Korean American UCLA students also observed a rise in concern among their parents.&#13;
&#13;
First-year business economics student Janice No, whose parents live in Virginia, expressed how her parents felt a heightened sense of uneasiness regarding Monday&amp;#39;s massacre.&#13;
&#13;
"My family was concerned for my safety as a general university student," she said. "But the fact the shooter was Korean only increased their worrying."&#13;
&#13;
Even the South Korean foreign ministry issued a statement earlier this week that it hoped the tragedy and Cho&amp;#39;s South Korean nationality wouldn&amp;#39;t incite "racial prejudice or confrontation."&#13;
&#13;
Although events in the past few years - such as the 1992 L.A. riots, in which Korean-owned businesses were targeted and looted - have burned a harsh memory within the Korean American community in Los Angeles, we must acknowledge that Cho&amp;#39;s actions were in no way a reflection on South Koreans as a whole.&#13;
&#13;
"Korean American students have assimilated more to American culture and don&amp;#39;t feel threatened by the situation. We understand the gunman had personal problems that caused his attack and that it could&amp;#39;ve been someone from any race," said second-year aerospace engineering student and L.A. resident Anthony Suh, who says his parents&amp;#39; concerns stemmed from their experience with the L.A. riots.&#13;
&#13;
In regards to UCLA, some students feel secure that no danger or harm will arise due to their racial identities as Korean Americans.&#13;
&#13;
"There&amp;#39;s such a big Korean community at UCLA, so I don&amp;#39;t feel threatened," third-year molecular, cell and developmental biology student Yoonah Lee said. "But the fact (the gunman) was Korean just makes me more aware of the situation."&#13;
&#13;
Awareness may be justified, but openly acknowledging a sense of responsibility for having a shared ethnicity with Cho is not the right approach; it will only allow for stereotypes and more negativity to ensue.&#13;
&#13;
By choosing to walk in shame, we allow ourselves to be targeted. By choosing to hide, we allow ourselves to be hunted.&#13;
&#13;
Now is not the time for pointing fingers or living in fear. In the wake of such a horrible tragedy, our only collective responsibility - no matter what our ethnicity may be - is to offer support and sympathy to the Virginia Tech victims and their families in this time of need.&#13;
&#13;
-- &#13;
&#13;
Original Source: &lt;a href=http://www.dailybruin.ucla.edu/news/2007/apr/20/ikorean_sense_shame_unjustifiedi/&gt;The Daily Bruin - April 20, 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="9770">
                <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="11102">
                <text>The Daily Bruin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11750">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13193">
                <text>Korean sense of shame is unjustified</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="713">
        <name>backlash</name>
      </tag>
      <tag tagId="731">
        <name>ethnic identity</name>
      </tag>
      <tag tagId="358">
        <name>korean</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="731" 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="2051">
                <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="3942">
                <text>Annie Augustine  </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="5920">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7798">
                <text>By Annie Augustine&#13;
Friday, April 20, 2007&#13;
&#13;
This weekend, 35 cancer survivors will join nearly 1,000 UCLA students and community members for a 24-hour relay to raise money for the disease.&#13;
&#13;
UCLA&amp;#39;s Relay For Life is planned to take place in Drake Stadium from Saturday at 1 p.m. to 1 p.m. on Sunday. Ninety-six teams have signed up, and participants will include UCLA students, students from L.A. high schools and Westwood community members.&#13;
&#13;
At UCLA&amp;#39;s Relay For Life, the survivors who are attending will walk or run alongside participants.&#13;
&#13;
Brittany Maxwell, the mission delivery director for UCLA&amp;#39;s Relay For Life, said the relay&amp;#39;s opening ceremony will encourage and motivate participants.&#13;
&#13;
"A cancer survivor is planning to speak before the relay begins and survivors will walk the first lap around the stadium while all other participants stand inside the track to cheer them on," she said&#13;
&#13;
Eric Lam, a first-year mechanical engineering student who started Relay For Life at his high school and is the captain of two UCLA teams this year, said being involved in Relay For Life is a fun way to help a good cause.&#13;
&#13;
"At the ceremony you get to meet survivors and it is inspirational to watch them take the first lap," he said.&#13;
&#13;
Teams will spend the entire night in Drake Stadium with the goal of keeping one person from each team on the track at all times.&#13;
&#13;
The American Cancer Society&amp;#39;s annual Relay For Life began because of the efforts of one man. According to the Relay For Life Web site, Gordy Klatt, a colorectal surgeon from Tacoma, Wash., wanted to increase the income of his local American Cancer Society office. In May of 1985, Klatt spent 24 hours circling a track at the University of Puget Sound, covering more than 83 miles and raising nearly $27,000.&#13;
&#13;
The following year, 19 teams took part in the first Relay For Life event and raised nearly $33,000.&#13;
&#13;
Now more than 3.5 million people partake in 4,800 Relay For Life events nationwide each year, and in 2006, the UCLA Relay For Life raised over $60,000.&#13;
&#13;
According to the Web site, the purpose of Relay For Life is to celebrate cancer survivors, honor those who have lost their lives to the disease, and raise money to help fight it.&#13;
&#13;
"I had a couple of chances to participate in high school, but never actually did. I just thought that this would be a good opportunity and the people on my (residence hall) floor encouraged me," said Alex Yang, a first-year undeclared student.&#13;
&#13;
Maxwell said each participant is encouraged to raise $100 before Saturday. All participants who raise $100 will be given free food and T-shirts at the relay.&#13;
&#13;
Yaoyao Wang, a first-year undeclared student, said she used Facebook to help raise funds.&#13;
&#13;
"After fundraising for Dance Marathon, I couldn&amp;#39;t ask my parents&amp;#39; friends for more money. I created a Facebook group to get donations from students," she said.&#13;
&#13;
Several bands, including Mikey G and Dan from Danville, will be performing at the relay. Maxwell also said there will be a variety of games for teams to participate in throughout the night.&#13;
&#13;
Relay For Life will be held at many schools around the country this weekend, including Virginia Tech. In a statement released by Mary Vaughn Smith, the event chair for Relay For Life at Virginia Tech, said the school would hold the event despite Monday&amp;#39;s shootings.&#13;
&#13;
"We&amp;#39;ve decided to move forward with the Relay For Life because this is a time when we just want to make sure that this event - with a focus on celebration of life and hope - is available to all those who need it in our community," she said.&#13;
&#13;
Many colleges throughout the country have posted encouraging messages on the "Relay For Life at Virginia Tech Forum."&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.dailybruin.ucla.edu/news/2007/apr/20/students_relay_message_hope/&gt;The Daily Bruin - April 20, 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="9769">
                <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="11101">
                <text>The Daily Bruin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11749">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13192">
                <text>Students to relay a message of hope</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="849">
        <name>relay for life</name>
      </tag>
      <tag tagId="850">
        <name>relay for life at virginia tech forum</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="730" public="1" featured="0">
    <fileContainer>
      <file fileId="430">
        <src>https://www.april16.vtlibraries.net/files/original/vigilF_t600_7feb6f76af.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="14818">
                    <text>2007-07-15</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15938">
                    <text>2007-07-15 14:29:10</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2050">
                <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="3941">
                <text>Photo by: Jessica Lum</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="5919">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7797">
                <text>Photo by: Jessica Lum&#13;
&#13;
Students and university employees joined together last night in De Neve Plaza in remembrance of victims at Virginia Tech.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9768">
                <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="11100">
                <text>The Daily Bruin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11748">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13191">
                <text>UCLA Vigil</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="729" public="1" featured="0">
    <fileContainer>
      <file fileId="429">
        <src>https://www.april16.vtlibraries.net/files/original/picE_t600_47a3390845.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="14817">
                    <text>2007-07-15</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15937">
                    <text>2007-07-15 14:26:55</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2049">
                <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="3940">
                <text>Leigh Alvarez</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="5918">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7796">
                <text>Photo by: Leigh Alvarez&#13;
&#13;
Approximately 500 candles were handed out to attendees.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9767">
                <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="11099">
                <text>The Daily Bruin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11747">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13190">
                <text>UCLA Vigil</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="728" public="1" featured="0">
    <fileContainer>
      <file fileId="428">
        <src>https://www.april16.vtlibraries.net/files/original/picD_t600_8a5e9d5715.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="14816">
                    <text>2007-07-15</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15936">
                    <text>2007-07-15 14:24:36</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="2048">
                <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="3939">
                <text>Leigh Alvarez</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="5917">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7795">
                <text>Photo by: Leigh Alvarez&#13;
&#13;
First-year psychobiology student John Seo (Left) and first-year undeclared student Jenny Lee (next) listen to student speakers sharing their thoughts during the vigil.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9766">
                <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="11746">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13189">
                <text>UCLA Vigil</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="723" public="1" featured="0">
    <fileContainer>
      <file fileId="424">
        <src>https://www.april16.vtlibraries.net/files/original/web_fff784a815.ns.vigil.picA__t600.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="14812">
                    <text>2007-07-15</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15932">
                    <text>2007-07-15 14:10:13</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2044">
                <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="3935">
                <text>Jessica Lum</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="5913">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7791">
                <text>Photo by: Jessica Lum&#13;
&#13;
Students stand in De Neve Plaza on Thursday night for a vigil in memory of those who lost their lives in Monday&amp;#39;s shootings at Virginia Tech. Speakers and students expressed sympathy for the victims&amp;#39; families and for the university.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9762">
                <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="11742">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13185">
                <text>UCLA Vigil</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="724" public="1" featured="0">
    <fileContainer>
      <file fileId="425">
        <src>https://www.april16.vtlibraries.net/files/original/web_d2ec1425be.ns.vigil.picB__t600.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="14813">
                    <text>2007-07-15</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15933">
                    <text>2007-07-15 14:13:49</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.  Recommended best practice is to assign the type "text" to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="40">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2045">
                <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="3936">
                <text>Leigh Alvarez</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="5914">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7792">
                <text>Photo by: Leigh Alvarez&#13;
&#13;
Reider Larsen, a first-year undeclared student, signs a quilt Thursday night that will be sent to Virginia Tech. An alumna of Virginia Tech attended the vigil to thank UCLA.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9763">
                <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="11743">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13186">
                <text>UCLA Vigil</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="725" public="1" featured="0">
    <fileContainer>
      <file fileId="426">
        <src>https://www.april16.vtlibraries.net/files/original/picA_t600_799a07d704.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="14814">
                    <text>2007-07-15</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15934">
                    <text>2007-07-15 14:16:27</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="2046">
                <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="3937">
                <text>Alvarez</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="5915">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7793">
                <text>Photo by: Leigh Alvarez&#13;
&#13;
Students comfort each other during yesterday&amp;#39;s candlelight vigil held in memory of the victims of the Virginia Tech shooting.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9764">
                <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="11744">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13187">
                <text>UCLA Vigil</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="726" public="1" featured="0">
    <fileContainer>
      <file fileId="427">
        <src>https://www.april16.vtlibraries.net/files/original/picB_t600_b095f9c9f9.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="14815">
                    <text>2007-07-15</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
          <elementSet elementSetId="4">
            <name>Omeka Legacy File</name>
            <description>The metadata element set that, in addition to the Dublin Core element set, was included in the `files` table in previous versions of Omeka. These elements are common to all Omeka files. This set may be deprecated in future versions.</description>
            <elementContainer>
              <element elementId="66">
                <name>Capture Date</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15935">
                    <text>2007-07-15 14:19:11</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="2047">
                <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="3938">
                <text>Jessica Lum</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="5916">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7794">
                <text>Photo by: Jessica Lum&#13;
&#13;
Samara Leader, a second-year political science student and Sarah Peters, a first-year mathematics and economics student share in a moment of silence.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9765">
                <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="11098">
                <text>The Daily Bruin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11745">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13188">
                <text>UCLA Vigil</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
      <tag tagId="232">
        <name>vigil</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="722" 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="2043">
                <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="3934">
                <text>Carolyn McGough,</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="5912">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7790">
                <text>By Carolyn McGough&#13;
Friday, April 20, 2007&#13;
&#13;
Tears rolled down many UCLA community members&amp;#39; faces in De Neve Plaza on Thursday night, as hundreds gathered to honor the memory of the victims of the recent tragedy at Virginia Tech.&#13;
&#13;
Following Monday morning&amp;#39;s shootings - in which 33 were killed, including professors and students - a vigil was planned by the Office of Residential Life and the Undergraduate Students Association Council.&#13;
&#13;
Five hundred tea candles were distributed before the somber ceremony began, but there still were not enough for each person in the huge crowd that gathered, said USAC President Marwa Kaisey.&#13;
&#13;
Kaisey was the first to speak, as she strived to bring community members together and encouraged them to share feelings.&#13;
&#13;
"We want to show Virginia Tech support, to show that the Bruins care and have been touched by the tragedy," Kaisey said.&#13;
&#13;
During the ceremony, Kaisey read the names of each of the victims in an effort to "humanize the tragedy."&#13;
&#13;
A quilt will be sent to Virginia Tech to show that UCLA identifies with and cares for the Blacksburg, Va. school, she said.&#13;
&#13;
Students were invited to decorate a patch for the quilt and become a direct part of the support.&#13;
&#13;
Former member of the Peace Corps and UCLA Ombudsperson Donald Hartsock also spoke. He emphasized the close bond UCLA and Virginia Tech have with each other, both great American universities.&#13;
&#13;
"Respectfully, I say &amp;#39;Go Hokies.&amp;#39; And I say to us now, &amp;#39;Go Bruins.&amp;#39; We are family," he said.&#13;
&#13;
This is the largest shooting massacre in the United States that has occurred on another college campus - a campus not too unlike UCLA, she said.&#13;
&#13;
Cho Seung-Hui, a 23-year-old student at Virginia Tech, opened fire Monday morning in two buildings, killing two students in a dorm room and then 30 more in one of the buildings on campus. Afterward, Seung-Hui then proceeded to kill himself.&#13;
&#13;
The gunman had mailed NBC a package containing a 23-page written statement, which exemplified a struggle he had between himself and his surrounding environment. Photos and videos were also sent of himself holding and aiming guns.&#13;
&#13;
Since the event, many universities and students across the country have shown their support for the Virginia Tech community through social-networking Web sites such as Facebook and MySpace. Some students have also changed their profile pictures to Virginia Tech insignias.&#13;
&#13;
Kristin Gardner, a Virginia Tech alumna from the class of 2003, attended the vigil to thank UCLA for its consideration.&#13;
&#13;
Encouraging all to wear orange and maroon - the colors of Virginia Tech - students and alumni of the university have declared today as "Hokie Hope Day," she said.&#13;
&#13;
Students were encouraged to seek support from friends, family and university resources, said Director of Student Psychological Services Elizabeth Gong-Guy.&#13;
&#13;
"SPS wishes to offer you whatever support you need. But the best support really does come from your peers," she said.&#13;
&#13;
A theme of the night portrayed by speeches and the somber environment was the closeness between UCLA and Virginia Tech students.&#13;
&#13;
"Even though it seems so far away, it&amp;#39;s an American university," said Angie Noffsinger, a fourth-year communication studies student.&#13;
&#13;
"It&amp;#39;s important for us to show that at UCLA we identify with the students at Virginia Tech."&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.dailybruin.ucla.edu/news/2007/apr/20/bruins_gather_grieve/&gt;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="9761">
                <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="11097">
                <text>The Daily Bruin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11741">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13184">
                <text>Bruins gather to grieve</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="717">
        <name>grief</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
      <tag tagId="174">
        <name>vigils</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="721" 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="2042">
                <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="3933">
                <text>Mark Humphrey  </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="5911">
                <text>2007-07-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7789">
                <text>By Mark Humphrey&#13;
Monday, April 23, 2007&#13;
&#13;
It&amp;#39;s no secret that the news media exercises bad judgment at times.&#13;
&#13;
Granted, we, as journalists, try to make informed decisions about what to cover and how. For example, during summer training at the Daily Bruin, we did a news-judgment exercise involving an actual story.&#13;
&#13;
The story was about a baby who had been murdered by her father, and the story also highlighted how a welfare program had failed the family. The issue was whether to run a photo of a coroner holding a bag that had the baby&amp;#39;s body in it - was the photo just simply shocking, or did it further the purpose of the story?&#13;
&#13;
We ultimately decided we would run the photo. Our reasoning was that the photo, while shocking and potentially in poor taste, further hammered home the main point of the story - how social programs had failed this family so terribly.&#13;
&#13;
Judging by the mainstream media&amp;#39;s recent coverage of certain events, I think many journalists would do well to take part in this same exercise.&#13;
&#13;
In the past few weeks we&amp;#39;ve been bombarded by three stories. First came radio douche bag Don Imus&amp;#39; derogatory remarks about the Rutgers women&amp;#39;s basketball team. Then came NBC&amp;#39;s decision to broadcast Virginia Tech killer Cho Seung-Hui&amp;#39;s videotaped rantings. Finally, there came Alec Baldwin&amp;#39;s disturbing phone message to his daughter.&#13;
&#13;
Aside from showing the ugly side of humanity, these stories have one thing in common: They were all covered in a misguided fashion.&#13;
&#13;
With Imus, people were right to be up in arms. He defamed a group of talented young women at what was supposed to be their finest moment. Unfortunately, this story got hammered into the ground, filling the airwaves at every single second of the day. Why was this a problem? Because of media hypocrisy.&#13;
&#13;
One of the main reasons the media gave for covering this so relentlessly was to right Imus&amp;#39; wrong: defaming a group of women because of what he thought of their physical appearance.&#13;
&#13;
Yet, by covering this so excessively, Imus&amp;#39; comments have been replayed so many times it&amp;#39;s gotten to the point where some would associate the Rutgers women less with basketball and more with Imus. It doesn&amp;#39;t matter how untrue his remarks are, as the Rutgers women have almost solely been associated with Don Imus since their season ended because of the media firestorm.&#13;
&#13;
Then there&amp;#39;s Alec Baldwin&amp;#39;s voice-mail tirade, where he refers to his 11-year-old daughter as a "thoughtless little pig" and vows to "straighten (her) out." Once again, media hypocrisy rears its ugly head. Ironically, so much has been said about the well-being of Baldwin&amp;#39;s daughter while the real issue has gone ignored.&#13;
&#13;
Namely, how well does it serve Baldwin&amp;#39;s daughter to not only hear her parents&amp;#39; dirty laundry aired in public, but also to hear the phone message repeated on television? Wouldn&amp;#39;t most sane people say that divorce hurts children, and that the more public the divorce, the more negative the effect on the child?&#13;
&#13;
Bad news judgment reached its zenith with NBC&amp;#39;s decision to air videos made by Virginia Tech killer Cho Seung-Hui. Naturally, the videos are all over YouTube.&#13;
&#13;
Not only was the decision to air these videos in poor taste, but it didn&amp;#39;t serve any purpose from a news standpoint. These videos added no new information and, more importantly, gave Cho exactly what he wanted: attention. Cho died, but NBC&amp;#39;s airing of his videos got his message out to everyone.&#13;
&#13;
In journalism, as much as some hate to admit it, the bottom line is still the bottom line. NBC aired these videos to get a jump on the competition, just like every news outlet jumped on them immediately afterward. Anyone who&amp;#39;s shocked when the media does something sensational is hopelessly naive. If it bleeds, it leads and, more importantly, makes money.&#13;
&#13;
When the media covers stories like this, it often claims moral superiority. It proclaims outrage and to know what is best for everyone. But if the way these situations have played out is any indication, it&amp;#39;s clear that much of the time, the media doesn&amp;#39;t have a clue.&#13;
&#13;
While I&amp;#39;m often disgusted by what gets covered and how, I can&amp;#39;t begrudge the news media for making a living.&#13;
&#13;
But if they&amp;#39;re going to proclaim they know what is best for everyone, they should think about who their coverage is really hurting first.&#13;
&#13;
--&#13;
&#13;
Original Source:&lt;a href=http://www.dailybruin.ucla.edu/news/2007/apr/23/imedia_doesnt_always_know_besti/&gt;The Daily Bruin - 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="9760">
                <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="11740">
                <text>Saba Riazati &lt;editor@media.ucla.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13183">
                <text>Media doesn&amp;#39;t always know best</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="847">
        <name>media response</name>
      </tag>
      <tag tagId="848">
        <name>tragedy response</name>
      </tag>
      <tag tagId="833">
        <name>ucla</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
