<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="http://dar.cah.ucf.edu/items/browse?output=omeka-xml&amp;page=22&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-12T14:11:11+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>22</pageNumber>
      <perPage>10</perPage>
      <totalResults>454</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="29" public="1" featured="0">
    <fileContainer>
      <file fileId="45">
        <src>http://dar.cah.ucf.edu/files/original/49cce79b86454ba913ca430d086f0443.jpg</src>
        <authentication>91e218704ebf710a28cdabcb3a7dc599</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="4384">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="4385">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="4386">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="4387">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="25">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26256">
                  <text>Web Archiving</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26257">
                  <text>In 2003, the Library of Congress and the national libraries of Australia, Canada, Denmark, Finland, France, England and other countries formed the International Internet Preservation Consortium, and have spearheaded an international effort to preserve Internet content for future generations.&#13;
&#13;
This collection aims to highlight materials that pertain to the process of  preserving elements of the World Wide Web using of web crawlers for automated capture of content.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="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="25533">
                <text>Functionalities of Web Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25534">
                <text>The functionalities that are important to the users of web archives range from basic searching and browsing to advanced personalized and customized services, data mining, and website reconstruction. The author examined ten of the most established English language web archives to determine which functionalities each of the archives supported, and how they compared. &#13;
&#13;
A functionality checklist was designed, based on use cases created by the International Internet Preservation Consortium (IIPC), and the findings of two related user studies. The functionality review was conducted, along with a comprehensive literature review of web archiving methods, in preparation for the development of a web archiving course for Library and Information School students. This paper describes the functionalities used in the checklist, the extent to which those functionalities are implemented by the various archives, and discusses the author's findings. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25535">
                <text>Niu, Jinfang </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="25536">
                <text>D-Lib Magazine</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25537">
                <text>2012-03</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25538">
                <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="25539">
                <text>2012 Jinfang Niu</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25540">
                <text>Online Journal </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="25541">
                <text>http://dlib.org/dlib/march12/niu/03niu2.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="25542">
                <text>Niu, Jinfang. "Functionalities of Web Archives."&lt;em&gt; D-Lib Magazine&lt;/em&gt; 18.3/4 (2012): n. pag. Web. 27 Apr. 2015.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27737">
                <text>Web archiving</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="92">
        <name>data mining</name>
      </tag>
      <tag tagId="85">
        <name>usability</name>
      </tag>
      <tag tagId="97">
        <name>web archiving</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="261" public="1" featured="0">
    <fileContainer>
      <file fileId="307">
        <src>http://dar.cah.ucf.edu/files/original/fede4c9a6cb950effe80b13c78f55140.jpg</src>
        <authentication>f90d93f3541ccf0699b71dfadf7be116</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="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>
    <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="26490">
                <text>Functionalities of Web Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26491">
                <text>This paper examines the key functionality for users of a web archive. The author argues the following components must be addressed: basic searching, browsing, advanced personalization, customized services, and data mining. A selection of ten English language web archives were examined with a checklist of the outlined criteria. In addition to the criteria, information from usability studies from the International Internet Preservation Consortium was included. The author began the study by reading each archive’s about me/f.a.q. pages to expedite the evaluation process. Additional functionality was identified as beneficial that was not included on the checklist: duplication management, Indicating non-archived content by search engines. At the conclusion of the study, the author found basic functionality was included in all the archives however advanced features were lacking. The author summarizes each archive has different priorities and resources challenges.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26492">
                <text>Niu, Jinfang</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="26493">
                <text>D-Lib Magazine</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26495">
                <text>Raible, John</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26496">
                <text>Web Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26497">
                <text>Journal Article</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="26498">
                <text>Niu, Jinfang. "Functionalities of Web Archives." D-Lib Magazine 18, no. 3/4 (March/April 2012)&#13;
