<?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=19&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-04T12:45:41-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>19</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="218" public="1" featured="0">
    <fileContainer>
      <file fileId="311">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/5bd8c222d6b8bf19f250378640717a31.jpg</src>
        <authentication>d290ff0eca2584c5775bad2964bef568</authentication>
      </file>
    </fileContainer>
    <collection collectionId="5">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5">
                  <text>2017 - Sketch 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="433">
                <text>Sarah Wu</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="434">
                <text>My initial hypothesis going into this exercise was that I would be able to clearly draw the places that I frequent most. Though this proved mostly true, some familiar spaces were difficult to remember and did not make it onto my map. For example, every week I walk from Leverett House to Pennypacker, cutting through two church parking lots. Neither parking lots are included in my map. I think this may be a function of time – I always walk this route at night, and am walking as quickly as possible. &#13;
&#13;
While working on this map, I realized that how I perceive urban space not only depends on my familiarity with that space, but also on the way I interact with the space. The spaces that I habitually inhabit and do meaningful things in—classrooms, gyms, upperclassman houses, the Crimson and other extracurricular locations, research centers, cafes and restaurants—dominate my map. Areas that I do not know well (i.e. most freshmen dorms, as I lived in the isolated Pennypacker dorm) were difficult to draw and I ended up missing quite a few. &#13;
&#13;
One difference between my map and the one on Google Maps lays in the lengths and shapes of streets. When drawing, I was going off of time (how long it takes me to walk different street sections), but these were not always accurate. I also imagined a grid system, when in reality, the streets are far more irregular. Another key difference is that I tend to think of buildings as squares or rectangles, when many buildings vary in their shapes – this suggests that I envision the built environment more conceptually and focus on function of space rather than architectural details. &#13;
&#13;
I am most surprised by how selective my memory is. Looking at my map, it seems like I ignore much of the retail scene. This makes sense as I do not go shopping much and these spaces are not important to me. The differences in the two maps also reveal that I experience Harvard Square subjectively. My personal experiences and interactions (or lack thereof) with spaces influence how I perceive and portray them.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="86" public="1" featured="0">
    <fileContainer>
      <file fileId="86">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/3ab3b8c2f5226bfab38be80218fece98.JPG</src>
        <authentication>eaf0d2c4284e0316f2f2e1e7d2d9a778</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="173">
                <text>Sarah Zaghouani</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="174">
                <text>As it turns out, my map is pretty inaccurate, but the relative location of each school is more or less correct. The most obvious inaccuracy is in the intricacies of all of the roads that connect Harvard Square. The most accurate part of my map with regards to roads is around the river houses, which makes sense, as I walk those roads every day. Additionally, in looking at the actual map of campus, I realized that there are quite a few more areas of heavy foot traffic than what I represented on my own map, but, again, I only depicted that foot traffic that corresponded to my daily route, more or less. Additionally, the way that I proportioned the map, the part of campus (Yard and River Houses) take up a disproportionate amount of space compared to the parts of campus that I almost never visit (the Quad, Law School, the Stadium and Business School campus). Moreover, it seems that as far as categories of building spaces go, the number of dorms that I drew is closest to the actual number of dorms that exist, whereas I vastly underrepresented every other type of building. This again hints at the fact that I am an undergraduate, and reflects where I spend most of my time. What I took away from this is that I have a very skewed perception of campus, and I should get out more!</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="171" public="1" featured="0">
    <fileContainer>
      <file fileId="254">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/31b8b3e5de979f65c0f342dd98986291.jpg</src>
        <authentication>60af0c915aa7d030a72b3ebb9c4f9f66</authentication>
      </file>
      <file fileId="255">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/2f614365ab0ceb060170d6c190dae096.jpg</src>
        <authentication>a4d1b74dbe176207ad27999ffacebfb1</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="343">
                <text>Sarah Zaghouani</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="344">
                <text>Prudential (and Copley, to a lesser degree) attempts to replicate the experience of outdoor shopping/leisure—but in a sheltered environment. Prudential lets in a LOT of light. There is a preponderance of indoor greenery, ironically concentrated in the Huntington Arcade, which consists largely of banks and investment centers. Additionally, 101 Huntington Avenue, though it faces indoors, has a brick façade, much like one you would find on a public street, again giving the illusion of outdoor shopping. When one enters the walkway to cross into Copley, the walls are entirely transparent, and you can see that you are walking right over a major road intersection—giving you the feeling of being immersed in the city, while protected from the hustle and bustle. Additionally, at both the Shops at Prudential and at Copley Place, upon entering the buildings, you have to travel pretty high up on an escalator in order to reach the retail level. This immediately transplants you from the action happening on the urban streets at ground level to a more enclosed, peaceful, almost suburban community—where whatever you need, be it food, clothing, watch repair, the gym, or the bank—is all located in one covered, climate-controlled space and is easily accessible. At the same time, signage orienting you toward such Boston landmarks as the Hynes Convention Center, the Copley Mariott, or various iconic streets, all connected by the Prudential Center, is a reminder that you are still in the city. Additionally, like on city sidewalks, there are a number of benches lined along each arcade for people watchers and tired shoppers. Therefore, what is unique about the Prudential Center is that you find a suburban venue of respite in the midst of the city. &#13;
