<?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=9&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-02T22:34:05-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>9</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="180" public="1" featured="0">
    <fileContainer>
      <file fileId="268">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/b9909bcbcfce583e37d8b8de107eb6de.pdf</src>
        <authentication>d996fe2bd1e3ae3b2cb482e56624b24d</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="360">
                <text>Isabella Chiu</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="361">
                <text>I sought to recreate my culinary experience in the Harvard Square area in this map. The eateries are colour coded with green being my strongest recommendation and red being my weakest, while orange is in between. I noticed that I often clustered the eateries by general area but did not place them in the correct precise location (e.g. side of the street, or left/right position relative to neighbours). The ones that were most accurate were the eateries that I frequent the most. I omitted a few eateries that I have either seldom or never visited. &#13;
&#13;
Other elements of the map that were fairly accurate included the buildings I have/have had class in and the streets where I have driven before. There are major gaps beyond the core of Harvard Square, most likely because I quite rarely walk to those regions. Other elements that were mistakenly omitted from the map include small green spaces and plazas around the Harvard Square area. This is most likely because I spend more winter months than summer months on campus and do not often sit outside in those spaces. In the colder weather, it is easy to rush through the outdoors, aiming to get back into the warmth of the indoors as quickly as possible. &#13;
&#13;
Overall, I would conclude that the map is extremely skewed to portray my specific experience of Harvard Square.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="16" public="1" featured="0">
    <fileContainer>
      <file fileId="16">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/d7cd4cd0b1c4fc777c19a41783a93578.jpg</src>
        <authentication>26fb3ef700016323c9ba20af9d60f42e</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="35">
                <text>Jackie Delmuto</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="64" public="1" featured="0">
    <fileContainer>
      <file fileId="64">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/b5541eebf38c0ccb8b20208912f3cc17.JPG</src>
        <authentication>bfb4824afdb1949975acca4d8dbd9f11</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="129">
                <text>Jacob Steinberg-Otter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="130">
                <text>Although I’m biased, after comparing my map to a Google Maps image of the area, I would say my illustration was decently accurate. I have accounted relatively well for the positions of Harvard Yard relative to the law school, as well as the undergraduate houses on the river and Cambridge Common. My map’s scale is a bit off in certain areas, particularly Garden Street leading up to the Harvard Quad, and I did not accurately portray the edge of land to water by the Charles River. I don’t quite know why that’s true, but I imagine that the fact I drew Harvard Yard first and felt constrained by the edge of the paper played a role. In general, it appears as though my memory was much more accurate regarding placement of streets than other things like placement of buildings, etc. I’ve found this true in other parts of my life as well – I’ve always had a bad sense of direction, and that may be because I have a hard time remembering “landmarks” and their placement in space. At the same time, I’ve always been good with a map – If I have one, I can navigate my way around quite well. Indeed, I could picture a map in my brain relatively well once I’ve seen it a few times. The fact that my depiction of streets was more accurate than other objects may be a reflection of these.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="149" public="1" featured="0">
    <fileContainer>
      <file fileId="208">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/b4f84b5d2409b71ed161ad474918cd0f.JPG</src>
        <authentication>393d53382f720c59a7d469dcf41c41f6</authentication>
      </file>
      <file fileId="209">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/eb080b4a66d14faa6623426c14538213.JPG</src>
        <authentication>13c1f527dd36a8e29c7fd773761be2c9</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="299">
                <text>Jacob Steinberg-Otter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="300">
                <text>After visiting both the Prudential Center and Newbury Street, a strong irony in their respective designs stood out to me, and it manifested in particular in degrees of naturalness and of symmetry/uniformity in the designs. The irony was that the Prudential Center, the indoor environment that was centrally designed, seemed more natural and less symmetrical/uniform, while Newbury Street, the outdoor thoroughfare that did not develop under centralized planning, was less natural and more symmetrical/uniform. &#13;
