<?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=16&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-02T13:39:54-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>16</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="74" public="1" featured="0">
    <fileContainer>
      <file fileId="74">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/9d74d3ba129c14b25c85116769165a72.jpg</src>
        <authentication>f18952c6e9096be07e6860c6172ea7d3</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="149">
                <text>Oriana Wang</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="150">
                <text>In my sketch, I aimed to draw an accurate representation of the heart of Harvard square, slightly off center from the main T stop, so that I could include the Yard in greater proportion. Overlaid on top of the physical layout of the buildings, shuttle stops, and pathways, I drew a time-signifying color coded map. In the morning, orange highlights my commute from the Quad to the Square and Yard area for classes and meetings. Afternoons perhaps have the widest range, with paths to the bank and other stops for errands, lunch spots, and sometimes the Harvard Book Store. Evenings in purple display the habit of my life after 5pm, which is either heading to the shuttle stops to go home, or to various spots such as JP Licks for ice cream with friends, Dumpling House off the map for dinner, or to the River and back, depending on my schedule for the day.&#13;
&#13;
 I had the most difficulty with trying to accurately portray the relationships between different spots I knew well. The actual geometry of the Square, which I walk through multiple times a day, was embarrassingly difficult to draw, and I needed to piece together a quick rough draft after many erasures. Other details have been blatantly omitted, such as the many streets that are perpendicular to Mass Ave, since they all seem to blend together with their similar brick cobblestones and shops lining the sidewalk, although the assortment may vary. My sketch was generally accurate, but featured more heavily seemed to be places to study and to eat, since that symbolizes two of my priorities at Harvard. Both locations of classrooms, and food establishments where I meet friends and catch up and reflect on this period of our lives spent studying highlight the beginning and ends of the arrows I drew for my movements throughout different times of day.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="159" public="1" featured="0">
    <fileContainer>
      <file fileId="230">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/846f8fa44f273dd8c53506a7988651d1.jpg</src>
        <authentication>a1a323a236ef07a7471b3327248ce017</authentication>
      </file>
      <file fileId="231">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/965b37775105c951ab15b3b04c0ddcaa.jpg</src>
        <authentication>7fe7ea07cef49506281f35e047618e8f</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="319">
                <text>Oriana Wang</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="320">
                <text>To sketch Copley Place/Prudential Center Malls and Newbury St., I first stopped by Newbury St. since it was earlier in the morning and the shops at the mall were not open yet. At Newbury St., it was extremely easy to navigate to, just one block away from the Copley T Stop. The shops along Newbury St were renting out of larger buildings, the 2nd, 3rd, and 4th floor of which were being used for residences or offices and were rather nondescript. However, the street level and basement level were much more aesthetic, with pretty shop windows, outdoor tables and seating, and the promise of finding something unique and wonderful. The modern glass storefronts were contrasted with the old brick buildings and the narrow one-way street, which at 8am was already left with no free parking spots. Parking meters, bike racks, and wide sidewalks allowed the normal heavy foot traffic during the busy times to influx into this elongated shopping area. Planters separated sidewalks from store fronts, basements were finished and sometimes housed fancy restaurants, and trash cans lined the streets. There were signs for sales, for real estate properties, for streets, and for city events, all to attract customers to individual stores, which seemed to be competing with one another for your attention. Although filled with its fair share of luxury stores, Newbury St. still seemed grounded as it had to face traffic and parking issues, inconsistent weather, city dwellers by the masses, and the unpredictable inevitability of change as stores would pop up or go out of business.&#13;
