<?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://usworld24.omeka.fas.harvard.edu/items/browse?output=omeka-xml&amp;page=4&amp;sort_field=Dublin+Core%2CCreator" accessDate="2026-05-09T13:53:51-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>4</pageNumber>
      <perPage>10</perPage>
      <totalResults>343</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="10" public="1" featured="0">
    <fileContainer>
      <file fileId="10">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld24/original/67a5952e6cefb8fa691f07379876903e.png</src>
        <authentication>93d2c8c5fbc81a9f82cb7aeb37fbb2a9</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>Final Projects Spring 2015</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="32">
                <text>Visits to the New England Aquarium and Franklin Park Zoo  </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="33">
                <text>My paper focused on the roles that institutions like the aquarium and zoo play in a city like Boston. Both institutions offer people a unique experience to see and sometimes interact with animals that are usually only seen on television or films since they come from all around the world. Some of the questions that I’ve tried to answer are how do people explore these sites? What are the things people do and don’t do? Who goes to these sites? Do they promote social cohesion among its community members or is social mixing confined to the group one comes in? </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="34">
                <text>Naddy Camacho</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="38" public="1" featured="0">
    <fileContainer>
      <file fileId="38">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld24/original/60d062159b9bd3a1fe7aaa268ae7c41a.png</src>
        <authentication>97440a0e2c259d504b141554084c9d61</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>Final Projects Spring 2015</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>Neighborhood Borders: Exploring behavior on the boundary and way-finding in the North End&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="116">
                <text>My project focuses on the North End in Boston, a unique part of the city as it has a dual role as a residential neighborhood and tourist attraction. After finding the street layout of the North End drastically different from the city around it, I decided to focus on how the boundary between the North End and the rest of the city is received by those who cross into and out of the neighborhood. In particular, in my fieldwork, I focused on the behavior of tourists and of residents as they entered and exited the North End on the boundary line, which I claim to be where the North End meets the Rose Kennedy Greenway. I focused on two street corners, Hanover and Salem Street, finding that the behaviors of tourists/outsiders differed from those of residents, particularly in terms of how many people travelled together and the pace at which they entered and exited the neighborhood. To complement behavior on the boundary, I also looked into way-finding in the neighborhood itself and what it meant for each group, tourists versus residents, respectively. The purpose of the project is to shed light on how neighborhood boundaries and borders are received by those who interact with it and what types of mechanisms govern how people find their way through the neighborhood.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="117">
                <text>Natalia Rzepka</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="30" public="1" featured="0">
    <fileContainer>
      <file fileId="30">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld24/original/8b033fe35f942a41dd0f871e2d6c06bc.png</src>
        <authentication>1b3db470629ef48a4f9b4485656b6336</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>Final Projects Spring 2015</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="91">
                <text>The Red Sox’s Unification of the City of Boston</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="92">
                <text>I leave my room wearing the only Red Sox gear I own: the traditional navy t-shirt with red block letters displaying the team’s name prominently across the front. I remember back to when I bought it while attending a Red Sox game five years ago. As a high school sophomore, I accompanied my dad on a trip to Boston. The two of us, avid sports fans, couldn’t possibly leave the city without visiting the sacred ground of Fenway Park. Like Michael Borer finds of tourists from around the country in Faithful to Fenway, my dad and I wanted to “become part of a shared history of triumph and tragedy, heroes and villains, beer and hot dogs…[by making the] pilgrimage to Fenway to pay homage to one of American culture’s most cherished shrines.”  Five years ago, we arrived at the game about two hours before the opening pitch, taking the opportunity to walk along Yawkey Way, observing the throngs of loyal fans mingling with and jostled by baseball enthusiasts from around the country. I remember taking it all in as we pushed our way through the crowd: the aromatic smoky sausage fresh off the grill, the warm, sticky beer spilling over the edge of its cup as its owner simultaneously attempts to put away his wallet and text among the hoards, the men on stilts moving clumsily along the road while yelling chants to excite fans. I remember walking into one of the memorabilia shops, perusing the various gear options, and finally selecting the shirt I am wearing today.&#13;