&#13;
In the Pru, I was struck by the natural elements the designers built into the building, especially in the Huntington Arcade, which is the area I illustrated. Up above, the rafters were large skylight window pains that allowed mid-morning to afternoon and early evening sun to shine through. Along the center of the arcade, there were large dirt-filled areas in which trees and bushes rested – I counted around a dozen or so, and all held numerous plants. While Newbury street was lined with trees on both sides, they did not compare to the dense, green foliage that occupied the Huntington Arcade. Plus, the effect that being outside had on the degree of naturalness of the environment of Newbury Street was, in my opinion, easily dissipated and overcome by the appearance and smell of exhaust fumes and pollution. &#13;
&#13;
Additionally, in the Pru, the Huntington Arcade had a windy, inconsistent pattern. The skylights on one half of the ceiling did not have uniform patterns, instead curving to make way for an adjacent building structure. The pathway with plants was interspersed with kiosks in no consistent form. Meanwhile, the buildings on Newbury Street exhibited a remarkable degree of likeness: each had a set of stairs leading up to a door, large bay windows, triangular brick structures with windows towards the top, half-hexagon brick protrusions with windows, etc.&#13;
&#13;
I can imagine a reason why the designers of the Pru created a natural environment – it seems like they intended that arcade to be a place where people came to sit and relax, as exhibited by the numerous benches where I noticed people sitting and even the occasional passerby walking his/her dog. However, I don’t quite understand why the Pru designers made a varying pattern to the progression of the arcade, and I’m struck by how uniform the design of the buildings were along Newbury Street. The reasons that the centrally designed structure was not uniform and that the non-centrally designed street was do not seem readily obvious to me.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="205" public="1" featured="0">
    <fileContainer>
      <file fileId="297">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/7554b1f30036cfacba6886341a79aa1a.jpg</src>
        <authentication>9f931838673ff85517f14389f7e41ebb</authentication>
      </file>
      <file fileId="298">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/0c03e0cf87754376a2dbc605326a1e32.jpg</src>
        <authentication>c0dc09fbafc56f9465de86a0b93ecff1</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="409">
                <text>Jake Nunley</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="75" public="1" featured="0">
    <fileContainer>
      <file fileId="75">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/ebe90a41a82e2200b47838c8c589f410.pdf</src>
        <authentication>fe6dc3688816be704f77370c4adbc7ec</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="151">
                <text>Jarrod Wetzel-Brown</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152">
                <text>For this sketch exercise I mapped out a very small part of campus that is mostly centered around the portion of Cambridge where I find myself walking often when not in class. This is the region where JFK Street meets Memorial Drive near the Charles River. I am a resident of Winthrop House (one of the twelve upperclassmen houses), and this building is my home away from home. I am originally from Michigan, and water has always been a very important part of my life, so I am extremely fortunate to be so close to the Charles River. The river itself and the surrounding bits of green/ makeshift gardens are reminiscent of the lush landscape of my farming village, and they comfort me when I am missing my family. &#13;
&#13;
Along with Winthrop House, I have also highlighted six other locations on the map with a star icon because those places are locations where I have had precious experiences or made some sort of memory. I have highlighted one of my favorite study spots in the John F. Kennedy Park, the bar where I spent a stupendous evening for my twenty-first birthday, and even the Office of International Education where I have been developing my upcoming study abroad experience! There are obviously many more places that mean something to me on Harvard’s campus, but a few special locations have been noted on this first exercise! I hope you enjoy observing it!</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="160" public="1" featured="0">
    <fileContainer>
      <file fileId="232">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/1d36d559e74e2011539f16cf28729af0.jpg</src>
        <authentication>8a2fc79de9ed562878fd6aa6758c1e29</authentication>
      </file>
      <file fileId="233">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/8d4c02a1df02dc2e8fd1656a7ac3d4c2.jpg</src>
        <authentication>2619f1330f04f82a12f7226d0d7cd343</authentication>
      </file>
      <file fileId="234">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/db0484e0ddd5c303b4485d463b7993df.jpg</src>
        <authentication>17f3ccd34d0573c0d7df0ae9bc22edc7</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="321">
                <text>Jarrod Wetzel-Brown</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="322">
                <text>The Prudential Center: Spatial Consumerism &#13;
