<?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=5&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-01T17:00:31-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>5</pageNumber>
      <perPage>10</perPage>
      <totalResults>221</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="162" public="1" featured="0">
    <fileContainer>
      <file fileId="237">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/9e1eda683ae54f11c67fda0ca5048476.jpeg</src>
        <authentication>a71cfbfdd1bff21a062cec7758166705</authentication>
      </file>
      <file fileId="238">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/d878f26837c1299d0ee01b384d675c6a.jpeg</src>
        <authentication>64b0a9e5ee419f80bf8617c1bcf12f7d</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="325">
                <text>Dylan Wong</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="326">
                <text>Although Newbury Street and Copley Center/Prudential Mall are very different shopping settings, they surprisingly share very similar characteristics. Copley Center and the Prudential Mall are indoor shopping malls with an emphasis on open space and natural lighting, almost imitating an outdoor shopping experience, like at Newbury Street. Shoppers enter Copley Place through either glass skybridges or a glass-covered entryway, which let in natural light, while still sheltering shoppers from the elements. The main arcade is open to the levels above, making it feel big and open. At the very center, a multistory glass atrium with a waterfall allows shoppers to sit on the centrally located benches and enjoy sunlight. Even the smaller, non-open arcades have high ceilings, wide walkways, and bright marble floors. The openness of the arcade seems to be effective as it attracted many pedestrians and was a popular place for convening (especially under the atrium). The design of the mall also has only two main entrances, “forcing” consumers to walk through the entire mall before they can exit. My sketch is a basic floorplan of the mall that shows the design elements of the walkways that make them feel open and allow in light. &#13;
&#13;
Although a completely different setting, Newbury Street has striking similarities to the two malls. The street also has very wide sidewalks and light, one-way traffic; it invites pedestrians to walk on it, even if they aren’t shopping. Most of the buildings have multistory bay windows displaying the products and drawing buyers into the stores. Also, the end of the street is the Public Garden, which attracts lots of tourists and park-goers to casually shop on Newbury. Unlike the mall, though, shoppers can “exit” the shopping center at any point by sampling turning off the street at any intersection. My sketch shows the inviting bay windows of the buildings and the wide sidewalks that people can easily walk on.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="200" public="1" featured="0">
    <fileContainer>
      <file fileId="292">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/0ab9bac77d9e54bfc1d93b3492842c4f.pdf</src>
        <authentication>705aa160a2d73865e4e3fda87813fb38</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="399">
                <text>Eana Meng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="400">
                <text>This"was"much"harder"than"I"expected!"I"made"a"few"drafts"because"I"kept"getting"the"proportions"and"the"layout"incorrect."I"think"I"still"could"have"done"a"better"job"with"the"proportions"–"it"seems"like"certain"buildings"and"streets"are"far"too"big,"but"I"was"happy"I"could"fit"most"of"the"things"I"wanted"into"the"sketch."I"wanted"mostly"to"focus"on"public/green"spaces"and"their"usage"–"which"is"what"my"sketch"highlights."I"wanted"to"show"how"much"of"the"green"space"or"public"spaces"designated"for"people"to"use"was"actually"being"used"–"which"is"very"little."The"main"flow"happens"on"the"small"streets"which"causes"a"lot"of"congestion."There"is"proper"use"of"green"space"in"the"Yard,"but"during"the"winter"months"much"of"the"space"is"blocked"off"so"there"is"some"congestion."Overall,"it"seems"like"there"is"ineffective"use"of"the"common"spaces"that"the"city"has"designated."""Comparing"my"sketch"to"the"actual"map,"I"didn’t"curve"my"streets"and"I"definitely"had"some"issues"with"sizing"and"shape!"Originally,"I"was"also"going"to"add"a"lot"more"details"and"other"aspects"but"I"realized"it"might"have"detracted"from"what"I"was"trying"to"show"–"thus"my"sketch"is"clearly"a"lot"less"detailed"than"the"actual"map!"</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="72" public="1" featured="0">
    <fileContainer>
      <file fileId="72">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/7684af68d198af32200c67598312b0e9.JPG</src>
        <authentication>d5706d2928e8bcf7ff71382587b60744</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="145">
                <text>Edward Vasquez</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="146">
                <text>In my drawings, I tended to focus on areas of Harvard’s campus at which I have spent significant amounts of time, places that I tend to pass through somewhat carelessly or with haste. In some sense, that is how I interact with the campus and with my environment: I focus on the bigger picture, and I infrequently take the time to appreciate smaller details which are designed with as much detail and care as the large ones.&#13;
