<?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/browse?output=omeka-xml&amp;page=9" accessDate="2026-04-30T16:36:36-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>9</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="141" public="1" featured="0">
    <fileContainer>
      <file fileId="193">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/2c7fa10e00355013f9d20dd4f8cea92b.pdf</src>
        <authentication>f2cce1456ca8caa5f825b22bd5ef2696</authentication>
      </file>
      <file fileId="194">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/c1651dd41f396397abbf907ce5ec1532.pdf</src>
        <authentication>023f313a6ea6ef33490391f7292d9554</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="283">
                <text>Carl Rogers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="284">
                <text>Copley/Prudential &#13;
&#13;
As I ascend flight upon flight of escalators up to Copley Place, I feel myself being transported to another world—to a quiet and glamorous realm, safely perched several floors above the hustle and bustle of the streets below. I’m struck by just how conscious of a design effort the elevation changes present at each entrance/exit must have been, and by the message that they not-so-subtly convey—that Copley, and to some extent, the Pru, are elevated, literally “high” class spaces. The contrast in design materials as one descends from Copley into the Pru is marked: gone are the cool stone benches, glitzy gold-trimmed handrails and multicolored marble floors of Copley. While the Pru admittedly lacks some of the sophistication of its conjoined twin, this change is clearly intentional, and the Pru feels decidedly more welcoming as a result. Friendlier to weary shoppers than Copley’s skylit, centralized plaza approach which limited to benches and greenery primarily to one main area, wooden benches and potted plants dot the hallways of the Pru. In a single hallway, I count more benches than the total number I saw in all of Copley—a logical choice, given that the Pru appears to have far more shoppers than the almost prohibitively expensive Copley. The trio of security guards standing vigilantly at their posts throughout Copley also seems to have been reduced to one sole guard stationed by the Pru's entrance.&#13;
&#13;
Newbury Street&#13;
&#13;
Reminiscent of some of the sights common throughout the Pru and Copley, brightly lit brand names (albeit stuck to brownstones) and sale promotions littering both sides of the sidewalk announce that I have arrived at Newbury. Glancing above the throngs of people at the windows above the storefront to my left, I catch a glimpse of what I can only assume is someone watching TV in their apartment, and I find myself reminded of Newbury’s multiple identities and purposes. Vastly different from the lofty, secluded Copley, or even the Pru, Newbury is embedded into the city's fabric with T stops marking its length, blurring the lines between residential area, commercial center, and commuter thoroughfare. I move along the public street, weaving my way through groups of people who could be found on any other street in Boston—Newbury's dog walkers, homeless, and buskers, in contrast Newbury's meandering shoppers, however, would likely not be looked upon favorably by mall security in places like Copley or the Pru. Apart from its distinctly non-mall-like outdoor restaurant seating, Newbury also lacks benches of any kind, and shoppers in need of a rest need either walk to the bench-filled Commonwealth Mall to the north, or to pop down into any of Newbury's many cafés, inserted into spaces that must have once been Newbury's garden-level apartments.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="140" public="1" featured="0">
    <fileContainer>
      <file fileId="191">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/99c4ad0be698d5629565f2c08e59496f.JPG</src>
        <authentication>c2f233bf09a1907efb1c251a14e9a733</authentication>
      </file>
      <file fileId="192">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/b6eff67de00947bc89c7282a3b475820.JPG</src>
        <authentication>c2f233bf09a1907efb1c251a14e9a733</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="281">
                <text>Daniel Prosky</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="282">
                <text>The two shopping areas are vastly different—the first, obvious difference is that Copley Place and the Prudential Center are indoor shopping malls, and Newbury Street is an outdoor street lined with individual shops. That being said, the traffic throughout much of these locations was nearly identical. On a weekday, mostly tourists wandered the shops. Newbury Street was far more crowded, and seemed to be a far more exciting location to visit. The interior of the Copley Place and Prudential Center malls appeared a far more controlled shopping environment—few food options and the indoor, mostly artificially-lit arena contributed to a far less compelling experience. In addition to that, the mall’s waterfall and planters make an ineffective attempt at suggesting outdoor space, where Newbury Street’s charming tree-lined avenue and cute brownstone buildings, along with literally being outdoors, strongly outshine the indoor malls. Furthermore, Copley Place and the Prudential Center are a mix of shopping areas and office buildings. During rush hour, their proximity to Back Bay Station filled them and their surrounding areas with commuters racing to their trains and buses. Newbury Street, in contrast, remained mostly unaffected by the onset of rush hour. Newbury street serves well as a location to visit and stroll through while the malls in Copley Place and the Prudential Center proves useful only as a place to go to make purchases or go to work.</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="138" public="1" featured="0">
    <fileContainer>
      <file fileId="187">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/0446ede2e18fb2d2570e74438bab5a99.jpg</src>
        <authentication>b2efd2806c1e1193af5d083d256ae1fc</authentication>
      </file>
      <file fileId="188">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/1d98bf42230ccb5b354155bda5ddc4a2.jpg</src>
        <authentication>f005cddcf8a3d9129b668bbd60777212</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="277">
                <text>Adam Oh</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="278">
                <text>Having visited both Newbury and Copley/Prudential shopping centers, I was most surprised by the difference of the vibes that these two places gave. In the Newbury’s shops/street, we notice that it has a more homey feeling due to the linear building of shops. All of the shops are accessible on the first floor whether. Another difference of the newbury shops that I found interesting was the outside sitting spaces provided by each of the shops. There were tiny patios made of brick which also made the viewer feel more comfortable because of the familiar brick structure. Along the top of the shops were residential buildings which contributed to the more at home feel. The wider streets also gave a feeling of openness and the natural light from the outside really made the shops on newbury more attractive and feel very homogeneous. Upon entry into Newbury St., you feel like you have entered a residential neighborhood rather than a commercial district. However, the owners of stores replicate the feeling of a commercial district by providing signs for their stores that really pop at you. The shops at Prudential had some similar things as Newbury such as the incorporation of natural lighting and lots of plants. I noticed that there were a lot of windows that let natural light flow through along with attempted greenery with artificial plants. However, one thing that really stuck out as a difference was the starkness of the shopping mall. The choice of white along with the narrow corridors and lack of sitting spaces made everything very “in your face”. The mall also felt very disjointed with very a different feeling as you step into a different part of the mall. Another theme that I noticed was that the mall was very vertically structured whereas the newbury shops were horizontal. This vertical architecture gave off a sense of grandeur and an elitist aura. The last difference that stuck out was the quality of stores in each location. While Newbury had more stores that were for the everyday customer such as smoke shops, convenience stores, etc., the shops at prudential were more high end clothing and accessory stores.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="137" public="1" featured="0">
    <fileContainer>
      <file fileId="184">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/cb4bd918c81127506f59d6050f6a6f82.jpg</src>
        <authentication>724726987fa0dc29ea570a65d5185566</authentication>
      </file>
      <file fileId="185">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/8c8be0c444670c3a44a9cb4b4fc04f1e.jpg</src>
        <authentication>c1ad57e23116d484ee3df6508c306ba6</authentication>
      </file>
      <file fileId="186">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/e34d821cdb161808d7a1173a06d6394b.jpg</src>
        <authentication>78adb72d51dc52e52ad2476c80c06148</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="275">
                <text>Harry Newman-Plotnick</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="276">
                <text>The main point I attempted to distinguish in these two/three drawings was the difference between non-commercial walkways in the two spaces. In the malls the walkways felt like these clearly defined pathways, with just a few entrances/exits, surrounded by a haze of stores with the street in the background. That is why the main path I followed was a thick blue arrow, with the stores and streets being loosely shaded in red and grey areas. While walking down Newbury Street, however, it felt like the exact opposite. The streets were clearly defined and the stores were obvious, with steps up to their doors and each store set apart from all the others. The sidewalk, though, was vague. There were gardens and little patios in front of some of the stores, and the demarcation between public and private property was unclear. Thus, the walkways were full of unclear exits, which is why there were many small arrows and the shading was vague. The streets and stores though were solidly colored. This shading is also meant to distinguish between the atmosphere of the two scenarios. In the mall the walking is confined, enclosed on all sides by walls and a steel and glass ceiling. Newbury Street, conversely, is open to the world, with a much larger variety of sounds, sights, and smells. In the malls the walkways were there to efficiently get between places to shop, whereas on Newbury Street, the stores seemed more like fun ways to punctuate your journey up and down the sidewalk.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="136" public="1" featured="0">
    <fileContainer>
      <file fileId="182">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/b7231136f4e6ab6aa4e9d539a507c124.JPG</src>
        <authentication>043eaffc51aadd0cd3a170d889f00248</authentication>
      </file>
      <file fileId="183">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/38be1668a8e6453ab45ebf3c89ae7428.JPG</src>
        <authentication>4c263f32c242b53425b598767336b691</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="273">
                <text>Quinn Mulholland</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="274">
                <text>As I walked through Copley Place and the Prudential Center, I was struck by how the visual experience of the mall changed, both in terms of types of stores and in terms of aesthetics. Copley Place seemed to be mostly high-end fashion retailers, and there was little natural light. The floor added to the sense of luxury, being made of marble and brick, although the ceiling offered a somewhat disorienting contrast, with bare lightbulbs and metal pipes that would normally be hidden exposed. There were a few benches, but very few people were using them; most people seemed to be on their way to somewhere else. Prudential Center, meanwhile, had an abundance of natural light because the ceilings were made of glass. There were also many more plants benches in the main arteries, and more people sitting down.&#13;
