<?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=4&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-01T17:00:33-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>4</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <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="55" public="1" featured="0">
    <fileContainer>
      <file fileId="55">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/8155e2ac7d5f9e977b1d1be400845122.JPG</src>
        <authentication>bb632548aa96f1b3681b8886533c5f6d</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="111">
                <text>Daniel Prosky</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="112">
                <text>The first striking difference between my map and an accurate one is the scale and spacing, especially between streets. I found that I drew relatively accurate depictions of areas I know well, and either exaggerated or reduced the distance between these areas. For example, the true distance between Harvard Yard and Dunster House is far smaller than depicted on my map, while the distance between Harvard Yard and the Quad is a bit larger than I drew. The streets are generally correctly placed, though they are far less straight on the actual map than on my map from memory. I omitted some streets from my map, imagining connections between certain blocks that do not exist. These differences likely stem from my familiarity with certain areas and how I navigate between them. I was far more likely to imagine streets as straight North-South paths as opposed to the curved, sometimes winding avenues that they are. This exercise really shows that the way one moves and stops throughout a city has a great impact on how one imagines it to be physically organized.</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="191" public="1" featured="0">
    <fileContainer>
      <file fileId="280">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/481f31232d6bd9551923b627ba4ee38d.JPG</src>
        <authentication>78143c3e37a078f2d4a2a4a688d9e50d</authentication>
      </file>
      <file fileId="281">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/854ac153b6702e58f74977dd4414577d.jpg</src>
        <authentication>66fb8cf57e8337765429070acced5d79</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="381">
                <text>Darrell Huang</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="382">
                <text>I started off the sketch quite unconfident in my memory of Harvard’s campus (and also in my ability to draw). However, comparing it to Google’s map of Harvard, my sketch does capture the locations of the Harvard Law School, the Yard, the Quad, and the Athletic complex relative to each other. Before I began my sketch, I was able to imagine a top-down view of the campus which gave me a clear sense of directionality. My memory failed when I was attempting to draw the streets that run through Harvard Square. I could not remember how long certain streets were, where streets intersected, and the directionality of the traffic. The reason for this may have been my lack of familiarity with certain parts of the campus; I have not been to parts of Brattle Street and have only made the trek to the Quad twice. &#13;