&#13;
Copley, while additionally an enclosed shopping mall that aims for integration into the outdoors, gives the feel of a much more rigid, high-end shopping experience. When you take the escalator up into the shopping area, immediately, the first store you see is Tiffany and Co. or Louis Vuitton, setting the tone for the rest of the shopping experience, and clearly indicating who has business shopping at Copley and who does not. or While the floors of the Prudential Center consist entirely of light-colored faux marble that invites one to wander around any which way, Copley is characterized by rich reddish marble with distinct borders and cobblestone-like demarcations that work together to lay out walking paths. Many elements of Copley’s interior design are gilded, and there is a noticeably warm, rich color theme. Besides the narrower walking paths, Copley also features lower ceilings and fewer places to sit than Prudential, suggesting a preference that shoppers actually shop instead of dilly-dallying. At the Central Court, however, which features a very high transparent ceiling, there is a return to emulation of the outdoors with an abundance of natural light and a ton of greenery, as well as a giant earth-toned abstract sculpture. &#13;
&#13;
Both Prudential and Copley integrate stores with unique, brand-specific storefronts into a singular building with a relatively cohesive design, giving both venues a more suburban feel. Additionally, both are anchored by large department stores: Saks Fifth Avenue, Neiman Marcus, Lord &amp; Taylor. Larger entrances/facades and mini store-specific atria distinguish these anchors from other stores. Additionally, they are all found at different poles of the enclosure, so that shoppers end up passing through large portions of the mall to arrive at each. When a shopper enters a branch that contains one of these large department stores, the shopper can see the store all the way at the end of the branch, which is typically quite large. &#13;
&#13;
In the case of Newbury Street, it is immediately apparent that the space is commercial, as nearly the entire street is lined by window displays of clothing, shoes, accessories, what have you. At street intersections, there tends to be more sidewalk space, and lots of outdoor seating provided by cafes and restaurants, and so individual retailers and buskers often set up shop in that area. Like Prudential, Copley, and other enclosed shopping spaces, Newbury St. is also anchored, but not by department stores: rather, by Boston Public Garden at one end, and Massachusetts Avenue on the other end. There is no branching around a central arcade, in contrast to Prudential/Copley, rendering shopping at Newbury more inconvenient. It is interesting to note, however, that shoppers can plan accordingly if they observe that the most high-end stores are located at the Boston Public Garden end of Newbury St., and gradually become edgier/more urban as one approaches Mass. Ave. Additionally, though malls make for quicker navigation, at both malls and a setup like Newbury, visibility of shops ahead is greatly obscured, whether by turns at indoor malls, or by the trees that line Newbury. Therefore, there is the impetus to continue to walk and pass by stores in order to discover new stores. &#13;
&#13;
Another observable similarity between Newbury and the enclosed mall is the unique storefronts blended into a cohesive design; in the case of Newbury, this is largely 19th century brownstone. That cohesion deviates occasionally, as is illustrated in my sketch of Newbury, but quickly returns to a series of brownstone facades. It is interesting to note that larger, more well-known stores have extra sidewalk space and notably large, unique facades, much like the department stores in enclosed malls. &#13;
&#13;
An additional feature of enclosed malls that we mentioned, the element of almost suburban isolation, is also seen on Newbury. Compared to surrounding streets, Newbury feels quieter and more isolated from the hectic nature of urban life. Sidewalk spaces are bigger, and the space allotted to cars is narrower, placing greater importance on the strolling pedestrian. Additionally, the tall skyscrapers of the Back Bay area are largely hidden from view, peaking out occasionally. That, combined with the blending of Newbury St buildings into other residential buildings, especially toward the Charles River, gives the street a very suburban feel. There are also restaurants/cafes interspersed with shops, providing similar convenience to that of the mall, though there is a notable absence of other connected features that make Prudential and Copley so convenient, like banks, gyms, etc. Additionally, while enclosed malls have two or three discrete levels, on which all stores are located at ground level, adjacent shops on Newbury could be at, under, or above ground, reducing accessibility greatly. I came to realize that this is why I saw the most business at ground-level stores on Newbury—they are more easily accessible; this facilitates simply wandering it to have a look. Adding stairs makes a shopping trip more purposeful, and so I would guess that shoppers on Newbury tend to shop more decisively than Prudential shoppers. &#13;
&#13;
On Newbury, there is more of a strict emphasis on shopping and eating. As opposed to benches on the sidewalks, all sitting areas belong to some café or restaurant, encouraging eating for leisure. In enclosed malls, there are other places for people to hang out—benches, arcades, but often people are holding a drink in a Styrofoam cup or a take-out box—food for pleasure is not really a focus of the in-mall shopping experience. Exits from Newbury are located at street intersections, and differ based on which direction one takes. Exiting Newbury in the direction of the Charles River lands one in exclusively residential areas, while heading toward Copley gradually adds the hustle and bustle of urban life back into the scene. Newbury St. is perfectly situated at the crossroads of both scenes.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="79" public="1" featured="0">
    <fileContainer>
      <file fileId="79">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/91ceb7f660eeb8ba96124775c3788720.JPG</src>
        <authentication>74898e9ec9998db2383c9b92b9fc34a0</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="159">
                <text>Scarlett Yin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="160">
                <text>My sketch focuses on providing functional information to the viewers as I believe the essence of urban design is to serve diverse needs of the population. To highlight this idea, I specifically marked commercial stores and building functions around the yard area so that viewers have a straightforward sense of what we can do in this area. Then, I also provided information on metro/shuttle/bicycle stops, road directions and traffic lights. Transportation not only links the functional architectures, itself is also a "moving space" in which viewers experience architectures from different angles/aspects externally, then in return the experience stimulates viewers' immersion into their own world internally during the commute. I lastly marked the densely populated areas. I hope to ask viewers if Harvard's design of combining residential, leisure and academic buildings make sense. </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="164" public="1" featured="0">
    <fileContainer>
      <file fileId="241">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/1e4f7af9fd3f636fc408c8e2c8d1409e.jpg</src>
        <authentication>7fab8ceb2cd9751195310a13aa0a8a06</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="329">
                <text>Scarlett Yin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="330">
                <text>Interior v.s Exterior &#13;
