<?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.ssmp.mdocs.skidmore.edu/items/browse?output=omeka-xml&amp;page=14&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-26T08:47:54+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>14</pageNumber>
      <perPage>40</perPage>
      <totalResults>755</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1358" public="1" featured="0">
    <fileContainer>
      <file fileId="2464">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/936a7ba436f7af2660e098eb824bf44e.jpg</src>
        <authentication>39297d2899298cceee94b7fc675a4f60</authentication>
      </file>
    </fileContainer>
    <collection collectionId="42">
      <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="10665">
                  <text>Saratoga County</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="11653">
              <text>Grace Beneke</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="11654">
              <text>7 May, 2021</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="11648">
                <text>NOW: Hostesses in front of Hattie's Restaurant</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11649">
                <text>2020</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="11651">
                <text>&lt;a href="http://hattiesrestaurant.com/about/"&gt;Hattie's Restaurant&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11652">
                <text>Two hostesses stand in front of Hattie's Restaurant's Phila St. location. </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="807" public="1" featured="0">
    <fileContainer>
      <file fileId="1726">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/9639bc76f06b37539b373d77f4b78662.jpeg</src>
        <authentication>da4565bfb9cad24bc19a6ecde7c8f61d</authentication>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="7612">
              <text>Krystle Nowhitney Hernandez</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7604">
                <text>Ricardo Ernesto Parra Vargas</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7605">
                <text>Nuestro Transporte/Our Transportation </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="55">
            <name>Alternative Title</name>
            <description>An alternative name for the resource. The distinction between titles and alternative titles is application-specific.</description>
            <elementTextContainer>
              <elementText elementTextId="7606">
                <text>Ricardo Ernesto Parra Vargas_2017_2.jpg</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7607">
                <text>2017</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7608">
                <text>Saratoga Race Course, Saratoga Springs, NY, USA</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7609">
                <text>Calor, frio, lluvia,  nuestro transporte es tan rápido o lento como queramos, siempre en movimiento, siempre dándonos la oportunidad de contemplar la belleza de nuestro Saratoga. &#13;
 &#13;
Hot, cold, rain, our transportation is as fast or as slow as we want, always in motion, always giving us the chance to contemplate the beauty of our Saratoga. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="67">
            <name>License</name>
            <description>A legal document giving official permission to do something with the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="7610">
                <text>This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.</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="7611">
                <text>Digital Photograph, JPEG</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="244">
        <name>art</name>
      </tag>
      <tag tagId="270">
        <name>bilingual</name>
      </tag>
      <tag tagId="728">
        <name>Estamos Aqui</name>
      </tag>
      <tag tagId="263">
        <name>immigration</name>
      </tag>
      <tag tagId="256">
        <name>Latinx</name>
      </tag>
      <tag tagId="104">
        <name>race track</name>
      </tag>
      <tag tagId="727">
        <name>Saratoga Race Course</name>
      </tag>
      <tag tagId="269">
        <name>Spanish</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="816" public="1" featured="0">
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="7693">
              <text>Krystle Nowhitney Hernandez</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7685">
                <text>Luis Manuel Rentería Flores</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7686">
                <text>Nunca es Tarde/It’s Never Too Late</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="55">
            <name>Alternative Title</name>
            <description>An alternative name for the resource. The distinction between titles and alternative titles is application-specific.</description>
            <elementTextContainer>
              <elementText elementTextId="7687">
                <text>Luis Manuel Rentería Flores_2017_1.jpg</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7688">
                <text>2017</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7689">
                <text>Saratoga Race Course, Saratoga Springs, NY, USA</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7690">
                <text>Ganas querer aprender y  superarse aprendiendo un poquito más todos los días.&#13;&#13;You want to learn and excel by learning a little bit more every day.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="67">
            <name>License</name>
            <description>A legal document giving official permission to do something with the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="7691">
                <text>This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.</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="7692">
                <text>Digital Photograph, JPEG</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="244">
        <name>art</name>
      </tag>
      <tag tagId="270">
        <name>bilingual</name>
      </tag>
      <tag tagId="728">
        <name>Estamos Aqui</name>
      </tag>
      <tag tagId="263">
        <name>immigration</name>
      </tag>
      <tag tagId="256">
        <name>Latinx</name>
      </tag>
      <tag tagId="104">
        <name>race track</name>
      </tag>
      <tag tagId="727">
        <name>Saratoga Race Course</name>
      </tag>
      <tag tagId="269">
        <name>Spanish</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="314" public="1" featured="0">
    <fileContainer>
      <file fileId="862">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/4e76e28272950cca87fa388c1cca9a77.jpg</src>
        <authentication>7a8df03b2b5791ad0b2005408706426c</authentication>
      </file>
      <file fileId="863">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/e5485a08fdbf42fa80ef340f2957b59c.mp4</src>
        <authentication>b28f140b2b7ce661d39b31623857672a</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="4043">
                    <text>Migration Story</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="44">
                <name>Language</name>
                <description>A language of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="4044">
                    <text>eng</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
      <file fileId="864">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/3abc915f9c1c10c7fd9985ccdf5bce10.mp4</src>
        <authentication>5105b3866d5403d2947935d37aa5eb83</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="4045">
                    <text>Nurianny Montilla Identity Part 1: Trujillo, Food</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
      <file fileId="865">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/c8c845cd243d2f815c2f7fb995ceb5d4.mp4</src>
        <authentication>ed6866c913cbdede2ed527ffada16022</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="4046">
                    <text>Nurianny Montilla Identity Part 2: Hair</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
      <file fileId="866">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/ec94d846a7569f5c561b97c8f9565c50.mp4</src>
        <authentication>1a7441711c22e5f71197ea436fe24e72</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="4047">
                    <text>Nurianny Montilla Identity Part 3: Anthro 101</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
      <file fileId="867">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/2f59fe1037137da2f832618100ccefae.mp4</src>
        <authentication>c7b088fd8410339223df9a2d57827124</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="4048">
                    <text>Nurianny Montilla Daily Life at Skidmore</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
      <file fileId="868">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/19beb7c4e6f29f170c36b8aba16947ba.mp4</src>
        <authentication>ef7a29dcf14f3b475a288238581a6aab</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="4049">
                    <text>Nurianny Montilla Daily Life at Skidmore, Family</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="27">
      <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="4003">
                  <text>Latinx</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="4">
      <name>Oral History</name>
      <description>A resource containing historical information obtained in interviews with persons having firsthand knowledge.</description>
      <elementContainer>
        <element elementId="2">
          <name>Interviewer</name>
          <description>The person(s) performing the interview</description>
          <elementTextContainer>
            <elementText elementTextId="3949">
              <text>Abby Outterson</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="3">
          <name>Interviewee</name>
          <description>The person(s) being interviewed</description>
          <elementTextContainer>
            <elementText elementTextId="3950">
              <text>Nurianny Montilla</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="3951">
              <text>Abby Outterson</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="3952">
              <text>04/26/2016</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="4">
          <name>Location</name>
          <description>The location of the interview</description>
          <elementTextContainer>
            <elementText elementTextId="3982">
              <text>Skidmore College, Saratoga Springs, NY</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="3947">
                <text>Nurianny Montilla Interview</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3948">
                <text>Abby Outterson</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3980">
                <text>03/26/2016</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4089">
                <text>Nurianny Montilla is a Skidmore student living in Saratoga Springs, NY. She is a senior at Skidmore majoring in sociology, and she spoke with fellow Skidmore senior Abigail Outterson on March 26th, 2016 about her experiences being born in the Dominican Republic, growing up in New Jersey, and coming to Saratoga Springs to attend Skidmore College.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="264">
        <name>Dominican</name>
      </tag>
      <tag tagId="275">
        <name>identity</name>
      </tag>
      <tag tagId="223">
        <name>Latina</name>
      </tag>
      <tag tagId="256">
        <name>Latinx</name>
      </tag>
      <tag tagId="197">
        <name>oral history</name>
      </tag>
      <tag tagId="200">
        <name>Skidmore College</name>
      </tag>
      <tag tagId="290">
        <name>student</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1163" public="1" featured="0">
    <fileContainer>
      <file fileId="1928">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/905cf4da63c627ba19c2008bff9f4244.JPG</src>
        <authentication>a170f012a603a26a850b4c94c277b078</authentication>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="10087">
              <text>Scope Magazine</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="10084">
                <text>Nursing Alums at Reunion Weekend</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10085">
                <text>June 1st, 2019</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="10086">
                <text>Scope Magazine</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="813">
        <name>Nursing</name>
      </tag>
      <tag tagId="165">
        <name>public history</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1162" public="1" featured="0">
    <fileContainer>
      <file fileId="1927">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/baeee54e168a096046145401d80ef1b8.JPG</src>
        <authentication>9be870771a3b96096e4074d1bf5b71d6</authentication>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include 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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10082">
                <text>Nursing Alums Reunion Weekend </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10083">
                <text>June 1st, 2019</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="813">
        <name>Nursing</name>
      </tag>
      <tag tagId="165">
        <name>public history</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1120" public="1" featured="0">
    <fileContainer>
      <file fileId="1880">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/ff7ba513404ff79fc5c744466bfdd38e.png</src>
        <authentication>7386798d90ab498c58d1e4e1696e43c4</authentication>
      </file>
    </fileContainer>
    <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="10000">
                <text>Nursing Memory Project cover photo</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1125" public="1" featured="0">
    <fileContainer>
      <file fileId="1885">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/33def00fe1b7d43be88e99e287da2857.png</src>
        <authentication>daea5eaf8125e1c0f0934d138e1d3a1c</authentication>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include 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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10007">
                <text>Nursing student at work</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1131" public="1" featured="0">
    <fileContainer>
      <file fileId="1891">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/a672f0e7d7e6ea560c8f928aee09272d.png</src>
        <authentication>5cae8512948e45d6686e6f00498afdad</authentication>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include 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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10014">
                <text>Nursing students in NYC</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="813">
        <name>Nursing</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1042" public="1" featured="0">
    <fileContainer>
      <file fileId="1766">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/d49b741c22e67efb755156f24977c0fb.jpg</src>
        <authentication>0b7d1dcf452226103cf6f58d347e73d2</authentication>
      </file>
    </fileContainer>
    <collection collectionId="32">
      <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="5012">
                  <text>Saratoga Springs History</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5015">
                  <text>1706-</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>
      <elementContainer>
        <element elementId="118">
          <name>Repository</name>
          <description>Name of the repository that holds the original item.</description>
          <elementTextContainer>
            <elementText elementTextId="9085">
              <text>Saratoga Room, Saratoga Springs Public Library</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="9088">
              <text>Jillian Seigel</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="9089">
              <text>43270</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="9079">
                <text>NYC bus company adds Saratoga run</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9080">
                <text>7/7/10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9081">
                <text>Zarnowski, Tatiana</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="9082">
                <text>The Daily Gazette</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="93">
            <name>Provenance</name>
            <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="9083">
                <text>Saratoga Springs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9084">
                <text>Transportation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9086">
                <text>A bus line that is expanding its expres service to Saratoga Springs will pick up passengers at 6:30 a.m. in front of Congress Park at the tourist booth on Broadway, and leave from New York at 8 p.m. for a return trip each day. A ticket will cost approx. $20.</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="9087">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="784">
        <name>EnvironmentalJustice</name>
      </tag>
      <tag tagId="782">
        <name>SaratogaSprings</name>
      </tag>
      <tag tagId="26">
        <name>transportation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="792" public="1" featured="0">
    <fileContainer>
      <file fileId="1586">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/4d7706389ef2759ebf255690287c0c3d.jpg</src>
        <authentication>28b12138b85b23471cd309894579e6fc</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="7422">
                    <text>Unitled</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="40">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="7423">
                    <text>March, 2018</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Is Part Of</name>
                <description>A related resource in which the described resource is physically or logically included.</description>
                <elementTextContainer>
                  <elementText elementTextId="7424">
                    <text>NYC With My Dad</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="39">
                <name>Creator</name>
                <description>An entity primarily responsible for making the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="7425">
                    <text>Addy Lindley</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="7426">
                    <text>Photograph</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
      <file fileId="1587">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/cdec43242307bffb2dcdebe43689ebe9.jpg</src>
        <authentication>bf7eeefb4541d0be577bc7c7e4998fa2</authentication>
      </file>
      <file fileId="1588">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/688d53c416f12032de9eea5be9e2b86f.jpg</src>
        <authentication>c024b139716994c29fe4487b85f2d82c</authentication>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="7352">
              <text>Addie Lindley</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="7353">
              <text>19/4/2018</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="7341">
                <text>NYC with my Dad</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7342">
                <text>March 2018</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7343">
                <text>Lindley, Addie</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7344">
                <text>Addie Lindley</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="7345">
                <text>Photograph</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="436">
        <name>father</name>
      </tag>
      <tag tagId="741">
        <name>Lindley</name>
      </tag>
      <tag tagId="775">
        <name>MDOCS</name>
      </tag>
      <tag tagId="742">
        <name>Midtown</name>
      </tag>
      <tag tagId="743">
        <name>NYC</name>
      </tag>
      <tag tagId="234">
        <name>Principles of Documentary</name>
      </tag>
      <tag tagId="776">
        <name>Spring 2018</name>
      </tag>
      <tag tagId="777">
        <name>This Place</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="10" public="1" featured="0">
    <fileContainer>
      <file fileId="17">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/c475ded80275057ba5530fdf80e7554e.PDF</src>
        <authentication>2f6d1769ab84c372b95ce4b07f8c8b29</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="258">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="4933">
                    <text>li-;q

'l '?+9'

fal-,'. {4*'r''-,

Samuel J. Mott, Saratoga
Engineersiirce 1893, Deacl
CureerEn"ds
Samuel

J.

Mot

city engineer,
*tlr""'""tttt""t'

ins profession uPstate, died last
niEirt at the Saratoga HosPital
after a brief illness.
Mr. Mott was village engineer
with his father, the late Jesso S.
Mott, from 1893 until his father's
death in 1913, when he continued
as village engineer and became
city engineer at the tlme the pres-

|1

,

"

J

iProminent Enginegr
ir

I

, Samuel J. Mott Blilt Hydro-ElecfricI
'
Plsnt ffiffian
ManufacI
j
i
turing c'r4pany.

I eni charter was adoPted.in 1916.
In recent Years he had also been
in charge of the citY WPA Projects.
Born In Dcan's Corners
IIe was born in Dean's Corners
Feb. 22, 1869. He rvas educated st
Yates Saratoga Institute in North
Broadway, this city, and received
his engineering tlaining in appren,ticeship to his father, who rvas
II'
the late L
associated with
Cramer in the flrm of Cramer &amp;
Mott. Upon the withdrawal of Mr.
'Cramer
in 1892 Samuel J. Mott
'became bis father's
Partner in the
ffrm of J. S' Mott &amp; Son.
' As
and constructiolt
designer
engineer Mr. yott was connectecl
\yith many pi"ojects in lilorthern
Nerv York over a long term of
years. In 1892 he built the Sara'
He
rnac and Lake Placid Bailroad.
designed and constructed the Corinth sewage system and treatment
rplant. in 1904 and rvas in charge
ro! the constl'uction of the Saratoga
disPosal
sewage
Plant
Spfings
under Snow &amp; Barbour in 1902.
IIe was resident representative of
,Nicholas S. tIill, consulting engineer, during the construction of
the modern waterworks sY6te6 ilr
thi! cltY tn 1e36' t)^1
q Q
Surve]'ed Raccway VAI*'
'
Mr. Mott surveYed the grounds
and did a major Portion of the
and. engineering for
Llayout wolk
harness
Sarptog;a RacewaY
tle
'tfgck
bullt here two Years ego.
yearb ho had -been a
F6t'nrany
corriultant with.ofticials of the Sary
over
Association
Racing
atoga
at
track and engineeling )g,olli9t
the t'acecourse.
I 7
Y/r,
.
c
I over a long pef iod h0 \va.s- nSl\[anufaci neer for the American
I turin8 Co. at Victory Mills and

tl-J^171

a Not/, l+-S--rF

seliunr,

J. }IOTT

built the hydro-electlic plant there. I I
His advice was frequently sought l.
on engineering ploblems throughout Northern Nerv York, where his
integrity of chalacter and ability
as an engineer were widely recogn ized.
I{r. Mott was a }fason, and a
the
Plesbytilian
member
of
Chul'ch, tbe Old Guard AsspciatioB
of Company L and' the Tt'i-CountY
Chapter of the New York State
Society ef Prgfessional . Engineers.

