<?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" accessDate="2026-04-12T11:41:31-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>1</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="221" public="1" featured="0">
    <fileContainer>
      <file fileId="315">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/28c82d65f45716ad3c393c41ea91c12f.pdf</src>
        <authentication>59239662444475d1ce71b6c06153f16b</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="439">
                <text>Stephanie Ying</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="440">
                <text>My sketch is a very geometrically organized sketch of Harvard’s campus, as I thought it would be mentally clearer to represent complex areas and buildings as squares or rectangles. Additionally, my map is focused on and generated through two main benchmarks: major Harvard buildings or landmarks and the streets that cut through the campus and more specifically their directionality. The first of the two is rather simple, as I spatially oriented Harvard landmarks as points of interest because they are structures that are most familiar and frequented for me. However, as I found it rather difficult to properly orient these landmarks, it was helpful to utilize the second benchmark. I visualized my common walks to each of the buildings and how the cars on that street move, which surprisingly helped me in orienting the landmarks in an effective way. As the streets in Cambridge are quite random and also one-way, each one is distinct and memorable in my mind, and I especially thought of which way I turn to see if there are cars before I cross the street to help me orient myself. Thus, overall I think my commute and what I visualize during these walks is what defines and stands out in my sketch. I also started my sketch in the landscape orientation but after trial and error realized that portrait was more suitable. After comparing my sketch to Google maps, my map was more or less accurate in terms of spatial orientation, which surprised me. Although I did make some errors in the directionality of my streets, I think the biggest error was in the placement of the streets themselves, which are extremely intricate and complex. The streets in my sketch were also much simpler than in reality, and I think this difference suggests that we view the city through a less complicated lens in terms of the streets themselves and how we navigate them. When we walk, we don’t think about how much the street curves or how many intersections it has in total. Instead, we are just trying to get to our destination, which is how I oriented my map when thinking about walking to each landmark.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="220" public="1" featured="0">
    <fileContainer>
      <file fileId="313">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/a2cb5eb334bf7505e608a359d0609ac7.JPG</src>
        <authentication>e962b6da0fd5caf371c0dd15728dd5d1</authentication>
      </file>
      <file fileId="314">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/794ec85acb6603b1abdd2438995ad3a2.JPG</src>
        <authentication>2b1bf80eeace53ea86fa890267ee7b9e</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="437">
                <text>Sabrina Yates</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="438">
                <text>Compared to the Google Maps image of Harvard’s campus, I think my depiction of Harvard Yard and the River houses is pretty accurate. I couldn't recall several names of streets, and didn’t accurately capture their curvature. However, I knew the general location and formation of most of the houses. My rendition of the athletic facilities was rather terrible, which I attribute to my general apathy toward college sports. The features of the campus and its surrounding areas that I recalled most readily were the restaurants and churches. I always admire the churches' architectural styles as I pass them, and I eat in restaurants way more frequently than a student with an all-inclusive meal plan ought to. Those are the spaces that, for me, define Harvard Square. I was surprised by how many gates there are at Harvard. We talked in section last week about how Harvard is a very curated space, even the ones considered “public” in legal terms. It makes sense that private spaces like the Yard would be enclosed in gates, but seeing it on paper makes it seem like such an exclusive (or rather selectively inclusive, because the Yard is overflowing with tourists who are willing to spend money on Harvard tours an souvenirs) space. Interestingly, the Quad doesn’t really have gates, presumably because it’s so removed from the rest of Harvard’s campus.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="219" public="1" featured="0">
    <fileContainer>
      <file fileId="312">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/415764908a14a010a8d67e908ccb30e3.jpg</src>
        <authentication>41b15d8a9131fa96ff74f5f230843807</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="435">
                <text>Hayley Wyeth</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="436">
                <text>I’d say my map is fairly accurate, though not at all to scale. The areas of Harvard Square that I know well are quite detailed; I found while doing the assignment that I know almost every building in the four square blocks between the yard and the river. However, I also realized how poorly I know the area between the yard and the Quad (I live in Kirkland and avoid the Quad at all costs) and the athletic complex (I also avoid exercise at all costs). The buildings in the yard are scaled to miniature size, because I couldn’t figure out, even after three tries, how to scale the whole map to fit in the quad and athletic complex while keeping the yard large enough to draw in each of its 20 or so buildings. I found that I knew the Old Yard (surrounded by dorms) far better than I knew the New Yard (surrounded by class buildings), because I mainly take classes in the science center, so I’m not totally sure how Sever and its neighbors fit into the map. I was particularly impressed by my accuracy when sketching Church, Brattle, Mt. Auburn, and Eliot Streets, because they all merge at a pretty strange intersection. I’d attribute this fact to my horrendous attempts at driving in the square and having to circle that area several times before getting onto the correct one-way street. Overall, this assignment taught me that an individual’s experience and knowledge of a city is totally subjective; it’s obvious which parts of Harvard Square I’ve spent time in and which parts I haven’t. Additionally, I learned that I experience urban areas quite locally, in that I don’t really think about areas outside my field of vision — when drawing the map, I could only focus on one block at a time, mentally walking through the immediate area, then moving on, rather than thinking of the Square from a big picture sense. I’d guess that this is probably why the scaling is so off. This was a really fun exercise, though, and I’m looking forward to the next sketch.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="218" public="1" featured="0">
    <fileContainer>
      <file fileId="311">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/5bd8c222d6b8bf19f250378640717a31.jpg</src>
        <authentication>d290ff0eca2584c5775bad2964bef568</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="433">
                <text>Sarah Wu</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="434">
                <text>My initial hypothesis going into this exercise was that I would be able to clearly draw the places that I frequent most. Though this proved mostly true, some familiar spaces were difficult to remember and did not make it onto my map. For example, every week I walk from Leverett House to Pennypacker, cutting through two church parking lots. Neither parking lots are included in my map. I think this may be a function of time – I always walk this route at night, and am walking as quickly as possible. &#13;
