<?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?output=omeka-xml&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-10T23:41:44-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>1</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="52" public="1" featured="0">
    <fileContainer>
      <file fileId="52">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/5cdf34b27891e1f1aea7a706135cf7cd.pdf</src>
        <authentication>31e087c33d7503595d3a69f59ec0fc76</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="105">
                <text>Adam Oh</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="106">
                <text>After having finished my sketch, I compared what I drew with some of the Google map renderings and realized a significant difference. Where I decided to notate things so that it was easier for me to draw, google maps shows much more detail. However, I have decided to include topological features to my map showing where there are slopes in the streets and the places most traveled by pedestrians and students. Google maps fails to include these features because their rendering is much more informational. Similarly, both my sketch and Google maps include the directionality of the traffic which I found to be pretty cool. The difference in both renderings could be due to the humans’ tendency to remember things based on landmarks. When I was drawing, I constantly tried to relate things to certain landmarks that I remembered seeing as I was walking. I also associated certain locations to certain memories so my renderings include much more of what I perceived as I walked through the square. In the end, our renderings achieve the same goal of showing the idea of what the square looks like, but they are represented in different perspectives.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="138" public="1" featured="0">
    <fileContainer>
      <file fileId="187">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/0446ede2e18fb2d2570e74438bab5a99.jpg</src>
        <authentication>b2efd2806c1e1193af5d083d256ae1fc</authentication>
      </file>
      <file fileId="188">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/1d98bf42230ccb5b354155bda5ddc4a2.jpg</src>
        <authentication>f005cddcf8a3d9129b668bbd60777212</authentication>
      </file>
    </fileContainer>
    <collection collectionId="3">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="3">
                  <text>Sketch 2</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="277">
                <text>Adam Oh</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="278">
                <text>Having visited both Newbury and Copley/Prudential shopping centers, I was most surprised by the difference of the vibes that these two places gave. In the Newbury’s shops/street, we notice that it has a more homey feeling due to the linear building of shops. All of the shops are accessible on the first floor whether. Another difference of the newbury shops that I found interesting was the outside sitting spaces provided by each of the shops. There were tiny patios made of brick which also made the viewer feel more comfortable because of the familiar brick structure. Along the top of the shops were residential buildings which contributed to the more at home feel. The wider streets also gave a feeling of openness and the natural light from the outside really made the shops on newbury more attractive and feel very homogeneous. Upon entry into Newbury St., you feel like you have entered a residential neighborhood rather than a commercial district. However, the owners of stores replicate the feeling of a commercial district by providing signs for their stores that really pop at you. The shops at Prudential had some similar things as Newbury such as the incorporation of natural lighting and lots of plants. I noticed that there were a lot of windows that let natural light flow through along with attempted greenery with artificial plants. However, one thing that really stuck out as a difference was the starkness of the shopping mall. The choice of white along with the narrow corridors and lack of sitting spaces made everything very “in your face”. The mall also felt very disjointed with very a different feeling as you step into a different part of the mall. Another theme that I noticed was that the mall was very vertically structured whereas the newbury shops were horizontal. This vertical architecture gave off a sense of grandeur and an elitist aura. The last difference that stuck out was the quality of stores in each location. While Newbury had more stores that were for the everyday customer such as smoke shops, convenience stores, etc., the shops at prudential were more high end clothing and accessory stores.</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="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="108" public="1" featured="0">
    <fileContainer>
      <file fileId="128">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/fe8f378ecdbbcb58f9b3f713570dc0f3.pdf</src>
        <authentication>d0f5b332f28364dc8cc3ccecd3412aa7</authentication>
      </file>
      <file fileId="129">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/052bacb49f49c8b6fdf6f439f3e40755.pdf</src>
        <authentication>8f8ec3b5d588b0c99d1b9da5d5d402eb</authentication>
      </file>
    </fileContainer>
    <collection collectionId="3">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="3">
                  <text>Sketch 2</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="217">
                <text>Al Fernandez</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="218">
                <text>When thinking about the Prudential/Copley commercial center, the connecting hallways are the first features that come to mind. Although these paths do have stores off to their sides, they seem to be constructed, primarily, with the express purpose of keeping people moving. I came to realize how difficult it is for someone to turn around in the middle of one of these pathways and go back where they came from. What keeps people moving forward, I think, is the hope of a larger space, of more breathing room. And some of these spaces are either open atriums where people can sit down (in the case of Copley, with green spaces and even a small fountain) or larger, more brand-name stores or restaurants that encourage people to stick around for longer. &#13;