&#13;
</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="26552">
                <text>2012-03-02</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="92">
        <name>data mining</name>
      </tag>
      <tag tagId="97">
        <name>web archiving</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="395" public="1" featured="0">
    <fileContainer>
      <file fileId="475">
        <src>http://dar.cah.ucf.edu/files/original/9b1f2036d6000d1d740b08b2d7f3300e.jpg</src>
        <authentication>d706b8b7dfa31653f4a603a7f306783c</authentication>
      </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="27895">
                <text>Future Proof: The Transition to Digital at IFI Archive</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27896">
                <text>Curation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27897">
                <text>This journal article delineates the procedures undertaken and the standards implemented in the establishment of a time-withstanding digital audiovisual archive known as the IFI Irish Film Archive. After collecting the results of various research endeavors regarding archival strategies, the Irish Film Institute launched a six-year digital preservation and access strategy in 2014, which prioritized the design and installation of digital archive tools for extended preservation and workflow redesigning practices. It discusses the impact that these fresh strategies evidenced in the management of high-resolution digital film and related metadata. The article delves into the Irish Film Institute’s past and origins as well as that of the project itself, which partnered with technology professionals before the release of its new strategy to deliver an extensible, viable, and cost-efficient solution to the recurring challenge of digital preservation, especially the preservation of audiovisual media. It surveys the development of preservation budgets and constraints, implementing methods to eliminate all but the essential aspects of a system enabling the delivery of primary objectives, adjusting system designs and greatly reducing unnecessary costs. After detailing the decisions taken to facilitate high speed data transfer and the adoption and promotion of its digitization standards, the article concludes by listing its partners in the archive, film, and research communities and their considerable contributions to the resulting Irish Film Archive.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27898">
                <text>Mahler, Anja; Factor, Simon; and Casey, Raelene</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="27899">
                <text>New Review of Information Networking, Taylor &amp; Francis Online</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="27900">
                <text>2015-12-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27901">
                <text>Taveras, Sabrina</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27902">
                <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="27903">
                <text>ISSN: 1361-4576 (Print) 1740-7869 (Online)</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="27904">
                <text>Anja Mahler, Simon Factor &amp; Raelene Casey. "Future Proof: The Transition to Digital at IFI Archive." New Review of Information Networking, December 17, 2015. 20:1-2, 149-154, DOI: 10.1080/13614576.2015.1112683.&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="430">
        <name>archival standards</name>
      </tag>
      <tag tagId="191">
        <name>content management</name>
      </tag>
      <tag tagId="346">
        <name>digital technologies</name>
      </tag>
      <tag tagId="60">
        <name>preservation</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="355" public="1" featured="0">
    <fileContainer>
      <file fileId="408">
        <src>http://dar.cah.ucf.edu/files/original/dd1e552199e2b2f72700038024d2a10d.jpg</src>
        <authentication>cb92f022840929b0f0111550aeaa2dd0</authentication>
      </file>
    </fileContainer>
    <collection collectionId="12">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26250">
                  <text>Ethics, Privacy, Copyright, and Legislation</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26251">
                  <text>This collection represents the delicate balance digital archivists seek when designing an archive that preserves and provides access, while also ensuring all parties' right to privacy and intellectual property. Also known as risk management, archives must anticipate potential infringements of intellectual property and privacy rights, and guard the public's right to free and open access. Items in the collection address risk management issues and underscore the necessity for keeping current in legal and ethical archival practices.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="19">
      <name>Book</name>
      <description>A written or printed work consisting of pages. </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="27424">
                <text>Getting Permission: How to License &amp; Clear Copyrighted Materials Online &amp; Off</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27425">
                <text>Copyright</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27426">
                <text>Getting Permission offers a simple look into the copyright permission process, as well as going over content that is in the public domain and the "fair use" law, in addition to other intricacies related to the process of obtaining permission from copyright holders.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27427">
                <text>Stim, Richard</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="27428">
                <text>NOLO</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="27429">
                <text>2013</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27430">
                <text>Van Dresar, Megan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27431">
                <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="27432">
                <text>ISBN: 9781413319330</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="27433">
                <text>Stim, Richard. "Getting Permission: How to License &amp;amp; Clear Copyrighted Materials Online &amp;amp; Off".  &lt;em&gt;Digital Archiving Resources.  &lt;/em&gt;Accessed April 21, 2016. &lt;a href="http://www.nolo.com/products/getting-permission-riper.html"&gt; http://www.nolo.com/products/getting-permission-riper.html&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="191">
        <name>content management</name>
      </tag>
      <tag tagId="54">
        <name>copyright laws</name>
      </tag>
      <tag tagId="69">
        <name>ethics</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="469" public="1" featured="0">
    <fileContainer>
      <file fileId="553">
        <src>http://dar.cah.ucf.edu/files/original/cdccc5599ff9ede9a14759c61638f1d9.JPG</src>
        <authentication>1dc4fa55a12ad31350246a1e1d1988ff</authentication>
      </file>
    </fileContainer>
    <collection collectionId="3">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="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="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="28573">
                <text>Going Digital: Electronic Images in the Library Catalog and Beyond</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28574">
                <text>“Going digital: electronic images in the library catalog and beyond”  is a book published all the way in 1995. In this year was when practical consumers began using the internet and saving their own data into their personal hard drives. It was written by archiving consultants Ronald R Abbott and Mimi King. It is not available in a printing format,  but it can be accessed virtually as a digitized novel. It is 81 pages and originally written and solely released in English. The fact that the book is no longer allowed in paper back is very important because if it had not been digitized and archived it would no longer be able to read and would be an immense waste of such valuable information. Considering that the book was released in the late 90’s before many websites were updating digitized information, it shows how much the efficiency of digital archiving has changed much over time. The book explains the importance of beginning to archive not only written data, but visual data as well. This book would be an important addition to the website because it goes back to the basics and foundations of digital archiving through images. The text was extremely popular to teach students in the early 90’s at the University of Toronto in Canada. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28575">
                <text>Ronald R. Abbott, Howard Besser, Richard W. Boss, H. Thomas Hickerson, Marilyn Lutz, Pameia R. Mason, Willam E. Neale. </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="28576">
                <text>1995</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28577">
                <text>Clara Pulido, Jacquelyn Curtin, Truc Duong</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="28578">
                <text>ISBN: 9780838978146</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="28579">
                <text>King, Mimi, and Ronald R. Abbott. Going Digital: Electronic Images in the Library Catalog and Beyond. Chicago, IL: Library and Information Technology Association, 1995.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="216">
        <name>history</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
      <tag tagId="97">
        <name>web archiving</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="267" public="1" featured="0">
    <fileContainer>
      <file fileId="313">
        <src>http://dar.cah.ucf.edu/files/original/6ca18a17f0fc66824e1f8fd266edd4d5.png</src>
        <authentication>b55c6bf22a1e41c54ec080ce88bb6544</authentication>
      </file>
    </fileContainer>
    <collection collectionId="24">
      <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="26254">
                  <text>Personal Archiving</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26255">
                  <text>Individual, family, and community histories are increasingly being documented and preserved on the Internet through a wide array of social media, software products, and services. Stories, images, and video are being uploaded, organized, and accessed on the Web.  &#13;