I{e .b survived bv his wife and *
. -.^;
sister, Mlss. Cira- E.-NelL.
The funeral rvill .be.';!g_ldFetaurl

day at 2 p.m. at the late lesidence, | |
157 Spling St. The Rev.. Reuben lt

of
Saratoga
Samuel J. Mott,
''d'
Via"ty*tio*tfr'
engineer of
;Springsf
upper New York state, and a promi,nent figure in this vicinity over a
;long period when he acted as engineer
the - American Manufacturing
ifor
lcompany a't Victory Mills, died ThursI day night in the Saratoga hospital,
I
lf ollowing a brief ,illness. 'r.He was
I born in Deans Corners, February 22,
| 1869.
I Mr. Mott was a designer and cone;rgineer. He wae connectlstruction 'manf
led with
brajects in northern
I New York over &amp; long term of years.
lHe built the Saranaq and I,ake Placid
I railroad, designed . and constructed
Ithe,Corinth sewage.system and treatlment plant, and was in charge of the
l.construction of thb Saratoga Springs
I sewage disposal plant in 1902.
I Mr. Mott sulveyed the grounds and
ldid a major por,tion.ofl the layout
I work and engineering for the SaraItoga Raceway harness track buil.t at
lblie Spa two years ago.
I As engineer for the Arnerican Manthe
I ufacturing company, he built
lhydro-electric plant. At bhe time of
lhis death, he was city engineer of
l Saratoga Springs.
I The funeral took place at the late
lresidence .in Saratoga'Springs Satlurday afternoon. Burial was in the
Greenrid8e cemetery.
I
I

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="34">
      <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="5030">
                  <text>Mapping Saratoga Springs</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5031">
                  <text>1700-</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>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="448">
              <text>Allie Smith &#13;
Allie Smith </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="121">
          <name>Abstract (&amp; Historical Note)</name>
          <description>Natural language description of the map itself, providing a general summary of the map and noting significant features. &#13;
&#13;
This is the place to introduce keywords and proper names that might be of interest to researchers, but do not warrant a separate subject heading of their own. Inset maps should also be described here, with their full titles given.&#13;
&#13;
Whenever historical or explanatory information is available, it should be included here as well. This includes information about items or events that are larger than just the map itself; for example, information about cartographers, a description of the map's historical significance (for example, "This is the first printed map of Saratoga Springs"), notes on the laws leading to a map's creation, descriptions of changes in state or county lines, information about the organization that created the map, how often maps were updated, and information about the map's creation and publication. Many State Archives maps have historical information in the catalog record -- that should be captured in this field.</description>
          <elementTextContainer>
            <elementText elementTextId="449">
              <text>Obituaries dated:&#13;
10/29/1942&#13;
11/02/1942&#13;
&#13;
The obituary of Samuel J. Mott as written in the Saratogian and another newspaper following his death. This article not only remembers Mott as a person but focus on his career as a prominent city engineer for Saratoga Springs (N.Y.).&#13;
Information includes some of Mott's projects during his career including part of the Saratoga Raceway, as well as personal information such as his father's name and profession as an engineer. </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="111">
          <name>Subject - Details</name>
          <description>This subject field describes the amount of detail in a map.&#13;
&#13;
For maps:  (or layers) included on the map itself. This field might denote that the map includes information about, for example, Mountains, Railroads, Soundings, Elevation, or Population. These are controlled-vocabulary terms developed locally. The cataloger should be generous in assigning these terms -- even if only one canal is visible on the map, it should receive a "Canals" subject in this layer. &#13;
&#13;
Some of these terms are less specific than others and may warrant expansion in the Abstract field. For example, the "Businesses" term might be included here while the Abstract notes that the map shows mills and stores. Multiple terms can be used in this field.</description>
          <elementTextContainer>
            <elementText elementTextId="450">
              <text>Church-- Presbyterian&#13;
Saratoga Racecourse (Saratoga Springs, N.Y.)&#13;
American Manufacturing Company (Victory Mills, N.Y.)&#13;
Saratoga and Lake Placid R.R. (N.Y.)&#13;
Yates Saratoga Institute (Saratoga Springs, N.Y.)&#13;
Saratoga Springs (N.Y.)--Downtown--Businesses&#13;
J.S. Mott &amp; Son (Saratoga Springs, N.Y.)&#13;
Greenridge Cemetery (Saratoga Springs, N.Y.)&#13;
The Saratogian (Saratoga Springs, N.Y.)</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="112">
          <name>Subject - Geographic</name>
          <description>Library of Congress subject headings.&#13;
&#13;
For maps: for major geographic locations depicted on the map, followed, in nearly every case, by the "Maps" genre subheading. (For example, "Saratoga Springs (N.Y.) -- Maps.") This field will be especially important when the records from this collection are incorporated into larger databases and catalogs.</description>
          <elementTextContainer>
            <elementText elementTextId="451">
              <text>Saratoga Springs (N.Y.)&#13;
Victory Mills (N.Y.)</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="113">
          <name>Subject - Name</name>
          <description>Names of individuals associated with the item.  Last name first.&#13;
&#13;
For Maps: People represented on the map itself. In nearly every case, this field will be used when people are pictured on the map (several maps in this project are decorated with photographs or engravings in the margins). Use authorized versions of the name from the Library of Congress Name Authority File where possible.</description>
          <elementTextContainer>
            <elementText elementTextId="452">
              <text>Hill, Nicholas S. Consulting engineer. Saratoga Springs (N.Y.)&#13;
Mott, Samuel J.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="109">
          <name>Theme</name>
          <description>For browsing purposes, we are borrowing and adapting themes from the Library of Congress's American Memory project.</description>
          <elementTextContainer>
            <elementText elementTextId="453">
              <text>Civic Life</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="118">
          <name>Repository</name>
          <description>Name of the repository that holds the original item.</description>
          <elementTextContainer>
            <elementText elementTextId="1343">
              <text>The City Archives (Saratoga Springs, N.Y.)</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="108">
          <name>Related Maps</name>
          <description>There will be many cases where multiple maps are in effect only slight variations on a single original. If we are certain, or even pretty sure, that one map is just a slightly altered version of another,the related versions should be listed here.</description>
          <elementTextContainer>
            <elementText elementTextId="1344">
              <text>Item 64</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="7">
          <name>Original Format</name>
          <description>The type of object, such as painting, sculpture, paper, photo, and additional data</description>
          <elementTextContainer>
            <elementText elementTextId="2662">
              <text>Newspaper article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="7129">
              <text>6/9/2014&#13;
2/28/2015</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="96">
                <text>Obituaries of Samuel J. Mott</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="97">
                <text>Saratoga Springs (N.Y.)--Business--Development&#13;
Mott, Samuel J. -- Obituary&#13;
Civil Engineer&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="98">
                <text>Obituaries for Samuel J. Mott published in the Saratogian and another newspaper 10/29 and 11/2/1942</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="445">
                <text>1942</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="73">
            <name>Is Part Of</name>
            <description>A related resource in which the described resource is physically or logically included.</description>
            <elementTextContainer>
              <elementText elementTextId="446">
                <text>Newspaper</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="447">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="42">
        <name>20th century</name>
      </tag>
      <tag tagId="548">
        <name>city government</name>
      </tag>
      <tag tagId="85">
        <name>city planning</name>
      </tag>
      <tag tagId="14">
        <name>civil engineer</name>
      </tag>
      <tag tagId="552">
        <name>mapmaking</name>
      </tag>
      <tag tagId="12">
        <name>Mott</name>
      </tag>
      <tag tagId="39">
        <name>obituary</name>
      </tag>
      <tag tagId="40">
        <name>Saratogian</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1069" public="1" featured="0">
    <fileContainer>
      <file fileId="1815">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/83611040ef458415511facac7c1bbf6a.JPG</src>
        <authentication>a532ca02b7bfd8e9373185e4b1d64a15</authentication>
      </file>
    </fileContainer>
    <collection collectionId="32">
      <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="5012">
                  <text>Saratoga Springs History</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5015">
                  <text>1706-</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>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="9360">
              <text>Jillian Seigel</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="9361">
              <text>43270</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="9352">
                <text>Officials: Low-income city housing necessary</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9353">
                <text>9/6/88</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9354">
                <text>Cloos, Paul</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="93">
            <name>Provenance</name>
            <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="9355">
                <text>Saratoga Springs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9356">
                <text>Urban Renewal</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9358">
                <text>City Council members said they were not against low-income housing in the city.</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="9359">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="784">
        <name>EnvironmentalJustice</name>
      </tag>
      <tag tagId="782">
        <name>SaratogaSprings</name>
      </tag>
      <tag tagId="783">
        <name>UrbanRenewal</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="813" public="1" featured="0">
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="7666">
              <text>Krystle Nowhitney Hernandez</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7658">
                <text>Ceyla Guadalupe Macedo Soto</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7659">
                <text>Oficina/Office</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="55">
            <name>Alternative Title</name>
            <description>An alternative name for the resource. The distinction between titles and alternative titles is application-specific.</description>
            <elementTextContainer>
              <elementText elementTextId="7660">
                <text>Ceyla Guadalupe Macedo Soto_2017_2.jpg</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7661">
                <text>2017</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7662">
                <text>Saratoga Race Course, Saratoga Springs, NY</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7663">
                <text>Sin tanto que agregar. Tan solo con luz y sombra puedes sentir la paz y tranquilad de las personas que trabajan en este lugar  para apoyarnos y enseñarnos más.&#13;&#13;Without much to add.  With just light and shadow you can feel the peace and tranquility of the people who work in this place to support and teach us more.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="67">
            <name>License</name>
            <description>A legal document giving official permission to do something with the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="7664">
                <text>This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.</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="7665">
                <text>Digital Photograph, JPEG</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="244">
        <name>art</name>
      </tag>
      <tag tagId="270">
        <name>bilingual</name>
      </tag>
      <tag tagId="728">
        <name>Estamos Aqui</name>
      </tag>
      <tag tagId="263">
        <name>immigration</name>
      </tag>
      <tag tagId="256">
        <name>Latinx</name>
      </tag>
      <tag tagId="104">
        <name>race track</name>
      </tag>
      <tag tagId="727">
        <name>Saratoga Race Course</name>
      </tag>
      <tag tagId="269">
        <name>Spanish</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1384" public="1" featured="0">
    <fileContainer>
      <file fileId="2494">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/5b6498f42905a0cae7d2417790c87b3d.jpg</src>
        <authentication>62fd5208b889d01b9e973b5bcb43772f</authentication>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="11917">
              <text>Brookside Museum</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="11918">
              <text>2007</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="97">
          <name>Publisher</name>
          <description>Publisher of the item, or of the book or atlas in which it appears.</description>
          <elementTextContainer>
            <elementText elementTextId="11919">
              <text>Brookside Museum</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="11916">
                <text>Old Iron Spring</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1314" public="1" featured="0">
    <fileContainer>
      <file fileId="2411">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/73f81792702f0f44bfd7cf3f8c8e972a.png</src>
        <authentication>dbf3b6f6a9a28a1436e42dd4d594ce12</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="11231">
                    <text>Old Iron Spring, Ballston Spa, NY</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="40">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="11232">
                    <text>Unknown</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="42">
      <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="10665">
                  <text>Saratoga County</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="7">
          <name>Original Format</name>
          <description>The type of object, such as painting, sculpture, paper, photo, and additional data</description>
          <elementTextContainer>
            <elementText elementTextId="11321">
              <text>b/w photo</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="11322">
              <text>5/6/2021</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="101">
          <name>Date Depicted (Display)</name>
          <description>Text version of the date field -- can handle non-numeric characters (ca. 1850s, [1844]). This is the content date field that will display.</description>
          <elementTextContainer>
            <elementText elementTextId="11323">
              <text>Unknown</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="121">
          <name>Abstract (&amp; Historical Note)</name>
          <description>Natural language description of the map itself, providing a general summary of the map and noting significant features. &#13;
&#13;
This is the place to introduce keywords and proper names that might be of interest to researchers, but do not warrant a separate subject heading of their own. Inset maps should also be described here, with their full titles given.&#13;
&#13;
Whenever historical or explanatory information is available, it should be included here as well. This includes information about items or events that are larger than just the map itself; for example, information about cartographers, a description of the map's historical significance (for example, "This is the first printed map of Saratoga Springs"), notes on the laws leading to a map's creation, descriptions of changes in state or county lines, information about the organization that created the map, how often maps were updated, and information about the map's creation and publication. Many State Archives maps have historical information in the catalog record -- that should be captured in this field.</description>
          <elementTextContainer>
            <elementText elementTextId="11324">
              <text>Old Iron Spring - Ballston Spa - balneology - mineral water</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="28">
          <name>URL</name>
          <description/>
          <elementTextContainer>
            <elementText elementTextId="11325">
              <text>https://brookside.pastperfectonline.com/photo/E348B04B-11B8-4BDB-979C-070251333680</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="11369">
              <text>Miles Herman</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="11227">
                <text>Old Iron Spring, Ballston Spa, NY</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11228">
                <text>Unknown</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="73">
            <name>Is Part Of</name>
            <description>A related resource in which the described resource is physically or logically included.</description>
            <elementTextContainer>
              <elementText elementTextId="11229">
                <text>Brookside Museum, Saratoga County Historical Society&#13;
URL: https://brookside.pastperfectonline.com/photo/E348B04B-11B8-4BDB-979C-070251333680</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11230">
                <text>Ballston Spa, NY, where the Old Iron Spring is still working, was originally more popular than Saratoga Springs as a place for tourists to visit and take the waters in the 19th Century. But the opening of Gideon Putam's Tavern and Guesthouse helped shift spa tourists to Saratoga Springs. </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1253" public="1" featured="0">
    <fileContainer>
      <file fileId="2285">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/404dcaf964b79b68c29609207e07bc34.jpg</src>
        <authentication>b91ccf47786325dc21394255cbcc3e2f</authentication>
      </file>
    </fileContainer>
    <collection collectionId="42">
      <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="10665">
                  <text>Saratoga County</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="10818">
              <text>Will Kertzman</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="10814">
                <text>old stone church in Saratoga Springs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10815">
                <text>1826</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="10816">
                <text>Brookside Museum - https://brookside.pastperfectonline.com/webobject/B74943FC-14F9-4B83-A76C-990972280384</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="56">
            <name>Abstract</name>
            <description>A summary of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="10817">
                <text>pen and ink drawing of the old stone church in Saratoga Springs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10996">
                <text>Will Kertzman</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="884">
        <name>1800s</name>
      </tag>
      <tag tagId="871">
        <name>church</name>
      </tag>
      <tag tagId="29">
        <name>religion</name>
      </tag>
      <tag tagId="77">
        <name>Saratoga Springs</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="276" public="1" featured="0">
    <fileContainer>
      <file fileId="754">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/87aadbbaa9e8e4919a207fc41d3a232a.jpg</src>
        <authentication>6f207b3b4f67fb14888784e0e4258c29</authentication>
      </file>
    </fileContainer>
    <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="3771">
                <text>omeka-logo.jpg</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1083" public="1" featured="0">
    <fileContainer>
      <file fileId="1791">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/b335c41fd8774c5733e42b949d21e11e.jpg</src>
        <authentication>407b961896bba23d1a2413c791d8b0de</authentication>
      </file>
      <file fileId="1792">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/e6c131cf139ef089fecae5e8e1304f56.jpg</src>
        <authentication>2f8507bd56124ee0c9120f3a52f550a4</authentication>
      </file>
      <file fileId="1793">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/a2333a6d82af06d0863633665b8af6d7.jpg</src>
        <authentication>5b587fdecf30c01bdffe1b17709574d3</authentication>
      </file>
    </fileContainer>
    <collection collectionId="32">
      <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="5012">
                  <text>Saratoga Springs History</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5015">
                  <text>1706-</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>
      <elementContainer>
        <element elementId="118">
          <name>Repository</name>
          <description>Name of the repository that holds the original item.</description>
          <elementTextContainer>
            <elementText elementTextId="9506">
              <text>Saratoga Room, Saratoga Springs Public Library</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="9509">
              <text>Jillian Seigel</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="9510">
              <text>43270</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="9500">
                <text>On Track? Details of $12 million rail project emerge</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9501">
                <text>6/13/98</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9502">
                <text>Woodyard, Michael</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="9503">
                <text>The Post Star</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="93">
            <name>Provenance</name>
            <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="9504">
                <text>Glens Falls</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9505">
                <text>Transportation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9507">
                <text>Plans for a new rail project are emerging</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="9508">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="784">
        <name>EnvironmentalJustice</name>
      </tag>
      <tag tagId="782">
        <name>SaratogaSprings</name>
      </tag>
      <tag tagId="26">
        <name>transportation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1325" public="1" featured="0">
    <fileContainer>
      <file fileId="2428">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/a82837c5f293bb4097237083de1a98b8.jpg</src>
        <authentication>eb7c48c656cc2a27efb39e25225b542a</authentication>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="11397">
              <text>Mattie Saulnier</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="11398">
              <text>6/5/21</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="28">
          <name>URL</name>
          <description/>
          <elementTextContainer>
            <elementText elementTextId="11399">
              <text>https://www.asce.org/project/waterford-(union)-bridge-(replaced-in-1909)/</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="11396">
                <text>Original Waterford Bridge</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11405">
                <text>1804</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1068" public="1" featured="0">
    <fileContainer>
      <file fileId="1824">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/e261688dcc5185600aff4b01a4fd418e.JPG</src>
        <authentication>e8632e4ac7a5cd8d027ec60ed1091d74</authentication>
      </file>
      <file fileId="1825">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/de7cf5ee6aeda34664447e885d8dad57.JPG</src>
        <authentication>9af6dea5691c5cb0065abe924bc66237</authentication>
      </file>
    </fileContainer>
    <collection collectionId="32">
      <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="5012">
                  <text>Saratoga Springs History</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5015">
                  <text>1706-</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>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="9350">
              <text>Jillian Seigel</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="9351">
              <text>43270</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="9341">
                <text>Out in the cold: Lack of low-cost housing keeps people on streets</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9342">
                <text>2/13/88</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9343">
                <text>Powers, Mary Caroline</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="9344">
                <text>The Saratogian</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="93">
            <name>Provenance</name>
            <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="9345">
                <text>Saratoga Springs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9346">
                <text>Urban Renewal</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9348">
                <text>In Saratoga Springs, the Queen of the Spas, a lack of low-income housing and no emergency shelters force people on to the streets.</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="9349">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="782">
        <name>SaratogaSprings</name>
      </tag>
      <tag tagId="783">
        <name>UrbanRenewal</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="160" public="1" featured="0">
    <fileContainer>
      <file fileId="345">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/487764cb43950c4dd6f0bae958d8346c.jpg</src>
        <authentication>6680a39858b0ad4fdd70a42a99c51e74</authentication>
      </file>
      <file fileId="347">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/5b272597363605047ed3a5c0951c732b.jpg</src>
        <authentication>c87f58eddf8284ae83b2d1037d01ac68</authentication>
      </file>
    </fileContainer>
    <collection collectionId="34">
      <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="5030">
                  <text>Mapping Saratoga Springs</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5031">
                  <text>1700-</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="18">
      <name>Map</name>
      <description>Cartographic document</description>
      <elementContainer>
        <element elementId="95">
          <name>Creator - Individual</name>
          <description>Name of the person or people responsible for creating the item.</description>
          <elementTextContainer>
            <elementText elementTextId="2353">
              <text>Murphy &amp; Kren Planning Associates Inc.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="107">
          <name>Related Item</name>
          <description>If the item is a part of a book or a manuscript or archival collection, that should be noted here. Think of this field as the "parent item" or "parent collection". Entries in this field should generally be written as full citations.</description>
          <elementTextContainer>
            <elementText elementTextId="2355">
              <text>1970 Core Area Development Map, 1971 Core Area Development Map</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="101">
          <name>Date Depicted (Display)</name>
          <description>Text version of the date field -- can handle non-numeric characters (ca. 1850s, [1844]). This is the content date field that will display.</description>
          <elementTextContainer>
            <elementText elementTextId="2356">
              <text>1971</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="100">
          <name>Date Depicted (Numeric)</name>
          <description>Date that the information on the item depicts. In many cases, this will be the same date as that in the date field, but there will be exceptions. For example, a historical map drawnin 1890 might show Saratoga Springs as it was in 1820. Or, the information on the map itself might include detailed information that enables us to extrapolate a date, for example, "based on a survey done in 1841." Many State Archives map catalog records refer to this as the "situation date."</description>
          <elementTextContainer>
            <elementText elementTextId="2357">
              <text>1971</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="99">
          <name>Date Published (Display)</name>
          <description>Text version of the date field -- can handle non-numeric characters (ca. 1850s, [1844]). This is the date field that will display.</description>
          <elementTextContainer>
            <elementText elementTextId="2358">
              <text>1971</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="98">
          <name>Date Published (Numeric)</name>
          <description>Date the item was printed. This will be set as a date field, accommodating only numbers. The field will be able to handle single dates or date ranges. This will not display, but will be indexed and searchable.</description>
          <elementTextContainer>
            <elementText elementTextId="2359">
              <text>1971</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="102">
          <name>Caption</name>
          <description>This field will include transcriptions of text that appears on or around the item, at the discretion of the cataloger. It should include relevant bibliographic information that is not given in the title, for example, "Top of map: 'EXAMPLE NEEDED' Publisher and printer information might also be included in this field: "EXAMPLE NEEDED.'" Note that the location of the printed text is given in the field itself and that the caption information is always included in quotes.</description>
          <elementTextContainer>
            <elementText elementTextId="2360">
              <text>Core Area, May 1970, adopted by February 1971 &#13;
Outer Area Map, Revised June 17, 1971 and adopted by the City Council on July 7, 1971.  (colored)</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="108">
          <name>Related Maps</name>
          <description>There will be many cases where multiple maps are in effect only slight variations on a single original. If we are certain, or even pretty sure, that one map is just a slightly altered version of another,the related versions should be listed here.</description>
          <elementTextContainer>
            <elementText elementTextId="2361">
              <text>1970 and 1971 Core Area Development Maps</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="118">
          <name>Repository</name>
          <description>Name of the repository that holds the original item.</description>
          <elementTextContainer>
            <elementText elementTextId="2362">
              <text>Saratoga Room, Saratoga Springs Public Library</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="109">
          <name>Theme</name>
          <description>For browsing purposes, we are borrowing and adapting themes from the Library of Congress's American Memory project.</description>
          <elementTextContainer>
            <elementText elementTextId="2363">
              <text>Property and Development</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="2364">
              <text>Jordana Dym&#13;
Emily Sloan</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="2365">
              <text>12/2/2014</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="121">
          <name>Abstract (&amp; Historical Note)</name>
          <description>Natural language description of the map itself, providing a general summary of the map and noting significant features. &#13;
&#13;
This is the place to introduce keywords and proper names that might be of interest to researchers, but do not warrant a separate subject heading of their own. Inset maps should also be described here, with their full titles given.&#13;
&#13;
Whenever historical or explanatory information is available, it should be included here as well. This includes information about items or events that are larger than just the map itself; for example, information about cartographers, a description of the map's historical significance (for example, "This is the first printed map of Saratoga Springs"), notes on the laws leading to a map's creation, descriptions of changes in state or county lines, information about the organization that created the map, how often maps were updated, and information about the map's creation and publication. Many State Archives maps have historical information in the catalog record -- that should be captured in this field.</description>
          <elementTextContainer>
            <elementText elementTextId="3256">
              <text>In 1970, the City Planning Board worked with Murphy &amp; Kren Planning Associates, Inc. on a map and report for the New York State Department of Commerce Bureau making recommendations for a 20-year development plan that identified Cady Hill and the area by I-87 as places to grow industry, and Geyser Crest and the West Side as targets for residential development. This plan, financially aided by federal and state funds, was adopted by the city council in February 1971.&#13;
&#13;
This map includes more kinds of land use than in 1937 (seasonal, high and medium density residential, commercial; industrial; parks; public/semi-public; track), but the overall thrust is the same. The Murphy &amp; Kren map highlights development interests beyond Broadway’s axis and the corporation line “inner” district and the report underlines the need for schools to be integrated in new neighborhoods.</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="2351">
                <text>Outer Area Zoning Map and Core Area Zoning Map</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2352">
                <text>1970</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="3001">
                <text>Murphy &amp; Kren Planning Associates Inc.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3002">
                <text>A zoning map of Saratoga Springs' core and outer areas.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3003">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3004">
                <text>Murphy &amp; Kren Planning Associates Inc.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3005">
                <text>Saratoga Springs (N.Y.)--Maps</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3006">
                <text>City of Saratoga Springs City Planning Board</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="56">
            <name>Abstract</name>
            <description>A summary of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="3007">
                <text>This planning map shows that city planners in Saratoga Springs continued to focus on development and expansion throughout the 1970s. The map intends to draw businesses and investors into the area.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="83">
            <name>Bibliographic Citation</name>
            <description>A bibliographic reference for the resource. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.</description>
            <elementTextContainer>
              <elementText elementTextId="3008">
                <text>“Outer Area Zoning Map and Core Area Zoning Map,” Skidmore Saratoga Memory Project, accessed March 23, 2015, http://ssmp.skidmore.edu/items/show/160.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="94">
            <name>Rights Holder</name>
            <description>A person or organization owning or managing rights over the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="3009">
                <text>Saratoga Room, Saratoga Springs Public Library</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="245">
        <name>map</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="133" public="1" featured="0">
    <fileContainer>
      <file fileId="298">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/c64a59fc98fed850864a5738e2c602da.jpg</src>
        <authentication>43a420bc5e7e5bb8265fb474287e2a63</authentication>
      </file>
      <file fileId="299">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/a7811f686bac5a5419cdcaab6ff48358.jpg</src>
        <authentication>29620ebc9e9a1fe6ff9106f72c4fb11b</authentication>
      </file>
    </fileContainer>
    <collection collectionId="32">
      <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="5012">
                  <text>Saratoga Springs History</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5015">
                  <text>1706-</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="2120">
              <text>Allie Smith</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="7">
          <name>Original Format</name>
          <description>The type of object, such as painting, sculpture, paper, photo, and additional data</description>
          <elementTextContainer>
            <elementText elementTextId="2127">
              <text>postcard</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="118">
          <name>Repository</name>
          <description>Name of the repository that holds the original item.</description>
          <elementTextContainer>
            <elementText elementTextId="5023">
              <text>Private Collection</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="2119">
                <text>Over the Water Jump, Saratoga Race Track, Saratoga Springs, N.Y.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="787" public="1" featured="0">
    <fileContainer>
      <file fileId="1619">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/8c15bad8938626c04ba54ef1fb84de1b.jpg</src>
        <authentication>cef25b581ab69d5abe5a8f34d7e992e4</authentication>
      </file>
      <file fileId="1620">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/f6b46ece5afbd488d7a5e01bdab0b14a.jpg</src>
        <authentication>9280ca3453f224aa7b053d1899d4878c</authentication>
      </file>
      <file fileId="1621">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/768b9788a7d837bf3b6448cffd24b3a9.jpg</src>
        <authentication>071e9a9ed4229c56df8a82c7c1fe24ac</authentication>
      </file>
      <file fileId="1622">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/cf5d4103c29e6cb898fd4f1bf6575db6.jpg</src>
        <authentication>9ea2605789bb0eae4abfa4e8c883efaa</authentication>
      </file>
      <file fileId="1623">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/1d7b03c950f7ad1e62185020dfbe6a54.jpg</src>
        <authentication>f423c9b5a9927699d72f7cbaa2c9908e</authentication>
      </file>
      <file fileId="1624">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/66c36046231a0b53e2c2e3a83e2efb84.jpg</src>
        <authentication>ae07331857ee720fe0f0f7d7cf7f48ee</authentication>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="7335">
              <text>Gordon, Emily </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="7336">
              <text>19/4/2018</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="7304">
                <text>Palamountain 200</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7305">
                <text>2018</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7312">
                <text>Gordon, Emily</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="7313">
                <text>Photograph</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="765">
        <name>books</name>
      </tag>
      <tag tagId="739">
        <name>education department</name>
      </tag>
      <tag tagId="738">
        <name>Gordon</name>
      </tag>
      <tag tagId="775">
        <name>MDOCS</name>
      </tag>
      <tag tagId="234">
        <name>Principles of Documentary</name>
      </tag>
      <tag tagId="766">
        <name>projects</name>
      </tag>
      <tag tagId="200">
        <name>Skidmore College</name>
      </tag>
      <tag tagId="776">
        <name>Spring 2018</name>
      </tag>
      <tag tagId="777">
        <name>This Place</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="237" public="1" featured="0">
    <fileContainer>
      <file fileId="586">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/76b0fd17ab7f273b5506ca1cabfec3cd.jpg</src>
        <authentication>8334120d760df9539c7f048e11b46769</authentication>
      </file>
      <file fileId="587">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/4c353071b30fa59bb27282a1466c6e5f.jpg</src>
        <authentication>e3687b7d4d90a9dd3185682e2dd7fbc8</authentication>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="7">
          <name>Original Format</name>
          <description>The type of object, such as painting, sculpture, paper, photo, and additional data</description>
          <elementTextContainer>
            <elementText elementTextId="3426">
              <text>photo</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="3427">
              <text>D. Schiff</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="3428">
              <text>4/14/15</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="101">
          <name>Date Depicted (Display)</name>
          <description>Text version of the date field -- can handle non-numeric characters (ca. 1850s, [1844]). This is the content date field that will display.</description>
          <elementTextContainer>
            <elementText elementTextId="3429">
              <text>1951</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="100">
          <name>Date Depicted (Numeric)</name>
          <description>Date that the information on the item depicts. In many cases, this will be the same date as that in the date field, but there will be exceptions. For example, a historical map drawnin 1890 might show Saratoga Springs as it was in 1820. Or, the information on the map itself might include detailed information that enables us to extrapolate a date, for example, "based on a survey done in 1841." Many State Archives map catalog records refer to this as the "situation date."</description>
          <elementTextContainer>
            <elementText elementTextId="3430">
              <text>1951</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="99">
          <name>Date Published (Display)</name>
          <description>Text version of the date field -- can handle non-numeric characters (ca. 1850s, [1844]). This is the date field that will display.</description>
          <elementTextContainer>
            <elementText elementTextId="3431">
              <text>1951</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="109">
          <name>Theme</name>
          <description>For browsing purposes, we are borrowing and adapting themes from the Library of Congress's American Memory project.</description>
          <elementTextContainer>
            <elementText elementTextId="3432">
              <text>Recreation</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="118">
          <name>Repository</name>
          <description>Name of the repository that holds the original item.</description>
          <elementTextContainer>
            <elementText elementTextId="3433">
              <text>The Saratoga Springs History Museum (Saratoga Springs, N.Y.)</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="3423">
                <text>Parada of Progress reservation Map 1951 with Reservation Map painted by Chapman.GIF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3424">
                <text>1951</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="73">
            <name>Is Part Of</name>
            <description>A related resource in which the described resource is physically or logically included.</description>
            <elementTextContainer>
              <elementText elementTextId="3425">
                <text>George S. Bolster Collection</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1075" public="1" featured="0">
    <fileContainer>
      <file fileId="1801">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/fbcd092ee75f63a02221871d9de6901c.jpg</src>
        <authentication>7f2764296e67ace50c30f1f2e6558981</authentication>
      </file>
    </fileContainer>
    <collection collectionId="32">
      <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="5012">
                  <text>Saratoga Springs History</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5015">
                  <text>1706-</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>
      <elementContainer>
        <element elementId="118">
          <name>Repository</name>
          <description>Name of the repository that holds the original item.</description>
          <elementTextContainer>
            <elementText elementTextId="9418">
              <text>Saratoga Room, Saratoga Springs Public Library</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="9421">
              <text>Jillian Seigel</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="9422">
              <text>43270</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="9412">
                <text>Parking spaces freed for summer</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9413">
                <text>7/4/03</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9414">
                <text>Brady, Sally</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="9415">
                <text>The Post Star</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="93">
            <name>Provenance</name>
            <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="9416">
                <text>Saratoga Springs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9417">
                <text>Transportation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9419">
                <text>The city could have another 80 spaces downtown this summer to help aid its parking congestion.</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="9420">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="784">
        <name>EnvironmentalJustice</name>
      </tag>
      <tag tagId="782">
        <name>SaratogaSprings</name>
      </tag>
      <tag tagId="26">
        <name>transportation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1054" public="1" featured="0">
    <fileContainer>
      <file fileId="1781">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/e52b3e54e32a36801de1011c8d28b863.jpg</src>
        <authentication>eebf340aa3ead7130462c09829fa6a9d</authentication>
      </file>
    </fileContainer>
    <collection collectionId="32">
      <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="5012">
                  <text>Saratoga Springs History</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5015">
                  <text>1706-</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>
      <elementContainer>
        <element elementId="118">
          <name>Repository</name>
          <description>Name of the repository that holds the original item.</description>
          <elementTextContainer>
            <elementText elementTextId="9212">
              <text>Saratoga Room, Saratoga Springs Public Library</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="9215">
              <text>Jillian Seigel</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="9216">
              <text>43270</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="9206">
                <text>Parking to stay free in Spa City</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9207">
                <text>3/2/10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9208">
                <text>Dimopoulos, Thomas</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="9209">
                <text>The Post Star</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="93">
            <name>Provenance</name>
            <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="9210">
                <text>Saratoga Springs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9211">
                <text>Transportation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9213">
                <text>A week after an advisory committee administered the last rites to the city's paid parking plan, the proposal was declared dead by the city council.</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="9214">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="784">
        <name>EnvironmentalJustice</name>
      </tag>
      <tag tagId="782">
        <name>SaratogaSprings</name>
      </tag>
      <tag tagId="26">
        <name>transportation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="822" public="1" featured="0">
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="7747">
              <text>Krystle Nowhitney Hernandez</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7739">
                <text>Josué C. Soto</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7740">
                <text>Paso Estrecho/Narrow Passage</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="55">
            <name>Alternative Title</name>
            <description>An alternative name for the resource. The distinction between titles and alternative titles is application-specific.</description>
            <elementTextContainer>
              <elementText elementTextId="7741">
                <text>Josue C Soto_2017_1.jpg</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7742">
                <text>2017</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7743">
                <text>Saratoga National Historical Park, Stillwater, NY, USA</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7744">
                <text>Difícil de entender el camino tan estrecho y complicado que de oportunidades que existen para los inmigrantes como este estrecho de agua.&#13;&#13;It is difficult to understand a path so narrow and complicated which gives opportunities to immigrants such as these narrows.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="67">
            <name>License</name>
            <description>A legal document giving official permission to do something with the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="7745">
                <text>This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.</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="7746">
                <text>Digital Photograph, JPEG</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="244">
        <name>art</name>
      </tag>
      <tag tagId="270">
        <name>bilingual</name>
      </tag>
      <tag tagId="728">
        <name>Estamos Aqui</name>
      </tag>
      <tag tagId="263">
        <name>immigration</name>
      </tag>
      <tag tagId="256">
        <name>Latinx</name>
      </tag>
      <tag tagId="269">
        <name>Spanish</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="821" public="1" featured="0">
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="7738">
              <text>Krystle Nowhitney Hernandez</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7730">
                <text>Nicole Tineo Gonzalez</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7731">
                <text>Pato Sin Cabeza/Headless Duck</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="55">
            <name>Alternative Title</name>
            <description>An alternative name for the resource. The distinction between titles and alternative titles is application-specific.</description>
            <elementTextContainer>
              <elementText elementTextId="7732">
                <text>Nicole Tineo Gonzalez_2017_2.jpg</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7733">
                <text>2017</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7734">
                <text>Saratoga Springs, NY, USA</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7735">
                <text>Antes de juzgar,  observa y conoce detenidamente, ponte en su lugar para poder entender  quién es y lo que pasa por su mente.&#13;&#13;Before judging, observe and recognize carefully, put yourself in a place to be able to understand who someone is and what goes on in their mind.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="67">
            <name>License</name>
            <description>A legal document giving official permission to do something with the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="7736">
                <text>This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.</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="7737">
                <text>Digital Photograph, JPEG</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="244">
        <name>art</name>
      </tag>
      <tag tagId="270">
        <name>bilingual</name>
      </tag>
      <tag tagId="728">
        <name>Estamos Aqui</name>
      </tag>
      <tag tagId="263">
        <name>immigration</name>
      </tag>
      <tag tagId="256">
        <name>Latinx</name>
      </tag>
      <tag tagId="269">
        <name>Spanish</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1137" public="1" featured="0">
    <fileContainer>
      <file fileId="2013" order="1">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/67b144764f24db7586044aa8b45764c1.jpg</src>
        <authentication>5be0716b75515114b57b0de61eb85f2c</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="10140">
                    <text>Pat Loftman, May 23, 2016 (portrait)</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
      <file fileId="2012" order="2">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/609bad4d65366e068f899d5ea6f29d29.jpg</src>
        <authentication>0bcfaa024da4b0494445d1bd1dc83f2f</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="10138">
                    <text>Pat Loftman ACNM Fellows Induction, May 23, 2016</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="40">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="10139">
                    <text>2016</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
      <file fileId="1899" order="3">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/70a0804eeab16d011581caf4de53894f.m4a</src>
        <authentication>472c6612c54edacaf47be1d20baf8261</authentication>
      </file>
      <file fileId="2578">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/08311c540eff8c367af01343d9e61d69.pdf</src>
        <authentication>ec5cdbc55f7312dd3d6a66f604143118</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="258">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12217">
                    <text>Interview with Patricia Loftman '71 by Skidmore Student [Unknown],
COMPASSIONATE HANDS: Skidmore’s Nursing Program, 2019.
SKIDMORE STUDENT [00:00]: Could you start by saying your name and your class year?
PATRICIA LOFTMAN [00:02]: My name is Patricia Loftman. I graduated in 1971.
SS [00:10]: Okay. And, where were you from before you decided to attend Skidmore’s Nursing
program.
PL [00:15]: Where did I attend high school?
SS [00:17]: Where were you born? Where did you grow up?
PL [00:19]: Oh, where was I born. Oh, my family immigrated to the US from Jamaica in the
Caribbean. When I was about eight years old, actually my, my parents were here in the
state, I was raised by my grandparents in Jamaica.
SS [00:36]: And where did you move to, when you moved to the states?
PL [00:40]: Oh, we moved to Washington, D.C. where my dad was attending dental school at
Howard University.
SS [00:48]: Okay. did your family, so your dad was a dentist, did other family members have a
background in medicine and nursing?
PL [00:55]: No, he's actually the only one who has, any, any background in the healthcare field,
everybody else is in other industries.
SS [01:06]: And so, what was your educational background before you joined the program? Like
did you, did you work before? Did you, go to school?
PL [01:17]: Eventually we migrated to New York where I went to school, completed middle
school and high school in the Bronx. In New York City.
SS [01:30]: And did you always know you wanted to be a nurse? What drew you to the program?
PL [01:36]: Well, when I entered Skidmore in 1966, my plan was to go into medicine. I entered
as a pre-med major, completed my first year. My first year went fairly well, by the end.
By the beginning of my sophomore year there was just something about the socialization
into medicine that was just not appealing. And I began to look at other avenues and it
seemed that nursing, would be more cognizant with who I was as an Individual and in
terms of my interactions with human beings. So, I transferred my premed credits into
nursing.
SS [02:25]: And what about Skidmore, why did you choose here over other programs?

�PL [02:30]: Actually, I didn't choose Skidmore. There were, the 60s was a very interesting time
politically. It was very, very difficult for African Americans to get a decent quality
education, especially in colleges and universities. And at that time, it was in the middle of
the height of the civil rights era and there was a move to integrate a lot of the colleges
and universities as a way for students of color, specifically African Americans to gain
access to higher education. And at the time, a lot of the Ivy League schools were
beginning to open up their doors and Skidmore was one of them. And so, my guidance
counselor in high school actually chose it for me. My family didn't know anything about
it. I didn't know anything about Skidmore, didn't know where Skidmore was, didn't know
anything about it, but he thought it would be good for me. So, he chose it and I was
accepted and I went.
SS [03:28]: Wow, that’s got to be kind of intimidating, to go somewhere that you don’t know
about at all and pretty far from home.
PL [03:35]: It was. It was very intimidating.
SS [03:39]: So, what was it like being in the program? What was it like being part of that new
generation of women and people of color who were allowed to be in these programs?
What was that like?
PL [03:52]: It was, it actually was very, very traumatic and very painful. At the time, in 1966,
Skidmore was an all-women's college. It was a small liberal arts college. One of those
seven sister schools that you, you may or may not have heard about that existed at that
time. It would have included Skidmore, Bryn Mawr, Smith, those kinds of schools. And
Skidmore was somewhat smaller. If my memory serves me correct, there were less than
2000 women on campus and of those 2000 only, there were only seven students of color
and they were actually all African Americans. My incoming freshman class had the
largest number, four of us came in. There was one sophomore, her name was Linda
Taliaferro. She has since passed away. There was one junior and one senior. So, it was
very, very isolating actually.
SS [04:53]: Did you find it was difficult to socialize and be a member - did you not feel much
like a member of the community?
PL [05:00]: No, we really were not. We were not welcomed. As a matter of fact, the four of us
really stuck together for our own emotional health and sanity. At that time, because they
were unisex schools, the surrounding male schools such as Williams and Wesleyan, they
were all male at the time. So, by noon on Fridays, the campus was deserted because
everyone had transportation alternatives that we didn't have. This was our first exposure
to money and to wealth and to privilege, and to power. And we were not prepared for that
at all. So, by noon on Friday, there was this huge campus and we were the only ones on it
because everybody was gone. So, it was not, it was not a good time. It was not a good
time for us.

�SS [05:57]: I’m so sorry that that was your experience. Yeah, I mean I can't fathom because I
have not been in that position, but I believe that that must've been so awful and painful
and I'm just thankful that you are willing to talk to me about it. So, thank you so much.
So, um, in terms of academics, what was the course load like? What were the classes that
you are taking for the nursing program?
PL [06:26]: So, the curriculum for the nursing program was your standard curriculum that you
would find in any nursing program then and today. I have to say in retrospect, because
I've always wondered what my preparation was like academically compared to others. I
can say that Skidmore prepared me extremely well. I mean, I still remember my faculty. I
remember Doris Diller. I remember Jean, what was Jean's last name? I don't remember
her name, but I remember my faculty, they were absolutely wonderful. We had a rigorous
course of study and I think that it, I think academically it most definitely prepared me
quite well.
SS [07:14]: Um, do you have any memories about Agnes Gelinas?
PL [07:15]: She, I think she was before me. I know the name, but I never had her.
SS [07:20]: Okay. Yeah, I can't remember when she retired. It might've been ’61 or ’62. So that
was right before you.
PL [07:29]: Yeah, I came with Jean Campbell, Doris Diller. I'm trying to remember some of the
other people, but, Jean Campbell and Doris still, I remember vividly.
SS [07:39]: Do you have any favorite classes or favorite memories with them?
PL [07:45]: I don't know if you know, Doris Diller I remembered I had her for pediatrics and I
had her for a peds and something else, I don't remember, but Doris Diller, her
background had been in the military and she ran us like we were in the military and she
was rigid and she was strict. I mean, she was by the book, but boy do I, do I respect her
now and appreciate her, because I, you know, at the time you don't realize what you're
being prepared for and it's only after you've had that experience and reflected back that
you recognize that you, that she prepared you very, very well.
SS [08:34]: That's great. Do you remember, can you tell me a little bit about going to New York
City for that portion of the program?
PL [08:41]: The program. I loved it. I loved getting back to the city. Oh my God. That was one
of the perks and benefits that put me in nursing, I knew that I would get back to the city
for two years and it was just wonderful. We lived in a dorm, we lived in two dorms. The
first one was on 20th Street, East 20th Street between 2nd and 3rd Avenues. And it was an
older building that was, the norm at the time. But it was, it was just really nice being back
in New York and just not being isolated and the having the flexibility to just move
around. Plus, I was from the city, so I was able to get back and see my friends and my
family. It was just really nice being back in New York. And then after about, maybe

�about a year, a new dorm was constructed on 38th Street. So, we moved from Fahnestock
on 20th Street to 38th Street. The newer building was more aligned with the newer
construction that was going on at the time. Fahnestock was one of your older buildings. It
was very homely. And so, it had a nice quality to it. The newer dorm was just like a
regular building. But it didn't have the architecture that the old dorm had and it just didn't
have the home feel that the old dorm had. But you know, it was just a dorm and we made
it work.
SS [10:15]: Are there any memories you - that come back to you from your time in New York?
PL [10:21]: Nothing that really stands out because here again, there was one other student of
color, her name was Gloria Hairston, and she too has made her transition and passed on.
So, it was just Gloria and myself in the dorm and even in New York, I'm talking about
now as a student, we really were not, hang on one second... Even in the dorm we would
essentially go to class and then just disappear because even back here in New York, we
were not part of the Skidmore nursing program back here in New York. So, it was really
nice to be back in New York. All I had to do was go to school, go to class, you know, do
my work. But I didn't have to worry about being isolated anymore.
SS [11:18]: So, I’m excited to talk to you about your career after you left, Skidmore. What path
did you take?
PL [11:23]: So, once I graduated, I worked as a nurse in the emergency room and the intensive
care unit at one of the public hospitals here in New York called Lincoln Hospital. And I
don't know if you've seen the movie, The Godfather?
SS [11:40]: I haven't.
PL [11:41]: Okay. So, in that movie, The Godfather, there is a scene where, Marlon Brando gets
shot and he's taken to a hospital. Well, the hospital that was used in The Godfather movie
was where I worked, and I was there when they were shooting that particular scene. And
it was so interesting because that was, Lincoln Hospital, it was named after President
Abraham Lincoln. It was previously a home for formerly enslaved African Americans.
And after slavery was ended, it was converted into a hospital and named Lincoln
Hospital. As a matter of fact, I worked at Lincoln before I actually took my nursing
boards. In those days, and I think it still exists, after you finish your first formal year of
nursing [education], you could take the licensed practical nursing boards and work as a
practical nurse. I certainly was not privileged and I didn't have, my family didn't have
money, so I actually had to do that. After I completed my first year of nursing, I took my
licensed practical nursing exam, passed, and worked as a licensed practical nurse during
the summer so that I could get money to go back to school in the fall. And then, once I
completed my full nursing studies, then of course I took my registered nursing boards,
and passed those. So, I had already begun to work at Lincoln as a practical nurse. So, of
course, once I passed my registered nursing boards, I just continued.
SS [13:25]: And what path did you take, I know you’re a Nurse Midwife now. So how did you

�get there?
PL [13:28]: Now that is really interesting how that transition occurred. I worked at Lincoln for
many years. Then I became a mom and it was difficult for me to do the night schedule
and the weekend schedule, I wanted something that was more Monday through Friday,
nine to five. So, I transitioned and worked for a foster care agency as the nurse who
coordinated the medical care for children who were in foster care. And I did that for a
while. And while I was doing that, I learned about midwifery. I had always, always loved
OB. I mean always when I was in nursing school, OB and peds were my two favorites.
And those were the ones that I really excelled in. I learned about midwifery and I said,
‘oh, I had not known about midwifery.’ I knew about midway from when I was growing
up in Jamaica because in the Caribbean, midwives are utilized a lot. But I didn't know
that there were midwives in the U.S. and when I learned that there were midwives in the
U.S., I said, ‘that's what I'm going to do.’ So, I applied to Columbia University. They had
a program in the graduate school of nursing and I applied and was accepted. I went to
midwifery school for two years, from 1980 to 1982. During that time, going to midwifery
school was very, very challenging because, back in the 80s, the only way you could do
midwifery education was full time. That has subsequently changed. You can do
midwifery school now part time. But in those days, back in the 70s and 80s, you had to
go full time and it was two full years, four academic quarters, four academic semesters. I
always tell people, had I known, had I had a crystal ball and knew how rigorous that
program was, I don't know that I would have ever started. But once I was in it, I was in it
and I vowed to see it through to completion. And I'm glad I did. But it was probably one
of the most grueling courses of studies I have ever undertaken.
SS [15:46]: And then so, what was your career like after becoming, getting your licensure for
midwifery?
PL [15:52]: It was, it was wonderful. It was absolutely wonderful. I went to work at Harlem
Hospital, which is also one of the public hospitals here in New York. I have always
vowed to work in the public system. That's where most people of color are, most
underserved populations are. And historically these populations have believed that
because they are poor that they have to accept second class health care, second class
medical care. And I went, I, so I've always worked in public systems because I always
wanted to dispel this myth that because you receive your healthcare in a public
institution, that you're getting second class medical care because that for me was not the
case. And so, I went to Harlem. Harlem was my, was my only, employer. I stayed there
for 30 years. I went in as a brand-new midwife and left as a retiree and it was just
absolutely wonderful. During those 30 years the women taught me how to be a good
midwife. I had the opportunity to see health care, to see many things come and go. I was
there when HIV started. I was there when HIV became an issue for women. At Harlem
Hospital we took care of the first pregnant women with HIV in New York. I was there
and eventually ended up developing an expertise in taking care of those women, HIV
infected women, and women whose pregnancies were complicated by drug use. I really
developed an expertise. In the 80s and 90s, that's pretty much what I did. And then, once
crack and HIV somewhat subsided, I branched out into the total range of women's

�reproductive health care and that's what I did until I retired. It was really a wonderful,
wonderful career. So now I am more involved with the administrative part. I'm on the
board of the American College of Nurse Midwives, which is the professional
organization for midwives. I'm also now the chair of one of the committees in our
organization which is called the Midwives of Color. Our goals and objectives are to
promote the recruitment, the retention and the graduation of underrepresented racial and
ethnic groups - primarily African American, Latinos, Asians, indigenous Native
American students, and Alaskan Native students. So that's what I'm doing now.
SS [18:55]: Do you see a big change in the field, since you’ve moved to the more administrative
side of things?
PL [18:58]: Well, midwifery has changed considerably from when I was educated. First, the
amount of information that students learn today is almost quadruple, but I had to learn in
1980. Healthcare has changed, technology has changed. Health care, the amount of
information the students now have to learn is completely different. I learned about HIV
and chemical dependency and drug use as a professional, whereas students are now
learning about it now. The, clinical expertise of midwives has expanded. When I was a
student, we were primarily relegated to prenatal care, labor and delivery and we did some
reproductive women's health care. Now we are doing just a lot of procedures. Midwifery
practice has expanded into midwives doing sonograms, midwives, do a lot of the
technical skills that you would see a lot of physicians doing. We do terminations those of
us who, acquire the education and the skills. So, midwifery in terms of the practice has
just changed dramatically from when I was a student and even a beginning practitioner.
SS [20:27]: Um, how do you think your Skidmore education helped you with your career?
PL [20:29]: Well, in terms of my preparation, it was certainly very valuable. I mean, I, when I
walked into Lincoln Hospital as a nurse, I was prepared. I knew exactly what to do, and
actually, I actually excelled. But I also think it was very helpful when I went to
Columbia, when I went to graduate school. That was also very helpful. So, I mean, as
traumatic as my undergraduate days were at Skidmore in terms of my ability to
successfully navigate graduate education, it helped.
SS [21:05]: And remember we spoke a little bit about this, but you didn't seem to have too much
of an opinion about the closing of the program?
PL [21:11]: You know, I don't know anything about the closing of the program. When I finished
Skidmore, I just wanted to run away. I didn't want to have anything to do with Skidmore.
I just wanted to get out. And when I got out, that's exactly what I did. I didn't look back,
period. I didn't go back to Skidmore. I didn't go back to campus for many years. I think I
first went back for a reunion maybe about 10 years ago. I had not been back to Saratoga
and I hadn't done anything with Skidmore for many years. It was just that traumatic. So, I
didn't know when the school closed. I learned about the school closing maybe five or six
years after the school closed. I didn't know anything about it. I didn't read about it. I
really just wanted to drop off the face of the earth as far as Skidmore was concerned.

�SS [22:01]: What was it like being back?
PL [22:05]: Well, the biggest thing of course is the campus. I was raised on the old campus,
whereas everything is now on the new campus. They were just building the new campus
when I left. So, the new campus is completely new for me. My days were spent on the
old campus and I have to tell you, I loved the old campus. The old campus was beautiful.
I don't know if you've had any contact with the old campus, but we loved the old campus.
We loved those buildings. Oh my God, they're just so gracious. For me the new campus
is just brick and stone and it's cold.
SS [22:42]: Yes, I do have those feelings, especially in the dead of winter.
PL [22:49]: Yeah, the old campus was not like that. I mean the old campus was just really, really
warm and I missed, I’m not even talking about just the building, just the whole feel of the
campus, it's completely different. That campus had a sense of community where that I'd
never, I mean by the time I graduated, maybe, I think McClellan was finished, Kimball
was finished. I think there were maybe only two buildings and none of us ever wanted to
go to the new campus. So, we were glad we didn't have to.
SS [23:37]: I guess my last question would be, what does it mean to you to be a nurse?
PL [23:40]: Well, I have a background in nursing but I'm not a nurse. I'm a midwife. And those
are two completely distinct and separate professions. They do completely different
things. And that's something that we find ourselves having to explain all the time. It's
hard to explain. Nursing, is a distinct profession. Midwifery is a distinct profession.
Midwives are directly responsible for patient care. In other words, we have to assess and
make decisions. Not that nurses don't, but it's a different kind of decision. So, while my
background is in nursing, my profession is that of a midwife.
SS [24:39]: What does that mean to you? What is your purpose as a midwife?
PL [24:40]: My purpose is to number one, acquire the information, the knowledge and the skills
that I need to render the best medical care that I can for women. And I think that I was
very successful in that. One of the hallmarks of midwifery, we talk about this a lot, is that
midwives listen to women but we do a lot more than just listen. We literally do a lot, in
addition to just what you would expect us to do in terms of having the knowledge, having
the information and having the technical skills, we do a lot of teaching and a lot of
education. And that is just so important and it's not valued. Teaching, counseling,
educating patients... It's not valued in medicine, but that's really what, what individuals
need to keep themselves healthy. I think the bulk of Americans, if they understood that
their own health is literally in their hands, if they only had the information. And so, I
spent a lot of time teaching, you never left my office without a handout about something,
never. And we would talk about it on the next visit. You never left me without having
something in your hands to read that was pertinent to you. And the women valued that
because no one had ever taken the time to talk to them. And that's what they loved, is

�talking. Because it says that you were engaged in their healthcare and, one of the
problems is that people, both providers and, and women, tend to think of health care in
one direction - from the provider to the patient. But it's, it's bidirectional. Patient to
provide, provider to patient. But we have socialized Americans to believe that it's
unidirectional. Provider to patient. And so, they have, they have accepted that dynamic,
that relationship. And so, to have someone like midwives who say, ‘no, no, this is a by
directional relationship here. This is a relationship.’ And that's another thing when I
provide health care, it's a relationship. It's building a relationship. By the time, for
example, by the time I retired, I was attending the birth of children I had brought into this
world. I was now attending their children's births. That was amazing for me, to know that
I had attended the birth of someone and 18 or 20 years later here I was, that this
individual is now a young adult and they have entrusted me with attending the birth of
their child.
SS [27:47]: That’s incredible.
PL [27:48]: It was. The first time it happened, it was an absolutely weird feeling. I remember the
grandmother, this woman came. I walked into the room, they didn't know that they had
me in common. And so, the grandmother, who was my patient, pointed to me, I mean,
she was literally in my face pointing as she was trying to get, the words out. She kept
saying, “it's you, it's you, it's you, it's you”. And I didn't know what she was talking
about. And then by the time she calmed down, she explained that I had been her midwife
and had attended her birth. This was her child whose birth I was now attending.
SS: Wow that is so great, thank you for sharing that with me.
PL [28:33]: Yeah, no. You know, I look back, even though it's been almost 10 years since I've
retired because, I live close by in the neighborhood, I see the women all over the city.
There's no place I can go in New York as big as New York is. I cannot tell you how many
times I am literally walking the streets and someone says to me, ‘Hi Ms. Loftman, you
don't remember me, you were my midwife, you did this, you did that.’ I mean, I'm in
Costco, I'm on the bus. It's just amazing.
SS [29:09]: Wow. That's great. That actually used to happen to my grandfather a lot. He was a
neurosurgeon.
PL [29:15]: I didn't hear you.
SS [29:16]: I said that used to happen to my grandpa whenever we were out, he was a
neurosurgeon and people would always come up and say the same thing to him.
PL [29:26]: Yeah. that's when you know you've made a mark. That's when you know, if you
close your eyes and make your transition today, you left your mark behind in the world.
SS: [29:40]: I think that's all the questions I have for you if you want to go ahead and stop
recording.

��</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <itemType itemTypeId="4">
      <name>Oral History</name>
      <description>A resource containing historical information obtained in interviews with persons having firsthand knowledge.</description>
      <elementContainer>
        <element elementId="3">
          <name>Interviewee</name>
          <description>The person(s) being interviewed</description>
          <elementTextContainer>
            <elementText elementTextId="10027">
              <text>Patricia Loftman '71</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="11">
          <name>Duration</name>
          <description>Length of time involved (seconds, minutes, hours, days, class periods, etc.)</description>
          <elementTextContainer>
            <elementText elementTextId="12225">
              <text>29:46</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="12226">
              <text>Patricia Loftman, Jesse O'Connell</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="10026">
                <text>Patricia Loftman '71</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12218">
                <text>2019</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="73">
            <name>Is Part Of</name>
            <description>A related resource in which the described resource is physically or logically included.</description>
            <elementTextContainer>
              <elementText elementTextId="12219">
                <text>COMPASSIONATE HANDS: Skidmore’s Nursing Program</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12220">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12221">
                <text>Jesse O'Connell</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="12222">
                <text>Audio Interview</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12223">
                <text>Oral History</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="64">
            <name>Date Modified</name>
            <description>Date on which the resource was changed.</description>
            <elementTextContainer>
              <elementText elementTextId="12224">
                <text>April 5, 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="813">
        <name>Nursing</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1050" public="1" featured="0">
    <fileContainer>
      <file fileId="1775">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/cbed7dd3a8a0d383c1265337c169e22c.jpg</src>
        <authentication>88e29a870b94609bb8c3f5e161561654</authentication>
      </file>
    </fileContainer>
    <collection collectionId="32">
      <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="5012">
                  <text>Saratoga Springs History</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5015">
                  <text>1706-</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>
      <elementContainer>
        <element elementId="118">
          <name>Repository</name>
          <description>Name of the repository that holds the original item.</description>
          <elementTextContainer>
            <elementText elementTextId="9173">
              <text>Saratoga Room, Saratoga Springs Public Library</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="9176">
              <text>Jillian Seigel</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="9177">
              <text>43270</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="9167">
                <text>Pay to park sparks outcry in Saratoga</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9168">
                <text>ND</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9169">
                <text>Yusko, Dennis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="9170">
                <text>Times Union</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="93">
            <name>Provenance</name>
            <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="9171">
                <text>Saratoga Springs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9172">
                <text>Transportation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9174">
                <text>Instituting paid parking during a severe recession in this successful but seasonal downtown wil leither remake or destroy it, depending on who you ask. Some fear businesses will be harmed.</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="9175">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="784">
        <name>EnvironmentalJustice</name>
      </tag>
      <tag tagId="782">
        <name>SaratogaSprings</name>
      </tag>
      <tag tagId="26">
        <name>transportation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="305" public="1" featured="0">
    <fileContainer>
      <file fileId="808">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/bce5c9303ddcf12bb1b466681925a1c3.jpg</src>
        <authentication>4a764c2a8b653bd94b59fd267bb1b282</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="3985">
                    <text>Peg Boyers and Dog</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="39">
                <name>Creator</name>
                <description>An entity primarily responsible for making the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="3986">
                    <text>Emma Dodge Hanson</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
      <file fileId="809">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/d00f61792e3a7b0e5e7400b457407656.m4a</src>
        <authentication>8315cd4521b13d60393b20c6286072fc</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="3989">
                    <text>Peg Boyers From Venezuela to Cuba</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="40">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="3990">
                    <text>03/25/2016</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
      <file fileId="810">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/06883a235e04dc1e7ec11275a48c6b6d.m4a</src>
        <authentication>39dbfacf2202682ed408265cbdae173a</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="3991">
                    <text>Peg Boyers Identity</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="40">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="3992">
                    <text>03/25/2016</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
      <file fileId="811">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/85bc110106171961494309e7c292e05f.m4a</src>
        <authentication>0aff49cfa30df59697cfcea62e616a75</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="50">
                <name>Title</name>
                <description>A name given to the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="3993">
                    <text>Peg Boyers Migrant Community/Immigration</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="40">
                <name>Date</name>
                <description>A point or period of time associated with an event in the lifecycle of the resource</description>
                <elementTextContainer>
                  <elementText elementTextId="3994">
                    <text>03/25/2016</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="27">
      <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="4003">
                  <text>Latinx</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="4">
      <name>Oral History</name>
      <description>A resource containing historical information obtained in interviews with persons having firsthand knowledge.</description>
      <elementContainer>
        <element elementId="2">
          <name>Interviewer</name>
          <description>The person(s) performing the interview</description>
          <elementTextContainer>
            <elementText elementTextId="3906">
              <text>Sarah Coker</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="3">
          <name>Interviewee</name>
          <description>The person(s) being interviewed</description>
          <elementTextContainer>
            <elementText elementTextId="3907">
              <text>Peg Boyers</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="4">
          <name>Location</name>
          <description>The location of the interview</description>
          <elementTextContainer>
            <elementText elementTextId="3971">
              <text>Saratoga Springs, NY</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="3972">
              <text>Sarah Coker</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="3978">
              <text>04/26/2016</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="3905">
                <text>Peg Boyers Interview</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3963">
                <text>03/25/2016</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3988">
                <text>Sarah Coker</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4004">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4006">
                <text>&lt;div&gt;Peg Boyers is a Skidmore alumni and faculty lecturer in the English Department, as well as executive editor of Salmagundi Magazine. She spoke with Skidmore Student Sarah Coker at her home in Saratoga Springs on March 25&lt;span&gt;&lt;sup&gt;th&lt;/sup&gt;&lt;/span&gt;&amp;nbsp;2016 about Cuban identity, Cubans in the United States, and her travel experiences as a child.&lt;/div&gt;&#13;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="282">
        <name>Cuba</name>
      </tag>
      <tag tagId="283">
        <name>Cuban</name>
      </tag>
      <tag tagId="289">
        <name>culture</name>
      </tag>
      <tag tagId="259">
        <name>family</name>
      </tag>
      <tag tagId="275">
        <name>identity</name>
      </tag>
      <tag tagId="263">
        <name>immigration</name>
      </tag>
      <tag tagId="285">
        <name>Latin America</name>
      </tag>
      <tag tagId="223">
        <name>Latina</name>
      </tag>
      <tag tagId="266">
        <name>Latino</name>
      </tag>
      <tag tagId="256">
        <name>Latinx</name>
      </tag>
      <tag tagId="278">
        <name>migration</name>
      </tag>
      <tag tagId="197">
        <name>oral history</name>
      </tag>
      <tag tagId="200">
        <name>Skidmore College</name>
      </tag>
      <tag tagId="213">
        <name>Skidmore faculty</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="665" public="1" featured="0">
    <fileContainer>
      <file fileId="1439">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/fa66e39cd7c7a2aeca7f3caf726918d0.pdf</src>
        <authentication>f4f7bfd9646935bcada18cc143395ee2</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="258">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="6434">
                    <text>Pensions are Not Enough: The Individual Company and Its Older Workers
Author(s): Edwin Shields Hewitt
Source: The Journal of Business of the University of Chicago, Vol. 24, No. 2 (Apr., 1951), pp.
127-140
Published by: University of Chicago Press
Stable URL: http://www.jstor.org/stable/2349911
Accessed: 01-11-2015 14:05 UTC

Your use of the JSTOR archive indicates your acceptance of the Terms &amp; Conditions of Use, available at http://www.jstor.org/page/
info/about/policies/terms.jsp
JSTOR is a not-for-profit service that helps scholars, researchers, and students discover, use, and build upon a wide range of content
in a trusted digital archive. We use information technology and tools to increase productivity and facilitate new forms of scholarship.
For more information about JSTOR, please contact support@jstor.org.

University of Chicago Press is collaborating with JSTOR to digitize, preserve and extend access to The Journal of Business of
the University of Chicago.

http://www.jstor.org

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�PENSIONS ARE NOT ENOUGH: THE INDIVIDUAL
COMPANY AND ITS OLDER WORKERS
EDWIN SHIELDS HEWITT AND ASSOCIATES"

SOME employers have provided of society of a policy of retirementat age
who
a pension plan for their employees
consider that they have met the
problemof their older workers.Actually,
in the light of present knowledge of the
individual needs of older workersand of
the implications of an aging population
fromthe viewpointof both the individual
company and the economy as a whole,
private pension systems should be considered as merely one approach to the
problemof older workersin industry.
CHANGING POLICIES ABOUT RETIREMENT
I930-50

Ourthinkingabout the problemof the
aged has undergoneconsiderablechange
within the last two decades. Because of
the changing age distribution of the
population and the growing percentage
of the population over sixty-five, considerable thought has been directed to
the problem of the older worker.During
the decade of the thirties wide-scaleunemploymentled to agitation for compulsory retirement of workersat age sixtyfive as a device for making room for
younger workers. The enactment of a
national system of compulsory old age
insurance and a supplementaryfederalstate program of old age assistance for
the needy aged gave promiseof a partial
solution of the problem of financial insecurity for those over sixty-five.
The desirability from the viewpoint

sixty-five or even earlierand the advantages to the individual worker of a
period of well-earned rest and leisure
were generallyaccepted. It was assumed
that the availability of old age benefits
would give each worker an opportunity
to choose between continuingto work or
retiring from the labor force. It was expected that, given such a choice, most
workerswould prefer to retire.2Such an
expectation was, of course, based upon
the assumption that old age benefits
would be sufficient for the support of
aged workers.
The war years, with changedeconomic
conditions, brought modificationsin attitudes and practiceswith respect to the
employment of older workers and the
policy of compulsory retirement. Manpowershortagesopenedthe door to older
workers. Industry, which had for some
time discriminated
against olderworkers,
now hired older persons and urged retired workersto return to the job. Many
older persons who had stopped work
gladly applied for new jobs or returned
to their old jobs.
During the war years, because of the
restrictionson wage increases,becauseof
tax incentives, and because profitable

business made it easier for those selling
pension plans to convince employers of
their desirability, many employers established pension plans.
In the postwar period many of the
by
This reportwas prepared the staff of Edwin
older persons who were employed were
Shields Hewitt and Associates of Chicago, indeI

2 William H. Stead, "Trendsof Employment
pendentanalystsand actuaries,underthe direction
in
recently Relation to the Problemsof the Aging," Journal
of Sydney B. Scoville, directorof research,
Universityof Chicago.
assistantprofessor,
of Gerontology,IV (October, I949), 294.
I27

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�I28

THE JOURNAL OF BUSINESS

reluctant to retire, and the high level of
economic activity made it possible for
many of them to remain productively
active. Even with an economy operating
at peak levels, however, many older
workers
wereunableto find employment.
This situation, along with the rise in
prices and the consequent minimization
of the real benefits provided by the old
age insuranceprogram,led to increased
pressurefor enacting amendmentswhich
would provide more substantial old age
insurancebenefits and, in the absence of
such amendments,to increasedpressure
for private pension plans to supplement
social insurance. The acceptance by
certajn strong labor unions of pension
benefitsas a presumablynoninflationary
economic gain and the decision of the
National Labor Relations Board requiring employers to bargain collectively on
pensions and benefit plans accelerated
the trend toward the establishment of
retirementplans.
In the meantime the medical profession had turnedits attention to the growing problem of chronicillness and physical and mental impairment among the
aged. Psychiatrists, interested in the
mental health of the aged, saw clearly
the severe emotional stress induced by
premature retirement and the possible
disastrouseffects upon the individual of
compulsoryretirement. Social workers,
in daily contact- with aged persons in
financial need or with emotional difficulties, were concerned about the need
for individualizedtreatment of the aged.
Psychologistsstressed the need for using
the conceptsof physiologicaland psychologicalage ratherthan chronological
age,
as a basis for hiring, retaining, and
retiringworkers.
Threemajorquestionswere repeatedly
raised: (i) the effects of compulsoryretirement upon aged persons who were

psychologically unprepared for retirement; (2) the growing economic burden
of the support of the aged whether
throughsocial insurance,private pension
plans, or other means; (3) the effect upon
society and the economy of the lost productivity of many workers forced or
encouraged to retire at sixty-five or
before.
A growing body of knowledge based
upon medical research concerning the
physicaland mental problemsof the aged
has changed long-standing concepts
about the desirability of retirement for
all those who reach a designatedchronological age. Growing concern about the
economic as well as the personal effects
of compulsoryretirementhas led to considerableexaminationof the problemand
to attempts to enact legislation to prevent discriminationagainst the aged in
employment.
One of the most active groups interested in the problem, the New York
State Joint Legislative Committee on
Problemsof the Aging, in its I949 report
noted five basic shortcomingsin current
employment practices concerning the
aged:3
Wide-scale
prejudice
againsthiring workers
overforty-five
of
2. Compulsory
retirement workersat sixtyfive withoutregardto their ability to work,
need to work,or desireto work
facilities in govern3. Lack of job-counseling
mentorindustry
4. Inadequacyof existing industrialpension
plans which sometimesthwart the employmentof the elderly,fail to providesufficient
sumsto coverthe cost of living, and provide
little protection the oldperson
for
whowishes
to changeemployment
beforeretirement
age
workin
5. Lackof job analysisor classification
into
industryto fit elderlyworkers jobs they
can do profitably
i.

3New York State Joint Legislative Committee
on Problemsof the Aging, NeverToo Old (Legislative Doc. No. 32 [I949]), p. I3.

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�PENSIONS ARE NOT ENOUGH

Some of the reasons given by employers for their failure to hire older
workersdo not stand up under examination, as they have no basis in fact or are
basedupon exaggeratedor unusualsituations. Some of the reasons for failure to
hire older workersfollow.
ratesgo up
i. Workmen's
compensation
are
whenelderlyworkers employed.-This
belief has no basis in fact, since age does
not enter into the determination of
workmen's compensation rates. In the
main, rates are determined by the relative hazardsof the industry and the accident experience of the individual company. The formula for determining the
premiumrate does not considerthe type
of personnelinvolved, nor does the insurance contract say anything about the
age of the workersemployed.
2. Older workersare subject to higher
otherworkers.
accidentratesand endanger
-As a matter of fact, accidentfrequency
rates tend to declinewith advancingage.
Although older workers are involved in
fewer accidents, the duration of the period of disability tends to increase with
age. Thus the accidents sufferedby older
workers,while less frequent,are likely to
be more severe, and the healing process
is slower. According to Dr. Nathan W.
Shock: "The diminished accident rate
for older workersmore than counterbalances this longer healing period so that,
in general, it may be concluded that
older men have proved less expensive
from the standpointof accidentcost than
younger men."4One survey in this area,
made by the U.S. Bureau of Labor Statistics during the war, showed that disabling injuries (those involving a permanent impairment or disability for work
for at least one -full shift) occurred
4 Nathan W. Shock, "Older People and Their
Potentialities for Gainful Employment," Journal
II
of Gerontology, (April, I947), 99-IOO.

I29

slightly less frequently among workers
over fifty than among those under fifty,
while handicappinginjuries (those which
usually requireonly first aid) were much
less common at age fifty and over than
in the younger age groups. Once injured,
however, older workers generally took
longer to heal.5
3. Elderly workers cannot produce so
much as younger workers and are not so

profitable.-Nathan W. Shock, in discussing the alleged reducedproductivity of
older workers,states:
Since there are few occupations in which a
substantial number of workers are employed on
work of equal difficulty, the speed of which is
governed by the worker himself and for which
individual production records are available, it is
almost impossible to determine the role of age in
industrial output. However, on the basis of our
physiologic knowledge, it seems probable that
work output may diminish in older workers.
Hence it is important than an educational program be instituted which will make it possible
to place the older worker in positions where
speed is of lesser importance.6

Ewan Clague, the United States commissioner of labor statistics, lists reducedmuscularstrength, slowerreflexes,
decreasedkeenness of sight and hearing,
and various chronic disabilities as the
most obvioussourceof difficultyfaced by
older workers because of physiological
aging. He adds, however, that the extent of physical impairmentis exaggerated in popular thinking:
Many of the physical changes associated with
age not only tend to occur more slowly than
we once supposed, but also interfere less than
5 Max D. Kossoris, "Absenteeism and Injury
Experience of Older Workers," Monthly Labor Review, LXVII (July, 1948), I7-I8; gee also Ewan
Clague, "Some Industrial Aspects of Aging"
(address before the tenth annual Congress on Industrial Health, sponsored by the Council on Industrial Health of the American Medical Association,
New York, February 2I, I950), p. 8.
6

Shock, op. cit., pp. 99-I00.

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�I30

THE JOURNAL OF BUSINESS

we would expect with performance on the job.
There is evidence, for example, that experience
on a given job often tends to maintain the particular kind of vision that the job demands
after other visual functions become impaired.
Moreover, . . . many an oldster has keener
hearing and better vision than an average man
twenty or more years his junior.7

Claguebelievesthat the often mentioned
psychologicalaccompanimentsof aging,
such as reduction in learningspeed, lessened adaptability to new ways of doing
things, and the tendency to become unco-operative in ordinary working relationships, are also often overestimated.8
there is a generalfailureto
Furthermore,
that many older workersexunderstand
cel in jobs requiringlong training, experience, knowledge, and skill and have
positive qualities of dependability,judgment, and loyalty. Accordingto Thomas
C. Desmond, the chairman of the New
York committee, the older worker has
four basic advantages over the younger
which
employee.He has moreexperience,
motions; he is less ineliminateswasted
clined toward outside distractions;he is
more conscientious because of his long
service and mature attitudes; he appreciates his workmore and tries harderbecause he has more at stake than the
neweryounger employee.9In many jobs
at the professionaland manageriallevel,
maturity is an asset. This is also true in
many of the skilled crafts and in certain
types of service jobs where reliability is
especially important.'0Thus in factory
production,where speed is often an importantfactor, the older workermay not
be able to hold his own on an assembly
I

Clague, op. cit., p. 7.

8Ibid.

9 Thomas C. Desmond, "Industry Needs the
Older Workers," in New York State Joint Legislative Committee on Problems of the Aging, op. cit.,
p. 96.
IO Clague, op. cit., p. 8.

line. On the other hand, among professional people, the older worker may be
very successfulbecause of his experience
and maturity. Ewan Clague points out
that it is between these two extremes, in
the vast numbers of intermediate situations, that prejudiceand misinformation
appear as serious complications in the
older worker's employment problems."
4. It is unprofitableto invest in the
training of older workersbecauseof the
short work-life-expectancy.With increasing life-expectancy, many persons
over fifty-five or sixty have a considerable number of years ahead of them in
which they will be well able to continue
as productiveworkers.The man of sixtyfive has an expectancy of over a decade
more of life before him.
5. Thereis an increasedlaborturnover
among older workers.-Actually, the reverse of this is true. The increasein stability of older workersis of considerable
importance to industry, since the training of new employees is often very expensive.

6. Thereis increased
absenteeism
among
older workers.-In the population as a
whole, there is more illness among older
persons than among younger. On the
other hand, in a survey made during the
war by the Bureau of Labor Statistics of
absenteeismrates by age groupsin manufacturingindustries,there was very little
variation in the absenteeism rates because of illness. However, older workers
tend to be absent from work for a longer
period of time because of illness than do
younger workers. There is less absenteeism attributable to causes other than
illness among older workers.The survey
showedthat the absenteeismrates for all
reasons (illness and others) were lowest
in the fifty-five to fifty-nine age group
II

Ibid.

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�PENSIONS ARE NOT ENOUGH

and that, while workers over sixty-five
had a slightly higher rate than those of
fifty-fiveto fifty-nine, they lost much less
working time than did workers in their
teens and twenties and somewhat less
than those in their thirties and forties.12
7. The public prefers youngerworkers
in jobs requiringpublic contacts,such as
waitresses, clerks, office workers, salesmen.-This is a commonbelief, but there
is no conclusiveevidence to prove or disprove it.
8. Pension systems make it difficultto
hire older workers.-It is alleged that
undermany of the pension plans paying
flat monthly sums at retirement, employers who hire older workers face a
heavier future pension liability. It is also
argued that companies hesitate to hire
workers for short spans of time, for example, from fifty-five to sixty-five, since
this would be insufficient time to accumulate money in the pensionfund to pay
suchworkersreasonableretirementbenefits.
As a matter of fact, most pensionplans
do not operate against the hiringof older
workers. First, many pension plans do
not pay flat monthly benefits, but vary
the benefits with years of service. Thus
older workers hired for short spans of
time would rece'ivesmall benefits. Second, some pension plans exclude shortservice workers, that is, they require a
mininum numberof years of service for
eligibility for benefits. Third, some plans
contain a maximumage provisionso that
workershired when older than the maximum age are ineligible for inclusion in
the plan. Fourth, in some plans with no
specific exclusion of older or of shortservice workers, the company will have
no pension liability for such workers,
since the benefit formula provides for a
t2

op.
Kossoris, Cit., p.

I7;

see also Clague, op. cit.

I31

companypension less social security and
the company pension for short-service
workersis so small that it is completely
or largely offset by the social security
benefit. Thus there are several ways to
adjust a pensionplan formulaso that the
hiring of older workersdoes not place an
undue burden upon employers.
ADEQUATE RETIREMENT BENEFITS

What does all this mean as far as the
individual company and its interest in
its older workers is concerned? In the,
first place, if older workers are to be
treated as individuals, they should be
allowed to exercise some choice between
retiring and remainingproductive members of society. Furthermore,if management is to manage, it must have the
right to determine what constitutes an
effective working force. Both selections,
to be free choices, depend upon the existence of adequateretirementbenefitsso
that retirement does not constitute a
drastic cut in standards of living. It is
contemplatedthat old age benefitsunder
the Social Security Act will provide a
minimum of subsistence for all retired
workers. To the extent that social security benefits do not provide adequate
income, adequacy will be achieved only
if supplementary benefits are provided
throughprivate plans.
FLEXIBLE RETIREM1ENT AGE

In the second place, the pension plan
adopted should preferably not require
retirementfor all workersat a fixed, arbitrary age, such as sixty-five, since there
in
differences the rate
are wide indivridual
and degreeof aging. Selectionof the time
for retirement should be determined as
nearlyas possibleby inability to continue
as a productive worker. This is impossible to establish in advance for indi-

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�I32

THE JOURNALOF BUSINESS

viduals, but the span of time during
which such a condition is most likely to
occurfor a groupis predictable.
One of several alternatives for introducingflexibilityin retirementplans may
be chosen. For example, a pension plan
may provide for a normalretirementage
with optional earlierretirementpossible.
The normalretirementage may be set at
sixty-five, sixty-eight, or seventy. Factors influencingthe choice of an age later
than sixty-five are the larger benefits
whichmay be providedat later ages; the
fact that a later normalretirementage is
more acceptable, since, with increased
longevity,workersare reluctantto retire;
and the fact that a retirementage can be
lowered more easily than it can be
raised. A provision permitting optional
earlierretirement at any time after age
sixty furnishes some latitude for recognizing individual differences.Benefits at
an earlier age can be provided without
increasingthe liability of the plan, but in
such cases benefitsmay be reducedto 50
per cent or less of what would have been
paid at normal retirement.
A second possibility is to permit employees to retire over a span of years
(such as from sixty to seventy) with
benefitsbased on years of service at the
time of retirement. Such a span recognizes individual differencesand is more
practicaland useful than is a fixed retirement age. An employee continuingat his
regularjob beyond the youngest age at
which he is eligible to retire would increasethe ultimate pension benefitshe is
to receive.The plan may provide that no
largerbenefitsare earnedbeyond a limiting age, such as seventy, and that an
employeemay continue his employment
beyondthat age only with the employer's
consent.Such a provisionassists the company in maintaininga certain amount of
control over the maximum retirement

age. Since the span of years selected will
in part determinethe ages at which most
retirementsoccur, the employer'sability
to meet the liability produced as well as
individualdifferences
must be considered
in establishingsuch an age range.
A third possibility is to provide for a
span of years over which employees can
retire but provide for full benefits in
event of retirement in the early part of
the span, such as ages sixty to sixty-five,
only with the company's consent and
permit no increased benefits for years
workedbeyond sixty-five. In the absence
of a compulsory retirement provision
and in considerationof the currenttrend
to keep workersproductive,many workers actually retire later than age sixtyfive. Therefore, the funds released because of retirement after sixty-five can
in many cases be used to provide the increased cost of the earlier retirements.
Even though the total of all provisions
for a worker's retirement, including his
own accumulationsfor pension benefits
and his benefitsfrom social security,may
be adequate to make a workerself-sufficient during his period of retirement, it
is important in the effective operation
of a flexible retirement system that the
level of pensions remain such that continuation on the pay roll continues to be
more attractive than retirement at a
reduced level of company and social security benefit.
From the standpoint of the funding of
a pension system, it is, of course, uneconomical to fund for an earlier retirement age than will be called for by actual retirements. While it is possible to
establish in advance an expected rate of
retirement under such a system providing for a variableretirementage, funding
in future years will be governed by revision of this rate according to the experience of the system.

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�PENSIONS ARE NOT ENOUGH
SELECTIVE PLACEMENT OF
OLDER WORKERS

A company which realizesthat a fixed
retirement age does not conform to the
realities of individual differencesamong
its older workers will provide for some
flexibility in its retirementpolicy and in
the retirementage of its pensionplan. In
addition, such a company will be interested in other aspects of dealing with its
olderworkers,such as the selectiveplacement of older workers, the selection of
workersfor retirement,and the preparation of workersfor retirement.
In a survey conducted by the National Chamber of Commerce and the
National Association of Manufacturers
among large and small companies of
many types, it was found that a considerableproportionof the companieshired
and retainedolderworkersand that most
of these companiesreportedfavorablyon
the job performance of older workers.
However, proper selection of older
workersand carefuljob-placementmethods were emphasizedas highly important
if companies are to enjoy the greatest
success with the employment of older
workers.13

I33

who are not so productive as formerly
can continue at the same job only at reduced pay. For some of this group, adjustments may be made, such as a less
rigid schedule of attendance or hours or
a change in responsibility or type of
work. A third group of workerscan better be transferred to a new job more
suitable to their capacities, for which
they may need some training.Such a job
may be at the same or at reduced pay.
Dr. Nathan Shock comments that the
success in developingpersonnelselection
at the intake side of industryleads one to
regard with optimism the prospect of
developing similar techniques for selection in retirement.'5
The proper placement of the older
workerrequiresan evaluationof his experience, skills, and physical capacities in
relation to the demands of the job. The
first step in the adequate utilization of
the potentialities of older workers for
gainful employment should be careful
and complete job analysis. Jobs should
be analyzed as to the skills required to
performthem and with respect to factors
such as speed, energy requirements,fatigue effects, judgment, and experience.'6
Aging produces certain changes, such as
sensory impairment and reduced speed
of reaction.Thus olderworkersshouldbe
placed in jobs in which these factors are
of minimal importance. According to
WilliamH. Stead, industry shoulde-valuate its jobs in an effort to fit its aging
workersinto positions that would be advantageous both to industry and to the

Dr. Edward Stieglitz states that basing retirement upon chronologic age
alone results in a double source of waste
by discarding workers who are physiologically younger than their years and
by making obligatory the retention of
many workers who have become senile
prematurely.'4Some workers at sixtyfive can continue at their regularjob at
the same pay and be as productiveor in- workers.'7
creasingly productive. Other workers
I5 Dr. Nathan
U.S. Chamber of Commerce, Department of
Manufacture, Employment of Physically Handicapped and Older Workers (Washington, I949), pp.
5, 20.
'4 Edward J. Stieglitz, The Second Forty Years
(New York: J. B. Lippincott Co., I946), p. 287.
'3

W. Shock, "Physiological Capacities of Elderly Workers," in New York State Joint
Legislative Committee on Problems of the Aging,
Op. cit., p. I33.
I6 Shock, "Older People and Their Potentialities
for Gainful Employment," p. ioo.
I7 Op.

Cit.,

p.

296.

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�I34

THE JOURNAL OF BUSINESS

When a man reaches a certain period where
Clifford Kuh suggests that there be
analysisby the job analyst of the physi- he is not able to produce what he formerly procal and environmentaldemands of par- duced or what the employer wishes him to produce, we allow him to stay in that plant at a
ticularjobs.,8 For example, jobs may be lower salary, where he may keep at work doing
classified as involving mechanical fac- things which the employer would ordinarily
tors, such as lifting, carrying, handling, allot to, say, a semi-skilled worker. We have
pushing, climbing, seeing, hearing, etc., a semi-skilled branch in our union for those
and environmentalfactors, such as in- who have neither the experience nor the qualifications of a journeyman and their rate of pay
side, outside, high temperature, low is about half the rate of pay of a qualified
temperature, vibration, noise, working journeyman printer. If the man wishes to realone, working with others, day shift, tain a job and can't quite do the work he
used to, we allow him to stay there at that seminight shift, etc.
the skills and capacities of skilled rate.20
Next,
workers necessary to perform the parWhile seniority is the governing conticularjobs shouldbe determined.Some- sideration in choosing employees to be
times a simple matter of re-engineering laid off in most collective bargaining
is possible to suit the job to an aged per- agreements,many of these contractsproson. For example, Kuh suggests that, if vide for exemptions from layoff on the
a machine operation requires too much basis of seniority. One of the likely expulling, the plant engineercan rearrange emptions is that of efficiencyconsideraor alter the length of the levers to reduce tions. In some contractsseniorityis given
the effort required, or if a job requires equal consideration with other factors,
too much stooping, the work area may such as ability or skill, experience or
be moved nearer to the level of the physical fitness. In a third group of
worker'sshoulder.19 job re-engineering agreements, contract provisions state
If
is impossible,the older workershould be that seniority provisions shall be contransferredto work he can do, with the sidered where other factors are equal.
necessary training for the new job pro- Such other factors include differencesin
vided.
ability and physical fitness.2'
The objections of some unions to the
Shock suggests that individualtests to
of
downgrading workersmay present an assess the physiological age of various
obstacle to such a practice. Many collec- organ systems must be devised, as well
tive bargaining agreements, however, as individual tests for performance
affordspecial transferrights for aged or capacity:
handicappedpersons. For example, the
Because of wide individual differencesin
agreement may state that "employees physiologicaging among personsof the same
who have given long and faithful service chronologicage, it is essential that tests of
and can no longerhandle their duties are physiologicage be developedfor variousorgan
to be given preference or consideration systems. It will also be necessary to devise
for such lighter work as is available."
Charles W.
Views Its
CharlesW. Campbell,of the New York Elderly Workers,"Campbell, "LaborJoint Legisin New York State
TypographicalUnion No. 6, states:
lative Committee Problemsof the Aging,op. cit.,
on
20

p. ioo.
18 CliffordKuh,

"Selective Placement of Older

Workers," Journal of Gerontology,I Uuly,
3I4.

'9Ibid., p. 3I6.

I946),

