<?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://usworld29.omeka.fas.harvard.edu/items?output=omeka-xml&amp;page=21&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-03T09:54:30-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>21</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="131" public="1" featured="0">
    <fileContainer>
      <file fileId="173">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/fd62912d15a8e401fa7b075f333066d2.pdf</src>
        <authentication>355d194b3793e31bfc8fc09b9701e6d5</authentication>
      </file>
      <file fileId="174">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/ceebb61f1631596031ab1db2363b7b0a.pdf</src>
        <authentication>2b9fdd1a289d4c860c65bcb36dcc3181</authentication>
      </file>
    </fileContainer>
    <collection collectionId="3">
      <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="3">
                  <text>Sketch 2</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="263">
                <text>Tiffany Lopinsky</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264">
                <text>My sketches of Copley Place and Newbury Street reveal how these shopping spaces differ in terms of the types of activities they foster and their interaction with the surrounding environment. It’s clear that there is much more foot traffic on Newbury Street compared to Copley Place. Perhaps because it was a beautiful Sunday afternoon, Newbury Street was packed and people flowed in and out of the shops, cafes, and restaurants, often leading to congestion on the sidewalk. Additionally, pedestrians interacted with the surrounding space by holding up cars as they crossed Gloucester Street and Fairfield Street and j-walked across Newbury. &#13;
&#13;
Copley Place, while offering a similar selection of shops, feels much different. The modern design, white and marble floors, wide walkways, and lack of public seating, make it feel like a space that you only move through, rather than linger. When I visited, there was little activity, and visitors appeared to only be strolling through; in the space between the Prudential bridge and the waterfall, I hardly observed anybody walking in or out of the boutiques or shops, Starbucks being the exception. Also, compared to Newbury, which feels distinct yet still integrated into the rest of Boston, Copley Place feels oddly removed from the rest of urban space. A sense of seclusion from the rest of the city is created by the elevation, the hidden exits and entrances that are at least a story below most of the mall’s foot traffic, and the contrasting design style from the rest of the Back Bay properties.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="61" public="1" featured="0">
    <fileContainer>
      <file fileId="61">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/30134207e8ac2fe3a7a5efd8c3b1aae6.jpg</src>
        <authentication>bd5b45144963907cddb22994b8f32df4</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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="2">
                  <text>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="123">
                <text>Timothy Shea</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="124">
                <text>In my sketch, I drew Harvard Yard and its surrounding areas with symbols and colors representing student housing, class or study spaces, tourist gathering areas, student gathering areas, and paths that students use to go from place to place. My map is fairly accurate in the roads from the Charles River to the Yard, but I was inaccurate west of JFK St. and north of the Yard. I also decided that my symbols would suffice for dorm and class buildings, which makes my map distinct from others. I have been to the Radcliffe Quad and the Law School campus only a few times, and this lack of familiarity showed in my sketch. These observations suggest that I am aware only of the areas of Harvard Square where I walk, and that there are individuals with independent perspectives that would likely draw a sketch reflecting different communal and physical characteristics of this area. Therefor one must be well researched in order to sketch an image of Harvard Square that gives the viewer an accurate visual and social understanding of the surrounding area.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="145" public="1" featured="0">
    <fileContainer>
      <file fileId="201">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/033041d6d856b46b925125296c41d0b2.jpg</src>
        <authentication>4077fb5770e4df8727acdfb813ef2bee</authentication>
      </file>
      <file fileId="202">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/8f4781b7aaf1dfbd6d3ff65060b84fb2.jpg</src>
        <authentication>1b0b277959752ec2f8fc1d8d8f31006b</authentication>
      </file>
    </fileContainer>
    <collection collectionId="3">
      <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="3">
                  <text>Sketch 2</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="291">
                <text>Timothy Shea</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="292">
                <text>In my sketches of Newbury St and Copley Place and the Prudential Center Malls, I focused on two different themes that I noticed while walking through each. What immediately struck me in Copley Place and the Prudential Center Malls was a feeling of constant movement surrounding me in the somewhat narrow-feeling halls of the mall. If I stopped walking for a moment, the groups surrounding me would continue so that I had to pull myself to the side of the hall to stay out of their way. In the various wings of the Prudential Mall, direction seemed uniform between the hundreds of people surrounding me. It was easy to find myself following the crowd on my side of the hallway for the entire wing without noticing. However, once you reach central areas, where halls converged, there was a confusing mixing of directions. Perhaps I am not used to such crowded malls, which made this characteristic of Copley and the Prudential stick out to me. On Newbury Street, I started my walk near the Hynes Convention Center and Massachusetts Pike and as I continued down the street, the architecture had a very evident pattern. While my walk began with smaller, flat-faced brick buildings, it evolved to the characteristic larger curved-faced brick buildings, until I reached larger-still department stores, hotels, and churches that dominated my surroundings before I reached the Public Gardens. This change in building size made me feel like I was advancing into a larger more advanced city than the initial architecture hinted. Also it is important to note that the buildings on Newbury Street are so unique that my sketch paid less attention to the straight nature of the street, and more to what a shopper finds themself observing to their right and left. I indicated hypothetical individuals in both sketches by money signs, because of dominating theme of high-end shopping in both settings.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="54" public="1" featured="0">
    <fileContainer>
      <file fileId="54">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/bd9f2892bd9e8b2cae0b4abfee5d24ee.JPG</src>
        <authentication>22c95c2d9c91773e5f693460676b4460</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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="2">
                  <text>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="109">
                <text>Todd Preston</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="110">
                <text>My sketch includes a map of the Undergraduate campus at Harvard University, noting major roads and sidewalks that travel throughout the campus. An important note about my sketch is that it does not include all sidewalks, but rather the most congested sidewalks that can be found in Harvard Yard and throughout the Athletic fields. Additionally, the running trail along the river is another sidewalk that is heavily used and I found it was very important to include in my map. Roads are marked with arrows in order to indicate the direction of travel since most roads in the town of Cambridge are one-ways with an occasional two-way street. &#13;
