<?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?output=omeka-xml&amp;page=6&amp;sort_field=added" accessDate="2026-05-02T13:34:22+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>6</pageNumber>
      <perPage>10</perPage>
      <totalResults>454</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="65" public="1" featured="0">
    <fileContainer>
      <file fileId="76">
        <src>http://dar.cah.ucf.edu/files/original/7031f3a59fac86d85aa44eb4c079eaee.jpg</src>
        <authentication>15ac7aba1e86905e0a5d9b7ec09ba859</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="9492">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9493">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9494">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9495">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26242">
                  <text>What is an Archive?</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26243">
                  <text>Archives are collections of primary sources, cataloged and grouped for the purpose of preserving and making accessible the records of society’s cultural and historic heritage. Laura Millar, noted archivist and author of Archives principles and practices, defines the mission of archives “to acquire, preserve and make available the documentary memory of society…”(Millar 2010). These entries will focus on the explanation and description of an archive and why they are important to society. What does it mean to be an archive and what is the value of an archive?</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="25161">
                <text>The Converging Histories and Futures of Libraries, Archives, and Museums as Seen through the Case of the Curious Collector Myron Eells</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25162">
                <text>Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25164">
                <text>Michael J. Paulus, Jr., librarian and professor at Seattle Pacific University in Seattle, Washington, compares Myron Eells’ 19th century eclectic library and his method of recordkeeping to postmodern trends in contemporary libraries, archives, and museums (LAMs). These trends include establishing special collections of rare and unpublished materials in libraries, and developing selection policies and designing informative interfaces for public access in museums. Such activities were once considered institutionally specific, and following the implementation of standardized practices and principles for LAMs in the early 20th century, would not have occurred outside their respective institutions.&#13;
&#13;
Myron Eells, minister, educator, and collector of “curiosities,” created an extensive record of the history of our country’s northwest. He accompanied his array of materials with careful documentation, adopting an ethnographic approach to indexing his materials, based in part on his many visits to museums. In addition to his collections (cabinets), he wrote books and articles describing the history of the NW territories and its people. Paulus observes while Eells was constructing his collections and writing diaries and manuscripts, the late 19th and early 20th century libraries and museums were establishing modernist principles and standards. Libraries, museums, and archives focused on highly specialized roles and kept collections and standards separate from each other. Paulus says Eells was largely oblivious of the emerging fields of library science and museum curation, and combined his artefacts with historical and fictional literature. When his library and personal papers were donated to Whitman College, the collection was dispersed between the library and museum, without regard to provenance.&#13;
&#13;
With the advent of digital technology, the content, mission, and tasks of librarians, archivists, and museum curators are merging. Paulus hopes the blurring boundaries between these institutions will foster greater sharing of their collections as each adopts the other’s philosophy—to collect, preserve, interpret, and disseminate information for the public. He recognizes the potential for aggregating the widely scattered collection of Myron Eells into a digital space that could recreate his desire to capture a past for future use</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25165">
                <text>Paulus, Michael J. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="25166">
                <text>Libraries &amp; the Cultural Record </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="25167">
                <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="25168">
                <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="25169">
                <text>University of Texas Press</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25170">
                <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="25171">
                <text>http://muse.jhu.edu/journals/libraries_and_culture/summary/v046/46.2.paulus.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="25172">
                <text>Paulus, Michael J., Jr. “The Converging Histories and Futures of Libraries, Archives, and Museums as Seen through the Case of the Curious Collector Myron Eells.”&lt;em&gt; Libraries &amp;amp; the Cultural Record&lt;/em&gt; 46 (2011): 185-205.</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="318">
        <name>library</name>
      </tag>
      <tag tagId="140">
        <name>provenance</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="66" public="1" featured="0">
    <fileContainer>
      <file fileId="75">
        <src>http://dar.cah.ucf.edu/files/original/19a1e7defd9b40278c5c1d05c24de51e.jpg</src>
        <authentication>d543590ae600125ea6fb364357e4057a</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="9459">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9460">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9461">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9462">
                    <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="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="25151">
                <text>Future Watch: Strategies for Long-Term Preservation of Electronic Records</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25152">
                <text>Digital preservation </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25153">
                <text>There are several varied types of electronic records, including legal documents, images, receipts, and personal correspondence that require unique methods of preservation. Hoke explains that due to rapid obsolescence of both software and hardware, long-term preservation (ten years or more) may not be possible. To further complicate the preservation of electronic records, the different institutions, and categories of collections (such as medical transactions, insurance proceedings, court cases, or personal papers) also affect their long-term maintenance. Hoke classifies these challenges to digital preservation into four main categories: storage media; hardware; software; and governance. For each category, Hoke provides examples and concludes no universal principle or procedure can be applied. For example, software companies that do not provide backwards compatibility may require emulation as opposed to migration strategies for preservation.&#13;
