<?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=22&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-03T23:53:31-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>22</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="76" public="1" featured="0">
    <fileContainer>
      <file fileId="76">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/6f9e1eca511bad50e3ba6e0375a7e32f.pdf</src>
        <authentication>8878f6fa3002cc8d0cfc9222fea26b89</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="153">
                <text>Veronica Wickline</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="154">
                <text>Sitting in the Starbucks at the corner of Mass Ave. and JFK feels like being in the center of the world. You are the axis around which activity turns. I chose this view as the vantage point for my map because it captures the buzz I associate with Harvard Square. &#13;
&#13;
Furthermore, this view resonates with me for its accessibility: anyone can walk up to the second floor of Starbucks and get a top-down view of the Square. So often, aerial view maps are a mark of power, often military power. To see a space from the top down is to comprehend it, even to posses it in a way. Even now you must have money or clout to access an aerial view. For example, you must have permission from Harvard to see Cambridge from the top of William James Hall or the Science Center. You must have the money for a plane ticket to see Boston from the air. &#13;
&#13;
At Starbucks, one finds an inexpensive union of individual pleasure and commercial power. If Starbucks weren't such a successful business, it would not be able to afford this central location and its patrons could not enjoy a top-down view of the Square. At the same time, any individual with three or four dollars to his name can purchase a coffee along with a day's access to Wifi, shelter, restrooms, and an aerial view of his environs. Even though I have a vague (and not at all justified) distaste for commercial coffee chains instead of independently-owned coffee shops, I appreciate the ways in which this champion of Capitalism empowers its patrons for a very affordable rate.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="161" public="1" featured="0">
    <fileContainer>
      <file fileId="235">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/e2e2afcbe3e6af485296963d3bf54a6e.jpg</src>
        <authentication>3d4c4411ceec8cc4b3600f4f8c4469df</authentication>
      </file>
      <file fileId="236">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/e4dd07c6b070eba6c4708683d1d173d1.jpg</src>
        <authentication>b04f108c8a10d6d13588d0384195b23b</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="323">
                <text>Veronica Wickline</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="324">
                <text>The primary difference I noticed between the indoor mall organization and the design of Newberry Street was the manner in which merchandise was featured from the windows. Throughout the malls, storefront displays appeared in windows that were much larger than human beings. Each store was a microcosmic world, featuring fabrics, accessories, and atmospheres unique to that brand. Looking through an indoor mall vendor's window, one rarely saw more than one object type (e.g. handbags OR dresses OR watches). When a store had shut down, rather than put up a “CLOSED” sign, the mall painted the windows black or built a box around the space so that it became invisible. More than anything, the indoor mall policed its visual output. &#13;
&#13;
In contrast, Newberry Street emphasized an unplanned and casual atmosphere. Storefronts often consisted of small windows on the basement floor; however, one could also find large display cases for the high-end stores. Musicians in strange clothes played for money on the sidewalk. More people were walking their dogs. Because a street relies on city police rather than privately contracted security companies, there was less of a sense that someone could be out of place—though at neither location was anything like a formal dress code enforced. &#13;
&#13;
Copley Place succeeds as a suburban shopping area in an urban space by duplicating the suburban mall but only selling spaces to high-end vendors. It’s a chique mall, a mall with all the amenities that urban concentrations of resources can afford. They are even putting in a special food court dedicated to Italian food only will be run by a famous chef. Newberry Street, conversely, emphasizes the city layout. Boston brick is everywhere, and interspersed between shops are the occasional homes and schools. Even with often similar stores, these two shopping areas manage to not put each other out of business by maintaining distinct vibes.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="34" public="1" featured="0">
    <fileContainer>
      <file fileId="34">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/a4c3d6ff1ee067898a7fb33f4c9f7191.jpg</src>
        <authentication>57883edbbd48b746532dad49400ff73a</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="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="69">
                <text>For my sketch, I followed ChengHe’s advice and focused on the areas that are most meaningful to me on campus—these also happen to be the areas that I spend the most time in at Harvard. Most notable, although not central in my sketch, is my home away from home: Adams House. Harvard College really intends for the Houses to be fulfilling communities and I truly feel that Adams succeeds at this. This is why I have spent so much time and graphite on the bottom right corner of the map. I also (rather cheekily) did not mark the other houses on my map. Adams residents have a reputation for looking down upon and being snobby towards other houses—I used my map to perpetuate this notion. &#13;