&#13;
I also really paid attention to empty spaces at the shopping centers, so much so that it made it the center of my sketch. Malls, at least to me, never seem to be fully completed—there’s always another further stage of development. This means that there are sections of the shopping centers that are almost completely deserted, even if there are stores lining up the paths. In Newbury Street, I noticed how one side of the street was under construction, leaving the other one looking, for the most part, untouched. It also seemed to me that the more commercial side of the street—the right-hand side, as portrayed in my map, seemed to have many more stores, while the left-hand side seems to be more residential in nature, even if there are stores at the ground and first levels.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="177" public="1" featured="0">
    <fileContainer>
      <file fileId="263">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/1c87a939512f6d573ef1aa5002f3c0c8.jpg</src>
        <authentication>c90252fcdd74c21c969615fcc9fe505a</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="354">
                <text>Alex Afeyan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="355">
                <text>My map is quite accurate with regards to the buildings of the Yard, and relatively accurate with respect to the river house area of campus. However, it fell fall short of proportions on the location of the Quad. I was not familiar with the path to the Quad, as I do not spend a lot of time there. In addition, there were many paths in the Yard that I was not familiar with, as they are relatively randomly laid out. The shapes of the common spaces and houses by the river were also not clear in my memory, so I had to guess about a few of them. There was a large area West of the Yard the shape of which I had no idea, but none of it is part of the campus proper. Finally, the campus of the Law School and the Science Labs extends far North of where I drew, but I have not interacted with that part of campus yet. I am very familiar with the shape of the river and the bridges of the river because I have rowed on it, which helped me draw that part of campus.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="39" public="1" featured="0">
    <fileContainer>
      <file fileId="39">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/ebd460f4c9e9768aa5437a7d5356ad67.jpg</src>
        <authentication>f516144f942068f3a107caf83db81c4b</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="79">
                <text>Alma Lafler</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="80">
                <text>My map is accurate enough that it could help a tourist get around the included parts of town with little trouble. I commute around campus by bicycle and am very familiar with the road network around Harvard, which would likely make it different from a map drawn by someone who, for example, takes the bus and doesn’t need to pay attention to the roads between their origin and their destination. On top of this, I grew up in Cambridge, and was able to bring other personal landmarks to mind when I was thinking about the shape of the campus. &#13;
&#13;
I found that it was easiest to produce a more accurate representation of areas I couldn’t initially remember by envisioning myself on the street in a familiar area, and then imagining myself moving to the misremembered area. The shape and elements in the map are noticeably more accurate in the places I spend a lot of time or travel through every day than in the areas I only go occasionally. Interestingly, there are some buildings that extend back much farther from the street than I drew, which I didn’t realize because I have not been in them, and have only seen them from the street. &#13;
&#13;
I drew my map such that you could draw grid-like lines going North-South and East-West along the major roads, but in reality, Cambridge appears “tilted” to the northeast – something I knew but didn’t feel comfortable enough to accurately incorporate. I hadn’t thought this about much before, but the city seems to be aligned with the orientation of the river rather than the cardinal directions, which suggests to me that perhaps Cambridge was originally settled along the Charles, with homes slowly radiating out from that boundary.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="125" public="1" featured="0">
    <fileContainer>
      <file fileId="160">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/7e12558ae6364f602cbafd665a21553c.pdf</src>
        <authentication>2258d06ed01c2053a198d0776d56d819</authentication>
      </file>
      <file fileId="161">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/a52fa88c3ed9f43bb7352ea7cd1dece3.pdf</src>
        <authentication>09ddd2578772de8ae5bd169361ea582f</authentication>
      </file>
    </fileContainer>
    <collection collectionId="3">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="3">
                  <text>Sketch 2</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="251">
                <text>Alma Lafler</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="252">
                <text>Both the Prudential Center and Newbury street are commercial shopping areas, but they differ in that the Prudential could conceivably be modeled on a central meeting place with radiating streets in a town, whereas Newbury street harkens to the main street in a such a place. &#13;
