<?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=13&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-02T13:39:47-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>13</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="190" public="1" featured="0">
    <fileContainer>
      <file fileId="279">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/735ad058ff429fe07e3cdd043fe970d6.pdf</src>
        <authentication>46bc46f6ac58178b08f62f29ad6ac91d</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="379">
                <text>Leni Hirsch</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="380">
                <text>went into the exercise quite confident. After all, I don’t use a GPS to get to any destination between the Quad, athletic fields, HLS and the Square. In fact, I know many shortcuts and feel I give decent directions to the many tourists who ask for them. In the end though, I struggled so much I could not truly “complete” my map. I had a great deal of information still in my head that I could not represent spatially. I recognized this was the case when I started to draw Oxford and Kirkland Streets (two streets I rely on to get back to my dorm) and realized that my original placement and angle of the Quad, Yard and Law school were so wrong that drawing the streets between them in a sensible way was not possible. I’ve come to know these streets on foot and by bike by following other people and often times by trial and error. Therefore, I can easily tell you how to get from place to place, but I had never studied a map closely enough to know where one thing is in relation to another. I also learned that I have a very linear perspective of the streets; I know intersections, but not much else. Unless a street is significantly curved, I think of it as straight and therefore, in my sketch, I attempted to make the streets into a grid that does not actually exist. Despite the shortcomings of my map, I was able to depict the direction cars move on each street and if they have bike lanes. This finding makes sense given my life depends on this knowledge on a daily basis. I could also list many of the stores/sites on each street (far more than 10, but I went that far to demonstrate my relative confidence in locating popular shops). Again, in hindsight, this finding makes sense since I’ve learned this area from getting from some Point A to some Point B successfully, without really looking how they are laid out spatially.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="63" public="1" featured="0">
    <fileContainer>
      <file fileId="63">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/14b58555d24192ea6f0a9438f7db5c15.JPG</src>
        <authentication>21fbf3565fb273d2f4e2ab885ef05d90</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="127">
                <text>Liana Spiro</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="128">
                <text>I am a freshman. I barely live here. I’ve seen the Charles River probably five times in my entire life. I couldn’t get to Mather House even if you gave me a compass and directions printed off Google Maps. So this was a difficult exercise for me. My map is not very accurate. There are huge areas of the square that I had trouble transcribing accurately, or remembering at all. Obviously, the blurry areas are those which I occupy infrequently, usually because they house neither food nor friends. I think if I were given a blank layout of the streets of Cambridge, I could fill it in pretty easily. A lot of my confusion arose simply from the bending &amp; diagonals of streets like Bow &amp; Brattle. If Harvard were located in midtown Manhattan, this would have been a piece of cake. I am, however, very sure of the location of CVS. And I know where Thayer is. I live in Thayer.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="148" public="1" featured="0">
    <fileContainer>
      <file fileId="207">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/0528a3003c1888dd8d08fa620865cfc9.jpg</src>
        <authentication>29298e7b6583e27eb89a7c2cdabda56a</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="297">
                <text>Liana Spiro</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="298">
                <text>To me, a juxtaposition of Boston’s Newbury Street and Prudential Center ties in very neatly with the comparisons we’ve been drawing between urban and suburban landscapes. Obviously both sites exist within an urban environment. But the slight variations in the environments and experiences each commercial space offers align extremely well with what I see to be the main distinguishing factors of residential spaces across the nation. &#13;