&#13;
While working on this map, I realized that how I perceive urban space not only depends on my familiarity with that space, but also on the way I interact with the space. The spaces that I habitually inhabit and do meaningful things in—classrooms, gyms, upperclassman houses, the Crimson and other extracurricular locations, research centers, cafes and restaurants—dominate my map. Areas that I do not know well (i.e. most freshmen dorms, as I lived in the isolated Pennypacker dorm) were difficult to draw and I ended up missing quite a few. &#13;
&#13;
One difference between my map and the one on Google Maps lays in the lengths and shapes of streets. When drawing, I was going off of time (how long it takes me to walk different street sections), but these were not always accurate. I also imagined a grid system, when in reality, the streets are far more irregular. Another key difference is that I tend to think of buildings as squares or rectangles, when many buildings vary in their shapes – this suggests that I envision the built environment more conceptually and focus on function of space rather than architectural details. &#13;
&#13;
I am most surprised by how selective my memory is. Looking at my map, it seems like I ignore much of the retail scene. This makes sense as I do not go shopping much and these spaces are not important to me. The differences in the two maps also reveal that I experience Harvard Square subjectively. My personal experiences and interactions (or lack thereof) with spaces influence how I perceive and portray them.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="217" public="1" featured="0">
    <fileContainer>
      <file fileId="310">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/7d1e591da278df9f4d9ed8ba6e7bc593.JPG</src>
        <authentication>345631fe5991c0dc9ba116ae38e530a2</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="431">
                <text>Bennett Vogt</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="432">
                <text>This assignment certainly posed a unique challenge. It was fascinating to see how my mind is concentrated on the areas that I know best and how to get between them. My high school commute was prominently featured, as transportation hubs featured strongly as did the clearly defined route of the redline. Places where I spend a great deal of time, such as the quad, Adams House, and my laboratory in Northwest Labs were also evident. When I went to add color it was interesting how the most important aspect for me was greenery, which seemed to add some depth and texture to an otherwise soulless map. &#13;
&#13;
For the most part I correctly identified orientation and number of streets in the region, but I failed most to acknowledge the size and complexity of the blocks. Areas that I knew better tended to be smaller with greater detail paradoxically, and those that I did not grew large and incoherent.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="216" public="1" featured="0">
    <fileContainer>
      <file fileId="309">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/c325206506e259ca46ddac9eb6850788.JPG</src>
        <authentication>a6cdb7ce591607ce900a24824473578c</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="429">
                <text>Akshay Verma</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="430">
                <text>Comparing my map to an official campus one, it looks like my sense of where the streets are is a bit off. Before making this map, I walked around campus consciously, taking special note of where streets were in relation to one another so that I could better draw this map from memory. Another shortcoming of my map is its scale; I did not perhaps do the best job in portraying how big and far apart major buildings and parks are when compared to one another. &#13;