2!
Bureauof NationalAffairs,"Seniority,
Layoff,
Promotion, and Transfer," Collective
Bargaining
Negotiationsand Contracts,No. I24 (March io,

I950), pp. 43-52.

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�PENSIONS ARE NOT ENOUGH
more adequate methods of health examinations
which will permit the early recognition of chronic disease. Methods of assessing performance
capacities in individuals need to be developed
as well. It is in this area that research is most
urgently needed.22

As changes in the worker's abilities
and interests make it necessary, the
hours, arduousness,and difficultyof the
job can be reduced. As Lawton points
out, workersshould be placed on a modified schedule when the necessity is
proved by tests and by objective standards of working ability, not by a particular birthday or at the employer's
whim.23

In order to determine which workers
should be retained at the same job and
same pay, which need job modification,
and which should retire under a flexible
retirementplan, severalpossibilitiesmay
be considered. In some companies the
personnel bureau is used not only to
hire and fire workers but to shift them
from one type of activity to another.
One suggestionmeriting considerationis
the establishment within a company of
an impartial panel to evaluate older
workersperiodicallyfrom the standpoint
of health, productivity, emotional attitudes, and personal factors. In accordance with the findings of such a panel,
the olderworkercould remainin his present job, be placed in a less arduoustask,
be placed on partial pension with shorter
hours and a correspondingdecrease in
This would constipay, or be retired.24
a more logical approach to retiretute
ment than the class approachof throwing into a mass all those sixty-five years

