<?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=6&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-03T04:01:03-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>6</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="53" public="1" featured="0">
    <fileContainer>
      <file fileId="53">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/565af3c0559029e2d2365f4c8be85685.jpg</src>
        <authentication>480b0784c7caf80ca07f0cc2336fbcd3</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="107">
                <text>Ellen Poile</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="108">
                <text>I found this exercise surprisingly difficult. Trying to layout my mental image of the square onto paper stumped me. First, I could not figure out how to orient Harvard Square onto the dimensions of my notebook paper. The question of fitting everything on the page with the proper scale left me grasping for the right size and direction of my landmarks. Not surprisingly, the yard occupies a much larger area than appropriate, as it was the easiest starting point. I knew how the buildings related to each other and I knew that it was generally a rectangle. This left me squeezing other parts onto too small areas of paper. However, even in the yard, I didn’t know the footprint or the number of certain dorms and buildings that I had never visited. In the bottom area of my map (between the yard and the river) I became overwhelmed in the details and number of features. As these blocks are where I live and spend most of my time, I knew the buildings and the streets the best. However, towards the river (down JFK) I do not spend as much time, so I became more confused. In fact, I ended up excluding an entire block and street between Mt. Auburn and Memorial Drive that consisted of buildings I do not use; I had simplified this area to only the houses. This led to a problem on the other side of JFK, where I knew there were commercial buildings and a park, yet I couldn’t make the streets match up. As a result, the scale on one side of JFK is different than the other. Interestingly, I found the streets the most difficult aspect of the map to draw. I remembered what buildings they led to and their names, but not their lengths and directions, particularly the streets that are not in a grid (such as Eliot St., Brattle St., Arrow St.). However, when I began my map, I instinctively began with the main streets. For my studies, this led me to zoom in on certain difficult areas to organize them, such as the intersection by the T and how the JFK and Mt. Auburn intersection (which I knew was a 90 degree intersection) related to the river. I discovered later that it was actually easier to place the buildings I knew in relation to each other and connect them with the appropriate streets. As I added more buildings, I realized how little space I had left. I had to erase and redraw many of my landmarks as smaller and re-angle my streets to fit everything. In the end, I was most surprised by what I had to omit. I knew I was missing things, such as Winthrop St, buildings in the yard, the streets leading to the quad, but I genuinely did not know what they were; I just sensed a lack. Things I had noticed and moved around but never used or named. I learned that after four years, I still do not know how to get to the Quad, so I left it out of my map.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="33" public="1" featured="0">
    <fileContainer>
      <file fileId="33">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/f57ec89ea14a4e8cf35e8d849bdc4c22.pdf</src>
        <authentication>0038d2257ae117a376d9870de0288b19</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="67">
                <text>Eloise Kaehny</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68">
                <text>I tried to stay somewhat realistic in my interpretation of the Harvard campus and its surrounding area because my routes are relatively geometric and systematic when I am navigating my way around Harvard Yard and down to the athletic fields. I emphasized my personal route with an orange trail. I also detailed my corner of the Yard - the Union dorms. I visualize Harvard as being highly organized, and the routes that I take most often are also linear and follow the geometric organization of the campus. I found the perimeters of the Yard to be particularly important in my sketch because I, relative to the average Harvard freshmen, rarely frequent Harvard Yard. The terminals of my daily journeys are also on the perimeters of the Yard, starting at Pennypacker and ending with either the Science Center or Memorial Hall. I additionally highlighted the routes of the highest volume of foot traffic in pink, which I experience directly every day when walking to and from class. Finally, I attempted to outline Harvard property in blue. In addition, I could not detail the area of Cambridge because I rarely venture westward (from the Yard). I have learned from this sketch that walking certain routes will, obviously, lend you to be more familiar with spatial relationships between your destinations. I am extremely familiar with the areas between Pennypacker and Memorial Hall because I have made that walk so many time. I less sure about the area south of Mt. Auburn Ave and west of Mass Ave. My map is somewhat similar to the official university map, but not as detailed in areas that I do not walk through frequently.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="119" public="1" featured="0">
    <fileContainer>
      <file fileId="148">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/77cbaf42274788a9c43b86db9d7f33b3.pdf</src>
        <authentication>a8ca48785c4b3e5cb2b00abc77817482</authentication>
      </file>
      <file fileId="149">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/841450a69b1dd52b767cb9e91eb83d4f.pdf</src>
        <authentication>116c110f1a4ecaa306f90c6be1e900d5</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="239">
                <text>Eloise Kaehny</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="240">
                <text>Upon visiting both Copley Place/Prudential Center Mall and Newbury Street, I was surprised to find how each attempted to mimic certain characteristics of each other. The Copley Place and Prudential Center Malls are large, enclosed, shopping centers. High glass ceilings, shiny marble floors, and large glass storefronts create a pleasant, bright experience for shoppers and passerbyers. The extensive use of glass in the storefronts, ceilings, entrances, exits, and pedestrian walkways lets natural light illuminate the shopping areas, and glimpses of sky and surrounding streets and buildings are possible. In the center of the mall, a multi-story atrium with a waterfall and benches creates a central seating area. It seems that this shopping complex attempts to mimic a natural, outdoor environment while (obviously) remaining enclosed. It also seems that the shops located on Newbury Street attempted to”replicate the experience of a shopping mall” by using the same floor-to-ceiling glass storefronts, using different elevations as a way to catch the eyes of shoppers (eye-level and basement level shops), as well as marketing luxury products of the same caliber as those in the mall (designer bags, perfumes, watches, etc). Newbury is clearly a commercial area because of the significantly wide sidewalks that accommodate large volumes of foot traffic, as well as the numerous shops that continue adjacently for many blocks. Although some aspects of Newbury Street seem to mimic that of, for example, Copley Place, it is still clearly part of its surrounding urban environment to a greater extent. It is easier to take cross-streets to enter and exit the street, and it is possible to view the Boston skyline, residential buildings, banks, churches, etc that are on all sides of the street. The shopping complex, however, is somewhat isolated and requires the crossing of multiple heavy-traffic roads. The complex is less seamlessly incorporated in the urban fabric - multiple large parking buildings are nearby (maybe the complex is geared towards commuters who rely on their cars for transportation). While it is easy to enter and exit Newbury Street, there are fewer entrances/exits to the shopping center - once you have entered, it is easily navigable. But to actually leave the complex requires more effort than leaving Newbury Street.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="192" public="1" featured="0">
    <fileContainer>
      <file fileId="282">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/c887c78d417708191b3471614c7ced93.pdf</src>
        <authentication>cf4adcb9e8bbcfb43bddf8ca2248b395</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="383">
                <text>Emily Johansen</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="384">
                <text>Comparing my sketch to a map of Harvard Square, I was unsurprised to ﬁnd that the areas I walk were much more accurate than other areas in the square, but I was surprised that my ability to recall the region was markedly inﬂuenced by the types activities I do in those areas, rather than the amount of time I spend in them. I walk down Dunster Street everyday on my way to class, yet I forgot to include Winthrop Street, which is one of very few streets I cross to reach the Yard. On the other hand, I was able to easily recall the area along river (Eliot, Winthrop, Leverett Houses) with signiﬁcantly greater accuracy, even though I live in none of those houses and only spend a fraction of my day in the area. I have rowing practice along that stretch of the university almost everyday, where I am not mindlessly distracted by thoughts of the next class. Though I am not at that point of the river during practice for an extended period of time, my time there is directed and part of my identity in a way that walking to class simply isn’t. This caused me to think beyond the trope of the city’s ability to affect its inhabitants and see the reverse: that my activity changes (my perception) of the superstructures around me. In other words, while I am inﬂuenced by my built environment, it is simultaneously inﬂuenced by me.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="57" public="1" featured="0">
    <fileContainer>
      <file fileId="57">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/774885d7f8c54ec3848081bbc2b8a328.png</src>
        <authentication>c1a4768e66102f6f67ef97c9302e2a9d</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="115">
                <text>Eric Ronda</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="116">
                <text>I began my first sketch with outlining as well as detailing the buildings on the side of the river with the Athletic Facilities. After finishing the Athletic buildings I realized I had taken up over half of the page and still needed to include all of Harvard Square area and the Yard so I threw that sketch out and decided to start a new one. With the new sketch the first thing I did was map out the major buildings/parks on both the top and bottom sections of my paper to provide a basic outline and boundaries that I then filled in while completing the sketch. The basic grid outline of Harvard Square area was pretty simple to remember and sketch, however I ran into some difficulty trying to draw the tiny roads interviewing the river houses as well as which buildings were supposed to go on which plot of land. I also found it difficult to scale the roads and the buildings after creating the initial scale of the buildings on the athletic side of the river. Many of the buildings on the Academic side of the river turned out to be scaled differently because I was running out of room.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="142" public="1" featured="0">
    <fileContainer>
      <file fileId="195">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/e8dde3490242df3b6053d6602bd6e383.png</src>
        <authentication>bfe9b57331d5dc3ad634cfdb05e8331e</authentication>
      </file>
      <file fileId="196">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/e671209beb62d2094c4b98ba512a4272.png</src>
        <authentication>986a855d25405ec2e3cb7cea47af7214</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="285">
                <text>Eric Ronda</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="286">
                <text>When taking the elevator up from the ground floor to the main entrance of the Prudential center Shopping mall, you begin in a glass ceiling hallway that “begins” your journey throughout the mall. &#13;
