<?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="http://dar.cah.ucf.edu/items/browse?output=omeka-xml&amp;page=40" accessDate="2026-05-10T12:32:19+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>40</pageNumber>
      <perPage>10</perPage>
      <totalResults>454</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="86" public="1" featured="0">
    <fileContainer>
      <file fileId="158">
        <src>http://dar.cah.ucf.edu/files/original/a2d20986d7bf6569e7d49de9f7df1ca2.jpg</src>
        <authentication>ab2705193db5538fd76de9e96d0dd006</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12038">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12039">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12040">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12041">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="12">
      <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="26250">
                  <text>Ethics, Privacy, Copyright, and Legislation</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26251">
                  <text>This collection represents the delicate balance digital archivists seek when designing an archive that preserves and provides access, while also ensuring all parties' right to privacy and intellectual property. Also known as risk management, archives must anticipate potential infringements of intellectual property and privacy rights, and guard the public's right to free and open access. Items in the collection address risk management issues and underscore the necessity for keeping current in legal and ethical archival practices.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="17">
      <name>Online Journal</name>
      <description>An item published by an online journal or magazine.</description>
    </itemType>
    <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="24910">
                <text>The Right to Preserve: The Rights Issues of Digital Preservation&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24911">
                <text>The project's goal was to research how and whether licensed access to digital content and copyright legislation affected the capability of libraries to offer long-term availability to that specific content, and to advise possible answers for any issues identified. This article looks at the international perspective of general identified issues pertaining to copyright laws and publisher licenses.   </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24912">
                <text>Ayre, Catherine </text>
              </elementText>
              <elementText elementTextId="24913">
                <text>Muir, Adrienne</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="24914">
                <text> </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="24915">
                <text>D-Lib Magazine</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24916">
                <text>2004</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24917">
                <text>Victoria Polk </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24918">
                <text>Digital Preservation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24919">
                <text>Journal Article</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="24920">
                <text>http://www.dlib.org/dlib/march04/ayre/03ayre.html</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="290">
            <name>Bibliographic Citation</name>
            <description>A bibliographic reference for the resource. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.</description>
            <elementTextContainer>
              <elementText elementTextId="24921">
                <text>Ayre, Catherine and Adrienne Muir. "The Right to Preserve: The Rights Issues of Digital Preservation." &lt;em&gt;D-Lib Magazine &lt;/em&gt;v. 10, no. 3. (2004). &lt;a href="http://www.dlib.org/dlib/march04/ayre/03ayre.html"&gt;http://www.dlib.org/dlib/march04/ayre/03ayre.htm&lt;/a&gt;l</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27719">
                <text>Copyright</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="191">
        <name>content management</name>
      </tag>
      <tag tagId="54">
        <name>copyright laws</name>
      </tag>
      <tag tagId="318">
        <name>library</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="85" public="1" featured="0">
    <fileContainer>
      <file fileId="159">
        <src>http://dar.cah.ucf.edu/files/original/db7dc3ebdf28c959729fb6c4182c5576.jpg</src>
        <authentication>ab8d68421c96000f485ab01f67ecca24</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12048">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12049">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12050">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12051">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="12">
      <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="26250">
                  <text>Ethics, Privacy, Copyright, and Legislation</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26251">
                  <text>This collection represents the delicate balance digital archivists seek when designing an archive that preserves and provides access, while also ensuring all parties' right to privacy and intellectual property. Also known as risk management, archives must anticipate potential infringements of intellectual property and privacy rights, and guard the public's right to free and open access. Items in the collection address risk management issues and underscore the necessity for keeping current in legal and ethical archival practices.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="17">
      <name>Online Journal</name>
      <description>An item published by an online journal or magazine.</description>
    </itemType>
    <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="24922">
                <text>Exploring the Evolution of Access: Classified, Privacy, and Proprietary Restrictions</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24923">
                <text>Copyright</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24924">
                <text>The three authors of this article discuss three different repositories which house confidential, legally protected content and describe measures each institution takes to balance the archival values of preserving and providing access to its holdings against the equally important archival value of protecting the privacy rights and concerns of its donors. William C. Carpenter recounts the history of declassifying military and government documents and commends the succession of presidential orders that established automatic declassification in response to the ever-growing accumulation of military and government documents. While governments frequently halt declassification of certain documents during crises, such as 9-11, or open documents as in the Abu-Ghraib debacle, the automated declassification system places the onus on the donating agencies for keeping records sealed.  &#13;