I35

of age or over; it would be a case-by-case
approach, examining the actual rather
than the presumed capacity of men to
performtheir jobs adequately.25
ProfessorErnest W. Burgess speaks of
an indexof aging, an instrumentdesigned
to ascertain the actual process of aging
in its physiological, psychological, and
social aspects. Physiological aging, he
says, would be concerned with organic
conditions, such as heart trouble; psychological aging with decline in mental
ability; and sociologicalaging with contraction of social activities and interests:
The value of this index of aging is obvious.
When it has been designed and standardized,
retirement could be based on the scientific
determination of the physiological, psychological, and social efficiency of the person
rather than on the number of years he has
lived. Part time work might be assigned also
with consideration of functional rather than of
chronological age.26

To some employers automatic retirement at a fixed age appears to be easier
and kinder than singlingout individuals.
William G. Caples questions the advisability of selective retirement on the
of
recommendation a panel because "one
man is judging another man's fitness to
work and that can be cruel, if human
errorenters in.'27 He argues, in support
of a fixedretirementage, that it gives advance notice of the time of retirement
and allows a workerto plan accordingly;
it prevents favoritism; it avoids grievances; it is an incentive to youngermen;
25Clark Kerr, "Social and Economic ImplicaRetions of Private Pension Plans," Management

view, May, I950,