&#13;
This collection aims to highlight methods and materials having to do with personal archiving, and its relationship to the field of digital archiving.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="21">
      <name>Video Recording</name>
      <description>A recording of images and sounds made digitally or on videotape. </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="26538">
                <text>Gone in a Flash? Personal Digital Archiving Workshop</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26539">
                <text>Personal archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26540">
                <text>"Gone In a Flash?" is the recording of a digital archiving workshop conducted at Columbia University in 2012. The workshop illuminates organization and preservation practices important for individuals, especially academics, who want to make sure their work, whether textual or multimedia, is accessible in the future. The presenters emphasize the importance of writing an explicit archival policy for oneself that includes a list of items that need to be saved, as well as when, where, and how to save them. Individual items should be documented as in a professional archive so that if items are found much later, the viewer can tell where they came from, how they were created, and any software that one may need to access them. &lt;br /&gt;&lt;br /&gt;Personal archives, like any professional archive, must be managed and maintained. One must cull them for unnecessary information, and establish a backup calendar so that three copies of the work are kept at all times and in different places. The workshop also delves into university resources, such as academic creative commons, that can help scholars by backing up the information on a fixed schedule and completing the metadata.</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="26541">
                <text>2012-10-02</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="26543">
                <text>Columbia University. “Gone in a Flash? Personal Digital Archiving Workshop.” On YouTube. October 2, 2012.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26544">
                <text>Columbia University</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26708">
                <text>Sara Raffel</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27696">
                <text>Video recording </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="393">
        <name>archival practices</name>
      </tag>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="191">
        <name>content management</name>
      </tag>
      <tag tagId="235">
        <name>digital repositories</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="244" public="1" featured="0">
    <fileContainer>
      <file fileId="288">
        <src>http://dar.cah.ucf.edu/files/original/f8d0245aa1bf8dffecba5eb80e14c8f0.jpg</src>
        <authentication>7711a6e42ac7f73d552ad14e08a2b2ad</authentication>
      </file>
    </fileContainer>
    <collection collectionId="26">
      <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="26258">
                  <text>Teaching Strategies</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26259">
                  <text>Items in this collection pertain to the ways one can use digital archives to teach digital humanities or related subjects. Specific pedagogies associated with the creation, management, preservation of archive content are also collected here.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26332">
                <text>Googling the Archive: Digital Tools and the Practice of History</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26333">
                <text>Solberg suggests that new digital environments have the “potential to reorient us—both physically and conceptually,” allowing new methods and possibilities for research, and new opportunities to socio-politically reposition the field of rhetoric and composition. She charts the beginning of these opportunities by referencing a colleague who was at a meeting during the genesis of Google, then her realization of the power of emergent technologies while researching Frances Maule. Solberg continues that to preserve, and guide the field we must train students and faculty members to become experts in the use, and design, of digital information systems if we wish to produce responsible, and capable stewards of the field of the history of rhetoric and composition.  She outlines a heuristic for using new digital tools defined by “affective,” “geographical,” and “virtual proximity,” with which she defines the links between self (researcher) positioning, and the technological tools utilized by the researcher.&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26334">
                <text>Solberg, Janine</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="26335">
                <text>2012-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26336">
                <text>Foley, Christopher</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26337">
                <text>Journal Article</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="26338">
                <text>Solberg, Janine. "Googling the Archive: Digital Tools and the Practice of History." Advances In The History Of Rhetoric 15, no. 1 (January 2012): 53-76. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26339">
                <text>Digital humanities</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="346">
        <name>digital technologies</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="135" public="1" featured="0">
    <fileContainer>
      <file fileId="178">
        <src>http://dar.cah.ucf.edu/files/original/0cc21d01d6c25cb15c5222ba53645234.jpg</src>
        <authentication>d663d208864b6ca9449fb30c41205ff0</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="15528">
                    <text>1207</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15529">
                    <text>1500</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15530">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="15531">
                    <text>3</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="12">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26250">
                  <text>Ethics, Privacy, Copyright, and Legislation</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26251">
                  <text>This collection represents the delicate balance digital archivists seek when designing an archive that preserves and provides access, while also ensuring all parties' right to privacy and intellectual property. Also known as risk management, archives must anticipate potential infringements of intellectual property and privacy rights, and guard the public's right to free and open access. Items in the collection address risk management issues and underscore the necessity for keeping current in legal and ethical archival practices.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="19">
      <name>Book</name>
      <description>A written or printed work consisting of pages. </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="24282">
                <text>Guide to Security Considerations and Practices for Rare Book, Manuscript, and Special Collection Libraries</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24283">
                <text>Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24284">
                <text>The Guide to Security Considerations and Practices for Rare Book, Manuscript, and Special Collection Libraries is the first such book intended specifically to address security in special collection libraries. Containing nineteen chapters, the book covers such topics as background checks, reading room and general building design, technical processing, characteristics and methods of thieves, materials recovery after a theft, and security systems. While other topics are touched upon, the key focus of this volume is on the prevention of theft of rare materials. The work is supplemented by several appendices, one of which gives brief biographies of recent thieves and another of which publishes Allen s important Blumberg Survey, which she undertook after that thief s conviction. The text is supported by illustrations, a detailed index, and an extensive bibliography.&#13;