&#13;
The other places that are important to me on campus, namely coffee, libraries, and the art museum are also marked. &#13;
&#13;
The central part of campus is Harvard Yard and as such takes the central location on my sketch. If I had a bit more time and artistic ability, perhaps I could’ve inverted the map to make Adams the center of my sketch (since it is the center of my Harvard universe). I was able to draw out the big buildings in the Yard that I’m familiar with—i.e. freshman dorms, classroom buildings, but I definitely haven’t stepped foot in places like Robinson Hall or Loeb House to remember to include them. I think I also drew the paths incorrectly; however, the aim was more to show some representation of a walkway rather than necessarily depict the existing walkways. Additionally, I think my scale is some way off given that Adams appears much larger than some of the dorms in the Yard, and Widener is nowhere near as large as it should be (it is much bigger than most of the dorms), but the shapes and sizes I drew are the evocations of these places in my head and probably as such depict their relative importance to my life.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="70">
                <text>Victor Kamenker</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="120" public="1" featured="0">
    <fileContainer>
      <file fileId="150">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/6da3aff3dec68a0984833c458a5bc927.JPG</src>
        <authentication>c127dacd82e5d2f76d959b191f0e05d3</authentication>
      </file>
      <file fileId="151">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/5ac6d9305ec7a06f1c138f0547ee4448.JPG</src>
        <authentication>cc41e1f9f1ea5a791d96ecd334cbb725</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="241">
                <text>Victor Kamenker</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="242">
                <text>Ostensibly, both the Prudential Center and Newbury Street are urban spaces that are designed for commerce and public gathering. Despite this, the two have very specific idiosyncrasies and differences, but both still manage to create environments conducive to success of the urban marketplace. &#13;
&#13;
Both shopping centers are designed with the pedestrian in mind, but this is incorporated in different ways. In the Pru, the emphasis on the shopper is created through grand hallways with high ceilings and plenty of open space—the walls, ceilings, and floors are cream-colored, and there is plenty of natural light filtering in, giving the illusion of spaciousness. On Newbury Street, the sidewalks are practically as wide as the driving lanes (wider in some places), and there are a number of intersections toward the west end of the street that do not have streetlights, making them more pedestrian-focused. &#13;
&#13;
Additionally, the dearth of parking spaces and the draconian regulations make it very difficult for automobile drivers to navigate the area. Additionally, both shopping areas have stores of various characters interspersed with eateries and more quotidian establishments like pharmacies or grocery stores. Once inside the Pru or on Newbury Street, one does not go to just one store—the atmosphere created in both places encourages visitors to make an experience out of the visit and have a shopping afternoon or shopping day. On Newbury Street, there are many glass storefronts that simulate the experience of walking through a mall—visitors can peek in to stores with particularly intriguing window displays (like the sewing machines at Allsaints). &#13;
&#13;
The entrances and exits to both locations are very carefully planned. Obviously with the mall, there must be actual entrances; these are designed to let out either at major intersections, at subway stops (e.g. Prudential stop, Back Bay stop), and at the hotels that abut the malls (Westin, Marriott, Sheraton, Mandarin Oriental). Newbury Street has entrances from every cross street, and the corners everywhere are built in such a way that turning onto the street opens up the view for the pedestrian of everything on offer—i.e. the corners are not obscured with tall buildings that block everything else.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="42" public="1" featured="0">
    <fileContainer>
      <file fileId="42">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/53e7aac0f791906a165eb38cdafd063a.png</src>
        <authentication>d1e6a2263917218da8c1b1fb033e2ee0</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="85">
                <text>Yao Li</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="86">
                <text>The placement and proportion of the buildings within Harvard yard are fairly accurate on my map, probably because they’re enclosed in a square block (and then are located in specific geometric subdivisions within that block). This orientation helps me systematically rebuild the space in my mind. The general direction of landmarks in relation to each other is the only accurate characteristic on the rest of my map. The most striking difference and cause of inaccuracy is the proportion of buildings and streets – I tend to make them too large, or the space between them too distant. This reflects my perspective in that I only take notice of all the college-related buildings in the area (and some commercial stores); all other landmarks, buildings, and streets are hazy in my memory. This is likely true for all people – we only pass by, visit, and remember a very small portion of the environment we live in, and that portion depends heavily on our past interactions, memories, and habits. Most people do not have photographic memory (and do not need it because prioritizing is a natural survival instinct). In my map, Harvard Yard itself is proportionally too small in relation to the campus as a whole – perhaps the rest of the campus sprawled out so much in my mind because I didn’t have the simple geometric boundaries of the yard to judge distances and proportions with.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="128" public="1" featured="0">
    <fileContainer>
      <file fileId="166">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/610c2dd98d180972b9c5b62a13a647e1.pdf</src>
        <authentication>ae3b79a8d5ef09a3818327620a3783c2</authentication>
      </file>
      <file fileId="167">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/60d66035d38922253bf7f6776d4dc95d.pdf</src>
        <authentication>cf1acbfcfe9dc66a2abdbe374cc0ddc6</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="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="257">
                <text>Newbury Street and the Copley and Prudential malls both serve roughly the same purpose – commercial shopping – but do have vastly different impacts and experiences. In general, Newbury seems target younger and less affluent consumers and Copley/Prudential older, more established ones, simply by way of the kinds of shops in each location – bookstore-cafes, Newbury Comics, and Deluca’s Market vs. Dior, Gourmet Boutique, and Express, for example (although Starbucks, as one would expect, is ubiquitous). &#13;