p. 297.

26 ErnestW. Burgess,"The Growing
Nathan W. Shock, "OlderPeople and Their
Problemof
p.
the
Potentialitiesfor GainfulEmployment," I00.
Aging," in Clark Tibbits (ed.), Living through
23 George
(NewYork: Later Years (Ann Arbor:University of Michigan
Lawton,AgingSuccessfully
22

Columbia University Press, I946), p. 73.

Press, I949), pp.

24HowardRush, "When Are We Too Old To
Work?"TownMeeting(TownHall, June I3, I950),
P. 5.

WilliamG. Caples,"WhenAreWe Too OldTo
TownMeeting(Town Hall, June I3, I950),
Work?"

22-23.

27

p. I3.

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�136

THE JOURNAL OF BUSINESS

it results in general imnprovement the
of
average productivity of the working
force;it avoids the worker'sbeing termed
unfit and the consequentloss of prestige
with family, fellow-workers,
and friends.
It may also be arguedthat individualdeterminationsand adjustments are troublesome and may be costly; that possibilities for transfer of workers to other
jobs arelimited;28 that compulsoryretirement automaticallyopens up new opportunities for younger persons; that it
decreases pay-roll costs and eliminates
the worker who is not producing efficiently in an equitable and standard
manner.29 Moreover, employers may
fear that, under a policy of individual
consideration they might be accused by
unions and individual employees of favoritism and discrimination.30
It should be noted that compulsory
retirement does not always decrease
costs; it may add to them by eliminating
efficientproducers and substituting untrainedworkersfor trained. Compulsory
retirementmay also create considerable
ill-will among retiredworkers,especially
those who are retiredwhen they are well
able to produce as efficientlyas before.3'
GeorgeLawton points out that industry spends large sums on technological
research and should devote an equal
amount to the study of changeswith age
in patterns of vocational interest and
abilities, problemsof human relations in
industrial situations, types of occupa-

