<?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=3&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-16T20:13:08-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>3</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="5" public="1" featured="0">
    <fileContainer>
      <file fileId="5">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/f07572de8d515b7e7a01a9b96e6c2527.pdf</src>
        <authentication>724998bc346fa08a05f98cb07ca8e994</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="14">
                <text>Chad Benoit</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15">
                <text>Harvard Square is a really interesting place for our first sketch assignment because it’s an area that I spend so much time in on a daily basis, but I have never given much thought to it from a design perspective. Harvard Square is really interesting to me because it is the confluence of so many different types of movement. This movement is what I focused on for my sketch. For me, the center of Harvard Square is the T station because it is found at the boundary between Harvard proper (Harvard Yard) and the businesses of Harvard Square. It also serves as the main connection point between Harvard and Boston, and it’s the first thing that many people see when they come to Harvard Square for the first time. In my sketch I tried to indicate some of the defining buildings of the immediate area, but more importantly, I indicated the train (red), bus (yellow), traffic (blue), and pedestrian (purple dots) routes. I think it is really interesting how the Square is definitely dominated by busy pedestrian routes. I also think that like many places in Boston, it is interesting to think about how Harvard Square is where architecture that is centuries old meets very modern buildings. Also, a sketch of Harvard Square is very brick red because so many things are made out of brick (sidewalks, buildings). For the next sketch, I definitely want to focus more on the “diagraming” aspect of it because that is what is most interesting to me, and because drawing is not my strong suit. When doing this from memory, I definitely got the basic components, but I missed out on a lot of the architectural details of the buildings and some of the subterranean features (for example, there are bus routes that run through a tunnel under Harvard Square as well).</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="94" public="1" featured="0">
    <fileContainer>
      <file fileId="99">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/4ac5a9c36771c2df368b1c508436eefd.pdf</src>
        <authentication>8e8c0f7aa056fba6d24534a45eba48f2</authentication>
      </file>
      <file fileId="100">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/c211ef83fa27ff24f2478967a1c78a04.pdf</src>
        <authentication>7158806366e346cad1132be07a261b21</authentication>
      </file>
      <file fileId="101">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/b2f18212a4b395389f7638b4d237470c.pdf</src>
        <authentication>bbb43b2e60165d9032c5b52fd506d8ae</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="189">
                <text>Chad Benoit</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="190">
                <text>For these sketches, I emphasized the changes in elevation in the two different shopping areas. I thought it was interesting how while one might imagine an indoor mall to have shopping on multiple levels, the more traditional shopping on Newbury Street actually makes use of shopping on various levels as well. There are the street level shops with entrances at sidewalk level, but there are also shops upstairs from these and often shops below sidewalk level as well. In addition, in both the Copley Place mall and on Newbury Street, there is additional office space located above the retail levels. In the photos that I have also included alongside my sketches, you can see that the mall is characterized by large escalators and a waterfall in the atrium that highlights the enormity of the shopping on its three levels. In comparison, there are certainly no escalators on Newbury Street, and the change in elevation is subtler, the entrances to subterranean shops often hidden behind railings and shrubbery. Storefronts in the mall are large and imposing. For example, you can see that the Barney’s storefront is meant to invoke a sense of elegance and grandeur in the shopper’s mind. In comparison, the shops on Newbury are subtler, often with only a limited square footage of window and floor space to showcase their products. &#13;