&#13;
I had an easier time imagining the larger elements from which Harvard’s campus is composed, such as buildings and main arteries, rather than smaller details like trees and benches. I could easily locate, say, the different arenas on Soldiers Field (the athletic complex), or most of the buildings in the Yard. But I couldn’t connect the main paths and sidewalks—probably because I am a bad pedestrian and walk through lawns and streets more often than advised. I also tended to remember the different areas of importance to the Harvard Band (of which I am a member) and where we would normally travel—that is another way in which I frequently interact with the environment.&#13;
&#13;
I was also limited in my medium: I purchased a square notebook, and rather than drawing dozens of drawings trying to encapsulate all of the campus meticulously, I only focused on a vignette of the spaces assigned. This, too, made it difficult to consider where things began and ended, a problem we rarely encounter when we navigate with our favorite contemporary cartographer, Google. We rarely need to try and create our own mental images of the spaces we inhabit anymore, save for when a tourist or parent asks for directions (moments I relish because I like the mental challenge of envisioning routes and paths to a place). Thus it’s difficult to express our ideas well in written form, much less in a drawing. I enjoy the challenge, but it is difficult to settle for imperfection and incompleteness in the age of perfection and computers.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="157" public="1" featured="0">
    <fileContainer>
      <file fileId="224">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/f066cc41475ec4dea52e37cc33b52745.JPG</src>
        <authentication>bed59f5eb3bf3c7f36ecdd032c0e92fd</authentication>
      </file>
      <file fileId="225">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/57627261e2d9dcf61253b902ee9e5e4c.JPG</src>
        <authentication>924102419b3f07a3e398aa916e80eb9f</authentication>
      </file>
      <file fileId="226">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/256f9bcaaeae17d96a5de15eb6b11caf.JPG</src>
        <authentication>0dd5b190cfa9f292e50167807ddfd8d8</authentication>
      </file>
      <file fileId="227">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/836899ef28731ac57c6e7b64dd026210.JPG</src>
        <authentication>00a56cbe3f8a2ece9cbe7bac381ac094</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="315">
                <text>Edward Vasquez</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="316">
                <text>I am confident I know the purpose of Newbury St as of today: it is a shopping district, targeted toward affluent people. But it was not its only use historically—I walked by the old American Academy of Arts and Sciences building dedicated to Harvard’s own Louis Agassiz, now populated by a Gucci or a Victoria’s Secret. It is a street became commercial, an old street subsumed by shops that now reside within its shell of old Back Bay walk-ups, the new neighbors, say. And they are diverse, as well: you have the usual restaurant and food vendors to break up the shops (like a mall should), but also massage parlors, groomers—even pet shops and art galleries and a hardware store, all tailored to the Back Bay resident. What sets it apart from Faneuil Hall (another outdoor mall) and the Pru/Copley Plaza is that it does not pretend to be historical, despite incorporating historical buildings and businesses into its layout. Nor is it confusing in its design (more on that in a second). It is presented to one as a mall for malls’ sake, not as businesses brought in to break up the environment. It feels organic, in a word, like it developed naturally, though that may not necessarily be the case (depending on how you define “naturally”).&#13;