&#13;
Business archives, on the other hand, enjoy greater legal protection for sealing its records from public access. Sara A. Polirer explains U.S. trade laws and property rights consider business records economically valuable assets despite their intangible nature. Because digitization and Internet commerce place marketable ideas at greater risk of copyright infringement, and because economic value is a fundamental factor in writing legislation, business archives must implement policies that promote business needs over the public’s right to know. The archival practice, “due diligence” applies to business archives in the careful classification of content and anticipation of what future researchers may need to know. &#13;
&#13;
Health science archives face an especially difficult challenge in balancing the public’s right to know with protecting the privacy of patient records. Judith A. Wiener discusses the rationale for the patient privacy act, HIPAA, and identifies the problems incurred by health related archives ingesting health records. Because HIPAA does not designate time limits (as do military and government declassification regulations), nor does it provide guidelines for reformatting and digitizing health records, health science archives have had to restrict access and impede potential research and scholarship. In response, individual repositories and institutions are developing policies including the redactment of personally identifiable information and inserting time limits to both protect the privacy of the donors while providing access to the historically rich records. &#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24925">
                <text>Carpenter, William C. </text>
              </elementText>
              <elementText elementTextId="24926">
                <text>Nichols, Charlene </text>
              </elementText>
              <elementText elementTextId="24927">
                <text>Polirer, Sarah A. </text>
              </elementText>
              <elementText elementTextId="24928">
                <text>Wiener, Judith A. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="24929">
                <text>The American Archivist</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24930">
                <text>2011</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24931">
                <text>Polk, Victoria </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24932">
                <text>Journal Article</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="24933">
                <text>http://www2.archivists.org/sites/all/files/AAOSv074-Session602.pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="290">
            <name>Bibliographic Citation</name>
            <description>A bibliographic reference for the resource. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.</description>
            <elementTextContainer>
              <elementText elementTextId="24934">
                <text>Carpenter, William C. , et.al. "Exploring the Evolution of Access: Classified, Privacy, and Proprietary Restrictions." &lt;em&gt;The American Archivist &lt;/em&gt;vol. 74 (2011): 602:1-25. &lt;a href="http://www2.archivists.org/sites/all/files/AAOSv074-Session602.pdf"&gt;http://www2.archivists.org/sites/all/files/AAOSv074-Session602.pdf&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="191">
        <name>content management</name>
      </tag>
      <tag tagId="54">
        <name>copyright laws</name>
      </tag>
      <tag tagId="235">
        <name>digital repositories</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="84" public="1" featured="0">
    <fileContainer>
      <file fileId="160">
        <src>http://dar.cah.ucf.edu/files/original/b125978defb552a7a6639b1ba13af70f.jpg</src>
        <authentication>0e642820d24cbf94631eadb03aa2816e</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12059">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12060">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12061">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12062">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="25">
      <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="26256">
                  <text>Web Archiving</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26257">
                  <text>In 2003, the Library of Congress and the national libraries of Australia, Canada, Denmark, Finland, France, England and other countries formed the International Internet Preservation Consortium, and have spearheaded an international effort to preserve Internet content for future generations.&#13;
&#13;
This collection aims to highlight materials that pertain to the process of  preserving elements of the World Wide Web using of web crawlers for automated capture of content.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="22">
      <name>Conference Proceeding</name>
      <description>Academic papers published in the context of an academic conference. </description>
    </itemType>
    <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="24935">
                <text>A Vision of the Role and Future of Web Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24936">
                <text>Web archiving</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24937">
                <text>The history of the web and the record of its impact on society may never fully be realized if measures to record and preserve its content are not carefully and consistently maintained. Leetaru identifies the inconsistencies in web archiving by public institutions, such as the Library of Congress, and commercial enterprises, such as the New York Times. He explains current trends for limiting the size of the “crawl” (ingesting web content into the archive) and the web site’s rate of change may not promote discovery of patterns and insights for future scholars and historians. Leetaru proposes web archiving institutions solicit the users and data miners for selecting and presenting the web archive’s content and developing the protocol for ingesting web artefacts.&#13;