&#13;
 Hoke believes governance, the infrastructure and long-term commitment to preserving a collection, is perhaps the most vulnerable category. Knowing how to assign provenance to a record that must be migrated into a new form, or anticipating future demands for different types of records are examples of the difficulties affecting governance. Planning and developing strategies for governance are addressed in the second section of Hoke’s article. In this section, he discusses several preservation strategies, including periodic migration, using archival (non-proprietary) formats, and investigating new emerging technologies (such as nickel engraving). Throughout his article, Hoke reminds the reader that solutions must be tailored to the unique needs of the institution and the specific types of electronic records.  He concludes by providing four recommendations: determine the highest level of risk the institution is willing to take; assess the current effectiveness of the overall digital collection; survey the existing tools, strategies, and tactics used for preservation; and commit to long-term asset management.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25154">
                <text>Hoke, Gordon E. J.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="25155">
                <text>Information Management </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="25156">
                <text>2012-05</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25157">
                <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="25158">
                <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="25159">
                <text>http://content.arma.org/IMM/May-June2012/futurewatchstrategiesforlongtermpreservation.aspx</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="25160">
                <text>Hoke, Gordon E.J. “Future Watch: Strategies for Long-Term Preservation of Electronic Records.”&lt;em&gt; Information Management&lt;/em&gt; (May/June 2012): 1-7.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="346">
        <name>digital technologies</name>
      </tag>
      <tag tagId="358">
        <name>new media</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
      <tag tagId="140">
        <name>provenance</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="67" public="1" featured="0">
    <fileContainer>
      <file fileId="74">
        <src>http://dar.cah.ucf.edu/files/original/dbdd8517c82001d1817b5d753a464ce9.jpg</src>
        <authentication>5612789b74ed10152fef9e1a9d8491a8</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="9424">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9425">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9426">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9427">
                    <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="25135">
                <text>Preservation in the Digital Age: A Review of Preservation Literature, 2009-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25136">
                <text>Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25138">
                <text>In response to a ten-year gap between publishing surveys on library collections preservation, Karen F. Gracey and Miriam B. Kahn conducted an extensive review of the literature on digitization and preservation of libraries and archives. The literature includes such non-traditional sources as multimedia conference proceedings and blogs. Although their printed bibliography contains mainly traditional academic sources, including research articles and book chapters, their entire survey is available online.&#13;
&#13;
 The authors classify the literature into categories based on areas of current professional interest and emphasize the critical issues and key resources for digital archivists, librarians, and curators. Overarching issues for preservation include the transition from being a largely custodial function to developing principles for long-term preservation and the development of tools for promoting greater intellectual access to the content.  By combining curatorial principles with traditional preservation and risk management functions, digital archives, libraries, and museums are adopting similar, standardized practices. Several articles discuss the development of standard metadata schemes for multiple and heterogeneous artefacts and the corresponding open-access tool kits and consortiums dedicated to fostering systematic methods for digital preservation. &#13;
&#13;
Recommendations for implementing strategic planning recur throughout most of the articles, including those in the last section, “The New Preservationist.” Gracey and Kahn emphasize taking a wide view of the lifecycle and the potential uses of digital materials. One of the underlying themes is the expressed desire for robust, technical and organizational standards, matched by an awareness that universal standards, practices, funding, and digital curation skills are lagging behind the needs.&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="263">
            <name>Abstract</name>
            <description>A summary of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="25139">
                <text>This paper surveys research and professional literature on preservation-related topics published in 2009 and 2010, identifies key contributions to the field in periodicals, monographs, and research reports, and provides a guide to the changing landscape of preservation in the digital age. The authors have organized the reviewed literature into five major areas of interest: tensions in preservation work as libraries embrace digital resources, mass digitization and its effects on collections, risk management and disaster response, digital preservation and curation, and education for preservation in the digital age.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="264">
            <name>Table Of Contents</name>
            <description>A list of subunits of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="25140">
                <text>"The Physical and Virtual: Libraries and Collections in Transition"&#13;