&#13;
The work, compiled and edited by Everett C. Wilkie, Jr., contains contributions from Anne Marie Lane, Jeffrey Marshall, Alvan Bregman, Margaret Tenney, Elaine Shiner, Richard W. Oram, Ann Hartley, Susan M. Allen, and Daniel J. Slive, all members of the ACRL Rare Books &amp; Manuscripts Section (RBMS) and experts in rare materials and the security of these materials within special collections.&#13;
&#13;
This work is essential reading for all those concerned with special collection security, from general library administrators to rare book librarians.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24285">
                <text>Wilkie Jr., Everett C</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="24286">
                <text>ACRL</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="24287">
                <text>20 Sep. 2011</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="265">
            <name>Date Available</name>
            <description>Date (often a range) that the resource became or will become available.</description>
            <elementTextContainer>
              <elementText elementTextId="24288">
                <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="24289">
                <text>Tripson, Charlotte</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24290">
                <text>© 1996–2015 American Library Association</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24291">
                <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="24292">
                <text>ISBN-13: 978-0-8389-8592-2 </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="24293">
                <text>Wilkie Jr., Everett C. Guide to Security Considerations and Practices for Rare Book, Manuscript, and Special Collection Libraries. Chicago: ACRL, (2011). Print.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="191">
        <name>content management</name>
      </tag>
      <tag tagId="318">
        <name>library</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="334" public="1" featured="0">
    <fileContainer>
      <file fileId="387">
        <src>http://dar.cah.ucf.edu/files/original/cd28b018fc54e9be84b1c9acda7ae6cc.jpg</src>
        <authentication>9eb3d7d72cc32191d2cd4a9c63c9a5ab</authentication>
      </file>
    </fileContainer>
    <collection collectionId="25">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26256">
                  <text>Web Archiving</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="26257">
                  <text>In 2003, the Library of Congress and the national libraries of Australia, Canada, Denmark, Finland, France, England and other countries formed the International Internet Preservation Consortium, and have spearheaded an international effort to preserve Internet content for future generations.&#13;
