<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="810" public="1" featured="0" 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.911digitalarchive.org/items/show/810?output=omeka-xml" accessDate="2026-05-05T18:07:13-04:00">
  <collection collectionId="9">
    <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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10788">
                <text>Madison Area Peace Coalition E-mails</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10789">
                <text>The Madison Area Peace Coalition (MAPC) formed fourteen days after the September 11 attacks to oppose (among other goals) the use of U.S. military, economic, or political force – whether direct or proxy, overt or covert -- "that violates the sovereignty or human rights of any nation or people." The Archive has assembled here e-mails exchanges from MAPC dating from the group's founding until late November 2001.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="18">
    <name>September 11 Email</name>
    <description/>
    <elementContainer>
      <element elementId="65">
        <name>September 11 Email: Body</name>
        <description>The basic content, as unstructured text; sometimes containing a signature block at the end.</description>
        <elementTextContainer>
          <elementText elementTextId="10838">
            <text>
Either way works for me on the first paragraph.

The other paragraph you quoted seems to have a redundancy:

"The Coordinating Committee is empowered to make emergency decisions for
MAPC." and "The Coordinating Committee has the right to make emergency
decisions when necessary."

X


----- Original Message -----
From: "X" &lt;X&gt;
To: &lt;coordination@madpeace.org&gt;
Cc: &lt;X&gt;; &lt;X&gt;
Sent: Monday, November 12, 2001 10:14 PM
Subject: RE: [MAPC-coord] cc mission for approval, gm agenda


&gt; X,
&gt;
&gt; Thanks for doing this. I would change the first paragraph to the following
&gt; for readability:
&gt;
&gt; The main decision-making body of MAPC is the General Meeting. (moved this
&gt; next sentence forward from end of paragraph; seemed to flow better) The
&gt; Coordinating Committee ensures that the decisions of the General Meetings
&gt; are implemented. The General Meeting sets the politics and the overall
&gt; direction of MAPC.  The Coordinating Committee takes its direction from
the
&gt; General Meeting, and is accountable to the (deleted general) membership.
All
&gt; decisions made by the Coordinating Committee are subject to discussion and
&gt; review by the General Meeting.
&gt;
&gt; - The Coordinating Committee is empowered to make emergency decisions for
&gt; MAPC.  An emergency decision consists of responding appropriately to
rapidly
&gt; changing current events, or of initiating the coordination of plans that
are
&gt; under time constraint. The Coordinating Committee has the right to make
&gt; emergency decisions when necessary.  Emergency decisions will be reported
&gt; back to the General Meeting
&gt;
&gt; I'll print, but would need to know tonight about content so that I can do
it
&gt; between work tomorrow &amp; the meeting. I'll be in a time crunch, especially
&gt; with getting Jesse to a friend's house before the meeting.
&gt;
&gt; X
&gt;
&gt;
&gt; -----Original Message-----
&gt; From: X
&gt; Sent: Sunday, November 11, 2001 8:38 PM
&gt; To: coordination@madpeace.org
&gt; Cc: X; X
&gt; Subject: [MAPC-coord] cc mission for approval, gm agenda
&gt;
&gt; Here is the CC mission, combining Rae's original plus what we
added/changed:
&gt;
&gt; - The main decision-making body of MAPC is the General Meeting.  The
General
&gt; Meeting sets the politics and the general direction of MAPC.  The
&gt; Coordinating Committee takes its direction from the General Meeting, and
is
&gt; accountable to the general membership.  All decisions made by the
&gt; Coordinating Committee are subject to discussion and review by the General
&gt; Meeting.  The Coordinating Commitee ensures that the decisions of the
&gt; General Meetings are implemented.
&gt;
&gt; - The Coordinating Committee is the central orgainizing body of MAPC.  It
&gt; ensures that the work of the committees is coordinated.  It evaluates
&gt; ongoing work to make sure that MAPC is not missing opportunities for
&gt; outreach, growth, and political impact.
&gt;
&gt; - The Coordinating Committee is responsible for facilitating development
of
&gt; overall strategy for the coalition, subject to General Meeting approval,
and
&gt; for providing recommendations to ensure that the work of the committees is
&gt; coordinated in a matter consistent with that strategy.
&gt;
&gt; - The Coordinating Committee is empowered to make emergency decisions for
&gt; MAPC.  An emergency decision consists of responding appropriately to
rapidly
&gt; changing current events, or of initiating the coordination of plans that
are
&gt; under time constraint. The Coordinating Committee has the right to make
&gt; emergency decisions when necessary.  Emergency decisions will be reported
&gt; back to the General Meeting.
&gt;
&gt; - The Coordinating Committee is responsible for establishing policy on and
&gt; making decisions regarding disbursement of funds by the coaltion.
&gt;
&gt; - The Coordinating Committee is responsible for orgainizing the General
&gt; Meetings.  It will develop agendas for General Meetings.  It assures that
&gt; General Meetings are organized so that critical discussions are held and
&gt; important decisions are made in a timely fashion.
&gt; =========================================
&gt;
&gt; THis was a little more difficult than it seemed, since not all sentences
&gt; flowed well with what was sandwiched in.  The first paragraph is funky
with
&gt; using "general meeting" and "general membership" but I think it's probably
&gt; ok. I did some minor editing to make everything fit together. We agreed to
&gt; give 24 hours for corrections and feedback. X and X will present.
&gt; X, will you be printing for distribution at the meeting?
&gt;
&gt; Here is the agenda:
&gt;
&gt; GM meeting agenda
&gt;
&gt; 1) Welcome
&gt; 2) committee reports
&gt; - action
&gt; - outreach
&gt; - Student Youth
&gt; - Arts
&gt; - media
&gt; - policy
&gt; - fundraising
&gt; - labor movement report
&gt; 3) Proposals (new business)
&gt; - CC mission proposal
&gt; - Action committee vigil proposal
&gt; - SYC logo proposal
&gt; 4) Announcements
&gt; 5) Optional - Video
&gt;
&gt; I'll get the meeting notes out as soon as I can clean them up, probably
&gt; tomorrow evening.
&gt;
&gt; X
&gt;
&gt;
&gt;
&gt;
&gt; _________________________________________________________________
&gt; Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
&gt;
&gt;
&gt; _______________________________________________
&gt; coordination@madpeace.org
&gt; http://lists.OpenSoftwareServices.com/mailman/listinfo/madpeace-cc
&gt;
&gt;
&gt; _______________________________________________
&gt; coordination@madpeace.org
&gt; http://lists.OpenSoftwareServices.com/mailman/listinfo/madpeace-cc
&gt;