&#13;
Though it could improve: there were few, if any, seats around. Plenty of street parking, but why not have more than just the Shake Shack with tables and chairs and umbrellas for customers on a hot day? What about all the schools and churches and non-commercial buildings around: how do they fit in? What implications do these have: is this supposed to be a node, say, a central thoroughfare? I’m not so sure about that.&#13;
&#13;
Regardless, Newbury St. feels like it fits with that section of Boston, which is more commercial in character. It feels like a piece of the puzzle. The Pru, conversely, feels like a micro- puzzle itself: I would almost say it is its own little town, encased in glass and steel and marble and stone. There are shops like a mall, sure; little kiosks and carts and tour stations and benches and even a park. But it has its own grocery store, as well: there’s a Shaw’s out near the Mariott; there’s also a chapel complete with masses, and businesses and a gym somewhere and a park at the center of the shopping area and the hotel itself.&#13;
&#13;
The Pru is not an extension of the city environment but a microcosm, a miniature city within itself. And that idea is magnified to a grand scale, almost like a cathedral to the city with its giant roofs and long Roman-style hallways complete with gorgeous views of the Microsoft Store at one end and Dunkin’ on the other and grand staircases and escalators that raise you to the heights of the inside realm. But I am not sure what its purpose is, really. Is it a mall first? Then why businesses and a church? A church!1 Is it a new, much taller version of the company town, replete with everything a good employee would need? There where is the housing, or (more importantly) the parking? And why the luxury brands at every turn? This is what confuses me about the Pru area: how am I supposed to think of this place? How does it envision itself serving both the consumer and the Bostonian? Because it’s not an public space: it is a private tower, complete with security guards and no homeless people or vagrants. I am yet to understand how the Pru fits within its urban context.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="40" public="1" featured="0">
    <fileContainer>
      <file fileId="40">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/208e8a6e36fd26d516d368b6df23c67f.jpg</src>
        <authentication>fe34c9254b6ba7d637f7aba262bbb5a3</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="81">
                <text>Electra Lang</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="82">
                <text>It’s immediately obvious, looking at my map, that my knowledge of Harvard is very much concentrated on the Square and the Yard and as one gets further towards the periphery of the campus and surrounding area, my knowledge rapidly diminishes. While the center of the map is pretty accurate and recognizable as the Harvard Square area, the Quad looks absolutely nothing like how I drew it—for one thing it’s further away, but it’s also much larger with more buildings. The Law School, Mather, Dunster, the Kennedy School, the Business School, and much of the athletic complex fare the same way. I even forgot Leverett’s dining hall. &#13;
&#13;
Many of my angles are wrong too: JFK street is parallel to Holyoke and Dunster, whereas mine are at angles, creating very wide blocks in some places. The intersection of Quincy Street and Mass Ave is disproportionately large and the block with the Old Inn is in the wrong place. It’s interesting that in many cases the shapes of blocks I generally got right, but their relations to one another are often off. &#13;
&#13;
Scale, too, posed a problem. The Science Center is enormous (about a quarter the size of the whole of larger Harvard Yard), while Memorial Hall is too small. Boylston and Dudley ended up tiny. Blocks which should be near the same size, aren’t. Kirkland (one of the smallest houses) is hue in my map as a result of the incorrect angle of JFK. The connecting bridge between the Yard and the Science Center is also not wide enough in proportion to the rest of the plaza and the part of Mass Ave by the Common more than doubles in width. &#13;
&#13;
Though I’m largely pretty accurate towards the center of the map (it’s telling that I unconsciously centered the entire thing almost exactly on my dorm (Claverly), pushing the map too far to the left on the page), there are certain blocks where I could recall almost nothing about what was in them, despite walking past them nearly every day. There are also many storefronts which I completely forgot about, though I was fairly certain I could remember all the stores in a certain stretch. &#13;
&#13;
I chose to focus my map mostly on the green spaces in and around the Square and on the pattern of traffic flow—the latter of which can get quite tricky around here and so was fun to think through. By picturing every street corner to myself and trying to call up which way the cars passed me, I was able to reconstruct quite accurately the directions of traffic flow, though I’m seldom ever in a car here. As for the green spaces, my approximation of their distributions in the yard and in the quads of various houses is sometimes quite accurate and sometimes wholly off, leading me to think that what was guiding me in drawing them was less real memory of what they looked like and more the knowledge of the fact that they had to be there.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="126" public="1" featured="0">
    <fileContainer>
      <file fileId="162">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/b124996534d512ededf833f8125712b1.jpg</src>
        <authentication>a555ffc01692de7b6561009108f47f7b</authentication>
      </file>
      <file fileId="163">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/3e0990085d47f6ef2ef57a0cd47f5d8c.jpg</src>
        <authentication>df5a2e201050228f5bf2a9300c6256c5</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="253">
                <text>Electra Lang</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="254">
                <text>What’s fascinating about the Prudential Center and Copley Square malls is the way in which they both seek to simultaneously evoke the covered shopping street and, more complicatedly, the dynamics of a small market town. In the first case, the peaked glass roofs call to mind an arcade, a feeling added to by the occasional kiosks placed in the path. These particular malls are not merely a collection of little shopping streets, but a collection organized around central town square-like open places. I chose to focus my sketch on one of these places, which is not merely shapes as a town square with four main ways leading to and away from it, but contains a fountain (albeit a quite modern one), plant-life, plenty of natural light from a huge glass ceiling several stories up, and benches to sit on. The fountain is even filled with pennies, just as one in a town square might be. The storefronts, too, add to the illusion of being outside as they all are designed differently, as if they were actually separate buildings on a street (Williams Sonoma is actually designed to look like an old-fashioned shop front). The malls are arranged as a series of these “squares,” linked together by generally straight and not-too-long walkways. In the Copley Square Mall, these are lined in a pink marbleish material and their main part is of herringbone pattern brick, again recalling an outdoor street (perhaps of an older market town). These pathways are almost entirely devoid of places to sit or pause (this is truer of the Copley Mall than the Prudential Center) and instead function to keep people moving—moving towards more stores or towards the squares, where there are places to sit. I rarely saw anyone pause for long in these walkways, nor did anyone deviate from the general traffic plan of walking on the right side. All walking looked purposeful and barely anyone was there alone. &#13;
