<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="36" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://www.omeka01.611b.net/items/show/36?output=omeka-xml" accessDate="2026-10-24T00:42:46+00:00">
  <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="105">
                <text>BibTeX_Export</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="619">
              <text>Managing a Cluster of Single-Purpose Web Servers: Administrative and Technical Issues</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="620">
              <text>Conference Paper</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="621">
              <text>Paul A Soderdahl</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="622">
              <text>1997</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="623">
              <text>eng</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
    <elementSet elementSetId="4">
      <name>Zotero</name>
      <description/>
      <elementContainer>
        <element elementId="178">
          <name>Title</name>
          <description/>
          <elementTextContainer>
            <elementText elementTextId="624">
              <text>Managing a Cluster of Single-Purpose Web Servers: Administrative and Technical Issues</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="81">
          <name>Item Type</name>
          <description/>
          <elementTextContainer>
            <elementText elementTextId="625">
              <text>Conference Paper</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="54">
          <name>Author</name>
          <description/>
          <elementTextContainer>
            <elementText elementTextId="626">
              <text>Paul A Soderdahl</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="149">
          <name>Place</name>
          <description/>
          <elementTextContainer>
            <elementText elementTextId="627">
              <text>Orlando, Florida</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="110">
          <name>Date</name>
          <description/>
          <elementTextContainer>
            <elementText elementTextId="628">
              <text>1997</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="133">
          <name>Language</name>
          <description/>
          <elementTextContainer>
            <elementText elementTextId="629">
              <text>eng</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="86">
          <name>Abstract Note</name>
          <description/>
          <elementTextContainer>
            <elementText elementTextId="630">
              <text>While the preferred model for a web server at many institutions is to install, maintain, and support a single server for the entire organization, the University of Iowa Libraries uses an alternate model providing a number of different web servers across a number of different platforms in support of the Libraries' web project. This hybrid solution offers several advantages over a single-server solution. Such an implementation allows more content providers to deliver information in its existing format, and also allows the Libraries to offer new services quickly as more desktop applications integrate a web server component. Employing this type of solution, the University of Iowa Libraries currently provides information and services on 10 distinct web servers, with five additional servers either in development or under consideration. The solution enables the Libraries to embrace the web for delivery of important information and services to its clientele.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="153">
          <name>Proceedings Title</name>
          <description/>
          <elementTextContainer>
            <elementText elementTextId="631">
              <text>CAUSE</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
  <tagContainer>
    <tag tagId="2">
      <name>Library and Information Science</name>
    </tag>
  </tagContainer>
</item>
