<?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=2&amp;sort_field=added" accessDate="2026-05-01T16:45:06-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>2</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="11" public="1" featured="0">
    <fileContainer>
      <file fileId="11">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/3c4378f3be03e22162391f805ef35350.jpg</src>
        <authentication>1a6fb11e3a8fc85596a737df9f280c3a</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="26">
                <text>Molly Cinnamon</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27">
                <text>I drew the part of Harvard Yard that I frequented most as a Freshman. Immediately, I realized that for having walked through this area so many times, I struggled to remember the names of certain buildings, but just remembered their general shape. I even left out an entier building - Boylston Hall, where I had 2 classes last year! I realized that while the buildings of the yard are very well planned, the paths through the larger areas of the yard are a bit less logical from a bird's eye view. Even as someone walking through the yard, I knew that the paths got me to where I wanted to be, but I wasn't sure how. According to the actual Harvard map, they are even less organized and straight than I anticipated - but still effectively connect the routes and control a build up of congestion. Additionally, I wasn't entirely sure which direction was North, and I wasn't sure how to accurately measure the scale. But I approximated as closely as I could, and I'm curious to see how far off I am. For a place I go so often, this was remarkably difficult to accurately capture on paper!</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="12" public="1" featured="0">
    <fileContainer>
      <file fileId="12">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/92030350be0563c5a3a9e95ae582c735.png</src>
        <authentication>e2a443285b8c2e54540cc756023d1268</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="28">
                <text>Claire Collins</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29">
                <text>Two major things strike me about the official mapping of Harvard square. First and foremost is the level of detail; every path through the yard, every street and alley, every one of the endless engineering and science labs behind the science center is included, along with the names of all these places. The second major thing is the indifference with which it is all presented. The residential neighborhoods to the west of Harvard Yard, the Houses along the river, Cambridge Rindge &amp; Latin are all depicted with the same level of detail, their impact on the place solely relative to the amount of space they take up. In contrast, I could not even attempt the residential streets just off campus, and, for the sake of clarity, I only noted the buildings that I most often visit. &#13;
&#13;
The angle of the river is a little bit off, Mt Auburn Street is a little cut off to the West of JFK, and everything should be oriented a bit more towards to the north east. This last note really speaks to the relativity with which we orient ourselves in space. I know that the yard is north of the river, and thus that Mather to the east, Eliot to the west, but I could not point due north with any particular degree of accuracy.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="13" public="1" featured="0">
    <fileContainer>
      <file fileId="13">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/045ffaac0be61bf84103c8ff51859982.jpg</src>
        <authentication>06f36bf6183a5f6bcb637ccc17231505</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="30">
                <text>Jose Coronado</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="14" public="1" featured="0">
    <fileContainer>
      <file fileId="14">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/d77cacf0cf823f8451b4f8a11c75ebd1.jpg</src>
        <authentication>ef2c9d450da7039404b42416b5aae5ba</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="31">
                <text>Mary Kate Cruise</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32">
                <text>After taking a look at Harvard Square on Google Maps, I think I put together a pretty solid rendering of Harvard Square via memory. The most similar parts are the athletic complex, the river, and the main thoroughfares. I spent a lot of my time at Harvard as a Varsity athlete across the river, so I am very familiar with the lay out over there. Also, I periodically have a car on campus, which I park at the Harvard Business School, so that helped with me that section. I also grew up south of Boston, so I am quite familiar with the main thoroughfare roads, which are a strength of my drawing (JFK St, North Harvard St, Mass Ave, Memorial Drive, Storrow Drive). I’ve been down the river by boat many times and come from a nautical/boating background, so I was confident in drawing the rough shape of the Charles River. The parts that I struggled with were north of the Science Center, west of the yard, and west of JFK Street. I do not venture over to those parts very often, which is reflected in the lack of detail in my sketch. I look forward to better developing my sketching skills as we progress further in the USW 29 class.</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="16" public="1" featured="0">
    <fileContainer>
      <file fileId="16">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/d7cd4cd0b1c4fc777c19a41783a93578.jpg</src>
        <authentication>26fb3ef700016323c9ba20af9d60f42e</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="35">
                <text>Jackie Delmuto</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="17" public="1" featured="0">
    <fileContainer>
      <file fileId="17">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/664cb04a6c2efc9c83d5764093c0d88c.jpeg</src>
        <authentication>01b74c8ecdede8f47dd7b2c4fe317d44</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="36">
                <text>Sonja Eliason</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="37">
                <text>Looking at a map after attempting to sketch Harvard, I realize that Cambridge is not at all the grid system I ended up drawing.  Trying to visualize Cambridge in my mind led to a very organized structure, but looking at a map shows all the curves and edges and somewhat sprawling nature of the city.  Cambridge is definitely not the kind of grid that Jefferson would have designed, but conceptualizing a grid is much easier than the disorganized reality.   Maybe this suggests something about the grid system and its appeal to people’s desire to have an orderly conception of their city, a certain predictability that makes it easier to manage.  Perhaps it also says something about people’s search for patterns and their own perception of a city with which they are familiar.  &#13;