&#13;
While traveling through the mall, the experience is similar to driving down a the right side of a ride with stores on your right, and the other side with people traveling against you with stores on their side. Instead of dividers on the road, there are a series of stalls selling different merchandise. After each long straight walkway there is a large area where people tended to gather and talk to each other. Unlike the walkways which seemed to be built strictly for walking, the large areas had places to sit and relax. The Prudential Mall felt much more open and brighter due to the large use of glass, which gave the mall a much happier and fun feel than the Copley mall. When crossing the bridge to the Copley Mall, the red/orange granite floor along with the dim lighting gave a much more serious and more sophisticated feel to the mall. In the middle of the Copley Mall was a place for people to congregate and listen to the waterfall or plan the next area they will go to. However similar to the Prudential Mall there are walkways that seem to have one purpose and that is for travel, whereas the bigger sections in the center of the mall are for various activities and places for people to gather and communicate. Traveling through the mall, it seemed as though the plan was to make the exits on the very ends of the mall and very hard to find so you end up traveling on this constantly changing road until you reach the end. The Prudential Center also infused plants and shrubbery within the plan of the mall to liven the feeling. While traveling down Newbury Street I got a very similar feeling to when I was traveling through the walkway of the mall. The sidewalk that you walk down is separated from the stores by a small front yard that each store had. The Front yards were used for multiple purposes depending on what the sore was. Most restaurants utilized the space to have outdoor seating, which appeals to a lot of people who would like to eat outside while looking at the traffic walking by. Another commercial aspect of the street are the displays within the windows of dressed up mannequins.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="204" public="1" featured="0">
    <fileContainer>
      <file fileId="296">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/62a591fb4b661021996fcdae7336dede.jpg</src>
        <authentication>cd28299d0a4308245e3670bd26d41bd8</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="407">
                <text>Erica Newman-Corre</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="408">
                <text>In this drawing, while looking at private vs. public space, I tried to emphasize three kinds of space—Harvard space, green space, and streets (the most public space). Though there are more buildings in the area, I only included Harvard buildings and those with which I interact with in a Harvard setting because they are fall somewhere between public and private space. To my classmates and I, they are public—within the buildings outlined in gray, there are few places we are not allowed—but to the general populace, the buildings are largely guarded by swipe access or, in some cases, actual guards. The green space also falls in a gray area between public and private space. Some of these spaces are publically owned and accessible (Cambridge Common), some are privately owned but publically accessible (Harvard Yard), and some are fully private, gardens rather than parks (the courtyards within the houses). The streets share none of this fuzziness—they are open to everyone. What I found most enlightening and frustrating about creating this drawing was relating one section to the next—things would feel in scale, or seem right, but then when I would add the next piece, it wouldn’t fit together like it should. The streets feel straighter when you’re walking them.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="110" public="1" featured="0">
    <fileContainer>
      <file fileId="132">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/23e1738668d71ffea081909bde4cd40c.pdf</src>
        <authentication>86f093bc4acd0fb7149db5086661ad12</authentication>
      </file>
      <file fileId="133">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/a1f502cae500c5affe80907dd5d45923.pdf</src>
        <authentication>0818dfc4e252aaa14a78d4e1a17ec725</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="221">
                <text>Erik Filegauf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="222">
                <text>I chose to represent the two locations on a variety of scales and perspectives, both geospatially and thematically, rather than as one all-encompassing vision. I wanted to maximize the amount of information to include a breadth of visions while retaining depth in details. At the malls, I focused my time at the waterfall area, a node for shoppers and stores, because I felt that it related well to our class’s focus on the built “natural” environment. I sketched the indoor equivalent to the “picturesque garden”, but I also was interested in how shoppers interacted with the meticulously-designed space as a whole, as most (but not all) seemed more focused on shopping than appreciative of the gardenesque oasis. I was also interested in observing what types of stores situated near this environment for economic or other reasons, and which would be on the second floor. I also counted the number of people in each store, but I visited the two locations late in the day, so I do not believe that this even gives a good indication of typical consumer patterns. &#13;