_______________________________________________
coordination@madpeace.org
http://lists.OpenSoftwareServices.com/mailman/listinfo/madpeace-cc

</text>
          </elementText>
        </elementTextContainer>
      </element>
      <element elementId="66">
        <name>September 11 Email: Date</name>
        <description>The local time and date when the message was written.</description>
        <elementTextContainer>
          <elementText elementTextId="10839">
            <text>Monday, November 12, 2001 10:51 PM</text>
          </elementText>
        </elementTextContainer>
      </element>
      <element elementId="67">
        <name>September 11 Email: To</name>
        <description>The email addresses, and optionally names of the message's recipients</description>
        <elementTextContainer>
          <elementText elementTextId="10840">
            <text>coordination@madpeace.org</text>
          </elementText>
        </elementTextContainer>
      </element>
      <element elementId="68">
        <name>September 11 Email: From</name>
        <description>The email address, and optionally the name of the author.</description>
        <elementTextContainer>
          <elementText elementTextId="10841">
            <text>X</text>
          </elementText>
        </elementTextContainer>
      </element>
      <element elementId="69">
        <name>September 11 Email: CC</name>
        <description>The email addresses of those who received the message addressed primarily to another.</description>
        <elementTextContainer>
          <elementText elementTextId="10842">
            <text>NULL</text>
          </elementText>
        </elementTextContainer>
      </element>
      <element elementId="70">
        <name>September 11 Email: Subject</name>
        <description>A brief summary of the topic of the message.</description>
        <elementTextContainer>
          <elementText elementTextId="10843">
            <text>Re: [MAPC-coord] cc mission for approval, gm agenda</text>
          </elementText>
        </elementTextContainer>
      </element>
    </elementContainer>
  </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="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="10844">
              <text>Re: [MAPC-coord] cc mission for approval, gm agenda</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
    <elementSet elementSetId="4">
      <name>911DA Item</name>
      <description>Elements describing a September 11 Digital Archive item.</description>
      <elementContainer>
        <element elementId="52">
          <name>Status</name>
          <description>The process status of this item.</description>
          <elementTextContainer>
            <elementText elementTextId="10845">
              <text>approved</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="53">
          <name>Consent</name>
          <description>Whether September 11 Digital Archive has permission to possess this item.</description>
          <elementTextContainer>
            <elementText elementTextId="10846">
              <text>unknown</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="54">
          <name>Posting</name>
          <description>Whether the contributor gave permission to post this item.</description>
          <elementTextContainer>
            <elementText elementTextId="10847">
              <text>yes</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="55">
          <name>Copyright</name>
          <description>Whether the contributor holds copyright to this item.</description>
          <elementTextContainer>
            <elementText elementTextId="10848">
              <text>yes</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="56">
          <name>Source</name>
          <description>The source of this item.</description>
          <elementTextContainer>
            <elementText elementTextId="10849">
              <text>born-digital</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="57">
          <name>Media Type</name>
          <description>The media type of this item.</description>
          <elementTextContainer>
            <elementText elementTextId="10850">
              <text>email</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="59">
          <name>Created by Author</name>
          <description>Whether the author created this item.</description>
          <elementTextContainer>
            <elementText elementTextId="10851">
              <text>yes</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="60">
          <name>Described by Author</name>
          <description>Whether the description of this item was submitted by the author.</description>
          <elementTextContainer>
            <elementText elementTextId="10852">
              <text>no</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="61">
          <name>Date Entered</name>
          <description>The date this item was entered into the archive.</description>
          <elementTextContainer>
            <elementText elementTextId="10853">
              <text>2001-11-12</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