&#13;
In addition to increasing the collaboration of a broad web archiving community, Leetaru suggests web archives should also increase the visibility of its holdings and provide sufficient contextual information for the different versions and replacements of web content. Like Wikipedia’s chronology of updates and editions for each page of content, Leetaru believes a web archive should reveal the source code as well as origins of its content. In response to copyright restrictions and rights to privacy, he recommends “snapshots” and limiting algorithms to “surface-level analyses.” By opening access to the intellectual content of the web artefacts and simultaneously adhering to both property and technical standards, preservation of the web archive and the potential for future research can be assured.&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24938">
                <text>Leetaru, Kalev</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="24939">
                <text>University of Illinois</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24940">
                <text>2012</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24941">
                <text>Polk, Victoria </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24942">
                <text>Document</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="24943">
                <text>http://netpreserve.org/sites/default/files/resources/VisionRoles.pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="290">
            <name>Bibliographic Citation</name>
            <description>A bibliographic reference for the resource. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.</description>
            <elementTextContainer>
              <elementText elementTextId="24944">
                <text>Leetaru, Kalev. "A Vision of the Role and Future of Web Archives." A paper presented at the 2012 General Assembly of the International Internet Preservation Consortium, Washington, D.C., &lt;span class="field-content"&gt;April 30 - May 4, 2012.&lt;/span&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="167">
        <name>community archiving</name>
      </tag>
      <tag tagId="191">
        <name>content management</name>
      </tag>
      <tag tagId="37">
        <name>open access</name>
      </tag>
      <tag tagId="97">
        <name>web archiving</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="82" public="1" featured="0">
    <fileContainer>
      <file fileId="161">
        <src>http://dar.cah.ucf.edu/files/original/4d4100df560fd53ec60f41f960139e7b.jpg</src>
        <authentication>933aecb58d8ebb9c49b13f60e7b12937</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12084">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12085">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12086">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12087">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </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="26244">
                  <text>Preservation Issues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26245">
                  <text>Preservation in the archive involves the process of historical representation and connotes security, safety, and assurance that the collections will remain intact and uncorrupted for future generations to enjoy. Digital collections pose unique preservation challenges and require an assessment of risks, both material and intellectual, as part of the planning and  management policies. These entries illuminate standard archival preservation practices and present future trends.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="17">
      <name>Online Journal</name>
      <description>An item published by an online journal or magazine.</description>
    </itemType>
    <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="24945">
                <text>Practical Limits to the Scope of Digital Preservation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24946">
                <text>Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24947">
                <text>Mike Kastellec explores the technological and non-technological factors that impede a digital collection’s long-term sustainability. The technical issues, data loss and technical obsolescence affect all types of collecting institutions, including digital archives, libraries, and museums, and Kastellec argues such factors are continuously improved due to the intense focus devoted to their solution by most digital collecting institutions. However, the non-technological factors including access, selection policies, legal issues, and finances typically receive less attention and are, therefore, the greatest impediments to the collection’s sustainability. Kastellec identifies financial sustainability to be the ultimate limiting factor and explains that while the solution, creating redundant copies off-site, may currently be the best solution, the dynamics of all non-technological factors should receive greater focus and study for long-term preservation.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24948">
                <text>Kastellec, Mike</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="24949">
                <text>Information Technology &amp; Libraries</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24950">
                <text>2012</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24951">
                <text>Polk, Victoria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24952">
                <text>Journal Article</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="24953">
                <text>http://ejournals.bc.edu/ojs/index.php/ital/article/view/2167/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="290">
            <name>Bibliographic Citation</name>
            <description>A bibliographic reference for the resource. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.</description>
            <elementTextContainer>
              <elementText elementTextId="24954">
                <text>Kastellec, Mike. "Practical Limits to the Scope of Digital Preservation. &lt;em&gt;Information Technology &amp;amp; Libraries &lt;/em&gt;31, issue 2 (2012): 63-71. http://ejournals.bc.edu/ojs/index.php/ital/article/view/2167/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="346">
        <name>digital technologies</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="74" public="1" featured="0">
    <fileContainer>
      <file fileId="162">
        <src>http://dar.cah.ucf.edu/files/original/c7b967dcadca38724ae9513721b827ed.jpg</src>
        <authentication>46887c8816324d62035c5e0f43a3b40b</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12113">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12114">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12115">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="12116">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="11">
      <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="26246">
                  <text>Digital Humanities</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26247">
                  <text>Digital archiving is gaining increased attention by both the general public and the scholarly community. The proliferation of digital content through networked channels raises cultural awareness of the ephemeral as well as ubiquitous nature of digitization. This collection highlights critical arguments regarding the digital humanities and digital archiving. The featured studies provide a broad cultural context and essential questions for archive creation and scholarly digital humanities research.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="15">
      <name>E-Book</name>
      <description>Electronic version of printed book.</description>
    </itemType>
    <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="24955">
                <text>Understanding Digital Humanities</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24956">
                <text>Digital Humanities</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24957">
                <text>In his introduction to Understanding Digital Humanities, David Berry traces the history of digital humanities—an evolving method and theory of interpreting the effects of  digitization and computation on society and culture, while simultaneously adopting and inventing computational processes for guiding its nascent discipline. Notable scholars and pathfinders in the field were selected to write the essays featured in this book, which illuminate fundamental and often controversial issues of the digital humanities,. These issues include the relationship between computation and literacy, aesthetics, gender studies, and the invention and application of data mining tools for interpreting vast quantities of cultural data. &#13;