&#13;
I must admit that I was struck by how similar everything was in the Prudential Center/Copley Place. I understand that shopping malls are meant to be a cohesive conglomerate of boutiques, but, when walking around, I could not believe that the ceilings, walls, shop monikers, and even the shops themselves mimicked each other. The color scheme of these individual features was very limited and included beige wood features, crème-colored walls, and white and black store fronts and details. Even the wall sconces and light fixtures were the same colors. I did notice that the stores themselves had white fluorescent lighting, but the mall’s public spaces emitted a soft yellow light from what seemed to be incandescent lightbulbs. This intrigued me and aged the space for me substantially. It also made the space a bit warmer than the harsh lighting inside of the stores. &#13;
&#13;
The elevation of the store remained surprisingly constant other than when escalators and elevators were inserted for traveling to other levels. Glass was a major part of the program’s design which makes sense since stores want patrons to see their products. The outside of the building itself also utilized this “reveal” effect. You can see some of the stores and customers from across the street thanks to having a substantial part of the building consist of glass. Harsh lines and geometric patterns both on the outside of the building and within create sharp contrasts that add to the distinct separation of each store and individual departments. &#13;
&#13;
I observed people talking, walking, sitting on benches, eating, and, surprisingly, very few people were holding shopping bags. If anything, I was surprised to see how many people just seemed to be walking through the mall for fun. In terms of security, there were guards present near all of the entrances and even inside a few stores (four of them questioned me about what I was doing with a sketchbook). The walkways were relatively spacious and high ceilings gave the illusion of even more open spaces. I did not feel like anyone was particularly excluded by the building’s design, but, if physically handicapped, some of the stores were more accommodating than others in terms of entrance and aisle width. &#13;
&#13;
There was only one major meeting space which was similar to an indoor courtyard. The space reminded me of the gardens we have been discussing in class, but the fake places and placid water feature felt out of place. &#13;
&#13;
Lastly, I was really intrigued by how carefully planned out the stores were. For every men’s clothing store, there was a women’s clothing store either next door or across the aisle. Every watch shop was located next to another accessory shop or jewelry shop, and even shoe shops were placed next to one another.&#13;
&#13;
&#13;
Newbury Street: Open Air and Fresh Perspective&#13;
&#13;
Newbury Street is cluttered with shops and restaurants which all have massive monikers. Some were lit up, others had bright, painted letters, and anyone can see from meters away that the street possesses many stores to explore. On the street, I also saw lots of standing easels that had bright text that read “SALE!” Many of the buildings were duplexes with two shops that were literally stacked up on one another. I was very surprised by the contrast between Newbury Street’s setup versus the Prudential Center’s layout. Unlike the carefully planned out store schemes of the Center, Newbury Street’s shops were not really separated by the programs they housed. I saw a sportswear store ironically placed above an ice cream parlor, a used clothing store rested beneath a designer suit shop, and many other contrasting company tenants were around where space was available. &#13;
&#13;
I will say that the straight path of the street is actually really conveynient for consumers to see many stores at once. Unlike the Prudential Center, people can find all of the stores on one straight street which is wonderful. However, the street does remain different from the hallways of the shopping mall because it is separated by a busy street which makes it hard for people to cross, except at intersections, and so some of the stores are a bit more difficult to reach. &#13;
&#13;
The entrances and exits of the shops consist of two design schemes. The upper level shops possess large stone steps and rather ornate doorways (that preserve the architecture of the area). The lower-level shops have cobblestone entrances that are obviously separate from the smooth sidewalk. Smaller steps leading down to the store’s doors are also present. Unlike the mall, there are no wheelchair accessible entrances to any of the shops which is discouraging. &#13;
&#13;
As mentioned above, the shops use easels with sales taglines and large monikers that mimic the shopping mall storefronts. I will say that the stores seem much more independent because they are in separate buildings on a metropolitan street rather than all squeezed inside of one large building. Personally, the presence of real trees and simply designed lampposts also made the atmosphere more welcoming to me as a consumer, and I really appreciated the openness of the street. I did not feel crowded in that open space but felt a little crowded inside of the mall.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="186" public="1" featured="0">
    <fileContainer>
      <file fileId="275">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/18e9434c3a577ea014fac9eb9e52689e.jpg</src>
        <authentication>e3b9c974b7c958e644078799a7d623c9</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="371">
                <text>Jason Goodman</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="372">
                <text>I sketched a few routes that I’ve recently walked, along with landmark buildings that come to mind when I think about neighboring areas. My path is in red, landmarks are blue, and I made the sketch on top of a horizontal black grid to organize my thoughts. &#13;
