<mets:mets OBJID="eprint_22" LABEL="Eprints Item" xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/mets.xsd http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" xmlns:mets="http://www.loc.gov/METS/" xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><mets:metsHdr CREATEDATE="2026-06-09T08:32:08Z"><mets:agent ROLE="CUSTODIAN" TYPE="ORGANIZATION"><mets:name>ELUNA Document Repository</mets:name></mets:agent></mets:metsHdr><mets:dmdSec ID="DMD_eprint_22_mods"><mets:mdWrap MDTYPE="MODS"><mets:xmlData><mods:titleInfo><mods:title>Database Architecture for Consortia : How It Effects Your Use of ALEPH -- Sharing, Sort of&#13;
</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Michelle</mods:namePart><mods:namePart type="family">Newberry</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>This presentation will outline some of the intended and unintended consequences of database architecture choices (one/multiple ADM, one/multiple BIB, etc.). Representatives of three consortia will describe their systems’ architecture and their pros and cons. Areas that will be explored are: functionality, staffing, scalability, and so on. How much do their members share versus keep separate?&#13;
Version: all</mods:abstract><mods:classification authority="lcc">Aleph</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2005-06-07</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mets:xmlData></mets:mdWrap></mets:dmdSec><mets:amdSec ID="TMD_eprint_22"><mets:rightsMD ID="rights_eprint_22_mods"><mets:mdWrap MDTYPE="MODS"><mets:xmlData><mods:useAndReproduction>
<p xmlns="http://www.w3.org/1999/xhtml"><strong>For work being deposited by its own author:</strong> 
In self-archiving this collection of files and associated bibliographic 
metadata, I grant ELUNA Document Repository the right to store 
them and to make them permanently available publicly for free on-line. 
I declare that this material is my own intellectual property and I 
understand that ELUNA Document Repository does not assume any 
responsibility if there is any breach of copyright in distributing these 
files or metadata. (All authors are urged to prominently assert their 
copyright on the title page of their work.)</p>

<p xmlns="http://www.w3.org/1999/xhtml"><strong>For work being deposited by someone other than its 
author:</strong> I hereby declare that the collection of files and 
associated bibliographic metadata that I am archiving at 
ELUNA Document Repository) is in the public domain. If this is 
not the case, I accept full responsibility for any breach of copyright 
that distributing these files or metadata may entail.</p>

<p xmlns="http://www.w3.org/1999/xhtml">Clicking on the deposit button indicates your agreement to these 
terms.</p>
    </mods:useAndReproduction></mets:xmlData></mets:mdWrap></mets:rightsMD></mets:amdSec><mets:fileSec><mets:fileGrp USE="reference"><mets:file ID="eprint_22_27_1" SIZE="1289957" OWNERID="https://documents.el-una.org/id/eprint/22/1/naaug-2005-newberry.pdf" MIMETYPE="application/pdf"><mets:FLocat LOCTYPE="URL" xlink:type="simple" xlink:href="https://documents.el-una.org/id/eprint/22/1/naaug-2005-newberry.pdf"></mets:FLocat></mets:file></mets:fileGrp></mets:fileSec><mets:structMap><mets:div DMDID="DMD_eprint_22_mods" ADMID="TMD_eprint_22"><mets:fptr FILEID="eprint_22_document_27_1"></mets:fptr></mets:div></mets:structMap></mets:mets>