&#13;
Of particular interest to the digital archivist is the Jussi Parikka’s essay, “Archives in Media Theory: Material Media Archaeology and Digital Humanities.” Parikka believes the archive offers a basis for theory and theoretical backing for digital humanities work, especially studies that focus on calculating effects and representing patterns. The non-narrative, non-discursive, and database logic of the archive presents a digital space, a metaphor, and a method for ingesting and interpreting the vast amount of information transmitted daily through digital media. By breaking down the study of digital media and culture into a study of the digital object’s materiality, its purposes, its historical and cultural context, and its representation and preservation, the archive as method becomes apparent—an apt metaphor Berry uses to describe the Internet’s resources, the “new infinite archive.” &#13;
&#13;
Digital archivists will also find the final chapter, “Transdisciplinarity and Digital Humanities: Lessons Learned from Developing Text-Mining Tools for Textual Analysis” by Yu-Wei Lin, useful for promoting collaborative efforts between software engineers and humanists, and for extending the reach of archives into scholarly research and knowledge creation.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="263">
            <name>Abstract</name>
            <description>A summary of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="24958">
                <text> </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24959">
                <text>Berry, David M.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="24960">
                <text>Palgrave MacMillan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24961">
                <text>2012</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24962">
                <text>Polk, Victoria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="279">
            <name>Is Format Of</name>
            <description>A related resource that is substantially the same as the described resource, but in another format.</description>
            <elementTextContainer>
              <elementText elementTextId="24963">
                <text>Print version: &lt;em&gt;Understanding Digital Humanities.&lt;/em&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24964">
                <text>Book</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="24965">
                <text>Print ISBN: 9780230292642</text>
              </elementText>
              <elementText elementTextId="24966">
                <text> ISBN-10: 0230292658</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="290">
            <name>Bibliographic Citation</name>
            <description>A bibliographic reference for the resource. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.</description>
            <elementTextContainer>
              <elementText elementTextId="24967">
                <text>Barry, David M. &lt;em&gt;Understanding Digital Humanities. &lt;/em&gt;Houndmills, Basingstoke, Hampshire ; New York : Palgrave Macmillan, 2012.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="63">
        <name>collaboration</name>
      </tag>
      <tag tagId="257">
        <name>data</name>
      </tag>
      <tag tagId="346">
        <name>digital technologies</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="73" public="1" featured="0">
    <fileContainer>
      <file fileId="68">
        <src>http://dar.cah.ucf.edu/files/original/95f2b7dee132da713d5d9ea3db421f87.jpg</src>
        <authentication>5c19df72e350f41263ea3ccc93c90704</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9207">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9208">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9209">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9210">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="10">
      <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="26248">
                  <text>Planning, Building, and Curation</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26249">
                  <text>Archives may represent any number or size collection and institution. These different types of archives may include governmental, non-selective collecting, thematic or activist, with corresponding missions and purposes unique to each institution. The items of this collection engage the processes of archive planning, building, and curation, and also represent notable digital archives whose collections reflect their respective institution's history and community.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="20">
      <name>Journal</name>
      <description>An item printed in an academic or professional journal.</description>
    </itemType>
    <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="25060">
                <text>New Workflows for Born-Digital Assets: Managing Charles E. Bracker's Orchid Photographs Collection</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25061">
                <text>Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25063">
                <text>In this article, authors, Hurford and Runyon, describe the series of tasks and types of collaboration needed to create a digital collection. These tasks include strategies for classifying and managing files, developing metadata, establishing criteria for selecting, editing, and exporting items, and enhancing public access.  The unique challenges for creating a born-digital collection are illuminated in their detailed case study of the “Charles E. Bracker’s Photographic Digital Collection,” located in Ball State University’s Digital Media Repository. &#13;