&#13;
The brownstones in which stores are housed almost like homes; however, the purpose of Newbury Street – to window shop – is clearly demonstrated by its design. The leafless young trees lining the sidewalk are strung with holiday lights, likely intended to create an inviting atmosphere for nighttime shoppers. There is no place along the street to do anything more than pause to tie a shoe, as there are few benches and no common areas. Stores on Newbury Street are also likely subject to local business association rules – the scarcity of lit-up signs is noteworthy. The business association likely pays or lobbies for attentive cleaning and police patrol, for it has far less litter than all of the nearby avenues (even with thousands passing through hourly), and there are no street performers – or homeless people – in sight. &#13;
&#13;
Copley and the Prudential, in contrast, each have a central common area, from which the various arcades radiate. Many people sit in this area for a break between stores, as along the arcades, people are in constant motion, just like on Newbury Street. An interesting difference between the two types of space is that because the indoor malls are contained, delimited entities, it is clear where the shopping area begins and ends. In addition, all of the doors are open, allowing for a comparably lower barrier for entry (after you have gained entry to the mall itself, of course – also restricted, by security near the doors, from “undesirable” parties).</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="211" public="1" featured="0">
    <fileContainer>
      <file fileId="304">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/000671d6971b6474d590510cc47a8847.jpg</src>
        <authentication>4b93c4f99c085a7a53e5b05c4c9b63f8</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="419">
                <text>Andrew Soldini</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="420">
                <text>The sketch that I made was for the most part accurate in the depiction of known regions yet struggled on its representation of places not usually traveled. For example, the yard is represented fairly accurately down to the walking paths yet the law school shows very little accuracy to what is actually there. I also did not do a very good job of encompassing the full size of the places I have less knowledge of. There are missing regions and buildings. The exact alignment of streets with landmarks was a difficult task where there were a few misaligned areas due to making structures larger than they are proportionally in real life. It showed that I relate to the city in a very practical way. The stores I go to and the buildings I walk around and go into are the ones that I remember. The irregular shape of some buildings also provides a challenge to the fixed grid notions of uniformity that are easier to imagine and work with. Many times I had to go back and add the interesting features such as the road splitting where the Lampoon building is. It was also true that the buildings that are more prominent in my own life were disproportionately larger on my map, another sign of implicit bias toward the self in the mind’s eye.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="201" public="1" featured="0">
    <fileContainer>
      <file fileId="293">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/684983e943a3068d1ef23e8e63c41bf5.jpg</src>
        <authentication>26a29b886f33ab3d45a5ecb291104025</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="401">
                <text>Anja Moser</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="402">
                <text>Comparing the sketch I drew from memory for this assignment to a map I bought when I arrived here in Cambridge three weeks ago, it stroke me that there were vast areas on the campus and in the city I did not know – let alone how they looked like. Whereas I was able to measure distances quite accurately - I believe this is thanks to my daily commute either on my bicycle or by foot - I was not able to sketch a “complete” map of Harvard Square and surrounding. Rather, I realized that my sketch only features the environment I interact with on a daily basis such as the buildings I have courses in, my local bakery or green spaces I use to go for a run – short, the sketch only featured what is important for me as an individual to be able to interact with the city and to get around in it. &#13;
&#13;
Furthermore, in contrast to the map I bought, I structured my sketch in commercial, residential and green areas – again a help for me to get around. Whereas the map only showed streets and houses and made no distinctions between different uses of the buildings and streets, my sketch allowed me to locate shops, private homes or University property and even bike lanes on the streets. &#13;
&#13;
In my opinion these differences between my sketch and the map stem from the following reasoning: maps are a highly simplified reflection of reality. By reducing complexity to one specific layer of a city – such as the street system and adjacent housing in the example of the map I bought – they allow their users to be able to orient themselves and find what they are looking for. However in order to be able to do so maps only show one aspect of the complex reality. If we for example included a heat map on top of the street map it would definitely serve the homeless person to find what he is looking for (a warm shelter) – however it would confuse the car driver looking for a specific street. Each map hence serves its own purpose. Therefore, I believe my sketch is different from the map I bought because it represents the layers important to me personally (green spaces, university buildings, roads were I bike etc.) – or put it differently because it represents my view of reality and how I relate to and interact with the city I now live in.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