&#13;
Aside from this, my map does share general similarities to an “official” map. I used the Charles River as the starting point in making my sketch, which proved helpful in laying everything out. Although the scale might be a bit off, I seem to have gotten correct the general sense of where things are—the Quad, the Law School, Science Center, campus buildings, the River, the athletic fields, the Harvard Art Museums, and other campus buildings. &#13;
&#13;
The two are different largely because my rendition of the map was a reflection of how I walk around Harvard Square and the spaces I use most. When I sketched it out, I found myself marking the places I know best, and then going from there. This “skewed” my map a little because these spaces tended to be bigger and more defined than streets, buildings, and areas I don’t necessarily go to. This was a primary reason why, I think, my sketch is fairly different from the original, and why maps like this that are drawn from memory are inherently subjective representations of physical space. &#13;
&#13;
Apart from spatially mapping different major streets, buildings, and green spaces in my sketch, I also explore the relative density of different areas in the Square. These are represented by the dots. This allowed me to think back to my own experiences on the streets to note where people tend to congregate. Certain places, such as near the T and the Smith Center, are much more densely used than spaces like around JFK Park or between Cambridge Common and the Quad. This was a really fascinating look into how and why people congregate in certain places over others.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="215" public="1" featured="0">
    <fileContainer>
      <file fileId="308">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/a37bd03f8d2ef3a0e11b0816a9bdfb1c.JPG</src>
        <authentication>9f08cf0ad51aa0371fb65c961ae5b2e9</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="427">
                <text>Christopher Ulian</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="428">
                <text>The major issues that I faced with my sketch were scaling and framing. I began with the athletics complex, but the mental diagram I had pictured the athletic facilities as much more prominent than they actually are (although maybe it was just because I began with them that they are so large in my diagram). Because the athletic facilities are so large, I didn't have room to include the quad, even though I never really go to the quad and probably wouldn't have been able to sketch that area of campus accurately. I also didn't get to include much of the yard. Maybe it does make sense that my diagram is centered around Kirkland, where I live and spend most of my time. The central route up Dunster St. is one I take multiple times every day, and so I was able to sketch that part of the square very accurately. Overall, I was surprised by how inaccurate my mental diagram of the square was, and how hard it was to try and sketch accurately the space I inhabit every day.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="214" public="1" featured="0">
    <fileContainer>
      <file fileId="307">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/bdf21bfdd4e385ed93297c3651d56106.pdf</src>
        <authentication>7c052d9eea9140f808e5092284b1cb37</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="425">
                <text>Kaitlin Tse</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="426">
                <text>This process of sketching Harvard’s Map was sketching down the streets that I frequently use first. The athletic complex all the way up to Harvard Square thought JFK street was fairly easy as it were to draw the riverside dorms and Quincy Street. That makes sense because those are the streets that I use to most to travel to class and to the rink. The tricky part was identifying the law school location. All I knew was that it located to the right of the Science Center and left of the Quad. I think I could argue the familiarization of my surroundings reflected in my map – in the case that I use the street or building throughout most of my week or that I can locate among the larger picture of Harvard’s campus.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="213" public="1" featured="0">
    <fileContainer>
      <file fileId="306">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/7e8e052ab77aabc77511aeda84e49d59.jpg</src>
        <authentication>0ebed3c5de4825437cc0e1c67d8f791d</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="423">
                <text>Tomas Spiers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="424">
                <text>Comparing my sketch and an overhead image of Harvard Square on Google Maps, I have several major takeaways. First of all, my general conception of proportion is generally good. The size of Cambridge Common relative to the size of Harvard Yard on my map is pretty accurate. My locations of buildings relative to each other are accurate as well. My main inaccuracies stem from street locations and angles as well as building sizes. I grossly overestimated or underestimated the sizes of some buildings and the orientations of some streets (I also neglected to include a lot of the streets I use daily!). I also neglected the curve of the Charles River in my sketch, which is surprising because I am a rower and on the river frequency. My accuracies and inaccuracies tell me that my conception of space largely comes from my relation to buildings. I start and end my day in Harvard Yard, which is now the focal point of my daily experience, and the accuracy of my map diminishes as I get further and further from my dorm, Stoughton Hall. I think my roads are especially inaccurate because of my strong relation to buildings - I depend on using notable buildings to orient myself rather than using street directions. I found this exercise thought-provoking regarding how I relate to the world around me.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="212" public="1" featured="0">
    <fileContainer>
      <file fileId="305">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/087df0f81365c373ece5e5087da9b68a.pdf</src>
        <authentication>ed29416aa51887f2e2bdb35e6a2c6710</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="421">
                <text>Morgan Spaulding</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="422">
                <text>When thinking about my sketch, I started with Harvard Yard because that seemed like the center of campus to me. As I was drawing, I realized that I tended to group certain things together. For instance, I grouped all of the parallel streets between Mass Ave and Mt. Auburn as a single unit, subdivided into individual streets. I travel down these streets often, so it was easy for me to remember their names. I also thought of the “river houses” as a group. In this case, I could draw the outline of Kirkland house with a lot of specific details because that’s where I live, but I couldn’t think about what Dunster looked like from an aerial view because I don’t know the floor plan of that house as well. When drawing Harvard square, it helped me to think about the locations of specific stores relative to each other. This approach of grouping caused the buildings on my map to be disproportionate. The size of each does not necessarily correspond to relative importance, but is rather the result of stretching and compressing individual blocks of space as I worked out how they related to each other in terms of proximity. Finally, as I compare my sketch to an actual map of Harvard, I realize I forgot to include several buildings. I think this is because I don’t frequent those places as often and blocked them out of my mental map.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