&#13;
The Prudential Center is a complex that decorates the interior as exterior. Glass ceilings, tropical trees and roof gardens all yield a sense of organic nature within the artificial world. The glass ceiling is especially interesting for a shopping mall because normally owners wouldn't want customers to notice the time in reality so as to immerse themselves more (and spend more money) in the mall-world. On the other hand, shops along Newbury Street are mansions whose design has a clear boundary between interior and exterior: roof is not transparent, plants are outside, streetwalkers see only models in the window but no further into the shop, etc.&#13;
&#13;
Social Boundary: Top v.s Down &#13;
&#13;
The Prudential Center uses height and levitation to delineate the unspoken "class." I circled three levitation - one elevator at the Boylston gate next to Gucci store, one staircase to luxury store Saks Fifth Ave, one gateway to premier cuisine Top of the Hub - in red circles. These design partition social boundaries. The Newbury shops, on the contrary, focus on digging down. A typical shop would have a basement level that serves as a bar, a restaurant, or a bookstore. In line with these mansions' essence as "private territory", Newbury shops deliver a sense of social intimacy.&#13;
&#13;
Function Boundary: Mixed v.s Single &#13;
&#13;
The Prudential Center mixes a variety of clothing, lifestyle, restaurant and entertainment places organically in its floor plan. They also have little cart selling cellphone cases, hats and local souvenirs in the center of the pathways. There are also resting seats and open snack/dessert space scattered in public area. The Newbury shop, restricted by its much smaller room, endorses one function to one space - for example, clothing shop on the first floor and bar in basement. On the other hand, The Prudential Center restricts all staff area to the customers, while at a Newbury shop, customers see or even interact in the office area. This brings the notion that the Prudential Center (and shopping malls in general) is a "stage" where every shop on set is trying to create a compound experience, ideally a virtual reality. Customers are invited to the virtual reality by the design itself; other customers are also merely experiencers. The Newbury shop (and other street-side shops) gives customers more free will and independence as they browse in-and-out hopping different stores; the design itself is not as seamless and coherent as in the shopping mall. Yet in this case, it is the pedestrians that are coming and going on the street serve as "actors" that complete this commercial experience.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="209" public="1" featured="0">
    <fileContainer>
      <file fileId="302">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/e75b771d1cab04ecc455532201857b56.jpg</src>
        <authentication>64a78e98bd5b45c768ddcb4cd35302b3</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="416">
                <text>Sofia Schreiber</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="210" public="1" featured="0">
    <fileContainer>
      <file fileId="303">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/8df611b8b6a46440e3837eeede83855c.pdf</src>
        <authentication>6a756da78924b447fd512ebbc9a1df31</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="417">
                <text>Sofia Shapiro</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="418">
                <text>As a resident of Adams House, which is right next to the yard, without thinking too much about the scale of my drawing, I ended up focusing pretty narrowly on the aspects of Harvard Square that I visit regularly. What was very surprising to me after the fact was how large I had draw certain shopping center areas, like the Garage, relative to Harvard dorm buildings, including ones I had lived in. Since I do not spend a lot of time shopping but do have to pass by those stores, in my map they took up far more space because that’s how it feels when navigating through the shopping areas - like an inconvenient time loss. Perhaps a tourist would have drawn a map with more detail and correctness of the shops as opposed to a busy student going to and from class.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="17" public="1" featured="0">
    <fileContainer>
      <file fileId="17">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/664cb04a6c2efc9c83d5764093c0d88c.jpeg</src>
        <authentication>01b74c8ecdede8f47dd7b2c4fe317d44</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="2">
                  <text>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36">
                <text>Sonja Eliason</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="37">
                <text>Looking at a map after attempting to sketch Harvard, I realize that Cambridge is not at all the grid system I ended up drawing.  Trying to visualize Cambridge in my mind led to a very organized structure, but looking at a map shows all the curves and edges and somewhat sprawling nature of the city.  Cambridge is definitely not the kind of grid that Jefferson would have designed, but conceptualizing a grid is much easier than the disorganized reality.   Maybe this suggests something about the grid system and its appeal to people’s desire to have an orderly conception of their city, a certain predictability that makes it easier to manage.  Perhaps it also says something about people’s search for patterns and their own perception of a city with which they are familiar.  &#13;