&#13;
Overall, my sketch was accurate in depicting the main parts of the campus, but failed to capture everything in between (i.e. streets, number of blocks, and other buildings). The parts of my sketch that were accurate include Harvard Yard, the Law School, and the surrounding areas. The parts that were a little off include JFK street and its surrounding blocks and the Quad. The parts that were completely false include the space west of the bridge to the athletic center as well as the neighborhood around the Quad. Furthermore, my roads were astonishingly off in regards to directionality and length. I suppose this reveals my lack of understanding of certain parts of the campus as well as my inattentiveness to the streets and roads of Harvard Square. This also reveals that I, along with many other freshmen I presume, spend the majority of my time in the Harvard Yard/Science Center area. Perhaps upperclassmen, graduate students, and residents would produce a wholly different sketch of Harvard Square.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10" public="1" featured="0">
    <fileContainer>
      <file fileId="10">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/c4e9c3715b7ed9d894ea08ddf70f4043.jpg</src>
        <authentication>c1117202d39ce7f528e26ae1b7731edb</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="24">
                <text>Drew Chamberlain</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25">
                <text>My sketch of a map of Harvard Square and the Harvard Campus was not that far off from the actual layout of the area; however, there are many major differences. First, the orientation of my sketch is so that JFK Street runs directly north through the square. In reality, JFK St runs northeast more than directly north. This shift in orientation is likely due to the fact that, while living on campus, the river seems “down” and the area around the science center and the Law School seems “up,” so my orientation made them directly north and south. Another major difference is that the Quad in my sketch is almost directly west of the yard, when in reality it is northwest, almost closer to north. This difference is likely due to the fact that the road to the quad seems to be perpendicular to the yard; however, it is only actually perpendicular for a moment and then bends slightly north. Another major discrepancy of my sketch is the river houses. Because I live in the Quad, I am much more familiar with the route to and from the Quad and the area around the yard; I am much less familiar with the exact layout of the buildings and streets around the river, and my sketch reflects that. I tried to include some paths that I use frequently in the yard, in Cambridge Commons, or in JFK Park, though some of those were not exactly accurate either. Overall, this sketch really made me reflect on how the different areas around Harvard’s campus are connected, and made me appreciate the very strange circular and triangular layout of some of the roads around the square.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="99" public="1" featured="0">
    <fileContainer>
      <file fileId="110">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/6346778a33d9555b4573d420bbbcc6df.pdf</src>
        <authentication>7c0d9b961582a6a969b8a70742ae396e</authentication>
      </file>
      <file fileId="111">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/5da1d7ad12a15569a57bc65897214e4c.pdf</src>
        <authentication>60b4803dbad47a885348deb340c503ed</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="199">
                <text>Drew Chamberlain</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="200">
                <text>My sketches of the Prudential Center Mall and Newbury Street were stills of sections of each area. For the Prudential Center Mall, I chose to sketch a small section of the large and elaborate mall. The section I chose felt to me like the most representative section of the feeling I had walking around the mall. This section, just past the center of the main mall, included several clean, very upscale stores, benches that allowed people to sit, and wide-open sky lights along the entire ceiling, as this area was above the street level. While walking around the mall, I noticed how bright, clean, and white many of the stores were, and how the fact that everything was at least one floor above street level made everything feel removed from the dirt and business of the city. There were benches and large walking spaces throughout the mall, to encourage pedestrians to roam and rest throughout the mall. Although the mall was very different than the hustle and bustle of Newbury Street, both had several elements in common which allowed them to be major commercial spaces. They both had large storefronts with a lot of windows to encourage shoppers to come into the stores. They both also had visible brand signs over every store entrance, to attract customers. Both also had large walkways for pedestrians, which allowed large crowds to roam around the commercial area. However, Newbury Street was unique in that it was also a place with a lot of vehicular traffic in the streets. The storefronts on Newbury Street were all unique, as they were individual buildings as opposed to one continuous mall. Above each storefront, there were also apartment complexes, which allowed integration of the commercial and residential lives. The entrances to the storefronts were also very interesting, as they were usually either slightly above or below street level, which again allowed the commercial aspect of the stores to be slightly removed from the street. Overall, I feel like I gained an appreciation for the effects of design for commercial spaces.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="49" public="1" featured="0">
    <fileContainer>
      <file fileId="49">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/95895bf1eaec3751f0be7409d1b2d824.png</src>
        <authentication>3b3dedaed9d93f629d3a07095e8c6f21</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="99">
                <text>Drisana Mosaphir</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="100">
                <text>The main focus of this image was centered on finding where I experience the most motion within Harvard Square. Coming to the cross-section facing Mass. Ave. and the Yard from the T station, more specifically from the point of view of someone slightly above (e.g., in one of the stores behind the T station a few floors up) pinpointed the area in which I’ve been able to note, especially as a tour guide, the coming-together of so many people, from the groups who live outside the stores and spend much of their time on the benches in front of Mass Ave’s banks and businesses, to tourists attempting to orient themselves by the visitor center, to students throughout campus, to people commuting in and out of the station. Additionally, the bustle of the square and the openness of this area gave a good backdrop on which to reflect about the gates closing off the houses and the pathway to the Charles River. While campus is largely intertwined with the city, it is also evident through the opening and closing of these gates that the campus can be selective of how much access people get to us, despite the fact that the relationships doesn’t necessarily work in reverse.</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="208" public="1" featured="0">
    <fileContainer>
      <file fileId="301">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/65ce58fd64f36312ab4b49e7bde71f4a.pdf</src>
        <authentication>db69b17def7ee243b47dd4019e37c0d5</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="414">
                <text>Dylan Polachi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="415">
                <text>I sketched the spaces of the square that have played an important role in my experience here at Harvard. Several things stand out to me after reviewing my final sketch. First, I underestimated the size of Dunster House relative to neighboring houses. This was a pattern I noticed over the several sketches that I attempted for my final. Additionally, I inflated the size of the buildings north of the yard. I don’t take many classes there, and the unfamiliarity is likely the reason that the buildings are so large relative to the spaces I know well. I also inflated the size of the green off of Massachusetts Avenue, probably due to this strangeness as well. This exercise is important for understanding how individuals interact with cities. It suggests that we should explore areas of urban environments with which we are unfamiliar. Detailed investigations of these environments would help us create a more accurate mental map of spaces, and help us better understand the communities that we inhabit. Personally, I feel I could better understand Harvard Square and the areas previously unknown to me by simply walking through them and interacting with the people that inhabit them.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="77" public="1" featured="0">
    <fileContainer>
      <file fileId="77">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/5cc1939ca236b130e58cdc3cd5421d49.pdf</src>
        <authentication>f8d9a21ac5023b5046aeaf0dded3ca9e</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="155">
                <text>Dylan Wong</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156">
                <text>Although I initially sought out to draw the most accurate map of Harvard I could by memory, my sketch turned out to be a map of what is important to me in my daily life at Harvard. Most evidently, Harvard Yard is the most accurate part of the map and is displayed larger than scale in comparison to other parts of campus. I live in Harvard Yard and walk through it every time I go somewhere, so I knew the location of all the buildings and even had a reasonably accurate representation of the walking paths within the yard. Besides the yard, my map is filled based on places I go frequently. For example, the entire Harvard Square map was built using my knowledge of where restaurants are. I didn’t know exactly how the streets lined up, but I was able to recreate the city blocks after plotting the various restaurants that I knew. I did not know how to draw any of the upperclassmen houses. I drew the houses in the right order, but I had no idea of the shape of the houses and did not line them up with the city streets whatsoever. In the end, I think my map was exactly what I should have expected when I started drawing. It’s representative of what’s important to me: where I live and where I eat.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