&#13;
Going from this mall to Newbury Street was interesting, because there were a lot of&#13;
similarities, but some important differences. Newbury had similar types of stores,&#13;
although perhaps more restaurants and coffee shops, and it was also similar to a&#13;
private mall in that similar types of stores were grouped together (restaurants on its&#13;
western side and clothing stores to the east). However, the public nature of the&#13;
street made the experience walking through it much different from that of walking&#13;
through a mall. I passed several beggars on the street, while there weren’t any in the&#13;
mall. This is probably a function of the visible police presence in the mall (I didn’t&#13;
see any police officers on Newbury) as well as the accessible nature of Newbury’s&#13;
entrances and exits, since they were public streets, rather than doors. This also&#13;
resulted in a lot of people on the street that weren’t necessarily shopping but simply&#13;
passing through.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="135" public="1" featured="0">
    <fileContainer>
      <file fileId="181">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/ce38a818bbb3cd0f26f159feb0ceca93.png</src>
        <authentication>d55dc2b83b84ad1ca16490a6e4997b71</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="271">
                <text>Drisana Mosaphir</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="272">
                <text>One feature of Copley Place that I found interesting was the instinct to mirror the layout of outdoor places. The signs that functioned almost as outdoor directional signs, as well as the fact that seating areas within the mall almost mirrored the outside gathering square, seemed to want to emulate avenues/an outdoor shopping experience recast in a more luxurious set of materials. Further, the main difference was that the seating areas were slightly more desolate/empty, and some were located just within the entrance doors but below the stairs one would need to take to get up, leading not as many people to be gathered there to socialize as were found in the square outside and across from the large T station. Since a security guard was sitting right by the entrance, it is evident that this was not as much of an “open” social space.&#13;