&#13;
The authors cite the challenges of archiving Bracker’s digital photographs, including a lack of captions, context clues, and order of creation, as evidence for requiring the collaboration and expertise of various specialists. Archivists, librarians, technology systems administrators, and in this case, an orchid specialist, developed file categories, descriptive metadata fields, and developed a web interface capable of integrating and cross-referencing the data. In addition to the principle of collaboration, the authors defend the rationale for replacing a traditional archival principle, “original order,” with specialized directories--a principle of practicality necessitated by the massive amount of digital data without contextual information.&#13;
&#13;
 &#13;
&#13;
 </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="263">
            <name>Abstract</name>
            <description>A summary of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="25064">
                <text>Traditional archival processing methods and description standards often do not apply to born-digital media, requiring the development of new methods and standards.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25065">
                <text>Hurford, Amanda A. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="25066">
                <text>Computers in Libraries</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25067">
                <text>2011</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25068">
                <text>Runyon, Carolyn F. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25069">
                <text>Journal Article</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="25070">
                <text>http://eric.ed.gov/?id=EJ914845</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="290">
            <name>Bibliographic Citation</name>
            <description>A bibliographic reference for the resource. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.</description>
            <elementTextContainer>
              <elementText elementTextId="25071">
                <text>Hurford, Amanda A. “New Workflows for Born-Digital Assets: Managing Charles E. Bracker's Orchid Photographs Collection.” &lt;em&gt;Computers in Libraries&lt;/em&gt; 31.1 (2011): 6-10,40.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="299">
            <name>Instructional Method</name>
            <description>A process, used to engender knowledge, attitudes and skills, that the described resource is designed to support. Instructional Method will typically include ways of presenting instructional materials or conducting instructional activities, patterns of learner-to-learner and learner-to-instructor interactions, and mechanisms by which group and individual levels of learning are measured. Instructional methods include all aspects of the instruction and learning processes from planning and implementation through evaluation and feedback.</description>
            <elementTextContainer>
              <elementText elementTextId="25072">
                <text>The article outlines a workflow of tasks and strategies unique to the Charles E. Bracker’s Photographic Digital Collection, but common to the field of digital archiving. Key points, including file management, metadata, designing a web interface, and planning for both preservation and growth of the archive, are critical elements in building a digital archive.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="430">
        <name>archival standards</name>
      </tag>
      <tag tagId="66">
        <name>born digital</name>
      </tag>
      <tag tagId="63">
        <name>collaboration</name>
      </tag>
      <tag tagId="163">
        <name>digital conversion</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="72" public="1" featured="0">
    <fileContainer>
      <file fileId="69">
        <src>http://dar.cah.ucf.edu/files/original/76310c77da7f4df5841d886b927c6b22.jpg</src>
        <authentication>157b89e2d846981a29d675c38d0b09c0</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9243">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9244">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9245">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9246">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="10">
      <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="26248">
                  <text>Planning, Building, and Curation</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26249">
                  <text>Archives may represent any number or size collection and institution. These different types of archives may include governmental, non-selective collecting, thematic or activist, with corresponding missions and purposes unique to each institution. The items of this collection engage the processes of archive planning, building, and curation, and also represent notable digital archives whose collections reflect their respective institution's history and community.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="20">
      <name>Journal</name>
      <description>An item printed in an academic or professional journal.</description>
    </itemType>
    <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="25073">
                <text>Sustaining Community Archives.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25074">
                <text>Curation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25076">
                <text>In this article, author Joanna Newman reports the findings of her survey of local community archives in New Zealand. Newman designed a survey to evaluate only archives whose records held sustained value for the governance, historical research, and legal administration of their respective communities. Newman also distinguished these archives from libraries and museums by their stated mission to preserve and sustain long-term access to its records. She incorporated the standards and principles of archival theory adopted by the United States and New Zealand in the survey and synthesized them into three main categories for comparison: organization, the archives, themselves, and community engagement.&#13;