&#13;
However, when I walked to Copley Place, the busy yet mundane daily car traffic of the streets gave way to an overload of consumerism as I entered the glass doors through the handicapped non-revolving entrance (which had been propped open). It was much more modern, and far more self-contained, as if you had stepped into a glass capsule. Inviting at first due to the chilly air outside, I soon realized it all felt too perfectly controlled. Centralized store directories coordinated with signs everywhere to direct shoppers. Though necessary and convenient, they were all directed towards making it easier and more enjoyable to spend your money. Colors, logos, marble, gold trim, and luxury abounded at Copley Place. Through the skybridge, you could see an advertisement for Harvard Summer School while peering down at the traffic of the city and the honking. Then you could look up to see the other skyscrapers, impenetrable to the gaze with their reflective glass exteriors (to be fair, I am a fan of the modern glass aesthetic in large part, but it was odd and counterintuitive to be in one glass building looking out the crystal clear windows and unable to visually enter another skyscraper made of the same material).&#13;
&#13;
Prudential Center was similar, although slightly geared towards the middle class consumer as opposed to the luxury consumer. Advertisements were everywhere, marked exits were through department stores, benches provided some minimal seating in the center aisles, and it was easy to get lost in the maze of stores. I had a far harder time navigating my way around the mall trying to sketch. Linearity was broken. As for security, I was stopped and turned away at the 3rd floor of Copley Place, the boundary between shops and businesses. I was also questioned by a security guard as I stopped to write in a notebook and take pictures of some store fronts. Yet at Newbury St., I felt free to roam as I pleased, finding a welcoming city neighborhood as opposed to a patronizing conglomerate mall. Interestingly enough, I had never been so opposed to indoor shopping malls, and their design and implementation, until I was forced to take notice of everything through sketching. I will praise their convenience and centrality, but would much rather stroll along a street with charm and character.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="6" public="1" featured="0">
    <fileContainer>
      <file fileId="6">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/59a4bce4e716b3c7924fd31f5dce2ef7.JPG</src>
        <authentication>809afd2e9750d20d6c54fb9a510f9e64</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="16">
                <text>Owen Borges</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17">
                <text>For this assignment I chose to draw a plan of the pathways from my dorm, Greenough, to the yard. I walk this pathway multiple times each day, and it is an integral yet monotonous part of my routine. I thought that my familiarity with this area would grant me an advantage in attempting to map it from memory. In comparing my drawing with an actual map, it is clear that my only familiarity with this space is in transit. I realized in drawing the space that I have never stopped to simply observe or take in the space, and I have never been in any of the buildings on this route. I think it is because of this that my drawing gets most of the paths correct; however there are many details missing and the proportions are largely incorrect. It is also worth noting that I placed almost all of the trees and hedges correctly. I think this shows that there are certain aspects of transit- focused spaces which we begin to focus on, perhaps because they are the beautifying aspects of these spaces, the aspects which bring some life and happiness to these spaces.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="95" public="1" featured="0">
    <fileContainer>
      <file fileId="102">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/b9533ceffe8b96b485307a6c837810f4.JPG</src>
        <authentication>bedf8825cf8bec64f19a0bc1997dbe78</authentication>
      </file>
      <file fileId="103">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/e7cbb90de16561ffcd3971497ffa8600.JPG</src>
        <authentication>636b789abefe0576ed5a20f5ffaf58b7</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="191">
                <text>Owen Borges</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="192">
                <text>I visited Newbury Street before I visited the malls and was immediately intrigued by its spatial feel. It feels very wide and light in comparison to most streets so I attempted to do a sketch that would capture that essence in some way. I decided that the best way to organize my sketch was by height, because I believe that this street’s width in combination with its relatively low height. I was also interested in the way that people move through this space, in a generally linear fashion down one side of the street, entering stores of interest. &#13;
&#13;
Upon going to Copley Place mall, I realized that the large, two story corridor was constructed using many of the same principles. It provides for a large amount of open space between the stores and people move about the space in roughly the same way. That is, it is a sort of promenade that forces people to walk past all of the shops to get to the one they want to find. The Shopping spaces are both linear, seemingly designed to maximize the amount of interface a shopper has with the storefronts they are passing. The wide open spacing and large amount of natural lighting also make these shopping spaces much more enjoyable. The mall also has less seating options than Newbury Street, making it ultimately a very dynamic place. While one can either promenade or sit and enjoy the space on Newbury Street, they are almost forced into shopping by the very construction of the mall.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="206" public="1" featured="0">
    <fileContainer>
      <file fileId="299">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/8bff8c5c1c488fc1495a7c9c4724bda1.jpg</src>
        <authentication>3e056f9068a7e0c6985c709c5fc06e52</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="410">
                <text>Patrick Pan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="411">
                <text>My initial reaction upon comparing my map was honestly accuracy -- everything in terms of streets and intersections is mostly accurate between the River Houses and the Science Center, with the exceptions of having 1 fewer street between Mass Ave and Mt. Auburn St. and forgetting Bow St., near Mt. Auburn. What I had in accuracy for streets I definitely did not have for specific buildings, other than Harvard dorms. I could quite accurately depict most of the shapes of the houses and position of the first-year dorms, once I thought about it.&#13;
