<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="295" 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/295?output=omeka-xml" accessDate="2026-06-10T20:48:57+00:00">
  <fileContainer>
    <file fileId="115">
      <src>https://thorntonco.cvlcollections.org/files/original/3a132a4634cfe6d7442dc8b06f893268.pdf</src>
      <authentication>c72108fd049402702d5436d105766932</authentication>
      <elementSetContainer>
        <elementSet elementSetId="4">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="93">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="2653">
                  <text>.

.

-

f);..AAJ.VIIVL&gt;--' -

INTEROFFICE

VicK)

TO:

FROM:

MEMORANDUM

All Computer Users

DATE:

August 14, 1980

D.C.Rohrbaugh, EDP Supervisor

SUBJECT:

REQUEST&amp; FOR COMPUTER OPERATIONS.

Effective Tuesday, September 2, 1980, all persons requesting any
computer operations of Data Processing personnel must complete a
"REQUEST FOR COMPUTER. OPERATIONS" form. After th:Ls date there
will be no "automatic" runs or verbal requests accepted. Supplies
of this form are available from Data Processing.
The "REQUEST FOR COMPUTER OPERATIONS" is a three part form.
After completing the form, Part 3 (pink) is to be retained by
the requester and Parts l (white) and 2 (yellow) are to be sent
to Data Processing. Part 1 (white) will be returned to the
requestor (or person designated as "Deliver To11) with the
printed output from the computer run. Part 2 (yellow) will be
retained by Data Processing as a processing record.
Please fill in all requested information on the form.
Date - The date the form was filled out.
From - The name of the person making the request. This is
the individual who will be contacted if Data Processing
has any questions about the request.
3. Required by - The date and time that the run must be returned
to the reauestor.
4. Job - Fill in the name of the job exactly as it appears
on the menu. Use the System Identification and the Joo
nane. i.e. IFMS - EXPENDITURE &amp; REVENUE APPLICATION CHECK RUN. or UTILITY BILLING-OPERATOR PROCESSINGTRIAL CALCULATION RUN.
5 .. Special Instructions - Fill in any special instructions
required by computer operations to process the job.
i.e. Funds to be processed, account numbe~s, employee
numbers, billing cycles, etc.
6. Number of copies of listings.
7 . Deliver To - Name of person to whom the reports are to
be delivered.
8. Mark either Hand Carry or Mail.
1.
2.

Do not send a "REQUEST FOR COMPUTER OPERATIONS" to
Data Processing until you are certain the job is ready
to be run.
Data Processing will make every effert to complete all runs
within four working hours plus the actual time it requires
·to process the job.
~

ATT.:

Request For Computer Operations Form.

�</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="1613">
              <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="1614">
              <text>Interoffice memorandum about computer operation requests</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="56">
          <name>Date Created</name>
          <description>Date of creation of the resource.</description>
          <elementTextContainer>
            <elementText elementTextId="1615">
              <text>1980-08-14</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1616">
              <text>City of Thornton</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1617">
              <text>Memo to all Thornton employees establishing a policy for submitting computer operation request forms for all data processing needs</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="81">
          <name>Spatial Coverage</name>
          <description>Spatial characteristics of the resource.</description>
          <elementTextContainer>
            <elementText elementTextId="1618">
              <text>Thornton</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1619">
              <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="1620">
              <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="1621">
              <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="1623">
              <text>COTA-001-023</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="1622">
              <text>C:\Users\amilliga\Digital Archive Items</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