&#13;
This dynamic is reflected in every characteristic of these places. Newbury Street is located outside in open air, sharing pedestrian space with cars and residential sections and other businesses (e.g. Beacon Realty), while Copley and Prudential are entirely enclosed and only accessible by pedestrians (except that one strip with the indoor birds and trees), and they contain almost only shops (and banks so people can get more money to shop). Newbury is largely a small-scale renovation of a street with existing four-story red brick buildings, or at least designed to look that way, while the Copley-Prudential complex consists of huge, grandiose structures of glass and steel and marble and linoleum. The regulars at Newbury tend to be students and local community members, while the regulars at Copley and Prudential tend to be middle- or upper-class business people (many of whom probably work but don’t in the immediate area) and occasionally their families. The very plan of these commercial centers have different influences – Newbury’s linear one-street plan echoes the gridiron and egalitarianism, while the cross and nodal plans of Copley and Prudential reflect churches, palace gardens, and the concentration of power.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="258">
                <text>Yao Li</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="32" public="1" featured="0">
    <fileContainer>
      <file fileId="32">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/816fda2f04bbf74cd23e5affa056f427.jpeg</src>
        <authentication>6a00a5530bae90c7c516f070a0d93d10</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="65">
                <text>Yesenia Jimenez</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="66">
                <text>While drawing this map, I realized how little I knew about the specific businesses located in the Square and how difficult it was to draw what I perceived. I tried to draw a map that was more or less to scale with how I saw the area, but I soon realized that it was quite a challenge. I had a good idea of the orientation of buildings and the general location of clusters of buildings and such, but I think I tried to be too specific and did not have enough room for what I wanted to draw. Before the final sketch I attempted two others that mapped out the well-known spots, and then I realized that even if I knew the smaller “boxes” on the map, I could not fit the names on to the sheet. I also realized that aside from the known courtyards and small gardens, not much green was mapped out on my map of the Square. It really demonstrated what I see as representative of the area, and logically that is the University.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="118" public="1" featured="0">
    <fileContainer>
      <file fileId="146">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/abe722f9eaf5ddf14820581ff8960edf.jpeg</src>
        <authentication>8b54a44b35209e0de906eca9782b5305</authentication>
      </file>
      <file fileId="147">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/62999d85b46d5b9810889697b2184ea1.jpeg</src>
        <authentication>0caa73794420739557d85d198e77e511</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="237">
                <text>Yesenia Jimenez</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="238">
                <text>I focused on the physical atmosphere more on Newbury Street than in the Prudential/Copley Place Shopping Center. I tended to centralize my ideas on the people passing through the space in the latter. I noticed that even though Newbury Street is essentially a landmark in Boston, it has foreign elements in its atmospheric architectural design. “La Voile” café is representative of the fact that there is a Parisian atmosphere on a Bostonian street and that is what draws consumers and pedestrians. I almost took it as a commentary on how Boston can learn something from the more relaxed, people lingering Parisian café atmosphere. I also noticed that everyone walked with a speedy pace, aiming to a final destination. There weren’t people walking slowly and really enjoying the shops or restaurants from the outside, but aiming to get inside. I found that more people walked on the right side of the street towards Gloucester and away from Dartmouth, than the other way around. I thought this was because although people aimed to sit in shady locations, the sun shone on this side so it was more enjoyable. &#13;