&#13;
One thing that occurred to me as I was drawing was that much of my knowledge came from times when I biked around the area, because vehicular transportation -- even by bicycle -- transports you quickly enough to expose the patterns of streets and intersections quickly enough to be remembered and mentally connected. Places where I could not or did not bike are almost invariably hazier. &#13;
&#13;
I think it is partially for this reason that the grid system, for example, is a construct with many American cities, where vehicular transport is an assumption, since pedestrians can wayfind without a grid but it is more heavily perceived by those in vehicles.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="38" public="1" featured="0">
    <fileContainer>
      <file fileId="38">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/d47853061090cc7b0685044aed727107.pdf</src>
        <authentication>cf23bd28dce984ffedf589536b663e37</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="77">
                <text>Pearly Kim</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="78">
                <text>Compared to the actual map, the relative positions of the buildings and sites I labeled on the map are close to being accurate, but the scales and relative sizes are quite off. The most notable differences are the relative sizes of different blocks, roads, and buildings. Other key differences are the shapes of buildings and the curvature and presence of roads. These inaccuracies were expected because I am usually a destination oriented person—I only pay attention to WHERE I’m going, and thus do not put much effort to remembering either the pathway or the shape and size of the destination. In addition, I am not a driver, and this makes my memory of Harvard very pedestrian-centered. I am not as aware of where the roads end, at what angle they intersect, or how they curve. During this assignment, I recalled the roads by remembering where I had to cross them. Another interesting discovery I made is that it was harder to recall the academic side of campus compared to Harvard Square. Hurrying in between classes seems to be more detrimental in establishing a mental map than leisurely walking to my favorite restaurant. From these observations, it can be concluded that how we use and relate to a city determines how we interpret and remember the city. I, as a student and pedestrian, have a focus on pedestrian paths, academic buildings, public transportations and food. These are the parts of the city that I expose myself to, and as a result, is what consists of my personalized experience of Harvard.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="124" public="1" featured="0">
    <fileContainer>
      <file fileId="158">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/2a3f6bf9dfe69dfbc8824e221c100f80.pdf</src>
        <authentication>0bb9525e776329720b4b85f2af145d69</authentication>
      </file>
      <file fileId="159">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/4ef74e52aeec02f257d7b9e506d1529c.pdf</src>
        <authentication>324e802855b2f1b6906ee123a6673ff1</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="249">
                <text>Pearly Kim</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="250">
                <text>Copley, Prudential Center, and Newbury Street are all popular commercial spaces in close proximity. However, by virtue of some being an indoors shopping space and the other being an outdoor shopping space, the problems each commercial space have to address and the images they try portray to the customers are different. The Copley and Prudential Center malls are obviously separate buildings, but the general theme that prevails throughout is shared. First, the shopping areas of Copley and Prudential are within an enclosed building; there is even an enclosed walkway connecting Copley to Prudential Center. However, despite its limiting nature as an enclosed space, these two shopping centers make every effort to convince the customers otherwise: that the shopping center is open and “infinite” in space. To start off with the most obvious, both buildings have large entrances, wide corridors, long hallways, and high ceilings to emphasize the magnitude of space inside the building. There are often openings in between different floors that further the effect of high ceilings. However, the key element for this illusion of infinite space is windows, especially those as ceilings. By allowing a view of the blue sky from above, the building takes the vertical expansion to the next level; its limit only being the sky. The enclosed shopping spaces want to keep the customers inside for as long as possible because the longer they stay, the more they spend. In order to do that, they must make sure that their customers do not feel confined or restricted inside. &#13;