&#13;
Newbury Street, in the very fact of its existence, highlights spontaneity and change. The first few floors, and often basement, of every building on the strip has clearly been repurposed from an old, residential brownstone into a high-end commercial storefront. Most spaces are relatively small, storefronts are stacked on top of each other; often businesses with very different target demographics share a facade. People are shopping, but adults also stroll leisurely. And I imagine the space above storefronts is still residential. Newbury Street highlights all the qualities people treasure about urban life - the miscellany, the history, the compact spaces, and the charming character. &#13;
&#13;
If Newbury Street emphasizes the city, then the Prudential Center displays everything valued in suburban life. Everything appears to have been planned and built at the same time. Storefronts are clearly thoughtfully organized and placed - useful and practical, but perhaps overly intentional. There aren’t any local, unique boutiques or coffee shops. Everything is a national chain, and everything takes up a lot more space. Teenage girls do the strolling here, perhaps because it feels more enclosed, therefore more safe. There are still plants, but many are species not native to New England. It’s all very practical, functional, and modern. But to me it seems fake. However! The Free People in the Prudential Center has a larger sale section than the Newbury Street location. So that’s a pretty big plus.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="62" public="1" featured="0">
    <fileContainer>
      <file fileId="62">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/67d1e43f091d9cbbf46a6a7e7b47cdb7.jpg</src>
        <authentication>8f5888cbdc5550a22a5d932e4cf95709</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="125">
                <text>Linda Song</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="126">
                <text>My sketch tends to heavily focus on the riverside of Harvard Square. Unlike the actual map, I found that in my sketch I disproportionately scaled the buildings to a bigger size, making the other buildings along the northern end of Harvard difficult to fit. In part, this is due to my natural lack of understanding/experience/exposure to the northern part of the square -- I spend the most time along the river in my house (Leverett), and travel mostly up and down DeWolfe St. to get to and from my classes. The lack of detail I have in between the Quad and the yard is indicative of my lack of understanding of the space between the two either -- my perception is that the Quad exists and is there, but is in a way distanced from the rest of Harvard, as suggested by the abyss of blankness that separates it from the rest of the map. Overall, my map is relatively accurate along the riverside, but anything beyond that falls quickly out of proportion and detail.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="147" public="1" featured="0">
    <fileContainer>
      <file fileId="205">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/06f7fda794eebf730c808e40b26fdbe0.JPG</src>
        <authentication>d9f101bca8bd545074c4f1883099a730</authentication>
      </file>
      <file fileId="206">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/642d53f55cbe5f2ea4b29f9271ee5f07.JPG</src>
        <authentication>a7fcc02ac05165319f0f720cbfb0f972</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="295">
                <text>Linda Song</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="296">
                <text>The theme that I focused on in my sketches and observations was the notion of inside/outside. I found that the two spaces each conveyed a sense of an interior and exterior, blurring the lines between what is actually outside or inside throughout the shopping experience. Upon observations, the distinction between the two became less clear in the Copley/Prudential Shopping Center as indoor gardens or facades gave the illusion that the corridors and hallways were actually exteriors rather than interiors in the shopping complex. In comparison, the interior/exterior dichotomy was much more direct in Newbury Street as the "hallways" of the shopping center were in actuality the sidewalks of the street itself -- the only interior in Newbury was the actual interior of the shops themselves. This resulted in a difference in how people interacted with the spaces as the perception of interior/exterior forced shoppers in Copley/Prudential Shopping Center to be wander more in the stores than loiter in the hallways between them, similar to how the people at Newbury were forced to go into stores if they wanted to sit and rest some place due to a lack of benches on the street. Although I didn't have much of a chance to express it in my sketches, there were many different elements such as flooring or the exteriors of the shops in the shopping center, replicated from outdoor malls such as Newbury, that conveyed this sense more clearly as well.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="197" public="1" featured="0">
    <fileContainer>
      <file fileId="289">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/e3dda8db83494d2c42bd0b7e5a3aca29.jpg</src>
        <authentication>0711dcc0704de08e4a837a7bae0d949a</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="393">
                <text>Lisa Lu</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="394">
                <text>Overall, my map based on purely my memory of Harvard's campus depicted the relative locations of the different parts of campus (e.g. the Quad, the Yard, the SEAS area) accurately, but it was clear from the inaccuracies in the scaling, the location of the roads, and how well I could detail each area which places I frequented most often. As an upperclassmen living in the Quad, I was most familiar with the houses in the Quad along with the SOCH, as well as the shuttle route to the Yard. In actuality, the distance between the Quad and the rest of campus should appear to be longer. Compared to a normal map of campus, I was able to include more details on student commute (usually to class from their dorms), shuttle routes, and small details one might spot on the way from the Quad to class (like the cannons and statues in Cambridge Common), since I'm obviously familiar with those from personal experience. In contrast, my map lacked the details of the campus map in the Yard, the River Houses, and HBS Campus/athletic ﬁelds, and it contained inaccuracies in the roads, likely because I rarely frequent those areas, and I don't drive or go on the roads other than Oxford St. &amp; Mass Ave. This exercise suggests that how we relate to an area is largely determined by our personal experiences and routines in the area as locals/inhabitants, as it's clear that my being an upperclassmen in the Quad as well as an engineering student dictates how I use the space.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="15" public="1" featured="0">
    <fileContainer>
      <file fileId="15">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/e03f3585fec9f43b4f16b8a4f601b4c2.pdf</src>
        <authentication>55c5ec7536fc0a2c32e5c098a0ffaccf</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="33">
                <text>Lucas Cuatrecasas</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34">
                <text>Aside from a predictable prioritization of those features and regions of the Harvard-dominated part of Cambridge that I observe or use most often, my map doesn't seem to stray too far from more standard cartographies (namely, Google Maps). One surprisingly stark discrepancy is in the contour of the Charles, which is dramatically more curvy in Google Maps's aerial view. In my map I've unintentionally smoothed out the river's sinusoid pattern and almost totally elided the deep trough where the bridge from JFK Street to Soldier's Field is. At first, I found this confusing, as I often run along Memorial Drive and know very well that the Cambridge side of the river makes for a shorter run because it's on the inside of these curves. But then I figured that my straightening of the Charles follows a different logic—that of perceiving space as organized around the underlying intentions of one's movements. The river's banks seem straight to me because, running along them, I concentrate on moving toward a point on the horizon, not on the sinuous way I'll get there.&#13;
