<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="992" public="1" featured="0" 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="http://collections.ecu.edu/items/show/992?output=omeka-xml" accessDate="2026-04-16T04:31:54+00:00">
  <fileContainer>
    <file fileId="1195">
      <src>http://collections.ecu.edu/files/original/34/992/PuertodeFrutosMakaylaHarris.pdf</src>
      <authentication>713bd806e8e31d6b5a4d6110a3b7b392</authentication>
      <elementSetContainer>
        <elementSet elementSetId="4">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="92">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="3547">
                  <text>Puerto de Frutos is located in Tigre. It is a marketplace, approximately six blocks worth. Puerto de
Frutos is not like any other. It is as if each department of Walmart had its own shop and then some. You
can get just about anything at this large marketplace. Fresh fruit, bags, scents, lamps, kitchen
appliances, the list goes on. It is the place for shopping for souvenirs and gifts for your family and
friends. You can find something for everyone at a reasonable price. Most importantly, it is the spot to
get the cheapest Mate cups and straws. Mate is a large part of Argentinian culture, especially near the
region of Buenos Aires. There is also a good selection of restaurants to choose from. There is a great
view of the Lujan River. There is even a peaceful boat tour around Tigre, which is a great break from the
city. Puerto de Frutos along with other activities surrounding the marketplace is a day long excursion.
Be sure to have three or more hours for shopping and a quick lunch break.

�</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </file>
    <file fileId="1219">
      <src>http://collections.ecu.edu/files/original/34/992/tigre-argentina-puerto.jpg</src>
      <authentication>ac61a35211250f438103e110e318d11a</authentication>
    </file>
  </fileContainer>
  <collection collectionId="34">
    <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="3480">
                <text>Digital Buenos Aires</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3481">
                <text>Digital Buenos Aires</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3482">
                <text>Digital Buenos Aires</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3483">
                <text>Irina Swain, Brandon Sugg, Laura Levi Altstaedter, Magali Krosl</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3484">
                <text>Irina Swain, Brandon Sugg, Laura Levi Altstaedter, Magali Krosl</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="3527">
              <text>Puerto de Frutos, El Tigre, Buenos Aires Provence</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="3528">
              <text>The Puerto de Frutos marketplace in El Tigre, Buenos Aires Provence</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="3529">
              <text>Makayla Harris, Brandon Sugg</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
