<mods:mods version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><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></mods:mods>