<?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.april16archive.org/items/browse?tags=text-message+initiative&amp;sort_field=Dublin+Core%2CTitle&amp;sort_dir=d&amp;output=omeka-xml" accessDate="2026-04-18T21:07:10+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>1</pageNumber>
      <perPage>20</perPage>
      <totalResults>1</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1780" 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="2901">
                <text>Kacey Beddoes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4792">
                <text>Editorial Staff</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6770">
                <text>2008-02-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="8648">
                <text>Staff Editorial&#13;
Issue date: 4/20/07 Section: Viewpoint&#13;
&#13;
There are still plenty of questions surrounding what happened Monday at Virginia Tech.&#13;
&#13;
But one thing that isn&amp;#39;t up for discussion is that Notre Dame should have a plan in case the unthinkable happens here.&#13;
&#13;
Which is why University President Father John Jenkins&amp;#39; e-mail Thursday discussing emergency plans was a welcome - and much needed - announcement for students, faculty and, maybe most of all, parents.&#13;
&#13;
That message didn&amp;#39;t come, however, until days after the shooting - days of wondering and worrying and wanting to know what Notre Dame would do.&#13;
&#13;
Earlier this week, members of the administration and Notre Dame Security/Police were unwilling to comment on the University&amp;#39;s preparedness for such an emergency, leaving students questioning if the plan was fully developed.&#13;
&#13;
But now, Jenkins has reassured the community through an e-mail that, while somewhat vague, promises the University will work to further prepare for anything that may come along.&#13;
&#13;
It&amp;#39;s understandable that Notre Dame would need time to work out certain details before making a plan public. Still, when information of this nature isn&amp;#39;t being released, it&amp;#39;s important to tell people why, instead of generating anxious speculation that no plan exists.&#13;
&#13;
Hopefully, Notre Dame&amp;#39;s plan will eventually include the text-message initiative, one of the few specifics Jenkins included in his e-mail. If implemented, the procedure would go a long way to helping Notre Dame not repeat the delay in warning students that happened in Blacksburg.&#13;
&#13;
While other details of the plan will likely always be kept secret, it&amp;#39;s necessary to be open about all procedures and safety measures that do not compromise security - and open in telling students when information isn&amp;#39;t released due to security concerns.&#13;
&#13;
--&#13;
&#13;
Original Source:&#13;
&lt;a href="http://media.www.ndsmcobserver.com/media/storage/paper660/news/2007/04/20/Viewpoint/Security.With.Transparency-2870855.shtml"&gt;http://media.www.ndsmcobserver.com/media/storage/paper660/news/2007/04/20/Viewpoint/Security.With.Transparency-2870855.shtml&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10619">
                <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="12257">
                <text>Christopher Hine &lt;chine@nd.edu&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="53">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13964">
                <text>Security with transparency</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="729">
        <name>campus security</name>
      </tag>
      <tag tagId="1956">
        <name>emergency plan</name>
      </tag>
      <tag tagId="2002">
        <name>notre dame</name>
      </tag>
      <tag tagId="2009">
        <name>text-message initiative</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