tions most suitable for older people, and
methods of rehabilitation.32
There is great need for researchand experimentation on a company-by-company basis to develop methods for the
selection of employees for job transfer
and retirement. Objective, measurable
factors which could be used to determine
which workers should retire, which
should be transferred,and which should
remainin their formerjobs wouldgreatly
simplify the problem. A critical clinical
medical examination, including blood
pressure, blood counts, chest X-rays,
urineanalysis,visual and otologicaltests,
would help to measure the individual's
physiological age. This could be combined with a measure of factors such as
attendance, promptness, accidents, errors, spoilage, reworks,complaints, output, and individual morale, weighted in
terms of their relationshipto costs.
PREPARATION FOR RETIREMENT

Even though retirement is discretionary rather than arbitraryat any definite
chronologicalage, for those workerswho
retire some preparationis desirable.Dr.
Anthony Lanza points out that it is inconsistent to follow an elaborate ritual
for conditioning a man for his employment and to give no thought to preparThere is a
ing him for his retirement.33
growingbody of opinion that no healthy
man should retireuntil he is fit both economically and emotionally to retire.
28 Charles A. Pearce, "Present Employment Emotional acceptanceof retirementmay
Statusof OlderWorkers," New YorkState Joint require considerablepreparation.A proin
LegislativeCommitteeon Problemsof the Aging, gram for retirementorientation, counselop. cit., p. 4I.
ing, and preparation tailored to the
29
New York State Joint Legislative Committee
on Problems of the Aging, op. cit., p. i6.

