<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>Aleph Deployment Process: Why you need multiple Aleph environments&#13;
</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Nelson</mods:namePart><mods:namePart type="family">Sandberg</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Brian</mods:namePart><mods:namePart type="family">Romrell</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>This session highlights the benefits on running multiple Aleph environments in development, test, and production. We will discuss how quality assurance and application testing guarantees successful change control. Our session includes a demo on rolling up Aleph configurations through the different environments.&#13;
</mods:abstract><mods:classification authority="lcc">Aleph</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2012-05-11</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>