The space on Newbury St. that I chose to focus on was a “hidden” passageway between Newbury and another street that displayed a mixture of shops with a large church building. There seemed to be an intentional effort to blend the styles of the shop buildings with the more historic appearance of the church, as well as to create a quieter brick alleyway to the next row of shops. This seemed to simulate the experience of a “mall” while at the same time being different in that there was intentional effort to blend the shopping areas with the existing cityscape.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="134" public="1" featured="0">
    <fileContainer>
      <file fileId="179">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/b58bfcd93b40205fce783809fd96f787.jpeg</src>
        <authentication>b66dc427128e44465188fdbe38f6eeba</authentication>
      </file>
      <file fileId="180">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/dad9f7885e21814dd1530621e81f6971.jpeg</src>
        <authentication>e7ae935295faa7c9800e31ed4442c400</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="269">
                <text>Daniel Montoya</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="270">
                <text>Beginning with the spatial analysis of the Prudential Mall, one can see the development of commerce in a unique geographic dimension. The first things you notice when entering this mall is the sheer magnitude and monumental size of both the stores and the high-rise walls. The overwhelming space creates an unbalance power dynamic between the shopper and the physical space that promotes a sense of capitalism above all. Other important factors to include is the very plain but regal walls that give a sense of classic appreciation, as well as the prevalent use of windows that plays around with the outside scenery. The crystal roof makes the skyline become part of the physical space of the shopping mall, meaning you see a gorgeous residential building springing in the horizon. Entrances to the Fashion Plaza are very fluid with the movement of persons and is not big on the promotion of 90º turns. Likewise, the entrances all pour into one big center as a way of directing traffic into a main commercial node which comes to benefit of both the shopping and commercial experience. The activities I see mostly are individuals coming with their families (Sunday) casually strolling, window shopping, every so often actually shopping and sitting. Sitting places are strategically placed in order to give a panoramic view of the shops around, meaning, while causally sitting, people will look around at shops they might had not noticed. It also provides further incentive for people to explore the entirety of the mall, without getting tired, do the sitting arrangements are placed in key center points before people begin a new route of shopping. Security is achieved by having a limited amount of entrances with top designer lines like Salvatore Ferragamo as to discourage those who might not afford such brands from moving too forward. Commerce attracts money and money attracts commerce.&#13;