&#13;
Newbury Street, unlike the malls, does not have a captive audience to work with and so the signage on the street is adapted accordingly. Whereas in the malls, the names of stores simply appear above their doorways, on Newbury St almost every shopkeeper has devised some sort of sign for his establishment which will present itself directly to the eye of the pedestrian—whether a sandwich board on the sidewalk or a sign protruding perpendicularly from above the doorway. Whereas everyone in a mall is almost certainly there to shop, this is not necessarily the case on Newbury St as it is also simply a street, and so shopkeepers must do what they can to attract not only the shopper, but the random passerby. In order to further accommodate shoppers, Newbury St has been made particularly convenient for pedestrians, who control the traffic at most intersections as a result of the one-way traffic and stop signs. Making it more mall-like, there is not only parking on every available inch of the street, but the commercial section of the street is flanked by parking lots, making the street more conducive to the all- day shopping expeditions more usually associated with the shopping mall.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="7" public="1" featured="0">
    <fileContainer>
      <file fileId="7">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/7006f49fcb7c2526910550aad3f81b80.pdf</src>
        <authentication>0416dbf7b7e27066fadf859d211ed6fe</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="18">
                <text>Elena Breer</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19">
                <text>The end result of my map sketch, while being nowhere close to completely accurate, was actually considerably more on target than I had anticipated. While working on this project, I realized how many spaces on campus I pass through regularly without ever taking a moment to consider my environment. This was a disappointing realization for me to make, as I like to think that I am in tune with my surroundings, and I often make a point to appreciate the world around me. However, to me, this experience points out a difference between appreciating scenic beauty, such as the trees or green ivy against a brick wall, and truly considering your environment, including the dynamics of how the space is used and how it was designed. Throughout the process of this sketch assignment, I became a bit more aware of my surroundings, especially when passing through unfamiliar areas and areas of high traffic. I was much more conscious of the way certain streets fit together, of the walkways people tended to prefer—sometimes astray from the intended path—and the areas where people tended to congregate. It encouraged me to take routes I less often travel by and was an excellent exercise in mindfulness.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="96" public="1" featured="0">
    <fileContainer>
      <file fileId="104">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/2b15a0c82a860f0203da46da28ac7675.JPG</src>
        <authentication>d7b77b6cb4369643dc50afc7440daecf</authentication>
      </file>
      <file fileId="105">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/55f4e87d0a0f9b3716de9a136252997f.JPG</src>
        <authentication>f2daa55d47dd3a204ed6ccc0093de7dd</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="193">
                <text>Elena Breer</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="194">
                <text>My map of Newbury Street is actually a combination of multiple segments of Newbury: the image of the street and walkways depict the segment between Gloucester and Dartmouth, where the storefronts, which are former residential spaces turned commercial, are abutted by small, gated gardens. This street segment however is disjointed from its actual location and is instead depicted as adjoining to Boylston, which runs along the Boston Public Garden. I did this in light of our recent discussions concerning how the pastoral appeal of natural gardens attracts society’s upper classes—exactly the type of people who would do their shopping in a high-end commercial space like Newbury Street. My map also depicts a bold black line of storefronts, with the shop entryways marked by blue lines. This demonstrates the vague sense of separation and inaccessibility that I—a person who does not typically shop such high-end brands—felt while passing through the space. In comparison, the shops in Copley Center, which were for the most part just as high-end as those on Newbury, felt somewhat more accessible because of the casual, communal nature of shopping malls. Because I felt more integrated into the atmosphere, I was more comfortable entering into a high-end store in Copley than I would have been entering into an equally pricy store on Newbury. The mall also featured multiple layers of elevated walkways and various overlapping shopping levels, which were easily accessible by a series of escalators, elevators, and staircases that connected all the traffic areas in a somewhat complex network. The walkways were wide, and the high ceilings and glass architecture contributed to a sense of spaciousness that is often associated with affluence. The Copley equivalent to Newbury’s small front yard gardens was its central atrium, an area with a water feature and live plants, surrounded by seating. Prudential had a similar parallel: its large outdoor courtyard, which features a grassy area, trees, and a fountain. Interestingly, the transition from Copley to Prudential brought about some noticeable atmospheric changes. The walkways of Prudential were narrower and divided down the center by kiosks selling cheap wares. The shops were also more diverse and slightly less high-end than Copley’s, although this may have been a false perception influenced by the less grand atmosphere of the Prudential shopping center, and also the fact that some commercial spaces were empty due to construction.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="188" public="1" featured="0">
    <fileContainer>
      <file fileId="277">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/eb5baf9e6a8ebbc5d389472622b8ac8b.jpg</src>
        <authentication>edc3497c08259dd79feb2a4e33490678</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="375">
                <text>Eliot Harrison</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="376">
                <text>In my map of Harvard, I prioritised the spaces that I interact with. I largely ignored places across the river, in the quad, or beyond the Science Center, because I rarely venture to those areas of the campus. I live in Eliot House. I started my sketch at this intersection between the river and JFK Street which leads up to the Square and the Yard. Sketching showed me that everything—campus, shops, streets—are crammed into a dense area. However, shops are clearly delineated from campus. While the buildings are physically close together, the stores in Harvard Square occupy an entirely different world than the college. This includes residential Houses. As a result, an urban campus exists without being hectically intertwined with the city around it. Doing my sketch, I think I did a pretty good job at mapping the streets, as they follow a loose grid. Towards the edge of campus, I found that I didn’t know what to draw next because, as I wrote earlier, there are places that I just don’t go. I tried to draw pedestrian traffic in blue pen as a nebulous, sprawling mess. I thought about where I walk on any normal day and thought about how many people I might see around me at those times.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="105" public="1" featured="0">
    <fileContainer>
      <file fileId="122">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/cc5bc93634aef0249e390d2394d5b154.jpg</src>
        <authentication>deeb4c920a27c35a2a63848359cb1ae0</authentication>
      </file>
      <file fileId="123">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/6fe001894d132ea818c07a96bf46f407.jpg</src>
        <authentication>a78980c7abacefdb4ad9ba75524f2057</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="211">
                <text>Eliza Decubellis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="212">
                <text>Examining these two different commercial spaces was very interesting because it became evident how they were trying to imitate one another, but also how different they still were. To start, I went to the Prudential/Copley Malls, and I noticed that the use of glass both in storefronts and in the walls and ceilings was very prominent. This creates a fluid feel between indoors and outdoors to make the shoppers feel like they are in a more natural and less commercial, man-made space. The use of plants and large greenery in certain spaces also helps to achieve this natural feel, as does a large outdoor garden that can be clearly seen right outside the mall through large glass walls. The smaller signs hanging off many of the storefronts (which I tried to portray in my sketch) also give the feeling of walking down an outdoor street with small boutiques all in a row. The high, uneven, glass ceilings are also artfully constructed to blend in with the natural sky and give a very open feeling. The people in the space seem to mainly be there to shop and spend money in some way, whether that is in shops or in restaurants, but there are also a few gathering spaces with seating near the foliage and large windows. The entrances and exits to the mall are very streamlined because they are only in a few, designated spots, so it seems to attract people who are coming in with a purpose (and with money to spend). &#13;
&#13;
I then went Newbury Street and sat across from Shake Shack (between Fairfield and Exeter Streets) to observe that space. The commercial aspects of the space are comparable to the indoor mall because all of the stores are very close together, and they utilize the same large, glass storefronts to display goods and small signs hanging off the buildings with the store names. However, the interesting thing about Newbury Street is that it is very clearly a space used for activities other than commerce as well, so people just out walking with dogs or kids or friends are integrated with shoppers. The entrances and exits to the streets also reflect this inclusivity because they are much more decentralized than they are in the mall – you can enter and exit from many different side streets – so anyone, even those who are just passing through without any intention to spend money, can experience the space. There are also people hanging out and doing things they love like playing music on the street, which is actually in an attempt to make money rather than spend it. The obvious presence of cars and the sounds that accompany them also point out how different this space is from a mall and how much more integrated it is into the urban fabric, which differs from the man-made, disruptive indoor mall.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