&#13;
Newman discovered officially sanctioned local community archives were more likely to receive the funding and highly skilled staff necessary for maintaining the physical environment and professional standards associated with other institutional archives. She also noted that while inter-institutional collaboration was less evident and significant for the New Zealand community archives than comparable archives in the United States, the archivist’s enthusiasm and support of local volunteers were influential factors in the archive’s overall sustainability. Newman explains that archivists offer assurance that standards will be upheld and local volunteers strengthen the connections between the archive and its community. Together these factors help ensure continued use and funding by the local authorities.&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25077">
                <text>Newman, Joanna </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="25078">
                <text>Australasian Public Libraries and Information Services </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25079">
                <text>2012</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25080">
                <text>Polk, Victoria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25081">
                <text>Journal Article</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="25082">
                <text>http://ica2012.ica.org/files/pdf/Full%20papers%20upload/ica12Final00190.pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="290">
            <name>Bibliographic Citation</name>
            <description>A bibliographic reference for the resource. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.</description>
            <elementTextContainer>
              <elementText elementTextId="25083">
                <text>Newman, Joanna. “Sustaining Community Archives.” &lt;em&gt;Australasian Public Libraries and Information Services&lt;/em&gt; 25.1 (2012): 37-45.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="167">
        <name>community archiving</name>
      </tag>
      <tag tagId="318">
        <name>library</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="71" public="1" featured="0">
    <fileContainer>
      <file fileId="70">
        <src>http://dar.cah.ucf.edu/files/original/d1da52bfa4b3fd4420fc76447662e38b.jpg</src>
        <authentication>003f5a0dbaf043cbd994250f24b84b23</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9279">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9280">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9281">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9282">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="10">
      <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="26248">
                  <text>Planning, Building, and Curation</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26249">
                  <text>Archives may represent any number or size collection and institution. These different types of archives may include governmental, non-selective collecting, thematic or activist, with corresponding missions and purposes unique to each institution. The items of this collection engage the processes of archive planning, building, and curation, and also represent notable digital archives whose collections reflect their respective institution's history and community.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="20">
      <name>Journal</name>
      <description>An item printed in an academic or professional journal.</description>
    </itemType>
    <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="25084">
                <text>Without the Data the Tools are Useless; Without the Software, the Data is Unmanageable</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25085">
                <text>Web archiving</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25087">
                <text>In this article, Michael Moss archivist and professor of Library and Information Science at the University of Glasgow, Scotland, decries the user-centered philosophy of Web 2.0 and believes the emphases on “collective intelligence” and “lightweight user interfaces” challenge the integrity of records and are responsible for critical losses of data and the current global financial crisis. He believes data is being compromised by such Web 2.0 technologies as anonymous tagging and blogs, and advocates a return to traditional archival principles, including “authenticity, integrity, and trust.”&#13;