&#13;
I definitely underestimated the size of Harvard Yard and overestimated the size of the park.  It’s possible that my perception of size was affected by the relative importance of certain places in my day-to-day life, or what I prioritized.  The places I had the most trouble visualizing were those that I didn’t frequent or that were unrelated to Harvard.  I knew if specific sections were residential or storefronts, and having that organized within the city was helpful, but if I didn’t frequent the area I had no idea how to conceptualize specifics. &#13;
&#13;
If I were to redo my sketch, I think I would start with making the large geometric centers of Cambridge, and then fill in around them, since that is the way the city appears to be organized.  The Yard is a large square, then there’s the large triangle of the park, and the smaller triangle of Brattle Square.  If I had started with organizing those first, I think I would have had an easier time; my mistake was trying to draw streets and connections without giving myself easy landmarks, so nothing is in correct proportions.  The streets all seem to move out in a fan formation from the intersection of those three major geometric locations, so I could have more easily produced the city from starting at the center and then moving progressively outwards. It’s very difficult to conceptualize a bird’s-eye-view of a city that I am used to seeing only from walking.  &#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="18" public="1" featured="0">
    <fileContainer>
      <file fileId="18">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/71cc4ae44de96e6918ec635b6ad43777.pdf</src>
        <authentication>ecfc1bd3bee0f781fe697e7dacef138e</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="38">
                <text>Tania Fabo</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39">
                <text>For my map, I decided to focus on Harvard as not simply a campus, but rather as a community. I attempted to do this by depicting the various populations that are represented at Harvard: not just the students, faculty, and other Harvard affiliates, but also the Cambridge community residents, the homeless population around Harvard, and the tourists. Harvard has effectively taken over the Square and surrounding areas, from the upperclassman houses all around, to the random affiliate buildings scattered about the Cambridge area. Thus, Harvard has also had to “deal” with the effect of taking over a space. After looking at the map, I believe that Harvard has struck a good balance between being an open campus and an academic institution. There are a number of spaces in which Harvard has allowed/welcomed the presence on non-Harvard affiliates, from the Science Center Plaza as a major tourist site, to the Smith Campus Center as a restaurant hub for local residents, and the Harvard student-run youth homeless shelter. But while Harvard students co-inhabit the space with Cambridge residents, the homeless, and tourists, there is still a degree of safety found in the Harvard-only spaces. Notice how the non-Harvard affiliates are always on the outskirts. Rarely inside any of the buildings, never inside the upperclassman house courtyards. This allows for what one might call “selective interaction”: we can acknowledge your presence when we want to, but at the end of the day, we will always have our own spaces to return to.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="19" public="1" featured="0">
    <fileContainer>
      <file fileId="19">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/fc6f0f0ca871cd6a611ad98ee2a2cdbf.jpg</src>
        <authentication>2f9460d427d1df1eb58480ecd7158021</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="40">
                <text>Al Fernandez</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="41">
                <text>After a couple of drafts in which I made several buildings (namely, Annenberg, the Mac Gym, and Widener) the center of my sketch, I realized that I was having problems with the proportion of the streets. Afterwards, I came to rely on the streets as the most accurate outline for the sketch. The problem with this approach, however, is that Cambridge seems to be a city not really organized by streets. There's no other way to explain the sudden appearance of Oxford Street, the short-lived existence of South Street, and the strange looping shape that Massachusetts Avenue takes. On top of that, I started having problems with accurately representing the slant of the streets, often keeping something straight when the street was, slowly but surely, curving one way or another. &#13;
&#13;
Something that I realized as I was drawing, which was then confirmed when I looked at an actual map, was just how many green spaces there are around campus. Many of these spaces, however, are crowded and jammed in, so that, while you know they are there, they don't really contribute in any significant way to the landscape of the city. I think that, in order for these green spaces to really show up in our perception of a city, they need to border a well-frequented street. Most of Harvard's green spaces, however, seem to be surrounded by either dormitories or lecture halls.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="20" public="1" featured="0">
    <fileContainer>
      <file fileId="20">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/a0f1d871d5892f5b84c3c5f91a4fe3cb.jpg</src>
        <authentication>8bde9827dada9abbe211d1d804f3869e</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="42">
                <text>Nicole Flanary</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="43">
                <text>In completing the assignment, it’s obvious that the areas with which we are most familiar come to us easier and larger than others. As a person that both lives in the Quad and completed the majority of studies in the engineering school, my map shows relatively accurately the walk between the yard and the Quad (down Garden street) in terms of spacing and landmarks but the area below the Square by the river houses and athletic fields, is spaced much too tight and has significantly less detail in terms of known buildings. &#13;
&#13;
It’s also clear in how I distributed space between these two areas, with the walk to the Quad and Porter Square taking up far more space than other parts. I imagine those with close ties to, or with more exposure to, these areas would have the opposite perspective. It’s also interesting in Harvard Square that my map has little detail in the Square – I think that reflects my own perspective of the Square in that it is a litany of shops but I do not really frequent any of them nor could I point out any specific ones and their locations. While I am familiar with the relative locations, orders and lengths somewhat of the streets, the details on these streets are hard for me to conjure from memory.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