&#13;
The Prudential Center’s Boylston Arcade area was very interesting because I found myself focusing less on the structural design than on the way people moved in and out of the space. The only physical structures in the space were the kiosks that sold Boston souvenirs and clothing, but nothing to sit on or admire otherwise. Most people moved towards the Huntington Arcade, the corridor with plenty of plants and greenery, because it offered more opportunities to sit and relax. Many moved towards the Prudential Arcade probably because of the large amount of shops down this corridor. The Boylston Arcade had a large number of people moving towards it, but not necessarily to shop or to sit but to exit the building. These were faster paced than others. I sensed that unless there was a store people could peruse or a place they could perch on, they would continue walking. Lastly, I saw that both on Newbury Street and in the shops, people in groups or pairs tended to walk slower than those alone. Those alone also tended to be using their phone and/or have headphones more than those with others.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="59" public="1" featured="0">
    <fileContainer>
      <file fileId="59">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/c186596d8f32a8721c53cbf173bc4a14.jpg</src>
        <authentication>8130f4301d9356657c092e6cfe1c11d9</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="119">
                <text>Yigit Sezener</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="120">
                <text>In this amateurish mental map which I have devised solely using my memory, and images that come to my mind when I think of the places around Harvard Square; depicts a path I take quite oftenly, the path that leads from my apartment to the river side. I live off-campus on Harvard Street, in the building I have depicted with the smoke coming from its' chimney. I usually take the road down to Harvard Sq, then turn left onto JFK Street to get to the river. I really enjoy the riverside either for exercise or contemplation and really like the duck who inhabit there, which I attempted to artistically convey. Comparing my map to an accurate one of course reveals the plethora of inaccuracies that are inherent in my mind map; but it also showed me how much mental space and importance we accredit to pathways we take often. This often leads to the architecture of these pathways and the building we come across on these pathways to plays bigger roles on our psyche and have influence on our everyday.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="143" public="1" featured="0">
    <fileContainer>
      <file fileId="197">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/d37eb823f5e9ffa2011ccbf7d054db11.JPG</src>
        <authentication>a027a8eddd6d6e4f4458243869b15a23</authentication>
      </file>
      <file fileId="198">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/2e6d513aa83a836bb8e05b03df38016e.JPG</src>
        <authentication>e2e6d4a05f2f8d56e9b6b9adb32ac9a6</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="287">
                <text>Yigit Sezener</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="288">
                <text>Newbury street offers a very unique shopping experience that is at once very similar to that of a shopping mall, but also carries with it great discrepancies. The first aspect of Newbury street that is mall-like is the continuous stream of un-interrupted shopping locales. Unlike many other shopping streets in the world, this particular segment of Newbury Street is not interrupted with residential settlements or eateries. Furthermore much like the uniform facade of shop-fronts in a wall, Newbury Street offers the same uniformity on the facade of it’s buildings. Each building is adorned with a Neo-Georgian pointy roof and the entrance to each building is through a wrought-iron post-industrial bridge. This is the part where Newbury Street differs from a mall, in the sense that every shop has an extended entrance and sometimes it is even confusing to figure out which bridge leads to which shop! &#13;
&#13;
Contrastingly Copley Center offers a much less confusing shopping experience. It is built as a series of narrow pathways that lead up to great big spaces that contain shops and offer an open floor plan that allows the shopper to see other floor. This combined with the massive waterfall in the middle creates a sense of commotion, movement and bustling the mall even on a very non-busy today. If the floor plan wasn’t this open and the levels layered the mall would feel much less crowded; which is an interesting contrast to Newbury which always feels like it’s crowded and bustling due it being a narrow street.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