&#13;
Moss cites historic cases in which archives were used to defend the public’s right to know in opposition to executive power. From England’s Civil War in the 1660s to illegal arms contracting between the Syrian government and BAE System (a London-based global company marketing defense, aerospace, and security service), Moss defends the archive’s objectivity and commitment to preserving the authenticity and integrity of its records. Without traditional archival values and methods, information exposing injustices would be lost. &#13;
&#13;
Moss is not recommending a return to manual forms of record keeping whereby several levels of staff would check and cross-reference each other’s work. He does propose, however, a coordinated effort among IT managers, record keepers, and archivists, to control the classification and dissemination of data through greater focus on content. Moreover, by encouraging archivists to embrace their “fiduciary responsibilities” (serving public institutions with practiced objectivity and authority), the public is protected from lax accounting or illegal actions perpetuated by unrestricted, open-access digital commerce.&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="263">
            <name>Abstract</name>
            <description>A summary of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="25088">
                <text>This essay explores the relationship between the curation of information in the digital environment by archivists and records managers and the technologies that support it. The author argues that this will require a sharing of responsibility within a framework of trust. He maintains that a consequence of the financial crisis, in which technology has played a large contributing part, is that there will be a greater emphasis on transparency of electronic processes and not just inputs and outputs. In these developments, he draws a distinction between records management operating within an institutional framework of risk, and the archive, particularly in the public sector, curating the records that will allow the executive to be brought to account. He concludes that such a restatement in a period of severe financial restraint will without doubt impact on the current ‘access’ agenda.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25089">
                <text>Moss, Michael </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="25090">
                <text>Journal of the Society of Archivists </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25091">
                <text>April 2010</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25092">
                <text>Polk, Victoria </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25093">
                <text>Society of Archivists</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25094">
                <text>Journal Article</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="25095">
                <text>http://www.tandfonline.com/doi/abs/10.1080/00379811003658443#.VTYrxc4bAmI</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="290">
            <name>Bibliographic Citation</name>
            <description>A bibliographic reference for the resource. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.</description>
            <elementTextContainer>
              <elementText elementTextId="25096">
                <text>Moss, Michael. “Without the Data, the Tools are Useless; Without the Software, the Data is Unmanageable.” &lt;em&gt;Journal of the Society of Archivists&lt;/em&gt; 31 (April 2010): 1-14.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="299">
            <name>Instructional Method</name>
            <description>A process, used to engender knowledge, attitudes and skills, that the described resource is designed to support. Instructional Method will typically include ways of presenting instructional materials or conducting instructional activities, patterns of learner-to-learner and learner-to-instructor interactions, and mechanisms by which group and individual levels of learning are measured. Instructional methods include all aspects of the instruction and learning processes from planning and implementation through evaluation and feedback.</description>
            <elementTextContainer>
              <elementText elementTextId="25097">
                <text>Moss cautions archivists against uncritically integrating Web 2.0 technologies into archival practices. Social networking applications, such as blogs and wikis alter the principles of authority, privacy, and trust between the archive and the record, and the between the archivist and the public.  Traditional practices, including formal documentation and file plans for ingested materials, are just as critical, if not more so, in the digital archive.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="346">
        <name>digital technologies</name>
      </tag>
      <tag tagId="37">
        <name>open access</name>
      </tag>
      <tag tagId="97">
        <name>web archiving</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="70" public="1" featured="0">
    <fileContainer>
      <file fileId="71">
        <src>http://dar.cah.ucf.edu/files/original/ca183496358182f60a1598822cc321da.jpg</src>
        <authentication>003f5a0dbaf043cbd994250f24b84b23</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9315">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9316">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9317">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9318">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </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="26244">
                  <text>Preservation Issues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26245">
                  <text>Preservation in the archive involves the process of historical representation and connotes security, safety, and assurance that the collections will remain intact and uncorrupted for future generations to enjoy. Digital collections pose unique preservation challenges and require an assessment of risks, both material and intellectual, as part of the planning and  management policies. These entries illuminate standard archival preservation practices and present future trends.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="17">
      <name>Online Journal</name>
      <description>An item published by an online journal or magazine.</description>
    </itemType>
    <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="25098">
                <text>Reflections on the Value of Metadata Archaeology for Recordkeeping in a Global, Digital World</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25099">
                <text>Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25101">
                <text>Recordkeeping metadata have been instrumental in constructing and promulgating, as well as reflecting, narratives for their era from antiquity into the digital age across cultures and belief systems. They thus can serve as a critical apparatus for articulating, delimiting and contextualizing the record and the archive on an infinite number of temporal dimensions. The implementations and worldviews of metadata, however, historically are often discontinuous or vary in different periods and settings, making it harder to discern their manifestations and influence. Metadata, and discourse formation around metadata, therefore, deserve and require careful excavation, contextualization, and analysis. The paper proposes using a Foucauldian ‘archaeological’ approach to gain a more nuanced and contextualized understanding of the diversity of metadata and metadata discourses. It illustrates this approach with perhaps one of the earliest of historical cases—that of the Royal Archive at Ebla.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25102">
                <text>Gililand, Anne J.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="25103">
                <text>Journal of the Society of Archivists </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25104">
                <text>2011</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25105">
                <text>Polk, Victoria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25106">
                <text>2011 Archives and Records Association</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25107">
                <text>Journal Article</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="25108">
                <text>http://www.tandfonline.com/doi/abs/10.1080/00379816.2011.563934#.VTYsX84bAmI</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="290">
            <name>Bibliographic Citation</name>
            <description>A bibliographic reference for the resource. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.</description>
            <elementTextContainer>
              <elementText elementTextId="25109">
                <text>Gilliland, Anne J. “Reflections on the Value of Metadata Archaeology for Recordkeeping in a Global, Digital World.” &lt;em&gt;Journal of the Society of Archivists&lt;/em&gt; 32,1 (April 2011):103-118.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="216">
        <name>history</name>
      </tag>
      <tag tagId="104">
        <name>metadata</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="69" public="1" featured="0">
    <fileContainer>
      <file fileId="223">
        <src>http://dar.cah.ucf.edu/files/original/ae4d9508f3a1dc51891ab102807c5fc7.jpg</src>
        <authentication>ed2475e8b5f6b08567fed91d1a80812b</authentication>
        <elementSetContainer>
          <elementSet elementSetId="5">
            <name>Omeka Image File</name>
            <description>The metadata element set that was included in the `files_images` table in previous versions of Omeka. These elements are common to all image files.</description>
            <elementContainer>
              <element elementId="72">
                <name>Width</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="19415">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="19416">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="19417">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="19418">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="10">
      <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="26248">
                  <text>Planning, Building, and Curation</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26249">
                  <text>Archives may represent any number or size collection and institution. These different types of archives may include governmental, non-selective collecting, thematic or activist, with corresponding missions and purposes unique to each institution. The items of this collection engage the processes of archive planning, building, and curation, and also represent notable digital archives whose collections reflect their respective institution's history and community.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="17">
      <name>Online Journal</name>
      <description>An item published by an online journal or magazine.</description>
    </itemType>
    <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="25110">
                <text>Looking Out and Keeping The Gate Open: Wairarapa Archive, New Zealand's Greatest Little Archive</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25111">
                <text>Collective memory </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25113">
                <text>Authors Sandy Green and Gareth Winter narrate the history of the Wairarapa Archive located in southeast New Zealand. They attribute the popularity and growth of this archive to its successful partnerships and community outreach program, as well as its adherence to archival standards. Green and Winter’s historical account traces the archive’s beginning as a print and photo-based collection housed in the basement of the local library, to a dynamic archive comprised of several collections, many of which are digitized. Wairarapa archive’s popularity is largely to due to what author/archivist Gareth Winter, describes “keeping the gate open.” The “open gate” refers to the accessibility of the archive and the staff’s willingness to provide several services and cooperative programs with the community. Services and collaborations include sponsoring oral history projects, supporting both technically and physically, the local genealogical society, digitizing photographs, records, and newspapers for other institutions as well as its own collections and providing both published works and school field trips to provide continuing education to its public.&#13;