&#13;
Scale plays an important role in my sketch because the building, roads, and sidewalks are not all drawn to scale. It is also important to note that the scale tends to vary between the different “main parts” of campus, including the River Housing, Harvard Yard, the Quad and the Athletic fields. Most of the blank space that surrounds the map is less detailed than the rest because I am very unfamiliar with the territory and felt it was best to leave it blank. As a Senior who is an athlete, I am very familiar with the Athletic fields but as a resident of Dunster, I have never been to the quad and am very unfamiliar with the layout of the Quad’s campus. &#13;
&#13;
On a related note to scale, there is an issue with spacing between buildings and sidewalks/roads. Although some buildings are nearly touching the road/sidewalk, it was important to draw them as separate lines and the spacing allowed me to provide a more detailed rendering of the areas and allowed me to provide insight including the direction of travel.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="139" public="1" featured="0">
    <fileContainer>
      <file fileId="189">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/e07e2cf7451096630564d6573689e28f.JPG</src>
        <authentication>6d923d40150d01225a41c44df6742ec5</authentication>
      </file>
      <file fileId="190">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/1cde70e6b20484d6a5a682249c6e05ce.JPG</src>
        <authentication>696a1bc3f644b375445b8931fd1ee23d</authentication>
      </file>
    </fileContainer>
    <collection collectionId="3">
      <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="3">
                  <text>Sketch 2</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="279">
                <text>Todd Preston</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="280">
                <text>This assignment offers the chance to view two separate, but close, locations. They are both very unique from one another. While most may get lost in the Prudential/Copley shopping district, it would be very difficult to lose your way while traveling Newbury Street. I found Newbury St to be very interesting for many reasons. First, it was very easy to follow. All you had to do was continue straight. Secondly, there seemed to be only restaurants and smaller shops on Newbury St. Nonetheless, it provided a small-town feel to it. If you were traveling the street at night and disregarded all of the commercial signs, you would feel as if you were traveling the streets of a friendly neighborhood. This was an aspect that I aimed to depict in my sketch of Newbury Street. Restaurants with “eat-in” lawns consume the left side of the street while shops line the right side of the street. Additionally, I drew the road as if it were disappearing into the horizon to depict the length of the road. It’s a shopping district that seems to continue with no end. &#13;