Another puzzling difference is my collapsing of the fire station near the Science Center plaza with the block directly behind it, a choice which erased the portion of Quicy St. running between them. I bike through this piece of Quincy at least twice a week, so it makes little sense to ignore what is essentially a vital artery for me. This decision, however, seems to be due to some kind of accretive space warping I've applied to the whole area surround this street. Looking closely at my map I see that I've actually shifted Quincy over to where Prescott ought to be (that is, behind the Harvard Art Museums) and made Prescott into an invisible alleyway between CGIS South and the buildings across the street from it, which I've never gone into. I assume that, given the particular way I experience the city, I never give much thought to the block that lies in between the Fire Station and the CGIS complex—this block is actually little more than an inconvenience I must overcome to get to CGIS—and my map demonstrates a passive-aggressive amnesia of this annoying congregation of buildings: they are literally "neither here nor there." These and other slight memory failures that have affected my map seem to all relate less to my daily physical experience of the city (since I do feel the effect of the features I've forgotten) and more to a psychological aversion to remembering that which does not align with my mental network of Cambridge’s important hubs and spokes.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="104" public="1" featured="0">
    <fileContainer>
      <file fileId="120">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/1fb14f28e742f0e93a3d290b56da59b6.jpg</src>
        <authentication>85f41ae379b0e121ba999ead874a69b1</authentication>
      </file>
      <file fileId="121">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/866cdaa44d1f7e9f4a8ea3e8833b9343.jpg</src>
        <authentication>902019c443653c8e3d7c3c0223119114</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="209">
                <text>Lucas Cuatrecasas</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="210">
                <text>I'll admit that I thought what I was going to learn from this assignment was that street-level commerce produces a convivial, integrated atmosphere whereas enclosed galleries make for predictable, contrived shopping—an opposition implying that wholly privatized space isn't fun unless you're buying something. And while the palpable differences between Newbury Street and the Prudential/Copley mall complex do confirm this bias of mine, the reality is a bit more complicated. First, as I've tried to indicate by using arrows in my sketch, both portions of the mall are surprisingly well-designed, allowing for a seamless passage from the street to the galleries, from the galleries into skyscraper-encircled walking spaces, from these spaces into hotels, and so on. This dynamic topography offers an entertainment of its own—kind of like the Chelsea High Line—that the zero-incline linearity of Newbury street can't match. Similarly, the galleries seem to blend public amenities (bad statuary, ample seating) with private capital (the looming skyscrapers and hotel lobbies with “elite” check-ins) in a way that seems admirable, if strained. Don't get me wrong, though: the mall is deeply sinister—it just makes for a pleasant, I. M. Pei-esque walk. &#13;
