<?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=12&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-03T18:33:43+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>12</pageNumber>
      <perPage>10</perPage>
      <totalResults>454</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="105" public="1" featured="0">
    <fileContainer>
      <file fileId="139">
        <src>http://dar.cah.ucf.edu/files/original/99c2ea57fdc9003c47b6336394dc5390.jpg</src>
        <authentication>21236c694b784b6ad5260d0b3b0650a9</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="11660">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="11661">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="11662">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="11663">
                    <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="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="24673">
                <text>Creating digital collections: a practical guide</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24674">
                <text>Archives</text>
              </elementText>
              <elementText elementTextId="24675">
                <text>Archives--Digitization</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24676">
                <text>Libraries recognize the importance of digitizing archival material to improve access to and preservation of their special collections. This book provides a step-by-step guide for creating digital collections, including examples and practical tips. &#13;
&#13;
It illustrates concepts with an ongoing case study at the end of each chapter, and provides detailed technical information and practical experience, along with  practitioners' insight in digitization. &#13;
It can be used as a guide for creating digital collections. &#13;
&#13;
Its contents include:&#13;
&#13;
Introduction&#13;
 - What are digital collections?&#13;
 - Why create digital collections?&#13;
 - Case study: the Digital Collections Production Center&#13;
&#13;
Planning and managing digitisation projects&#13;
 - Key components of a digitisation cycle&#13;
 - Project management&#13;
 - Developing a project plan&#13;
 - Case study: DCPC’s planning and management&#13;
&#13;
Selecting material for digitisation&#13;
 - Differences between selecting traditional material and selecting for digitisation&#13;
 - Major considerations in developing selection criteria&#13;
 - Case study: DCPC’s selection policy and service&#13;
&#13;
Metadata strategy&#13;
 - What is metadata?&#13;
 - Roles of metadata&#13;
 - Metadata standards&#13;
 - Metadata strategy&#13;
 - Digital object content model&#13;
 - Case study: DCPC metadata strategies&#13;
 - Creating digital collections&#13;
&#13;
Digitising material&#13;
 - Basic concepts for scanning&#13;
 - Scanning best practices&#13;
 - Image processing&#13;
 - Case study: DCPC’s scanning service&#13;
&#13;
Creating metadata&#13;
 - Content rules for metadata creation&#13;
 - Standards vs. local decisions&#13;
 - Controlled vocabularies&#13;
 - Tools for metadata creation&#13;
 - Computer-assisted metadata creation&#13;
 - Metadata crosswalk (data mapping)&#13;
 - Case study: DCPC’s metadata creation&#13;
&#13;
Designing a user interface for digital collections&#13;
 - Importance of user interface design&#13;
 - Related issues of user interface design&#13;
 - Principles of user interface design&#13;
 - Process of user interface design and configuration&#13;
 - Case study: designing the user interface for the DCPC’s digital collections&#13;
&#13;
The complete digitisation process and workflow management&#13;
 - Workflow management&#13;
 - Prototyping and quality control&#13;
 - Maintenance&#13;
&#13;
Digital collections management system&#13;
 - The digital collections production chain&#13;
 - Digital collections management system technology&#13;
 - Storage repository&#13;
 - Digital collections management system software&#13;
 - Case study: the DCPC digital collections management system&#13;
&#13;
Selecting software and hardware for digital collections management systems&#13;
 - Identify organisational requirements and resources&#13;
 - Develop selection criteria&#13;
 - Research available systems and equipment&#13;
 - Evaluate candidates – a checklist&#13;
 - Hardware selection&#13;
 - Case study: DCPC software selection for the DCMS&#13;
&#13;
Documentation&#13;
 - The importance of documentation&#13;
 - How to document a project and what to document&#13;
 - Planning documents&#13;
 - Management documents&#13;
 - Technical documents&#13;
 - Statistics&#13;
 - Case study: DCPC’s documentation&#13;
&#13;
The knowledge and skills required for creating digital collections&#13;
 - Management&#13;
 - Material selection&#13;
 - Scanning&#13;
 - Metadata&#13;
 - User interface&#13;
 - Information technology&#13;
 - Key qualities&#13;
