<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://usworld29.omeka.fas.harvard.edu/items/browse?collection=2&amp;output=omeka-xml" accessDate="2026-04-11T14:40:42-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>1</pageNumber>
      <perPage>10</perPage>
      <totalResults>93</totalResults>
    </pagination>
  </miscellaneousContainer>
  <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="196" public="1" featured="0">
    <fileContainer>
      <file fileId="288">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/3948d3d2fb66831dc518174b06f317ae.JPG</src>
        <authentication>020998d34ba747688e998d36cc5d68cb</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="391">
                <text>Tyler Lott</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="392">
                <text>My first impression was that after looking at a map, the scale of my drawing was a bit off. Some buildings were a bit larger in the sketch than they actually are (Harvard Coop). I think this reflects what locations I've been to most in the Square. &#13;
&#13;
While I do not frequent the various stores (shown by my inaccurate drawing of the places behind Curious George), I spend quite a bit of time at the Coop. So in the sketch the size of the Coop was overestimated. I think the areas we use more often are overrepresented in terms of scale. I drew Straus Hall and Mathews Hall nearly the same size, where in reality Mathews is much larger. I live in Straus Hall, so perhaps that accounts for my size discrepancy. While I would have originally thought that the places people frequent more would be represented more accurately in a sketch, this is not the case for me. I, instead, draw the areas that I visit most frequently larger than than their actual size. Perhaps this oversize of buildings shows the significance of a building in my life.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="195" public="1" featured="0">
    <fileContainer>
      <file fileId="285">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/265b68931ac3fbdfee66218d2e67188e.pdf</src>
        <authentication>32bfb18f2d8ee4a77f43a1cb29fa3679</authentication>
      </file>
      <file fileId="286">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/af50f834959f388d1c133e32010487e3.pdf</src>
        <authentication>fb35da97f00961249aff0a55992c9e38</authentication>
      </file>
      <file fileId="287">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/c03c72c5addf7775dfe768127b79af58.pdf</src>
        <authentication>064e95369eed1c33b8fcf4bfac0bbc1f</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="389">
                <text>Maxwell Lent</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="390">
                <text>In my sketch I realized the huge magnitude of the yard. The ins and outs that I normally walk through sorta paying attention. I remembered where things are that i usually never notice. The crowds of tourists and hungry patrons and where no one goes. The buildings whose shapes are just rectangles in my mind or abstract shapes. &#13;
&#13;
This assignment made me realize just how much of this campus I don't know. Some of my buildings just fade away into a cut off rectangle as i'm unsure of what's next. Or the missing spots, wrong angles, or totally off proportions. It made me realize the difference between day to day living and how a city can be so meticulously planned. One can live here all their life and not notice half the stuff until they take a step back and look at the city from a different perspective. &#13;
&#13;
While drawing this I made sure to focus on the green space. As it is the places I recognize the most, from walking across them to avoid crowds, to enjoying time there during the warmer seasons. They always stand out to me as places to attract people and help out the environment, visual and actual.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="194" public="1" featured="0">
    <fileContainer>
      <file fileId="284">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/eee4593d7a4bd499e5f6d1d11ebda94f.pdf</src>
        <authentication>1bea1a59a15d116cfe00f470eeaa50aa</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="387">
                <text>Tuongvan Le</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="388">
                <text>This drawing was heavily dependent on my personal exposure and time spent in each part of the Harvard&#13;
campus. I realized that drawing the relative positions and paths connecting the buildings were the most&#13;
difficult component. I generally know the direction of the places but sometimes it was hard to remember&#13;
all the buildings on the same streets and where the building is located relative to the entire map in&#13;
progress. I was more confident on the areas where I have had classes (SEAS) and spent lots of time walking&#13;
around (the Yard, the river houses). I also had a hard time drawing the relative sizes of the building&#13;
accurately but rather just drew a generic block to represent each building. This is because I usually just&#13;
walk inside one part of the building but not the entire building so I can’t grasp the entire size of each&#13;
building in my memory. There were also some buildings I remember exist but can’t quite remember the&#13;
names. I remember them because of specific landmarks or activities associated with it such as this is the&#13;
building where there’s a coffee shop or where a lot of my friends go to for labs.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <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="186" public="1" featured="0">
    <fileContainer>
      <file fileId="275">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/18e9434c3a577ea014fac9eb9e52689e.jpg</src>
        <authentication>e3b9c974b7c958e644078799a7d623c9</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="371">
                <text>Jason Goodman</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="372">
                <text>I sketched a few routes that I’ve recently walked, along with landmark buildings that come to mind when I think about neighboring areas. My path is in red, landmarks are blue, and I made the sketch on top of a horizontal black grid to organize my thoughts. &#13;