32Lawton, op. cit., p. 98.

33 Anthony J. Lanza, "The Industrial Physician's
Role in Geriatrics," in New York State Joint
3INew York State Joint Legislative Committee Legislative Committee on Problems of the Aging,
on Problems of the Aging, op. cit., p. I6.
op. cit., p. I42.
30

Pearce,Op.Cit., p.

4I.

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�PENSIONS ARE NOT ENOUGH

needs of the individual should be set up
in all companies.
In some companies organized lecture
courses and study groups have been instituted for discussingadjustmentsin old
age. Such educational meetings, combined with an informalsocial hour, may
lead workers to think as a group about
the period of retirement and thus increase their emotional acceptance of it.
In other companiesemployees are interviewed some years before the normal
retirement date to indicate the date of
retirement, the probable amount of the
pension, the pension options available,
and to discuss possible future plans.
Service may be offered in helping the
employee find part-time employment if
such employmentis essential. The counseling of workers about available positions outside the plant may be of great
service to them. Furthermore, many
workers, for whom retirement means
retrenchment in living expenses, are in
need of help with budgetary,investment,
and other financial and economic problems. The success of the preparation of
the worker for retirement through periodic interviews will depend to a large
extent upon the skill of the interviewer
in stimulating the workerto think about
the problems of retirement.
Besides these planned interviews,
which are usually the responsibility of
the Industrial Relations Department,
other opportunitiesmay be offeredfor a
discussion of retirement problems. For
example, the visits made to the medical
department provide opportunities for
counseling by the doctors about retirement problems. In any pre-retirenient
counseling, emphasis is usually placed
upon stimulating the workerto think of
retirementas a change in activity rather
than as the end of activity.

I37

Hobby showsput on by companiesfor
all their workershave sometimes been a
stimulusto olderworkersto develophobbies which will be of great interest to
them in their retired years. Articles on
retirement in the house organ, a dinner
for the employee at the time of retirement, service clubs for employees with
long service records, a diminishingwork
load with increasingtime off as the retirement age approaches, and vocational
training for a differentkind of work are
all used by companiesin their programs
designed to prepare workers for retirement.
An increasing number of books dealing with the subject of retirement has
been publishedwithin the last few years.
Most of these offer suggestionsas to the
proper use of time during retirement,
with emphasisupon planningretirement,
including the enjoyment of leisure, hobbies, travel, and new vocational and
avocational interests. Many retired
workerswill be happiest if they can perform some kind of useful and remunerative activity. For example,an interesting
suggestion for the use of the services of
retiredofficialsof bankingand industrial
concerns is as counselors to small businesses with young and inexperienced
owners. Retired officialscould be on call
several times a month on a fee basis.
Such counselorsmight be very useful to
small businessesin procuringbank loans
as well as consulting on financial and
This wouldpremanagementproblems.34
vent the economic waste of retiring a
trained and competent business executive at sixty-five to completeleisure and
would provide great satisfaction to the
retired official himself. Some sort of
34 Suggestionmade by Philip S. Shoemaker,
of
Cleveland, cited in Burroughs, Clearing House,
July, I950, pp. 6-7.

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�I38

THE JOURNALOF BUSINESS

communityclearinghouse to bringabout substantialreductionor at no cost. Some
contacts between the small business and companieshave an annual free picnic or
the retiredofficialwould be necessary.
dinner for annuitants. Some maintain a
service annuitants clubroomin the plant
FOLLOW-UP AFTER RETIREMENT
for the use of retiredemployees.The proA company which has carefully se- vision of medical service through the
lected its workersfor retirement,tried to company medical department and comprepare them for retirement, and pro- pany visiting nurseis still anotherservice
vided a pension benefit during retire- sometimesprovrided retiredworkers.35
for
ment can perform a still further funcSUMMARY
tion. Contact should be maintainedwith
In conclusion, an employer who has
retiredworkers,who may be encouraged
to comein to discuss their problemswith provideda pensionfor his employeesmay
counselors,and a representative of the believe that he has adequately disposed
industrial relations department may of the problem of the older worker. Acmakeperiodicvisits. In case of economic tually, he has taken only one step in the
hardship,aid may be offered to retired solution of this problem. Employers
workersin helpingthem locate part-time should make the age of retirement flexjobs or in granting them financialassist- ible and eliminate the barriers within
ance. Any company employee notices pensionplans which may operateagainst
and company publications may be sent hiring and retaining older workers.Jobs
to retiredworkers.Articles on the activi- should be analyzed on an industry basis
ties of pensionersmay be includedin the to determine the skills, physical ability,
house organ. Letters from company ex- training, and related factors required.
ecutives at periodic intervals, informing Objective tests should be devised to dethem of developmentsof interest in the termine the individual worker'sphysioplant, may be sent with the pension logical and psychologicalage, as well as
check. Also Christmasletters and letters his productivity. Plans should be estabof congratulationsor sympathy help to lished for transferof olderworkersto less
keep alive the association between the demanding jobs, to allow for part-time
retiredworkerand the company.Retired employment, and to retrain workersfor
workersmay be invited to company get- jobs better suited to their capacities. A
togethers which would be of interest to programof pre-retirementcounselingto
them, both social affairs and special help workers prepare for retirement
meetings of employees for policy an- should be established. There should be
follow-up of those workers who have
nouncements.
Accordingto the interesting survey of retired. Much of this can be effectively
companypre-retirement
practicesand of accomplishedby industry on a plant-bypracticesin relation to retiredemployees plant basis. The co-operationof governprepared by Socony-VacuumOil Com- ment, of unions, and of the public is
pany, some companies have granted needed, however, if the problems of the
honorarylife-membershipsin employee older workerare to be solved.
35Socony-Vacuum Oil Company, Employee
or company clubs and have continued
Service Section, Industrial Relations Department,
memberships in company musical or Survey of Pre-retirement
Practices (New York,
dramaticgroups or other activities at a October,I949), p. 8.
This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�PENSIONS ARE NOT ENOUGH

Within the area of government activity, for example, the development of
special facilities within the public employment service to care for the vocational needs of older workers would be
very helpful. Arnold S. Askin, in discussing the work of the Federation Employment Service, a free nonsectarian
guidance and placement agency devoting its primaryattention to personswho
are hard to place, suggests that special
facilities within the public employment
agency might take the form of a special
office for older workers or special staff
consultants within each public employment office.36
The Sub-committee on Low Income
Families of the Joint Committee on the
Economic Report recently recommended:
The Joint Committee on the Economic
Report request the appropriateGovernment
agenciesto study the incidenceand extent of
existing restrictions employment of older
and
workersin Government industry,and report to the Committeeon their findingswith
may be
regardto ways in whichthese barriers
to
removedand older workersencouraged remainin productiveemployment.37

I39

partment of Laborin this field,.In an address deliveredon December 3, I949, he
commentedas follows:
The problem calls for a fundamental reexamination of industry practices regarding the
hiring and utilization of older workers. Labor
unions and the older workers themselves must
be willing to cooperate, as many of them have,
in the adoption of a more flexible approach
towards the shifting of older employees to jobs
for which they are more suited. And we, in
the Department of Labor, can cooperate too
by making available the facts on how these
older workers are actually utilized, their productivity, and the types of work they can best
perform. We have had a long-standing interest
in the employment problem of older workers,
and are committed to assembling as much pertinent data as we can, within the limits of our
resources.38

On another occasion he said:
We, of the Department of Labor, are especially conscious of the need for much more research into the many facets of these problems.
There is a great dearth of current and comprehensive data on a number of key points.
We need to know more about the actual practices of employers in hiring and separating older
workers, and in reassigning superannuated
employees. We require more information on the
actual work performance of older people. How
does the quantity and quality of their work
compare with that of younger people? This
kind of information for various industries and
occupations could indicate the kinds of work
for which older persons are best adapted, and
least adapted.39

One of the "appropriategovernment
agencies" is the Department of Labor,
which has recognized its responsibility
for research in this area. Ewan Clague,
commissionerof labor statistics, in nuIn the area of union activity, there are
merous addresses and articles on probaged worker, has spoken of many labor-management agreements
lems of the
the need for further researchby the De- which protect the aging worker on the
job. Seniority rules offer protection to
36 Arnold S. Askin, "Can We Expand Employworkersin some industries.In the buildment of the Elderly? If So, How?" in New York
State Joint Legislative Committee on Problems of ing trades the union contract may rethe Aging, op. cit., p. II 4.
37U.S. Congress, Senate, Joint Committee on the
Economic Report, Sub-committee on Low Income
Families, Low Income Families and EconomicStability (Senate Doc. No. I46 [8ist Cong., 2d sess.1)
(Washington: Government Printing Office, I950),
p. I3.

38 Ewan Clague, "The Background of the Pension
Problem" (address before the Machinery and Allied
Products Institute, Washington, December 3,
p. 7.
I949),

39 Clague, "Some Industrial Aspects of Aging,"
p. I0.

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�I40

THE JOURNAL OF BUSINESS

quire the employment of an older man
foreachfive, seven, or ten journeymenon
the job. However, as Clague points out,
the senioritysystem, which increasesjob
securitywhen a workeris employed,may
work to his disadvantage when he is
unemployedand looking for a job. The
desireof employersto care for their own
aging workers may freeze out the older
personwho no longer has an employer.40
The co-operationof older workers, of
private and public agencies, and of specialists in the field is needed to institute
40Ibid., p. 9.

the necessary research in this area and
to develop a comprehensiveprogram to
meet the needs of older workers. Public
education as to the strengths and potentialities of older workersis essential.
Certainly, the problem is nation-wide
in scope, and its solution goes beyond the
efforts of any individual company or
union and requires the co-ordinated efforts of all groups in the community. It
may well be, however,that the individual
company has the basic role to play in
contributingto the solution of this pressing and highly significantproblem.

This content downloaded from 141.222.2.81 on Sun, 01 Nov 2015 14:05:44 UTC
All use subject to JSTOR Terms and Conditions

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="28">
      <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="4248">
                  <text>Adult and Senior Center of Saratoga</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>
      <elementContainer>
        <element elementId="1">
          <name>Text</name>
          <description>Any textual data included in the document</description>
          <elementTextContainer>
            <elementText elementTextId="6435">
              <text>Edwin Shields Hewitt, "Pensions are Not Enough: The Individual Company and Its Older Workers," The Journal of Business of the University of Chicago, Vol. 24, No. 2 (Apr., 1951), pp.&#13;
