<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="300" 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://thorntonco.cvlcollections.org/items/show/300?output=omeka-xml" accessDate="2026-06-10T11:38:10+00:00">
  <fileContainer>
    <file fileId="31">
      <src>https://thorntonco.cvlcollections.org/files/original/c0f9f837614bfa567b63a59c9062a2cc.pdf</src>
      <authentication>8a598b13f648ba67a572d6226221dda8</authentication>
      <elementSetContainer>
        <elementSet elementSetId="4">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="93">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="2569">
                  <text>THIS :vHGHT HELP

A few tips on the caper for who ever takes over. I have found over the years
these make getting the naper out much easier.
It helps if you keep a pad handy that is for the paper only, then as you hear
of items that would be good stories for the paper, make yourself a note. True
you end up with lots of notes, but it helps to jog your memory on whom to ask
for those special stories.
I put out a memo, usually right after the 15th of the month, on when the next
paper would be out and what the deadline would be for turning in news items. I
tryed toremember to remind people verbally of the deadline whenever I saw them.
I put a memo in each departments box in the City Managers office and in each
Ftility Departments box.
I also roBde sure the following people received the memo, writing their name in
top left corner, usually hand deli v~xed wheneil.'.er possible; Karm Sunday, Cy Leiker,
Jeff TerAvest, Sandra Kailey, Jim Perry, Cel Schenfeld, Duane Tinsley or Jim Keller,
Al Smith, Genny Pierce, Devere King and anyone else I thought might give me a story.
I would s ome t.i-nes write a r-e-ni.nder' 2t the top of a memo to a particular person
to jog their memory of a particular story they might write. There is a fine line
between encoura?ement and enthusiasm,and harassment. Be careful.
The most frequently heard cormnent from emnloyees when asked for news items is
thev don't know how to write the stories or don't have time to write the stories.
I always assured ne oo Le to just T)Ut down the facts or get them to me and I would
t2 ke i_ t from there •
Be very c~reful to nroof, correct and rewrite if necessary, all stories submitted for the naoe r , You don't want any emoloyee embrassed by printing something
tret is awkward or in bad form. This also holds true for department heads,
oarti.cularly in cas ua L stories. Try to feel what the writer Lnt.ended to say or
convey, straighten the story out and retain as much as possible of the original
story.as submitted.
Depending on iWhen the paper was due I tried to arrange the following schedule;
deadline- 5:00 p.m., 3 days before the oaner was due. I took all items home where
they could be read and proofed in peace and quiet, (I could never find time to do
this at work). Have everything ready to 5ive to Li.nda , Mi1G operator, next morning,
having previously alerted her to when I would be expecting the paper to be typed.
Having Linda tyne the paper is the answer to getting it printed in an efficient
manner. I have always found her to be co9perative and most helpful.
This schedule allows the entire day for her to type the 1:irst draft, return it
to you for getting it into final form, and return it to her for final typing.
Arrange for so7eone (usually the part-time high school girl) to run the paper
and staple it together.
If all goes smoothly, (and sometir.1es it does) the paDer can be tvped, run off
on the Xerox and -stapled all in one day. Usually it takes two days. The naner'
s bou.Ld be given to Lucille Miller, Finance Clerk, the afternoon before the last
Daycheck of the month is due.
This s cheduLe allows for such things as malfunction of the MAG or Xerox
machine, L&gt; te de.I i.very of naner, absence of ner's ons who normally help with the paper
due to illness or vacation or those times when all schedules are interrupted by an
edi.ct f rom the admi rri.at.r-a t i on to stop a11 routine matters and do thus and such
r-r ojec t., Be f Lexab.Ie , do the best y ou can and don't worry about what you can not
c0ntrol.
Don Krugrnire will provide you vii th a list of birthdays for the following month
w-i..thout you hav Lng to ask. It's on his schedule and he never fails.

�2.
A little history on the paper. We were stuck w i.t.h the name when it was decided to have a contest to name the paper. The submittals we received were not
too imaginative. The 1Voice of Thornton Employees' was added to help overcome
the rather cas~al name of the paper.
Volume denotes year, J.2 issues per year, and date is the day employees will
receive the paper. (You might want to read Ue first issue of the paper which
had artioles from the Mayor and City Manager for some idea of what was originally
planned for the paper) o
Select the stories for the front page and then arrange all other stories for
spacing. Astericks will denote top 2nd finish of each article.
Ar~anging the paner for typing is really very simnle once someone shows you
how ij~o~e. T:te qnickest method to learn how is to ask someone to show you how
it is done.

BJL

�</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </file>
  </fileContainer>
  <collection collectionId="4">
    <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="254">
                <text>City Chatter, the Voice of Thornton Employees</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="255">
                <text>Public Domain: &lt;a href="http://rightsstatements.org/vocab/NoC-US/1.0/"&gt;http://rightsstatements.org/vocab/NoC-US/1.0/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="56">
            <name>Date Created</name>
            <description>Date of creation of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="256">
                <text>1972-1982</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="257">
                <text>Municipal officials and employees--Colorado--Thornton&#13;
</text>
              </elementText>
              <elementText elementTextId="258">
                <text>Newsletters</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="259">
                <text>Drafts and published volumes of City Chatter, a newsletter by and for city employees.  It was published for roughly a decade from 1972 to 1982 and contains articles relating to local events, developments in city government, and other topics relevant to city employees.   </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="260">
                <text>Thornton, Colorado</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="261">
                <text>Collection</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="262">
                <text>City of Thornton</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="263">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="264">
                <text>COTA-001</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="1">
    <name>Text</name>
    <description>A resource consisting primarily of words for reading. Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. 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="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1666">
              <text>&lt;a href="http://rightsstatements.org/vocab/NoC-US/1.0/"&gt;http://rightsstatements.org/vocab/NoC-US/1.0/&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1667">
              <text>"This might help," instructions for next editor of The City Chatter</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1668">
              <text>City of Thornton</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1669">
              <text>An informal instructional document for continuing editors of The City Chatter.  It contains workflow tips and advice.  </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="81">
          <name>Spatial Coverage</name>
          <description>Spatial characteristics of the resource.</description>
          <elementTextContainer>
            <elementText elementTextId="1670">
              <text>Thornton</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1671">
              <text>Municipal officials and employees</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1672">
              <text>Text</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1673">
              <text>application/pdf</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="1675">
              <text>COTA-001-028</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
    <elementSet elementSetId="5">
      <name>EAD Archive</name>
      <description>The Encoded Archival Description is a common standard used to describe collections of small pieces and to create hierarchical and structured finding aids.</description>
      <elementContainer>
        <element elementId="97">
          <name>Arrangement</name>
          <description>Information on how the described materials have been subdivided into smaller units.</description>
          <elementTextContainer>
            <elementText elementTextId="1674">
              <text>C:\Users\amilliga\Digital Archive Items</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