&#13;
The fact that naturally wanted to use a grid made me realize that my perception of Harvard is in layers of distance from the river—and that most of my navigation is by getting to the right layer before walking “east” or “west” (as I perceive it) to my destination. My layers turned out very accurate in terms of scale and component buildings, though the actual grid is distorted by about 30 degrees above and below the Yard and varies somewhat in layer width. &#13;
&#13;
What was especially inaccurate about my drawing is the size of buildings and their horizontal alignment within the layers. For example, Chipotle is barely west of the Yard, and I botched how the SEAS buildings near the top ﬁt together. I also couldn’t recall most street names (a detail I didn’t attempt to include) and names of businesses around the Yard that I don’t frequent but walk past regularly. These seem like practical details not to know, since they aren’t important to navigation. What matters is getting to the right horizontal layer and walking in the correct direction.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="184" public="1" featured="0">
    <fileContainer>
      <file fileId="272">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/8a428f78605525532a755348c02aa784.jpg</src>
        <authentication>c1fc5b184ef3d3f4b277f3f51947b889</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="368">
                <text>Nate Dempsey</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="180" public="1" featured="0">
    <fileContainer>
      <file fileId="268">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/b9909bcbcfce583e37d8b8de107eb6de.pdf</src>
        <authentication>d996fe2bd1e3ae3b2cb482e56624b24d</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="360">
                <text>Isabella Chiu</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="361">
                <text>I sought to recreate my culinary experience in the Harvard Square area in this map. The eateries are colour coded with green being my strongest recommendation and red being my weakest, while orange is in between. I noticed that I often clustered the eateries by general area but did not place them in the correct precise location (e.g. side of the street, or left/right position relative to neighbours). The ones that were most accurate were the eateries that I frequent the most. I omitted a few eateries that I have either seldom or never visited. &#13;
&#13;
Other elements of the map that were fairly accurate included the buildings I have/have had class in and the streets where I have driven before. There are major gaps beyond the core of Harvard Square, most likely because I quite rarely walk to those regions. Other elements that were mistakenly omitted from the map include small green spaces and plazas around the Harvard Square area. This is most likely because I spend more winter months than summer months on campus and do not often sit outside in those spaces. In the colder weather, it is easy to rush through the outdoors, aiming to get back into the warmth of the indoors as quickly as possible. &#13;
&#13;
Overall, I would conclude that the map is extremely skewed to portray my specific experience of Harvard Square.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="179" public="1" featured="0">
    <fileContainer>
      <file fileId="267">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/c4f437f32466481f6a81c68a4e08cc4a.JPG</src>
        <authentication>81fbec030d81c1289a9a0f43d4367897</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="358">
                <text>Anne Cheng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="359">
                <text>When drawing Harvard’s campus (from Quad to athletic facilities) from memory, I mapped out the common Harvard shuttle routes and differentiated the buildings from undergraduate living spaces, classrooms, and businesses. After looking at my colored sketch from a distance, I realize that I am most familiar with the areas contained within the shuttle routes. I live in the Quad and walk to golf practice very often, so I feel like I have an unusually good sense of these relatively distant parts of campus. After comparing my own sketch to Google Maps, I am most surprised by how little I remember of walkways cutting through the yard and the streets that go through upperclassmen housing. My sketch also reminds me of a somewhat futile representation of Jeffersonian planning, where the Yard is the most central public space and all other surroundings are individual gardens in a somewhat grid-like format. In the vicinity of the Yard are buildings where classes take place, buildings where business occurs, and buildings where upperclassmen can live. It is interesting to see how living, learning, and business spaces all merge together at Massachusetts Avenue. I also found it interesting to find that streets that divide different sections (i.e. living, learning, business) tend to be bigger.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="88" public="1" featured="0">
    <fileContainer>
      <file fileId="88">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/97a4100c1e778c4f106281bb3d6f85e8.JPG</src>
        <authentication>3541a69b9f4b321b8e952412d81746ac</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="177">
                <text>Kelly Zhang</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="178">
                <text>After comparing my sketch to the Google Maps representation of Harvard Square, I realized that my perception of urban spaces is shaped heavily by the amount of time I spend in certain places. As an upperclassman, I spend most of my time in the houses by the river, or in the shops in the square; as a result, I made the size of the houses and stores much larger than the size of Harvard Yard, where the freshmen live. However, in reality, the “width” of both those areas is about the same. I also ignored a lot of the residential areas in the square that I’ve never spent time in because they didn’t occur to me as I imagined the square in my head. &#13;
&#13;
Another striking difference in my map was that I included many more right angles than the city has in reality. For example, because I’m accustomed to assuming ordinary geometric shapes in urban spaces, I drew Cambridge Common park as a rectangle, whereas the real park is a much more round-shaped triangle. I also drew Garden St., the street to the quad, at a right angle to the main street, while it is actually very diagonal in real life.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