&#13;
While the malls felt expressly designed for shoppers’ convenience and enjoyment from the beginning, Newbury Street had more of an organic, while also more homogenous, layout. Although the inclusion of nature seemed to be more patterned (trees every 20 feet or so, more formal gardens) it didn’t seem like an architect had tried to maximize the amount of money and time spent by visitors. The buildings were likely converted rowhouses, giving a residential atmosphere. There were few places to sit (pointed stone barriers seem to discourage this) and the straight street and wide sidewalks are more conducive to window- shopping and mobility.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="21" public="1" featured="0">
    <fileContainer>
      <file fileId="21">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/c6128fe08ae1b288519356c9feb9816e.jpg</src>
        <authentication>5c28f5bfc4642b72670546a39a7e351f</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="44">
                <text>Erik Fliegauf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45">
                <text>This sketch was much more difficult than I expected. However, I was satisfied with my final product. I was aware of some potential errors at the outset. For example, I knew that I would underestimate the distance from the Yard to Radcliffe Quad. Of course, I was more correct about familiar places, like around my dorm (Hurlbut), the Yard, and my tour route. A history as a pre-freshman obsessed with both Harvard and maps more generally gave me an advantage. Even so, there were certain mistakes that I was surprised and even embarrassed by. I knew no buildings a block east of my dorm, since I only drive past that area. I got Cambridge Common Park completely wrong, as it doesn’t border the Yard nearly as far as I thought. The main takeaway was that even if you know an area well, and can navigate perfectly while in that space, it is incredibly hard to construct a bird’s eye view of that place. We remember things in two-dimensional visual snapshots, not in three-dimensional space. &#13;