&#13;
The fact that naturally wanted to use a grid made me realize that my perception of Harvard is in layers of distance from the river—and that most of my navigation is by getting to the right layer before walking “east” or “west” (as I perceive it) to my destination. My layers turned out very accurate in terms of scale and component buildings, though the actual grid is distorted by about 30 degrees above and below the Yard and varies somewhat in layer width. &#13;
&#13;
What was especially inaccurate about my drawing is the size of buildings and their horizontal alignment within the layers. For example, Chipotle is barely west of the Yard, and I botched how the SEAS buildings near the top ﬁt together. I also couldn’t recall most street names (a detail I didn’t attempt to include) and names of businesses around the Yard that I don’t frequent but walk past regularly. These seem like practical details not to know, since they aren’t important to navigation. What matters is getting to the right horizontal layer and walking in the correct direction.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="25" public="1" featured="0">
    <fileContainer>
      <file fileId="25">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/60b853ef7def0eade21b4860ab2ba4f3.jpeg</src>
        <authentication>89ebfd5c0570f76badf47a4787a557ad</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="52">
                <text>John Griffin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="53">
                <text>Attempting to reproduce a map of campus from memory, I realized that my knowledge was very limited to a small triangle bounded roughly by Dunster, the Yard, and the intersection of JFK and Mt. Auburn. My ability to map anything on the "other" side of JFK or anything past Quincy Street was basically non-existent, despite going to both places with some frequency. I was also surprised at the extent to which my memory of the Yard and the areas bounding Quincy Street were significantly better even than my memory of places near my own house. I also seem to have made the Quad bigger and closer than it actually is.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="113" public="1" featured="0">
    <fileContainer>
      <file fileId="138">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/cc729ab7aa142312857ec02df79e7595.jpeg</src>
        <authentication>b61d4be61493d40d01a023b38dcea846</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="227">
                <text>John Griffin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="228">
                <text>I was interested both in how this space in the mall complex seemed to function as a segue between the two malls and in how it delineated public vs. non-public spaces. In regards to the first point, I noticed that the two malls had very different "feels." Copley Place was muted in color (lots of beiges and browns) and sound (materials didn't cause a lot of echo and there were less people in general). It also tended to feel like Copley Place had pretty "definite" boundaries as to where mallgoers could enter if they did not intend to buy something--there were stern-looking people standing in the doorways of many stores. There were also few windows or doors into the outside world that were not "below" mallgoers, accessible only by stairs. In the Pru Mall, by contrast, the colors were brighter, the materials caused lots of echo, there were many more people, and the floor-plan seemed more convoluted. It also had higher ceilings and several arcades lined on one side by brick walls and on the other by glass, giving the impression that one was "outside." In this intermediate section, the colors were muted but not earth tones (as in Copley Place); there were high ceilings and many windows, but most of them were at least somewhat opaque; and the sound echoed, but was fairly dispersed. This section also seemed to serve as an intermediary between Copley Place's stricter delineation of public and non-public spaces and the general openness of the Prudential Center. One example of this that confused me at first is the seating area outside the Marriott lobby. The area is open to the public, but bound on three sides by areas that are not (a Marriott-affiliated restaurant, stairways to the Marriott lobby, and an aperture in the floor that overlooks the lobby itself). Its fourth side abuts the main public walkway, but is set off by opaque green panels. The area is darker than the mall walkway and contains stern-looking attendants. Apparently as a result of these features, mallgoers seemed tentative to enter this space; most of those who did appeared to be well-dressed businessmen. Because I found this public/private delineation so interesting in the mall, I also paid attention to it on Newbury Street. I found there that on one side of the street, the buildings were mostly unmarked (and apparently residential). On that side, there is a pretty clear delineation between public and private space: the sidewalk is public and the buildings are private. On the other side, where there are more commercial buildings, the distinction is less clear. Many of these shops and restaurants have patio space jutting out into the public sidewalk; while these spaces seem meant to invite people into the business, they also seem the opposite of inviting to non-customers. There are also spaces between these patios that are ostensibly open to the public, but people did not seem to venture into those spaces.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