&#13;
Newbury Street is also a commercial space, as it is clearly shown through a similar emphasis on item displays and shop names, along with the side-by-side layout of shops that makes it convenient for the customers. But in Newbury Street, efforts to keep the customers by making the space look open are useless: it IS already in open space. In fact, it is even unclear where Newbury Street starts and ends, and the street is just a part of the surrounding city—if there is no definite barrier, it is impossible to try to keep people inside it. Therefore mobility along Newbury Street seems greater than that of the shopping malls, giving a more bustling feeling with greater variety of crowd: parents with strollers, people walking the dog and so on. This lively feeling is juxtaposed with the small red-brick buildings along either side of Newbury Street, each holding its own shops while making sure that the buildings are not too tall to block the view to the blue sky. This earthy color in Newbury Street creates a friendlier atmosphere. &#13;
&#13;
In contrast, Copley and Prudential Center maintain a “high-end” look of elegance and classicism with the use of light and color. Windows not only help create the illusion of expanding space, but also let in lots of natural light. This natural light works along with artificial lighting ubiquitously present inside to illuminate the whole complex, particularly the products on display and the brand names of each shop—the two most attention-requiring objects for high sales number. But sales, although important, is not the only aspect light plays into. The brightness across the entire shopping complex adds to the glamour of malls, giving it the prestigious look. In addition, setting aside the colors of each shop, the overall interior of the buildings are white. White, a color symbolic of classism, makes the building look clean and graceful.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4" public="1" featured="0">
    <fileContainer>
      <file fileId="4">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/da83e2fa9cb08be787c6e81873c6b88c.jpg</src>
        <authentication>0bfc3defa55da37a67ac2cd0f94d76d3</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="12">
                <text>In my sketch, I attempted a bird’s-eye view of the Harvard campus from the Harvard Law School to the athletic facilities across the river. Being a second-semester freshman, I was fairly confident with my judgment of the Yard, the Science Center Plaza, and the general area around Mass Ave and Harvard Square. However, I have little more than rudimentary knowledge about locations and streets that I am not required to visit often; areas such as the River houses, the Quad, the athletic facilities across the Charles, and the Law School are not quite on my radar. A comparison of my sketch to a map confirmed these suspicions that my drawing was accurate in some places and less accurate in others. For me, I believe my sketch suggests that I relate to the city as an area of both work and living. As a college student, I essentially work where I live. Thus, I’m more aware of the area around where I both work and live – that is, around the Yard and Science Center Plaza. On the other hand, my lack of knowledge about other areas shows that I do not appreciate the parts of the city where I do not either work or live. So, as opposed to viewing the city in an exploratory manner (as perhaps a tourist would), I view it as both a workplace and an abode.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="13">
                <text>Peter Bearse</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="93" public="1" featured="0">
    <fileContainer>
      <file fileId="97">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/4323efa67ff23987711e41d7f94743c3.jpg</src>
        <authentication>701c3843531d5b8ceaf593427950ea08</authentication>
      </file>
      <file fileId="98">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/4f9ee9edb8bda72b6a254e8fa32b1e6e.jpg</src>
        <authentication>021b9b6e77d446d58679d6315e9dab12</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="187">
                <text>Peter Bearse</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="188">
                <text>In these sketches, I compared the area of Newbury Street with the area of Copley Square and the Prudential Center, focusing on the usage of space and materials in each location and how those particular usages affected each environment differently. Walking through Newbury Street felt similar to walking through a residential, village-like neighborhood. More than anything else, the space achieved great uniformity throughout its layout; the buildings were all evenly spaced and made of red brick, and hardly would have been distinguishable as commercial shops without the modest signage on the structures. Natural elements such as trees and plants were smoothly transitioned throughout the pavement walkways, and casual outdoor dining areas were present along the walkways. I attempted to represent this leisurely, uniform design of Newbury Street with the symmetrical and uncongested style of my sketch. &#13;
&#13;
The shopping mall, however, resembled more of an opulent mansion than a casual, residential setting. Upon entering, the smooth marble composition of the architecture and the presence of flowing water, brush, and other natural elements immediately set a rich and vibrant tone. The space contained seemingly endless twists and turns, with each pathway bombarded by glamorous, attention-grabbing advertisements for various shops and restaurants. The space also created a peculiar combination of flashy interior design and natural, earthy landscape – Copley Place had a large waterfall on its third floor, and the Prudential Center had a small park in its midst. I attempted to represent the busy and multifaceted design of the malls with the colorful, packed, and distracting style of my sketch.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="50" public="1" featured="0">
    <fileContainer>
      <file fileId="50">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/64ba4c7601ee2d29157d2d8077350c6a.JPG</src>
        <authentication>323c3e12ab4649c1e28862baa4b0eb10</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="101">
                <text>Quinn Mulholland</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="102">
                <text>I was surprised by how accurate my depiction of Harvard Yard and the&#13;
upperclassmen houses along the river was. I have a lot of familiarity with that area,&#13;
having lived in the Yard last year and spending a lot of time in the Kennedy School&#13;
or visiting friends in river houses. I think my map emphasizes roads almost as&#13;
prominently as buildings, which makes sense because I bike almost everywhere&#13;
(since I live in the Quad), so I have to navigate those roads everyday. I made the&#13;
roads that I bike on a lot, like Garden Street, Mass Ave, Mt. Auburn, and Brattle&#13;
Street bigger, because I’m more familiar with them. My depiction of other locations,&#13;
however, like buildings north of the Yard or east of Quincy Street, was less accurate,&#13;
probably because I spend less time in those locations. Something that surprised me&#13;
was that I completely forgot about some streets, even in parts of campus that I see&#13;
everyday, because I rarely go down them. I also severely underestimated the&#13;
distance between the Quad and the Yard, probably because I travel that distance&#13;
everyday. Additionally, I completely forgot about some of the freshman dorms in the&#13;
Yard—because I rarely went in them, but made my own dorm, Canaday, much larger&#13;
and more prominent than it really is.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