&#13;
The “special features” had to do with people, movement, and activity, as my experience with Harvard focuses on the distinction between academics/work (and the associated places) and personal life. I also wanted to explore the distribution of tourists and students, as their interactions with space are completely different.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="60" public="1" featured="0">
    <fileContainer>
      <file fileId="60">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/1d13beea9256c891f51aaa52d84cbad2.pdf</src>
        <authentication>db8df454838b011cb1bb22089f7bcc14</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="121">
                <text>Eva Shang</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="122">
                <text>In this map of Harvard Yard and Harvard Square, I tried to first lay out an accurate scaling of the distance between major landmarks, but also to feature barriers or landmarks that are not entirely ADA compliant. My sister uses a wheelchair, and on her visits to Harvard Square, I’ve developed an eye for roads that her wheelchair would have trouble traversing. Harvard Square is particularly hilly, coming up from the river, and at some locations, there aren’t smooth pedestrian walkways for us to take. Some of the paths that are particularly tricky are Dunster St, which is brick-laid and incredibly bumpy, the road coming up from Adams to the Yard, which is extremely steep and often crowded, and the stairs coming out of Lowell, towards Quincy. I also sought to highlight some incredibly well-designed buildings, such as the Art museum, which features an aesthetically pleasing accessibility ramp that isn’t tucked behind a side entrance. Incorporating accessibility into how we think about and conceptualize design is incredibly important to me, and I wanted to highlight where it was done well and done poorly in Harvard Square. &#13;
&#13;
From a broad overview on Google Maps, I noticed that because I was coming from a handicapped pedestrian perspective, the location of buildings frequently did not correspond to where one could actually enter them. For instance, while the entrance to Widener is inside Harvard Yard, the handicapped entrance to Widener is all the way on the other side of the building. A map that directs based on the shortest route also might not be the easiest route for someone in a wheelchair.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