&#13;
Conclusion &#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24677">
                <text>Zhang, Allison B. </text>
              </elementText>
              <elementText elementTextId="24678">
                <text>Gourley, Don</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="24679">
                <text>Chandos</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="24680">
                <text>2008-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24681">
                <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="24682">
                <text>Chandos</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24683">
                <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="24684">
                <text>ISBN-10: 1843343967</text>
              </elementText>
              <elementText elementTextId="24685">
                <text>ISBN-13: 978-1843343967</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="24686">
                <text>Zhang, Allison B. and Don Gourley. &lt;em&gt;Creating digital collections: a practical guide.&lt;/em&gt; Oxford: Chandos Pub., 2009.</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="318">
        <name>library</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="260" public="1" featured="0">
    <fileContainer>
      <file fileId="306">
        <src>http://dar.cah.ucf.edu/files/original/69ecda6e0e229ba36d96ebe451a97cc9.jpg</src>
        <authentication>2bfc458b02257d08dd4151690d741e60</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>
    <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="26477">
                <text>Creating Virtual Exhibitions from an XML-based Digital Archive</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26478">
                <text>Curation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26479">
                <text>This paper presents a method for creating virtual exhibitions using source materials from the National Archives of Singapore. The organizational structure includes an introduction to virtual exhibits, the architecture and design of both the virtual exhibit system and the digital archive, and concluding with a discussion of the assembled product. This innovate approach allows a flexible user interface along with the reference and reuse gathering model for efficient retrieve of artifacts. The flexibility allows the presentation of the exactly same information in a variety of formats. This approach caters to the general public and advanced researchers alike. The customized appearance is controlled via Cascading Style Sheets (CSS) which controls how the final product is rendered in HTML to the user. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="26480">
                <text>Journal of Information Science</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="26481">
                <text>2003-06-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26482">
                <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="26484">
                <text>Lim, Johanna Chua, and Foo, Schubert.  "Creating virtual exhibitions from an XML-based digital archive." Journal of Information Science 29, no. 3 (June 2003)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26486">
                <text>Lim, Johanna Chua and Schubert, Foo</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26488">
                <text>Raible, John</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="257">
        <name>data</name>
      </tag>
      <tag tagId="346">
        <name>digital technologies</name>
      </tag>
      <tag tagId="284">
        <name>xml</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="113" public="1" featured="0">
    <fileContainer>
      <file fileId="132">
        <src>http://dar.cah.ucf.edu/files/original/17555b09912b4e73021f256fa5e6f83b.jpg</src>
        <authentication>e30e4f1b13bfa772780bb5c4df21e520</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="11523">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="11524">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="11525">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="11526">
                    <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="24597">
                <text>Custodial History, Provenance, and the Description of Personal Records.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24598">
                <text>Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24600">
                <text>17th century English royalist and diplomat, Sir Richard Fanshawe, left a rich collection of letters and papers to his wife that during the next centuries became dispersed and scattered. The acquisition of these scattered documents by a 20th century local history museum neglected to include the equally rich historical context of each "collector" and their collections of these scattered remnants. This neglect of assigning provenance and misinterpreting the concept of the fonds provides Geoffrey Yeo a case study for defending traditional archival standards. Yeo argues that rather than ignore such concepts as "fonds" and "provenance" when building archival collections, including those digitally-based, these concepts should be used to distinguish the original context and creators of the collections. &#13;