Through a series of interviews with fans on April 19th, before and during the Red Sox versus Orioles game, I explore the power of the team to unify the city, allowing the narratives of individuals attending the game to express the place and collective identity of the Red Sox and Fenway Park. I describe the unifying feature of the team through the way the Red Sox permit remote fans to retain their connection to Boston, through the unwavering obsession of fans transmitted through generations and shared between family members, and through the veneration of Fenway Park that attracts people simply passing through the city. &#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93">
                <text>Orlea Miller</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="45" public="1" featured="0">
    <fileContainer>
      <file fileId="45">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld24/original/fc3ea128e5c2eaa23c1bf53f95a268c2.png</src>
        <authentication>ad8b0ea3b431f993eb9ad68d7e27c024</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>Final Projects Spring 2015</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="136">
                <text>Boston Busing and Desegregation: An Examination of this Topic’s Inclusion in the Boston Public Schools Curriculum</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137">
                <text>This paper discusses the recent addition of the topic of Boston’s court-ordered desegregation and the resulting busing riots into the Boston Public Schools history and social studies curriculum. It examines the reasons why the topic was not previously included, the factors that led to its present inclusion, and the reactions of teachers and parents. The paper also looks at the potential long-term impacts of the curriculum addition and makes suggestions for its improvement in the future. It draws on interviews with teachers, community leaders, and members of the BPS history department.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138">
                <text>Paige Wallace</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="5" public="1" featured="0">
    <fileContainer>
      <file fileId="5">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld24/original/266854b229a92aa68803745146f83441.png</src>
        <authentication>6ff85ac45efba079bcb888ace8c10f8b</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>Final Projects Spring 2015</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="17">
                <text>A Community Resource? An Examination of the Museum of Fine Arts’ Hours of Voluntary Admission Fee</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18">
                <text>Boston’s Museum of Fine Arts (MFA) is ranked as one of the “most comprehensive art museums in the world,” boasting a collection of nearly 450,000 works—ranging from Ancient Egyptian artifacts to pieces of Contemporary Art. Access to such an incredible institution does not come without a corresponding price, though. During most hours, a general admission ticket to the Museum costs $25 for an adult, which is not affordable for many visitors. Fortunately, the Museum has launched several initiatives to help make the MFA’s collection and programming more accessible. One of the oldest and most well known of these initiatives is their hours of voluntary admission fee: on Wednesday nights after 4pm, visitors can choose whether to make a contribution to the MFA during their visit or to simply enter the Museum for free. Offering hours of voluntary admission fee has furthered the MFA in its mission of “serving a wide variety of people through direct encounters with works of art” by providing an opportunity and an incentive for people from diverse geographical regions and of diverse socio-economic backgrounds to come together and learn from the Museum’s collection and programs. After almost 100 informal interviews with Boston residents and visitors to the MFA, four sessions of observations at the MFA, and an examination of data released by the MFA, I learned that this this initiative does not, however, advance another of goal of the MFA—“to benefit the City of Boston”—for primarily four reasons. First, the hours of voluntary admission fee do not benefit only residents of Boston. Similarly, they do not benefit only people who would otherwise face financial barriers to visiting the Museum. Furthermore, this initiative alone does not address other barriers some residents face to accessing the Museum (including the price of commuting to the museum, lack of flexibility in scheduling visits to the Museum, and a lack of awareness about opportunities to access the Museum.) Finally, the relatively busy hours of voluntary admission fee could possibly interfere with visitors’ ability to learn about or become interested in the MFA’s collection, which works against the Museum’s “ultimate aim...to encourage inquiry and to heighten public understanding and appreciation of the visual world.”&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19">
                <text>Sarah Allen</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="24" public="1" featured="0">
    <fileContainer>
      <file fileId="24">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld24/original/c7c338c65127962cfa768b8784273f91.jpg</src>
        <authentication>ff995f5809f50418207fa48bbcabc1ab</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>Final Projects Spring 2015</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="73">
                <text>Urban Gardens Grow A Community</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74">
                <text>My paper is about the Fenway Victory Gardens and questions the continued promotion of its existence as an urban garden for the Boston community since World War II. Because it is obviously no longer in use as a World War II Victory Garden, I was curious about why gardeners might continue to be so passionate about its existence, even fighting movements to put important institutions such as hospitals and schools in this park area. My idea was that the group of gardeners who use this land for a sort of community, so using ethnography, I observed the interactions between gardeners and non-gardeners to find if there could be some social benefit from these gardens that is worth protecting and less obvious than its other benefits, such as aesthetic value and historic value.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="75">
                <text>Scout Leonard</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="34" public="1" featured="0">
    <fileContainer>
      <file fileId="34">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld24/original/616a720aa098fc7c4256a389b6b1c42d.png</src>
        <authentication>4716b7d4f51cc1e30f9066aff4fa5775</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>Final Projects Spring 2015</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="103">
                <text>Revitalizing Boston’s Transportation Infrastructure: The Impact of an Olympic Bid</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="104">
                <text>My paper is a policy memo addressed to the governor of Massachusetts, the mayor of Boston, and the state secretary of the department of transportation, detailing the potential for the Boston Olympics to improve the transportation infrastructure in Boston. The memo addresses many public concerns regarding the games, and includes analyses of previous Olympics, interviews with experts in the field, and an analysis of a potential new system of development for the MBTA to pursue. The memo presents three policy decisions for the relevant government stakeholders to pursue.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105">
                <text>Stefan Rajkovic</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="41" public="1" featured="0">
    <fileContainer>
      <file fileId="41">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld24/original/2edf9cdee2605945c2c62ea68609a3ac.png</src>
        <authentication>23aa29fa985128174519727bd889be7b</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>Final Projects Spring 2015</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="124">
                <text>The Readville Guys</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="125">
                <text>My dad grew up in a small part of Boston called Readville, located in the southern-most tip of Hyde Park between Dedham and Milton. He grew up playing baseball and hockey in the public parks of Readville with all of his friends. These friends, the “Readville Guys,” I call them, are still friends today. Although my father passed away nine years ago, I still see the members of this incredibly tight-knit group a few times a year. When we’re together, I become a part of the audience to their stories, as the mere presence of another Readville Guy brings out a shower of memories. For this project, I was motivated to learn about how the group got so close during their time in Readville, and what about the small neighborhood of Boston kept them close over time. I learned a lot about the strength of their friendship and their loyalty to their common roots. They have enormous pride for Readville. I entered into this endeavor with an understanding of the fun surface-stories, and learned beyond those about the times when they were really there for each other. I am coming away from this project with a stronger understanding of their group dynamic and what makes it as strong as it is, and I am left to compare the longevity of this group’s friendship to that of my own hometown friends. This project is in many ways not done. There is a lot more to unpack and understand. I don’t want people to think that my brief interpretation of what they said and what I captured in conversation is the true character of this group, but I understand that this may be the first step to ever actually achieving that. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="126">
                <text>Tanner Skenderian </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="19" public="1" featured="0">
    <fileContainer>
      <file fileId="19">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld24/original/80d75b198fd43641235d8afb637739fb.png</src>
        <authentication>7c27eede123cb0a7d4437b499e4dee97</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>Final Projects Spring 2015</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="59">
                <text>Fenway Park in the Context Fenway</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="60">
                <text>	With my paper, I am examining Fenway Park in the greater context of the Fenway-Kenmore neighborhood. I originally hoped to hear from someone on the Fenway Community Development Committee, but no one returned my correspondences in time. So, I substituted by looking for older news stories about the Fenway CDC’s most recent revitalization efforts. After writing about that for a bit, I will move on to talking about my trip to Fenway. I went down during a game to examine that neighborhood and how the stadium fits in, but also the overall atmosphere of the people at the time. Finally, I would go to a bar during the game to see more of the atmosphere and how the game itself feeds into it (without spending the money on an actual game ticket). I visited during a Tuesday night home game, and after surveying the perimeter, went into The Lansdowne.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="61">
                <text>Theo Gerome</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="26" public="1" featured="0">
    <fileContainer>
      <file fileId="26">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld24/original/a0612b55c26958ccea2124f85c1d29b8.jpg</src>
        <authentication>46628e49958686bdaadcd14ef0431a6f</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>Final Projects Spring 2015</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="79">
                <text>“She may ride forever ov’r the streets of Boston”: Exploring Boston’s Bus System</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="80">
                <text>	In order to learn more about the different neighborhoods of Boston, I decided to study the people taking various bus routes from Harvard and record their demographics as well as their interactions with each other. I ended up taking the 86 to Sullivan Square Station, the 73 to Waverly Square, the 71 to Watertown Square, the 77 to Arlington Heights, and the 66 through to Dudley Station. I found that although the demographics of each bus ride clearly depend on the time one takes it, it’s still possible to notice certain trends at any time. The racial composition of each bus ride was fairly reflective of what is indicated by official census records in each neighborhood. Gender did not appear to matter and SES was hard to estimate from simply observing people. However, I was surprised at just how much age mattered. Although it wasn’t always the best predictor of what neighborhood we were traveling through, it often indicated information about the purpose of one’s bus trip (e.g. younger students, older retired people with time to travel during work hours, etc.). Also age factored into what people did on the bus (e.g. young people were more likely to use their phone while older people read hard copies of books or newspapers). Interactions among passengers were much more limited than I had expected and I was surprised at the stark contrast of these experiences to the times I have taken the sociable and loud T. The routes the buses take are far more residential and thus more likely to be a solitary activity. The T also appears to be taken more for fun while, based on the number of grocery bags I saw, buses are used for chores in addition to work or school. These bus commutes are worth studying since they isolate many of the variables that may get lost in the more hectic and tourist-filled T system. By further studying the people who are taking the bus and why they are doing so, not only could we learn more about each neighborhood, we could learn more about how each neighborhood interacts with others.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="81">
                <text>Virginia Marcus</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