&#13;
Overall, I think that both forms of shopping make good use of space by having shopping on multiple levels. However, you can tell that the mall was specifically built with room to showcase lots of advertisements and products in each store whereas on Newbury Street, retailers have to make do with a limited amount of floor and window space to draw the customer in.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="37" public="1" featured="0">
    <fileContainer>
      <file fileId="37">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/296a64f727d2564d3d34ea9e89118f6b.pdf</src>
        <authentication>956dfcd61234709a1f55f3a49ca1b482</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="75">
                <text>Chiyoung Kim</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="76">
                <text>Because this is a path that I walk often, the map wasn't too different from online maps. There were, however, some noticeable distortions and some proportions were off as well. However, my map is different in that the positioning of many of the landmarks along my path were based on relative positioning rather than definite positioning along the street. However, I think this shows how we look at the city on our daily walks along paths we walk often. We walk along our paths knowing the order of landmarks to our final destination, but we might not know the absolute distances between each. This makes it so that the maps we make come out looking slightly like caricatures rather than a map from Google Maps – we know around where everything is located but not where everything is exactly. The city is a collection of landmarks we know of and have in a relatively ordered state in our minds.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="123" public="1" featured="0">
    <fileContainer>
      <file fileId="156">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/42b7d3e3508078482b864e4bf017677e.pdf</src>
        <authentication>f9ca968c27fee2e3ceac3768aceafa2d</authentication>
      </file>
      <file fileId="157">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/629406600887530463e8256268dff489.pdf</src>
        <authentication>97dc06aba082e0ddb9794cc2995b76bd</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="247">
                <text>Chiyoung Kim</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="248">
                <text>Copley Place is definitely catered for the wealthy upper class in its selection of stores. Neiman Marcus, Salvatore Ferragamo, and Tiffany and Co. are only a handful of the many higher-end brand name stores available here. The most interesting thing about Copley is that it builds up with multiple floors rather than outwards, and that it has a more of a cavelike feeling due to its darker lighting and closed atmosphere. It is upholstered with polished marble and a green space which showcases an indoor waterfall, and it is cloistered from the outside with an escalator, separating it from the rest of Boston. &#13;
&#13;
Newbury Street is completely opposite, with lots of restaurants and smaller boutiques. Compared to the classy elegance of Copley Place, it has a more town-like feel due to its brick buildings. Seating areas abound in ubiquitous sunken seating areas. The stores are clustered together practically in an unbroken wall that forms the “walls” of Newbury Street, turning the entire street into a mall. &#13;
&#13;
Prudential Center is somewhere in between these two. It is an indoor mall that is separated from the outside but open to the sky through a roof made almost completely out of glass. While it shows the kind of isolation that Copley Place presents, it has a more urban feel to it due to its shop selection, a mix of both economical and higher-end stores. It is in itself a social space with an array of seating areas scattered throughout the mall.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="178" public="1" featured="0">
    <fileContainer>
      <file fileId="264">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/77e0d869a22d6a7d920c50463f391d54.JPG</src>
        <authentication>0cc81c690ecda8c93bd596905024c963</authentication>
      </file>
      <file fileId="265">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/ae626ff28287c3e097111cdee33fa54c.JPG</src>
        <authentication>d60fa15f3caa93bab02f5a859cef6139</authentication>
      </file>
      <file fileId="266">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/d0dd355aa60dcc0ba33e49c83ef81da7.JPG</src>
        <authentication>86c1696f0c7df2cb62f74cebb2cd8d66</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="356">
                <text>Christopher Chen</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="357">
                <text>Christopher Chen The most difficult and different part of the sketch was getting the physical shapes, sizes, and relative orientations of the map features correctly. For example, most of the buildings are actually smaller than I expected. I am pretty proud of my map, in that I think it is pretty accurate. My perceptions of size and my memory make the two maps differently, suggesting I use and remember different features of the city than a camera would photograph.</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="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="101" public="1" featured="0">
    <fileContainer>
      <file fileId="114">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/617c3aafc848b955fe596c8b9e356dc9.png</src>
        <authentication>830192b46c9e6c5f3eed15ab98d9ce68</authentication>
      </file>
      <file fileId="115">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/794d6bdd06eee94446ff9935a44c6cc1.png</src>
        <authentication>7df8a34130d810de338d2fe0cb4cb5ee</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="203">
                <text>Claire Collins</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="204">
                <text>Everything about Copley Place screams upscale. From the sign out in front of the mall in the mini-plaza to the advertisements everywhere for the mall itself, as one of many Simon malls, to the fancy salmon-colored stone stairs to the shiny gold elevators and the waterfall in the middle of the atrium, not to mention the glass ceilings that allow for a ton of natural light in the small space in the city. The walkways are fairly wide, with a consistent stone pattern. There are few kiosks. Each store has its own exterior wall finish; the walls of the mall itself are not visible until you go down the path towards the restrooms and the parking. All of these spatial factors are reinforced by the signage. There is a code of conduct posted at the bottom of the escalator, a sign welcoming guests in seven different languages, and free Boston Common magazines in the center of the mall. All of this makes Copley Place enjoyable and accessible to only a certain type of customer: one with money to burn and a strong desire to shop. There aren’t many people milling about and the windows aren’t really big enough to permit for window shopping. &#13;