&#13;
Yeo explains the custodial history of a collection provides historical context and significant insight into the successive transfers of ownership. Collection descriptions should, therefore, include the custodial history, or provenance.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24602">
                <text>Yeo, Geoffrey</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="24603">
                <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="24604">
                <text>2009</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24605">
                <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="24606">
                <text>The 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="24607">
                <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="24609">
                <text>Yeo, Geoffrey. "Custodial History, Provenance, and the Description of Personal Records." &lt;em&gt;Libraries &amp;amp; the Cultural Record &lt;/em&gt;44, no.1 (2009): 50-64. Accessed April 20, 2013. doi:10.1353/lac.0.0062.</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="24610">
                <text>Yeo persuasively argues that traditional archival standards, particularly the fonds and provenance, should guide the development of contemporary archives. Despite the dynamic nature of digital collections and the potential for dispersing the original order of a collection, archivists provide historical context when they establish the provenance of a collection.  This article identifies one of the key debates within the archiving profession.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="430">
        <name>archival standards</name>
      </tag>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="216">
        <name>history</name>
      </tag>
      <tag tagId="140">
        <name>provenance</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="428" public="1" featured="0">
    <fileContainer>
      <file fileId="509">
        <src>http://dar.cah.ucf.edu/files/original/38ef7fb63ac7cac414eb9614cbe1e349.png</src>
        <authentication>f7fafbd8d841f672d9ccb465ac27b50c</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>
    <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="28194">
                <text>Data Archiving</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28195">
                <text>Whitlock Michael C., McPeek Mark A., Rausher Mark D., Rieseber Loren, and Morre Allen J,</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="28196">
                <text>The University of Chicago Press for The American Society of Naturalists</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="28197">
                <text>2010-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28198">
                <text>Stephen Taggart</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28199">
                <text>Online Journal</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="28200">
                <text>Whitlock, Michael C., Mark A. McPeek, Mark D. Rausher, Loren Rieseberg, and Allen J. Moore. "Data Archiving." The American Naturalist 175, no. 2 (2010): 145-46. Accessed April 13, 2020. doi:10.1086/650340.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28438">
                <text>Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28439">
                <text>Data Archiving discusses how science depends on good data. Most data are central to the understanding of the natural world. The results of the study, when published, the data on which those results were based are sometimes stored unreliably. The subject of loss can occur because of hard drive failure. Also, it can be because of hard drive failure, and it might be the research for getting the specific details required to use the data. For the broader community, most data are never available, which can be even after publication of the results. It also explains how the data, even after the main results for which they were collected, are published, are invaluable to science, for meta-analysis, new uses, and quality control. Necessary summary statistics are often not published. The study is only used if the original data are available to the meta-analysts. Data can be used in ways beyond the questions that sparked its collection. Error checking, making science more peon, and letting us more rapidly reach accurate conclusions can happened because of the availability of data of published studies. It even explains why data are adequately archived are saved for posterity.&#13;