&#13;
This collection aims to highlight materials that pertain to the process of  preserving elements of the World Wide Web using of web crawlers for automated capture of content.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="7">
      <name>Website</name>
      <description>A resource comprising of a web page or web pages and all related assets ( such as images, sound and video files, etc. ).</description>
      <elementContainer>
        <element elementId="6">
          <name>Local URL</name>
          <description>The URL of the local directory containing all assets of the website.</description>
          <elementTextContainer>
            <elementText elementTextId="27216">
              <text>http://guides.archaeologydataservice.ac.uk/g2gp/Main</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </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="27207">
                <text>Guides to Good Practice</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27208">
                <text>Web Archiving</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27209">
                <text>This website was designed and produced by the UK Archaeology Data Service and Digital Antiquity in the US over the course of a two-year collaborative project. Designed to be a guide for good standards to follow in the world of digital archiving, it outlines what digital archiving is, the goals a project should have as well as a list of principles for archiving digital data. These outlines will help to guide and keep a new project on its feet and on the right path instead of wavering and turning to a different and unrelated purpose.&#13;
Additionally the website goes a step beyond simply giving goals and principles and gives two case studies; one in the loss of digital data and another for the study of data recovery. Both of these invaluable information for seasoned or budding archivists.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27210">
                <text>Archaeology Data Service, Digital Antiquity</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="27211">
                <text>Archaeology Data Service, Digital Antiquity</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27212">
                <text>Donahue, Marisa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27213">
                <text>Website</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="27215">
                <text>Archaeology Data Service / Digital Antiquity. "Guides to Good Practice: ArchivalStrat_1-0." Guides to Good Practice: ArchivalStrat_1-0. Accessed April 20, 2016. &lt;a href="http://guides.archaeologydataservice.ac.uk/g2gp/ArchivalStrat_1-0"&gt;http://guides.archaeologydataservice.ac.uk/g2gp/ArchivalStrat_1-0.&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="430">
        <name>archival standards</name>
      </tag>
      <tag tagId="191">
        <name>content management</name>
      </tag>
      <tag tagId="104">
        <name>metadata</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
      <tag tagId="97">
        <name>web archiving</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