&#13;
Newbury Street is entirely different in character. The sidewalks are bustling with people, including those working the street for their causes. This kind of political advocacy is explicitly banned in Copley Place. The stores are a mixture of retail and grocery/general goods stores. What makes this street clearly commercial is the uniformity of it all. The buildings are all the same height, and often the same red brick with matching roofs. Trees are planted a specific distance apart. There is ample sidewalk room and trash bins, as well as lights for night. Once one steps off Newbury, the buildings again soar to higher, differing heights, the buildings aren’t made of brick anymore and there aren’t trees lining the one-way street.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="193" public="1" featured="0">
    <fileContainer>
      <file fileId="283">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/534af11e362e42a5e2b1aecd1ef4e938.pdf</src>
        <authentication>15b2180cef8f4c34f5f90f4e7a6ae0c1</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="385">
                <text>Claudia Laurie </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="386">
                <text>My sketch was based on a diagram relating to major landmarks and centralities and how they relate to each other. I found myself starting to draw the landmarks that meant the most to me at my earliest days art Harvard, such as by drawing Harvard Yard and marking John Harvard statue as that was a frequent meeting point freshman year. I then expanded the map to important buildings I have had classes in, such as the GSD and Science Center. When I noted areas north-west of the yard, my drawings were much less accurate as I hardly ever go to the quad and am not that familiar with the western Law-school region. I then moved south, and as I did, closer to where I now currently live, the scale of my diagram increased incredibly to the point where the houses I spend the most amount of time are disproportionately massive in comparison to where I spend time during my earlier years. My diagram doesn't even get to representing the Harvard campus over the bridge as I don't have any strong memories of time over there and therefore the area seems insigniﬁcant to me. I was also struck by how my representations of landmarks were all rectangular. I felt that I was struggling to get every building I have spend time in, represented and did not have enough space to do so, especially as the scale became more and more disproportionate.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="48" public="1" featured="0">
    <fileContainer>
      <file fileId="48">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/c2d34a639c465349869fbe30a548810b.jpeg</src>
        <authentication>a312c78d49700ad997fbd98a9f053317</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="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="97">
                <text>Urban design still remains a foreign concept: space, dimensions, structure can easily clutter the mind when drawing our fondest roads from memory. Despite the initial hesitation and frequent erasure marks, I believe the product that came out captured the spatial distribution of Harvard very closely. The map is not completely accurate, by no stretch of the imagination, but it really does encapsulate the most important landmarks of Harvard while respecting the spatial distribution of the urban/suburban settlement. Right off the back, the biggest difference I see is that of perception, meaning that in comparison to the actual map, my map elongates certain bottom portions. This is most apparent with Winthrop House which is my home, as well as the point of origin for the sketch. Winthrop is by no means the same size as the Science Center but the way I went about designing this map started from home and worked its way abroad causing certain levels of exaggeration in size for Winthrop (but not substantial). Furthermore, my map has very accurate points at times, the Yard, the walk to the Quad, the houses along the river symbolize places that matched up almost identically to the real map. This is most likely do to these places being centers of my life, and thus my memories that I can perfectly sketch them out. It seems that these three foci served as the triangle of urban planning for my mental map in which the great challenge was filling the in-between space and the peripheries with landmarks that I could easily recognize. &#13;
&#13;
As compared to a flat map, my map makes use of height in buildings that are stereotypically tall for the rather low (five floors or below) heights of the buildings in the area. The way it became manifested in the map was in the form of visual stylizations where a level of three-dimensionality was added to buildings like Memorial Hall, Annenberg Hall, The Smith Campus Center, the Leveret Towers among others. As a final note, somewhere that the two maps do align is with the demarcation of parks, green with the Google Maps and shaded in with my map. Parks and green spaces are extremely important in these areas, particularly considering the masses of brick buildings that align the streets, so there is extra attention placed on them for this unique purpose.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="98">
                <text>Daniel Montoya</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