This article has a well-detailed explanation of how science depends. It brings up various examples such as GenBank, which shows the value of availability of data for all those above reasons.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="257">
        <name>data</name>
      </tag>
      <tag tagId="92">
        <name>data mining</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="311" public="1" featured="0">
    <fileContainer>
      <file fileId="361">
        <src>http://dar.cah.ucf.edu/files/original/c2e588c9940542187efadcb682f2d66a.jpg</src>
        <authentication>2b1c58a406057643c67ffd40f2315932</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>
    <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="26966">
                <text>Data Drift: Archiving Media and Data Art in the 21st Century</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26967">
                <text>Archive</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26968">
                <text>A selection of papers concerning what new media art forms are to be selected for inclusion of preservation in archives. With the implementation of archiving and curating in regards to media art forms from previous technologies, new upcoming approaches are necessary to ensure the preservation of the 21st century media and art data. The papers develop upon the issue of what of contemporary digital culture is worth preserving for future study and historical inference to our culture.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26969">
                <text>Smite, Rasa, Lev Manovich, &amp; Raitis Smits</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="26970">
                <text>RIXC, LiepU MPLab</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="26971">
                <text>2015 October 08</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26972">
                <text>Waddington, Calyn</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26973">
                <text>Book</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="26974">
                <text>Smite, Rasa, Lev Manovich, &amp;amp; Raitis Smits. "Data Drift: Archiving Media and Data Art in the 21st Century." RIXC, LiepU MPLab, 2015</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="26997">
                <text>ISBN- 13: 978-9934843433&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="14">
        <name>cultural heritage</name>
      </tag>
      <tag tagId="346">
        <name>digital technologies</name>
      </tag>
      <tag tagId="60">
        <name>preservation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="372" public="1" featured="0">
    <fileContainer>
      <file fileId="450">
        <src>http://dar.cah.ucf.edu/files/original/bdab2eb56710b556e4c2262758818cfe.jpg</src>
        <authentication>538452c22d6d96b20d117989cdb1149c</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="27606">
                <text>Database Archiving: How to Keep Lots of Data for a Very Long Time</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27607">
                <text>With the amount of data a business accumulates now doubling every 12 to 18 months, IT professionals need to know how to develop a system for archiving important database data, in a way that both satisfies regulatory requirements and is durable and secure. This important and timely new book explains how to solve these challenges without compromising the operation of current systems. It shows how to do all this as part of a standardized archival process that requires modest contributions from team members throughout an organization, rather than the superhuman effort of a dedicated team. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27608">
                <text>Olson, Jack E.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="27609">
                <text>Morgan Kaufmann</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="27610">
                <text>2008</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27611">
                <text>Johnson, Richard</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="285">
            <name>References</name>
            <description>A related resource that is referenced, cited, or otherwise pointed to by the described resource.</description>
            <elementTextContainer>
              <elementText elementTextId="27612">
                <text>http://www.amazon.com/Database-Archiving-Keep-Lots-Press/dp/0123747201/ref=asap_bc?ie=UTF8</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27613">
                <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="27614">
                <text>ISBN-10: 0123747201</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="27615">
                <text>Olson, Jack E. Database Archiving: How to Keep Lots of Data for a Very Long Time. Burlington, MA: Morgan Kaufmann/Elsevier, 2009. Print</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="27704">
                <text>Archives </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="163">
        <name>digital conversion</name>
      </tag>
      <tag tagId="346">
        <name>digital technologies</name>
      </tag>
      <tag tagId="104">
        <name>metadata</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="248" public="1" featured="0">
    <fileContainer>
      <file fileId="294">
        <src>http://dar.cah.ucf.edu/files/original/6c35d172ed9eadc449feead2c8bdab9d.jpg</src>
        <authentication>bfc25e2cfb69eed2635756b6adeee35a</authentication>
      </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>
    <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="26369">
                <text>Database as Genre: The Epic Transformation of Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26370">
                <text>Archives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26371">
                <text>This article juxtaposes the database and the archive, creating the idea of database as its own genre. Folsom, one of the editors of The Whitman Archive, begins discusses how photography for Walt Whitman was a form of database and how the archive is now akin to what Deleuze and Guattari like to a rhizome. Folsom clarifies that an archive will always hold more information than a database but that information in a database is more flexible and moveable. Using information on the creation of The Whitman Archive and decisions made provides an idea of the scope of a large archival digital humanities project. Understanding that you can take documents that could not previously be seen side by side due to physical locale can now be viewed together creates an understanding of the details one must plan for while deciding on the direction of an digital archive project.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26372">
                <text>Folsom, Ed</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="26373">
                <text>2007-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26374">
                <text>Elena Rogalle</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26375">
                <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="26377">
                <text>Folsom, Ed. 2007. "Database as Genre: The Epic Transformation of Archives." PMLA, 2007. 1571. JSTOR Journals, EBSCOhost (accessed November 30, 2015).</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="212">
        <name>digital images</name>
      </tag>
      <tag tagId="249">
        <name>photography</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="262" public="1" featured="0">
    <fileContainer>
      <file fileId="308">
        <src>http://dar.cah.ucf.edu/files/original/4bd6042a76bc5bc117ab111a35b04928.png</src>
        <authentication>1053746662a829842735f266635d53d7</authentication>
      </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="23">
      <name>Book Chapter</name>
      <description>book chapter from an anthology or collections of essays</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="26500">
                <text>Database as Symbolic Form</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26501">
                <text>Web archiving</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26502">
                <text>In his essay, Lev Manovich argues for the database as the key form of expression in digital culture, stating that the new cultural algorithm is a progression of information from reality, to media, to data, to the database. Manovich connects database philosophy to linguist Ferdinand de Saussure’s semiotic philosophy, stating that the database reverses the relationship of systemic elements as syntagmatic (in praesentia) or paradigmatic (in absentia); new media turns narrative—once seen as explicit—into a mere series of links, while the database stores the elements themselves. According to Manovich, this leads to both a desire for new and experimental forms of narrative, and a valuation of computer logic by artists and within the culture at large.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26503">
                <text>Manovich, Lev&#13;