&#13;
I definitely underestimated the size of Harvard Yard and overestimated the size of the park.  It’s possible that my perception of size was affected by the relative importance of certain places in my day-to-day life, or what I prioritized.  The places I had the most trouble visualizing were those that I didn’t frequent or that were unrelated to Harvard.  I knew if specific sections were residential or storefronts, and having that organized within the city was helpful, but if I didn’t frequent the area I had no idea how to conceptualize specifics. &#13;
&#13;
If I were to redo my sketch, I think I would start with making the large geometric centers of Cambridge, and then fill in around them, since that is the way the city appears to be organized.  The Yard is a large square, then there’s the large triangle of the park, and the smaller triangle of Brattle Square.  If I had started with organizing those first, I think I would have had an easier time; my mistake was trying to draw streets and connections without giving myself easy landmarks, so nothing is in correct proportions.  The streets all seem to move out in a fan formation from the intersection of those three major geometric locations, so I could have more easily produced the city from starting at the center and then moving progressively outwards. It’s very difficult to conceptualize a bird’s-eye-view of a city that I am used to seeing only from walking.  &#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="106" public="1" featured="0">
    <fileContainer>
      <file fileId="124">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/6af9b143ab42a1f351111b6223a2b620.JPG</src>
        <authentication>6fad7538bec43059eb1505e7bf36e641</authentication>
      </file>
      <file fileId="125">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/9fff540be87cbe4c58f5bf45f02fa675.JPG</src>
        <authentication>d74fdc11843f6ac59a8bfdcdd1cd7b4a</authentication>
      </file>
      <file fileId="126">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/df730c491827eb7794b1a2051ef49d3e.JPG</src>
        <authentication>f8db9a686c362813a9dd4b9b9690681d</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="213">
                <text>Sonja Eliason</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214">
                <text>I chose to look at the comparative pattern of kinds of stores (retail vs. service vs. food) versus the presence of public spaces in each kind of shopping district. On Newbury Street, the stores were much more equally divided between food and retail, while the indoor malls were almost entirely retail. But the indoor malls had public spaces like gardens, as well as benches upon which people could rest. Newbury Street had neither of those. This seems to suggest that food establishments (the restaurants, cafes and coffee shops that are so prevalent on Newbury) play a similar role in the environment of the shopping district to public spaces: both are a place for people to rest and take a break. Indoor malls don’t feel the need to provide the same number of food stores since they provide public spaces for relaxation, so they can maximize their number of retail stores without denying people a place to rest and therefore risking them getting fatigued and leaving. Newbury, without these public spaces, has to provide a higher number of food establishments in which people can rest, otherwise they would decrease the length of time people would be willing to shop. Also to take into consideration would be that the indoor malls had an overall designer, so there was a voice for public spaces, compared to every storefront looking out for themselves as they do on Newbury, and there being no overall designer to advocate for public space. It’s interesting as well that the malls spend money on extensive interior gardens and plants, while Newbury seems to rely on the natural outdoors to provide that “garden” feeling. It’s almost like a smaller-scale version of the Park movement: shopping moved indoors, so people tried to figure out how to bring nature with it.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="82" public="1" featured="0">
    <fileContainer>
      <file fileId="82">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/a8a045ebbd7ba9ff16440e962c8d91af.pdf</src>
        <authentication>cb3efd2ceb3ad1e35271a2bab748b315</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="165">
                <text>Spencer York</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166">
                <text>This is a birds eye view of the area surrounding the MAC Quad. I chose this area because I live in Kirkland and I am very familiar with this area and knew I would be able to reproduce it well from memory. The scale may be slightly off and I do not know the exact layout of Eliot or Winthrop because I am never in them, but the general area I believe is correct. I drew in arrows to show the direction of traffic on the one and two way streets to show the general movement of the area.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