&#13;
"Mass Digitization and Its Impact on Preservation Activities&#13;
&#13;
"Risk Management"&#13;
&#13;
"From Preservation to Curation: Lifecycle of Digital Materials&#13;
&#13;
"The New Preservationist"</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25141">
                <text>Gracey, Karen F. </text>
              </elementText>
              <elementText elementTextId="25142">
                <text>Kahn, Miriam B. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="25143">
                <text>Library Resources &amp; Technical 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="25144">
                <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="25145">
                <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="25146">
                <text> Copyright 2011 Karen F. Gracy</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25147">
                <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="25148">
                <text>http://downloads.alcts.ala.org/lrts/digitalage_bib1111.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="25149">
                <text>Gracey, Karen F. and Miriam B. Kahn. “Preservation in the Digital Age: A Review of Preservation Literature.” &lt;em&gt;Library Resources &amp;amp; Technical Services&lt;/em&gt; 56 (January 2012): 25-43.</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="25150">
                <text>Gracey and Kahn supply a comprehensive bibliography on issues, strategies, and professional development designated for anyone interested in developing or maintaining a digital collection. There are several articles that contain highly technical information, but are included to provide a broad appreciation of the complexity of digital preservation. This addition to the &lt;em&gt;Digital Archiving Resources&lt;/em&gt; collection provides a resource for further research into the major components of digitizing collections, as well as an overview of the most current issues facing the profession.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="430">
        <name>archival standards</name>
      </tag>
      <tag tagId="163">
        <name>digital conversion</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="68" public="1" featured="0">
    <fileContainer>
      <file fileId="73">
        <src>http://dar.cah.ucf.edu/files/original/f1dee71eaefc9f280e14532b44155d4f.jpg</src>
        <authentication>3b311c48fafddecc19d7fc2a2d6234cb</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="9388">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9389">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9390">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="9391">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26242">
                  <text>What is an Archive?</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26243">
                  <text>Archives are collections of primary sources, cataloged and grouped for the purpose of preserving and making accessible the records of society’s cultural and historic heritage. Laura Millar, noted archivist and author of Archives principles and practices, defines the mission of archives “to acquire, preserve and make available the documentary memory of society…”(Millar 2010). These entries will focus on the explanation and description of an archive and why they are important to society. What does it mean to be an archive and what is the value of an archive?</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="25123">
                <text>Defining "born digital": an essay</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25124">
                <text>Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25126">
                <text>Erway provides a succinctly defined list of fundamental tasks and issues to consider when creating and preserving digital collections. Born-digital resources are simply “items created and managed in digital form.” Erway begins his essay by describing nine basic types of born-digital items including documents, images, data sets and digital media. He accompanies each description with recommended methods for preservation, noting that some types, such as documents, may require emulating the original software that created the document. Many factors affect born-digital preservation, such as whether or not the document was created with proprietary software, the hardware and operating system are obsolescent, or how the document might be used in the future.&#13;
&#13;
 Erway discusses key issues affecting the preservation of born-digital items by assessing the inherent risks and detailing seven fundamental archival challenges. A key issue, such as “bit rot” adds to the complexity of adapting archival standards to digital collections. Standard archival principles, including provenance, are jeopardized by loss or corruption of digital data or by the proprietary nature of some software. Documents protected by such software may not be able to provide contextual information that might be useful for establishing the document’s origins and relationships to other items in the collection. Erway also illuminates a fundamental archival challenge in balancing the creator’s right to privacy against the public right to access.&#13;
&#13;
In summary, Erway offers three steps for beginning a digital archive: establish basic policies for each type of born-digital item; inventory the digital collection and determine what formats and media storage ensure long-term sustainability; and seek other people and institutions developing similar digital collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25127">
                <text>Erway, Ricky </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="25128">
                <text>OCLC Research</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="25129">
                <text>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="25130">
                <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="25131">
                <text>OCLC Online Computer Library Center, Inc.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25132">
                <text>Ebook</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="25133">
                <text>http://www.oclc.org/content/dam/research/activities/hiddencollections/borndigital.pdf?urlm=168879</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="25134">
                <text>Erway, Ricky. &lt;em&gt;Defining "Born Digital": An Essay&lt;/em&gt;. Dublin, OH:OCLC Research, 2010. PDF e-book.</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="60">
        <name>preservation</name>
      </tag>
      <tag tagId="140">
        <name>provenance</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>
  <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="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="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="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="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>
</itemContainer>