&#13;
Newbury Street is a unique case in the sense that it impacts a very-high end residential area with the aesthetics and influences of a commercial zone. The design and integration of the first and basement floors through kitschy advertisement and colorful signs really inspires the commerce behind the street. More importantly, the usage of both floors, sometimes an even higher floor, for commerce parallels the high-rising effects of malls as to show variety and the same power dynamic between shopper and store. Newbury is one of the most exclusive residential areas of the city, so the street balances the influx of commercial exchange with the need for a tranquil residential life. You see that by the way streets are one-way as to prevent accumulation of traffic and the lack of mayor construction around (very in the horizon). Likewise, the strategic placement of trees along the sidewalks is designed to appeal to an aesthetic of naturalism that many residences appreciate in the green outside their second or third floor apartment. The setup of the street also alludes to the grand walkways of malls with ample space given for casual stroll, a relatively high quantity of sitting space whether it is public benches or café tables. The street still maintains its own with the presence of cars parked on the side, as well as the natural touch of trees on the outside, different factors than one would see inside a mall. Finally, Entrances to and from Newbury are also done in a one-way fashion as to maintain a circulation of traffic (especially since parking is so limited). Newbury is situated in a central location of town, next to prominent streets like Park and Boylston, but it still maintains its old town-commercial feel and if you look down the street, the building heights are very standardized. Newbury is one of the most desired places in Boston, and understanding its spatial analysis, makes it even more desirable.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="133" public="1" featured="0">
    <fileContainer>
      <file fileId="177">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/e3c3eec5246537564a8df37d24bbc0da.JPG</src>
        <authentication>4d5aa93db65cab1ed29c3d46fe25b630</authentication>
      </file>
      <file fileId="178">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/7b2eba6084f18b47806cc5df1f712f06.JPG</src>
        <authentication>a7a4d8d4a6708a1ede556fe7b952d859</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="267">
                <text>Maria McLaughlin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="268">
                <text>Copley Place and the Prudential Center make use of a lot of natural light let in by atrium- style ceilings and large windows. The white-accented walls reﬂect the natural light in a way that makes the entire mall seem bright, clean, and airy. The constant upward and downward and across mobility that the space necessitates makes the layout more organic and less monotonous. This can improve the shopping experience because it keeps the shopper walking around farther than they would have. &#13;
&#13;
I went during lunchtime on a weekday, so I noticed a lot of businesspeople using it as a lunch spot on their breaks. I also noticed a few younger women who looked like they were shopping on their lunch breaks, an elderly couple shopping, and a few tourists. &#13;
&#13;
In Bridge Court, I was asked for money from a homeless person sitting on a bench there, which leads me to believe that anyone is allowed to enter and exit. The doors are almost always revolving though, and there are a lot of escalators involved, so I would assume that it’s not the most handicap accessible place. There are many benches. Newbury Street is clearly commercial on the ﬁrst and second levels of the townhouse- like buildings because of the shop windows and subtle signs. The place is different because it resembles a neighborhood, complete with front yards. The other purposes for Newbury St. are learning facilities and some residences, although they are very high-priced. &#13;
&#13;
Newbury St. is situated so that you cannot see Hynes and the Pru from it, but so that you are close enough to walk there easily from the corresponding T stops</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="132" public="1" featured="0">
    <fileContainer>
      <file fileId="175">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/59531b5687003b0be76a298c211e2c45.jpg</src>
        <authentication>f249a117347cf0ab6e3b26105c6b9c36</authentication>
      </file>
      <file fileId="176">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/8d38b2f66c80cefe4cb39f6f4a802763.jpg</src>
        <authentication>b074df1e72d68ca3d908426ad830f88c</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="265">
                <text>Stephanie Manivanh</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="266">
                <text>The Prudential Shopping Mall was a very open-air atrium type of space with glass ceilings along the entirety of the mall’s length; this made the shopping experience feel very “open” and bright which I assume aids in helping customers spend more (haha). The materials in Copley were much more darker in color and more expensive-looking. This makes sense since Copley caters to a more high-end clientele. Along the Prudential near Barnes and Noble were a lot of small sitting nooks and windows that looked out into the courtyard whereas elsewhere in the malls there were no designated sitting areas. The security here was very strict in not letting people take pictures of the inside of the mall…(I got told off).&#13;
&#13;
Newbury Street is such an interesting mix of retail and residential. What I loved is that the first floors of each of the buildings was so tastefully transformed into residential units by the use of tall glass windows while the floors above were untouched. The biggest difference from a shopping mall is the fact that you feel like you are in a neighborhood rather than a specific shopping area which will clear out at night. It is clever that Newbury Street runs parallel to the Commonwealth green space; nature just around the corner at each street.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