&#13;
In contrast, the Prudential/Copley Place shops was very chaotic and confusing to get around. You constantly needed to view signs and maps in order to get where you were going. For this reason, I attempted to draw, to the best of my ability (and memory!), a general pedestrian map in order to help shoppers get around the shops. While it does not provide accurate details of each shop’s location, it provides a general sketch of the shops and the main areas that shoppers would most likely need to get to. In addition, it provides iconic parts of the shops, including the water fountain and the skybridge, to help shoppers maneuver the maze that is Copley Place.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="213" public="1" featured="0">
    <fileContainer>
      <file fileId="306">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/7e8e052ab77aabc77511aeda84e49d59.jpg</src>
        <authentication>0ebed3c5de4825437cc0e1c67d8f791d</authentication>
      </file>
    </fileContainer>
    <collection collectionId="5">
      <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="5">
                  <text>2017 - Sketch 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="423">
                <text>Tomas Spiers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="424">
                <text>Comparing my sketch and an overhead image of Harvard Square on Google Maps, I have several major takeaways. First of all, my general conception of proportion is generally good. The size of Cambridge Common relative to the size of Harvard Yard on my map is pretty accurate. My locations of buildings relative to each other are accurate as well. My main inaccuracies stem from street locations and angles as well as building sizes. I grossly overestimated or underestimated the sizes of some buildings and the orientations of some streets (I also neglected to include a lot of the streets I use daily!). I also neglected the curve of the Charles River in my sketch, which is surprising because I am a rower and on the river frequency. My accuracies and inaccuracies tell me that my conception of space largely comes from my relation to buildings. I start and end my day in Harvard Yard, which is now the focal point of my daily experience, and the accuracy of my map diminishes as I get further and further from my dorm, Stoughton Hall. I think my roads are especially inaccurate because of my strong relation to buildings - I depend on using notable buildings to orient myself rather than using street directions. I found this exercise thought-provoking regarding how I relate to the world around me.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="194" public="1" featured="0">
    <fileContainer>
      <file fileId="284">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/eee4593d7a4bd499e5f6d1d11ebda94f.pdf</src>
        <authentication>1bea1a59a15d116cfe00f470eeaa50aa</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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="2">
                  <text>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="387">
                <text>Tuongvan Le</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="388">
                <text>This drawing was heavily dependent on my personal exposure and time spent in each part of the Harvard&#13;
campus. I realized that drawing the relative positions and paths connecting the buildings were the most&#13;
difficult component. I generally know the direction of the places but sometimes it was hard to remember&#13;
all the buildings on the same streets and where the building is located relative to the entire map in&#13;
progress. I was more confident on the areas where I have had classes (SEAS) and spent lots of time walking&#13;
around (the Yard, the river houses). I also had a hard time drawing the relative sizes of the building&#13;
accurately but rather just drew a generic block to represent each building. This is because I usually just&#13;
walk inside one part of the building but not the entire building so I can’t grasp the entire size of each&#13;
building in my memory. There were also some buildings I remember exist but can’t quite remember the&#13;
names. I remember them because of specific landmarks or activities associated with it such as this is the&#13;
building where there’s a coffee shop or where a lot of my friends go to for labs.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="31" public="1" featured="0">
    <fileContainer>
      <file fileId="31">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/e335d0218dda8cb14785dd6e3907c95a.pdf</src>
        <authentication>dd8c11354523f47aea6984ff04be36b9</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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="2">
                  <text>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="63">
                <text>Tyler Jankauskas</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64">
                <text>It was most difficult to sketch the scale of the campus, because I conceive of the campus as a&#13;