&#13;
But while the mall adopts this mixed-use ethic to break up its commercial monotony, Newbury Street relies more on the shifting novelty of the street to do so, since even though it's a more organic space, it's still a parade of private interest. As I was trying to figure out how to sketch it, I realized that each section of each block followed nearly the same format: one store on the bottom, one on top, some apartments above that—then repeat with some variation. This, at least, applies to the formally commercial parts. Of course, there's another commerce in Newbury that's not so present in the mall: the economy of people and observing them. As I indicated in the "languages overheard" and "topics of conversation portion of my sketch," people seem to interact more freely and more loudly in Newbury. (In the mall, people seem slightly afraid to drown out the insipid, never-ending softcore jazz they are made to hear.) And while the mall has to advertise its cosmopolitanism—a message board reading Bienvenidos, Bem-Vindos, Willkommen, ようこそ, etc.—Newbury Street can't help but be cosmopolitan. A visitor with no knowledge of the conventions of American commercial spaces might find no aesthetic difference between Newbury and the mall, but she could certainly tell them apart by their sounds.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="175" public="1" featured="0">
    <fileContainer>
      <file fileId="261">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/3352e16e86a11d1e42b9a88247662c0f.jpg</src>
        <authentication>65c0d68dced2c59ec7d129c2c04a2c00</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="350">
                <text>Madeleine Ankhelyi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="351">
                <text>The experience of drawing something by memory was incredibly fun. I realized as soon as I began my drawing what areas of the square mattered most to me by how well I remembered them. I'm an athlete concentrating in biology who lives in Dunster. While my drawing doesn't include most of the academic buildings of Harvard that I frequent, it does feature the athletic facilities and Dunster House prominently. The river stands out to me because of my many runs along it. Road traffic is also a large feature of my drawing, probably because I notice it in my daily life-- a lot of the time spent walking around the square is spent simply dodging cars. All in all, I definitely misplaced some street and buildings, and left out things like foot traffic, or tother higher details, but I think that this drawing is a fairly good representation of the square as it exists in my head.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="29" public="1" featured="0">
    <fileContainer>
      <file fileId="29">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/612cb8240a819ecf2843e28c533b967c.JPG</src>
        <authentication>2fb076811ae6b0e8f1b5a21786e24ad7</authentication>
      </file>
    </fileContainer>
    <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="59">
                <text>Maeve Hoffstot</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="60">
                <text>Drawing this was a really interesting assignment as I tried to fit onto an 8”x11” piece of paper everything in the square that was important to me. I started with the two places that are most central to my life—Weld Boathouse and Cabot House (the Quad). From there, I added the main roads and intersections. Streets were definitely the easiest way to orient myself. As a result of including both the quad and the river, as well as making aspects of the square and yard visible, I had to distort the proportions a bit. Proportions and relations were definitely the hardest aspect. Memory of the square was pretty natural, as I just started with the places I frequent the most and added in surrounding objects. Lots of the emphasis on my map is because of my daily routine. For instance, I included the shuttle stops for the shuttles that run to and from the quad—something that many Harvard students never have to consider. The Radcliffe Yard, which is on my quad-route when I decide to walk to the river, or the Cambridge Common when I’m heading to the Science Center. Harvard Yard proved surprisingly challenging. It was less easy to regulate, as there are no roads that dictate blocks or relatives sizes, and my memory was much foggier as the Yard doesn’t factor too much into my everyday junior life. Looking at a map of the square afterwards, I think the think I did the poorest job representing was the bottom right corner of my map—Leverett, Dunster, Mather and Adams. I spend much less time in the area so I got a little messed up in the placements of the buildings. On a whole, however, Harvard was pretty easy to map out and I probably ought to credit a good part of my success (despite my drawing ability) to the fact that I’m a tour guide for the admissions office.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