127-140. &#13;
University of Chicago Press&#13;
Stable URL: http://www.jstor.org/stable/2349911&#13;
&#13;
</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="7">
          <name>Original Format</name>
          <description>The type of object, such as painting, sculpture, paper, photo, and additional data</description>
          <elementTextContainer>
            <elementText elementTextId="6436">
              <text>journal article</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="6432">
                <text>Pensions are not enough</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="6433">
                <text>1952</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1275" public="1" featured="0">
    <fileContainer>
      <file fileId="2337">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/07466f49e8c0ef0582b10c124b0871c6.jpg</src>
        <authentication>fbb5847b73da2d7ea1bf5eb80e9fbc3c</authentication>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include 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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10934">
                <text>Photo of Downtown Stillwater</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10935">
                <text>1910</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="73">
            <name>Is Part Of</name>
            <description>A related resource in which the described resource is physically or logically included.</description>
            <elementTextContainer>
              <elementText elementTextId="10936">
                <text>Brookside Collectio</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="10937">
                <text>Brookside</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="916">
        <name>buggy</name>
      </tag>
      <tag tagId="880">
        <name>everyday life</name>
      </tag>
      <tag tagId="837">
        <name>Photography</name>
      </tag>
      <tag tagId="913">
        <name>stillwater</name>
      </tag>
      <tag tagId="915">
        <name>store</name>
      </tag>
      <tag tagId="49">
        <name>tourism</name>
      </tag>
      <tag tagId="914">
        <name>town</name>
      </tag>
      <tag tagId="892">
        <name>trolly</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1268" public="1" featured="0">
    <fileContainer>
      <file fileId="2309">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/23ff197116864e9b36e5620b9b0b4787.jpg</src>
        <authentication>4122cca0567db09e7abc93b3f767d545</authentication>
      </file>
    </fileContainer>
    <collection collectionId="42">
      <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="10665">
                  <text>Saratoga County</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="11068">
              <text>Mattie Saulnier</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="11069">
              <text>5/5/21</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="28">
          <name>URL</name>
          <description/>
          <elementTextContainer>
            <elementText elementTextId="11070">
              <text>https://www.adirondackalmanack.com/2017/03/the-origin-of-interstate-87-the-adirondack-northway.html</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="10886">
                <text>Photo of the Northway</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10888">
                <text>Picture taken of the Northway.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="11071">
                <text>Anthony Hall</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="52">
        <name>highways</name>
      </tag>
      <tag tagId="896">
        <name>the Northway</name>
      </tag>
      <tag tagId="26">
        <name>transportation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1281" public="1" featured="0">
    <fileContainer>
      <file fileId="2343">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/5278b5c2df5a2aae3e15881b5013b7ba.jpg</src>
        <authentication>8853b7cbe30f6b151328d60fa959b3d4</authentication>
      </file>
    </fileContainer>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include 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="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10962">
                <text>Photo of the Saratoga Native American Festival in 2019</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10963">
                <text>2019</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="10964">
                <text>Saratoga Native American Festival website&#13;
http://saratoganativefestival.com/schedule-2/</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="56">
            <name>Abstract</name>
            <description>A summary of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="10966">
                <text>A photo of the Saratoga Native American Festival in 2019</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10983">
                <text>Will Kertzman</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="181" public="1" featured="0">
    <fileContainer>
      <file fileId="409">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/17d89c100ed03cd05be96147036d2ba2.tif</src>
        <authentication>f77a9ed2d93dff2e938e2e05b4a0e9db</authentication>
      </file>
      <file fileId="410">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/44808193584667b620c5497cf958802c.tif</src>
        <authentication>688d28c57007dcfad48bd8ccbbc1db48</authentication>
      </file>
    </fileContainer>
    <collection collectionId="32">
      <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="5012">
                  <text>Saratoga Springs History</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5015">
                  <text>1706-</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="7">
          <name>Original Format</name>
          <description>The type of object, such as painting, sculpture, paper, photo, and additional data</description>
          <elementTextContainer>
            <elementText elementTextId="2597">
              <text>Engraving</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="2598">
              <text>Allie Smith </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="101">
          <name>Date Depicted (Display)</name>
          <description>Text version of the date field -- can handle non-numeric characters (ca. 1850s, [1844]). This is the content date field that will display.</description>
          <elementTextContainer>
            <elementText elementTextId="2599">
              <text>1834</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="109">
          <name>Theme</name>
          <description>For browsing purposes, we are borrowing and adapting themes from the Library of Congress's American Memory project.</description>
          <elementTextContainer>
            <elementText elementTextId="2600">
              <text>Travel and Tourism</text>
            </elementText>
            <elementText elementTextId="2601">
              <text>Recreation</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="118">
          <name>Repository</name>
          <description>Name of the repository that holds the original item.</description>
          <elementTextContainer>
            <elementText elementTextId="2602">
              <text>Private Collection</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="121">
          <name>Abstract (&amp; Historical Note)</name>
          <description>Natural language description of the map itself, providing a general summary of the map and noting significant features. &#13;
&#13;
This is the place to introduce keywords and proper names that might be of interest to researchers, but do not warrant a separate subject heading of their own. Inset maps should also be described here, with their full titles given.&#13;
&#13;
Whenever historical or explanatory information is available, it should be included here as well. This includes information about items or events that are larger than just the map itself; for example, information about cartographers, a description of the map's historical significance (for example, "This is the first printed map of Saratoga Springs"), notes on the laws leading to a map's creation, descriptions of changes in state or county lines, information about the organization that created the map, how often maps were updated, and information about the map's creation and publication. Many State Archives maps have historical information in the catalog record -- that should be captured in this field.</description>
          <elementTextContainer>
            <elementText elementTextId="2605">
              <text>The 1830's were the first time the railroad came into Saratoga. This image depicts leisurely people in Victorian era dress on the Piazza of Congress Hall in Saratoga. </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="7284">
              <text>2/27/2015</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="2596">
                <text>Piazza of Congress Hall, Saratoga Springs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2603">
                <text>Drawn by C. Burton</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2604">
                <text>Enraved by T. Illman</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="61">
        <name>19th century</name>
      </tag>
      <tag tagId="523">
        <name>hotel</name>
      </tag>
      <tag tagId="544">
        <name>illustration</name>
      </tag>
      <tag tagId="236">
        <name>Leisure</name>
      </tag>
      <tag tagId="529">
        <name>mineral springs</name>
      </tag>
      <tag tagId="543">
        <name>print</name>
      </tag>
      <tag tagId="77">
        <name>Saratoga Springs</name>
      </tag>
      <tag tagId="49">
        <name>tourism</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="110" public="1" featured="0">
    <fileContainer>
      <file fileId="250">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/6309828929a86f4565b4a5c7225a59ed.jpg</src>
        <authentication>79946ee694216ec8abdc1d113a806509</authentication>
      </file>
      <file fileId="356">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/e2eedee340ad6603bc92c3c25fe0e15c.png</src>
        <authentication>a0953796dfb776ab7d8c9cf06021dfd8</authentication>
      </file>
      <file fileId="357">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/4e00d7c6012bb31249b122b0077e1c13.png</src>
        <authentication>9c9058889d387646a3a4f7b184384d86</authentication>
      </file>
    </fileContainer>
    <collection collectionId="34">
      <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="5030">
                  <text>Mapping Saratoga Springs</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5031">
                  <text>1700-</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="18">
      <name>Map</name>
      <description>Cartographic document</description>
      <elementContainer>
        <element elementId="101">
          <name>Date Depicted (Display)</name>
          <description>Text version of the date field -- can handle non-numeric characters (ca. 1850s, [1844]). This is the content date field that will display.</description>
          <elementTextContainer>
            <elementText elementTextId="1810">
              <text>1880</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="100">
          <name>Date Depicted (Numeric)</name>
          <description>Date that the information on the item depicts. In many cases, this will be the same date as that in the date field, but there will be exceptions. For example, a historical map drawnin 1890 might show Saratoga Springs as it was in 1820. Or, the information on the map itself might include detailed information that enables us to extrapolate a date, for example, "based on a survey done in 1841." Many State Archives map catalog records refer to this as the "situation date."</description>
          <elementTextContainer>
            <elementText elementTextId="1811">
              <text>1880</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="99">
          <name>Date Published (Display)</name>
          <description>Text version of the date field -- can handle non-numeric characters (ca. 1850s, [1844]). This is the date field that will display.</description>
          <elementTextContainer>
            <elementText elementTextId="1812">
              <text>1880</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="98">
          <name>Date Published (Numeric)</name>
          <description>Date the item was printed. This will be set as a date field, accommodating only numbers. The field will be able to handle single dates or date ranges. This will not display, but will be indexed and searchable.</description>
          <elementTextContainer>
            <elementText elementTextId="1813">
              <text>1880</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="121">
          <name>Abstract (&amp; Historical Note)</name>
          <description>Natural language description of the map itself, providing a general summary of the map and noting significant features. &#13;
&#13;
This is the place to introduce keywords and proper names that might be of interest to researchers, but do not warrant a separate subject heading of their own. Inset maps should also be described here, with their full titles given.&#13;
&#13;
Whenever historical or explanatory information is available, it should be included here as well. This includes information about items or events that are larger than just the map itself; for example, information about cartographers, a description of the map's historical significance (for example, "This is the first printed map of Saratoga Springs"), notes on the laws leading to a map's creation, descriptions of changes in state or county lines, information about the organization that created the map, how often maps were updated, and information about the map's creation and publication. Many State Archives maps have historical information in the catalog record -- that should be captured in this field.</description>
          <elementTextContainer>
            <elementText elementTextId="1814">
              <text>The map, which appears opposite the title page of the work, is part of a history of Saratoga Springs and Ballston Spa published in book form in 1880, but (as the dedication notes) originally appearing in the Saratogian, Saratoga Springs' daily newspaper, in 1874-5.  The author, Stone, dedicates his work to the Honorable Charles S. Lester, a judge, and signs himself a "friend and former townsman."  The book includes memories, history, and focuses on a range of topic, from graveyards to historical personages, schools, debating clubs, the histories of the Baptist and Presbyterian churches, and an 1832 cholera epidemic.  &#13;
&#13;
This map is enclosed by Circular Street and Congress street and shows only Congress Park itself. It lists references including Congress Spring, Reservoir, Drinking Fountain, Columbian Spring, Music Pavilion, Cafe, Music Platform, Main Entrance, and Circular St. Entrance</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="118">
          <name>Repository</name>
          <description>Name of the repository that holds the original item.</description>
          <elementTextContainer>
            <elementText elementTextId="1815">
              <text>Private Collection</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="117">
          <name>Scope</name>
          <description>Tiered geographical location (for example: United States, New York State, Saratoga County, Saratoga Springs, Congress Park).  This field is here for two reasons: first, to present, at its narrowest level, the scope of the entire item (in other words, not every place name has to be listed here). Second, this field will allow for accurate and helpful narrowing and broadening of geographic searches.</description>
          <elementTextContainer>
            <elementText elementTextId="1816">
              <text>Property</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="110">
          <name>Type</name>
          <description>For Maps: This subject field describes the purpose of the map. This is a controlled-vocabulary field using terms developed for this project. It is important to note that Map Theme and Map Type are not hierarchical, thus it is possible to have the two fields overlap or even duplicate each other. In determining the purpose of the map, the cataloger should consider the publisher, and, (if known) original use of the map. For example, a map that shows a wide variety of information might be a candidate for General in the map_type field, however, if it was prepared by the state geologist and contains, in addition to everything else, substantial information about the geology and topography of the state, it would be classified as a Geological map. Multiple terms can be used in this field.</description>
          <elementTextContainer>
            <elementText elementTextId="1817">
              <text>Property maps</text>
            </elementText>
            <elementText elementTextId="1818">
              <text>Site plans</text>
            </elementText>
            <elementText elementTextId="1819">
              <text>Outline maps</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="109">
          <name>Theme</name>
          <description>For browsing purposes, we are borrowing and adapting themes from the Library of Congress's American Memory project.</description>
          <elementTextContainer>
            <elementText elementTextId="1820">
              <text>Environment and Conservation</text>
            </elementText>
            <elementText elementTextId="1821">
              <text>Civic Life</text>
            </elementText>
            <elementText elementTextId="1822">
              <text>Property and Development</text>
            </elementText>
            <elementText elementTextId="1823">
              <text>Travel and Tourism</text>
            </elementText>
            <elementText elementTextId="1824">
              <text>Recreation</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="111">
          <name>Subject - Details</name>
          <description>This subject field describes the amount of detail in a map.&#13;
&#13;
For maps:  (or layers) included on the map itself. This field might denote that the map includes information about, for example, Mountains, Railroads, Soundings, Elevation, or Population. These are controlled-vocabulary terms developed locally. The cataloger should be generous in assigning these terms -- even if only one canal is visible on the map, it should receive a "Canals" subject in this layer. &#13;
&#13;
Some of these terms are less specific than others and may warrant expansion in the Abstract field. For example, the "Businesses" term might be included here while the Abstract notes that the map shows mills and stores. Multiple terms can be used in this field.</description>
          <elementTextContainer>
            <elementText elementTextId="1825">
              <text>Congress Park (Saratoga Springs, N.Y.)&#13;
City Reservoir (Saratoga Springs, N.Y.)&#13;
</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="112">
          <name>Subject - Geographic</name>
          <description>Library of Congress subject headings.&#13;
&#13;
For maps: for major geographic locations depicted on the map, followed, in nearly every case, by the "Maps" genre subheading. (For example, "Saratoga Springs (N.Y.) -- Maps.") This field will be especially important when the records from this collection are incorporated into larger databases and catalogs.</description>
          <elementTextContainer>
            <elementText elementTextId="1826">
              <text>Congress Spring (Saratoga Springs, N.Y.)&#13;
Columbian Spring (Saratoga Springs, N.Y.)</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="1827">
              <text>R. (Zach) Mooring &#13;
Jordana Dym </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="108">
          <name>Related Maps</name>
          <description>There will be many cases where multiple maps are in effect only slight variations on a single original. If we are certain, or even pretty sure, that one map is just a slightly altered version of another,the related versions should be listed here.</description>
          <elementTextContainer>
            <elementText elementTextId="2014">
              <text>A similar plan appears in Charles Taintor, &lt;em&gt;Saratoga Illustrated &lt;/em&gt;(&lt;a title="Taintor 1884 Saratoga Illustrated Congress Park" href="https://archive.org/stream/saratogaillustra01tain#page/n114/mode/1up"&gt;1884 &lt;/a&gt;) and (&lt;a title="1900 Taintor Saratoga Illustrated Congress Park" href="https://archive.org/stream/saratogaillustra02tain#page/n166/mode/1up"&gt;1900&lt;/a&gt;).</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="95">
          <name>Creator - Individual</name>
          <description>Name of the person or people responsible for creating the item.</description>
          <elementTextContainer>
            <elementText elementTextId="2440">
              <text>[Stone, William L.]</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="2441">
              <text>7/24/2014&#13;
12/16/2014</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="28">
          <name>URL</name>
          <description/>
          <elementTextContainer>
            <elementText elementTextId="2442">
              <text>Library of Congress copy &lt;a title="Reminiscences of Saratoga" href="https://archive.org/details/reminiscencesofs00ston"&gt;digitized on the Internet Archive.&lt;/a&gt;</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="1809">
                <text>Plan of Congress Spring Park, Saratoga Springs, N.Y.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="73">
            <name>Is Part Of</name>
            <description>A related resource in which the described resource is physically or logically included.</description>
            <elementTextContainer>
              <elementText elementTextId="2439">
                <text>William L. Stone, Reminiscences of Saratoga and Ballston....Illustrated (New York: R. Worthington, 1880).</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="3144">
                <text>R. Worthington</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="3145">
                <text>2 p. l., 451 p. front. (plan) illus., plates 20 cm</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1056" public="1" featured="0">
    <fileContainer>
      <file fileId="1811">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/d565dbcd20281c1de499069f71db446b.JPG</src>
        <authentication>7169ad0586c8e6f07905d91c71cd4dc9</authentication>
      </file>
    </fileContainer>
    <collection collectionId="32">
      <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="5012">
                  <text>Saratoga Springs History</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5015">
                  <text>1706-</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>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="9233">
              <text>Jillian Seigel</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="9234">
              <text>43270</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="9228">
                <text>Planning Board Approves Lake Ave. Development, Water Line to Be Extended</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9229">
                <text>5/17/49</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9230">
                <text>Urban Renewal</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="9232">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="782">
        <name>SaratogaSprings</name>
      </tag>
      <tag tagId="783">
        <name>UrbanRenewal</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="1064" public="1" featured="0">
    <fileContainer>
      <file fileId="1814">
        <src>https://www.ssmp.mdocs.skidmore.edu/files/original/65322976e2ea0bb7c213d35628ea6ea1.JPG</src>
        <authentication>900ecf2d0032defa0f3112a486cfcbf3</authentication>
      </file>
    </fileContainer>
    <collection collectionId="32">
      <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="5012">
                  <text>Saratoga Springs History</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5015">
                  <text>1706-</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>
      <elementContainer>
        <element elementId="119">
          <name>Record Contributor</name>
          <description>Individual who prepared the item and/or edited it.</description>
          <elementTextContainer>
            <elementText elementTextId="9308">
              <text>Jillian Seigel</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="120">
          <name>Record Creation Date</name>
          <description>Day/Month/Year of record creation/edit</description>
          <elementTextContainer>
            <elementText elementTextId="9309">
              <text>43270</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="9301">
                <text>Planning Board opposed to housing proposal</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9302">
                <text>12/12/74</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9303">
                <text>Shapiro, Seth</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="9304">
                <text>The Saratogian</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9305">
                <text>Urban Renewal</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="9307">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="782">
        <name>SaratogaSprings</name>
      </tag>
      <tag tagId="783">
        <name>UrbanRenewal</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