series of discrete, interconnected areas rather than conceiving it continuously (cf the Situationist ‘map’).&#13;
I found it interesting that there is a sort of ordering of discrete areas as well. In relation to the Common&#13;
or the river area I conceive of Harvard Yard as one area, but when thinking of the Yard or the Yard in&#13;
relation to to surrounding areas (eg Barker Center), I see the Yard as made of discrete areas as well (the&#13;
Yard proper, Tercentary theater, etc). The area north and northeast of the Science Center is one that I&#13;
do not frequent very often, and the space’s relations to others is very blurry for me. I am most familiar&#13;
with the area surrounding my home in Lowell House. My map is most likely distorted due to the time&#13;
spent in areas. I have spent more time in places like the Yard or my surrounding home environment.&#13;
Travel routes are interesting because I am more spatially aware of routes whose scenery I enjoy or am&#13;
attentive to (the Common) than areas where I space-out because there is not anything I am interested in&#13;
(Garden St from the Common to the Quad). I think it is interesting that the particular locations of the&#13;
shops on Mass Ave and on the streets connecting Mass Ave to Mt Auburn are jumbled to me. I do not&#13;
shop much, but I do pass them every day and I imagine that a business would like residents to know&#13;
where it is.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="117" public="1" featured="0">
    <fileContainer>
      <file fileId="144">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/1fc680ae4a98a2206e7c98485d24ba16.pdf</src>
        <authentication>cf88ce3571401015f7c3723f0c4a99ca</authentication>
      </file>
      <file fileId="145">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/4552bf7551842b4d498bc8fb44a8b9f5.pdf</src>
        <authentication>4bcc071ac2d8bd611e77ae817bee4a3a</authentication>
      </file>
    </fileContainer>
    <collection collectionId="3">
      <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="3">
                  <text>Sketch 2</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="235">
                <text>Tyler Jankauskas</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="236">
                <text>Newbury Street and the Prudential Center take different forms as commercial spaces due to the agency afforded in their constructions. The layout of the Prudential Center, being a designed center on a plot of land, could have taken really any form. As such it was designed with commercial interests in mind. There is a single level experience here, with escalators and elevators connected discrete floors. Stores fronts take up most every available visible space, and kiosks litter the walkways. There is an ambivalent sense of disorientation--the many turns of path the walker takes rarely have the experience of being a decided turn. The fungibility of the given franchises lends towards the experience of most any one location (and associated constellation of storefronts) being fungible with another. The consumer is always lost among the seemingly familiar, the layout ceding the best aspects of lostness (more time near stores, more likely to spend) without the worst (sense of alienation, not liking the space, wanting to leave and not wanting to come back). &#13;
&#13;
Newbury Street only definitely became a shopping district in the last 50 years, though it of course had storefronts previously. Walking in the contemporary permutation of one of Boston’s oldest streets reveals the ad hoc nature of its storefronts. Irregular, jumbled on top and underneath of street level shops are stairs and doors utilizing every inch of real estate possible. One of Boston’s few areas without curves, the streets are gridded—not in the perfect Cartesian grid but arrange in straight parallels and perpendiculars. One maintains a sense of location to the landmark Public Garden and Charles (which are likewise perpendicular and parallel to Newbury). The irregularity of shops does not lull consumers like those in the Prudential Center. A sense of spatial awareness remains, but the ad hoc arrangement is more pleasing than the sterile one of the Pru. The consumer needs no architecturally designed anesthetic because he is not undergoing an architecturally designed lobotomy.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="196" public="1" featured="0">
    <fileContainer>
      <file fileId="288">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/3948d3d2fb66831dc518174b06f317ae.JPG</src>
        <authentication>020998d34ba747688e998d36cc5d68cb</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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="2">
                  <text>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="391">
                <text>Tyler Lott</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="392">
                <text>My first impression was that after looking at a map, the scale of my drawing was a bit off. Some buildings were a bit larger in the sketch than they actually are (Harvard Coop). I think this reflects what locations I've been to most in the Square. &#13;
&#13;
While I do not frequent the various stores (shown by my inaccurate drawing of the places behind Curious George), I spend quite a bit of time at the Coop. So in the sketch the size of the Coop was overestimated. I think the areas we use more often are overrepresented in terms of scale. I drew Straus Hall and Mathews Hall nearly the same size, where in reality Mathews is much larger. I live in Straus Hall, so perhaps that accounts for my size discrepancy. While I would have originally thought that the places people frequent more would be represented more accurately in a sketch, this is not the case for me. I, instead, draw the areas that I visit most frequently larger than than their actual size. Perhaps this oversize of buildings shows the significance of a building in my life.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