&#13;
The archive thus evolved from primarily functioning as a holding repository for local historical and governmental records, to providing educational and historian services. The variety and extent of the collaboration between the Wairarapa archive and several local and national organizations is fundamental to the archive’s ongoing success and funding.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25114">
                <text>Green, Sandy A. </text>
              </elementText>
              <elementText elementTextId="25115">
                <text>Winter, Gareth </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="25116">
                <text>Auslib Press</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25117">
                <text>2011</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25118">
                <text>Polk, Victoria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25119">
                <text>© 2015</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25120">
                <text>Journal Article</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="25121">
                <text>https://www.questia.com/library/journal/1G1-284753463/looking-out-and-keeping-the-gate-open-wairarapa-archive</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="290">
            <name>Bibliographic Citation</name>
            <description>A bibliographic reference for the resource. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.</description>
            <elementTextContainer>
              <elementText elementTextId="25122">
                <text>Green, Sandy A., and Gareth Winter. “Looking Out and Keeping the Gate Open: Wairarapa Archive, New Zealand’s Greatest Little Archive.” &lt;em&gt;APLIS&lt;/em&gt; 25 (2012): 23-31</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="63">
        <name>collaboration</name>
      </tag>
      <tag tagId="167">
        <name>community archiving</name>
      </tag>
      <tag tagId="14">
        <name>cultural heritage</name>
      </tag>
      <tag tagId="37">
        <name>open access</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