Vesna, Victoria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="26504">
                <text>University of Minnesota 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="26505">
                <text>2007</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="26506">
                <text>Manovich, Lev. “Database as Symbolic Form.” In Database Aesthetics: Art in the Age of Information Overflow, edited by Victoria Vesna, 39-60. Minneapolis: University of Minnesota Press, 2007.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26711">
                <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="27751">
                <text>Essay</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="426">
        <name>computer</name>
      </tag>
      <tag tagId="346">
        <name>digital technologies</name>
      </tag>
      <tag tagId="358">
        <name>new media</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="275" public="1" featured="0">
    <fileContainer>
      <file fileId="321">
        <src>http://dar.cah.ucf.edu/files/original/0e9cab582e0d807a88dc14748c883c80.png</src>
        <authentication>f6b90d6b14f831040e5535ce7845a23e</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="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="26625">
              <text>http://www.davidrumsey.com/home</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="26615">
                <text>David Rumsey Map Collection</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26616">
                <text>Digital humanities</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26617">
                <text>The David Rumsey Map Collection features nearly 50,000 historical maps spanning from 1492 to the present-day. More than simply a repository, the website is an interactive database giving users the ability to download the actual record and create their own online content. The collection includes maps from Europe, the Americas, Africa, and the Middle East, covering a wide range of topics such as boundaries, wars, soil studies, and roads, to name a few. All of the images have been scanned and uploaded using the latest high-resolution technology, allowing viewers to zoom in and study the map in detail. In addition, many are also geo-tagged, expanding their usefulness in a variety of digital applications. Researchers can create a free account, login, and build “sets” of maps for their particular project using one of the several web applications such as Google Earth or the Luna Browser embedded into the site. Once these sets are created, images can be linked to or downloaded without restriction for non-commercial use under the Creative Commons license. &#13;
&#13;
This collection exemplifies best practices in the field, from high quality images to its intuitive, user-friendly interface and serves as a model for building a digital archive. By allowing fair-use of its content, this site is an important resource for those considering projects in digital history that explore spatial aspects.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26618">
                <text>Cartography Associates</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="26619">
                <text>Cartography Associates</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="26620">
                <text>2015</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26621">
                <text>Robert Clarke</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26622">
                <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="26624">
                <text>Cartography Associates. “David Rumsey Historical Map Collection.” Accessed September 10, 2015. http://www.davidrumsey.com/luna/servlet/</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="191">
        <name>content management</name>
      </tag>
      <tag tagId="235">
        <name>digital repositories</name>
      </tag>
      <tag tagId="216">
        <name>history</name>
      </tag>
      <tag tagId="97">
        <name>web archiving</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="55" public="1" featured="0">
    <fileContainer>
      <file fileId="27">
        <src>http://dar.cah.ucf.edu/files/original/db0321e2a8ac72af1cc1694a4077fb58.jpg</src>
        <authentication>b0d1c230c2e3c1a7196abd2c5fec886a</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="4004">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="73">
                <name>Height</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="4005">
                    <text>200</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="74">
                <name>Bit Depth</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="4006">
                    <text>8</text>
                  </elementText>
                </elementTextContainer>
              </element>
              <element elementId="75">
                <name>Channels</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="4007">
                    <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="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="25280">
              <text>http://dublincore.org/</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="25269">
                <text>DCMI Metadata Basics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25270">
                <text>Web archiving</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25271">
                <text>The Dublin Core Metadata Initiative, or "DCMI", is an open organization supporting innovation in metadata design and best practices across the metadata ecology. DCMI's activities include work on architecture and modeling, discussions and collaborative work in DCMI Communities and DCMI Task Groups, global conferences, meetings and workshops, and educational efforts to promote widespread acceptance of metadata standards and best practices. &#13;
&#13;
The DCMI website details the history and rationale of the Dublin Core Metadata Initiative and includes a thorough analysis of the metadata standards and guidelines. The site also provides a public space for communicating events, issues and publications sponsored by the DCMI.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25272">
                <text>Dublin Core Metadata Initiative</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="25273">
                <text>Dublin Core Metadata Initiative</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="25274">
                <text>1995-2012</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="266">
            <name>Date Created</name>
            <description>Date of creation of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="25275">
                <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="25276">
                <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="25277">
                <text>1995-2015 DCMI</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="25278">
                <text>Website</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="25279">
                <text>http://dublincore.org/metadata-basics/</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="430">
        <name>archival standards</name>
      </tag>
      <tag tagId="9">
        <name>archive practices</name>
      </tag>
      <tag tagId="63">
        <name>collaboration</name>
      </tag>
      <tag tagId="104">
        <name>metadata</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
