<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>Manage - rather than be managed by - your Primo Sandbox environment</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Kevin J.</mods:namePart><mods:namePart type="family">Collins</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Alevtina</mods:namePart><mods:namePart type="family">Verbovetskaya</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>Does your Primo Sandbox automatically update from your non-production ILS environment, even after you update your non-production ILS? Do you make it easy for all staff (including that one cataloger who doesn't like working with ILS batch processes) to have records moved into Primo Sandbox--without anyone stopping their work to finagle yet another batch load?&#13;
&#13;
Do you have a streamlined procedure for bringing tested Sandbox rule changes over to Production? Keeping your test environments in sync (ILS&lt;--&gt;Primo, Primo Sandbox&lt;--&gt;Primo Production) can be made more responsive and nimble to allow staff to focus on higher value projects. Find out how CUNY does it!</mods:abstract><mods:classification authority="lcc">Aleph</mods:classification><mods:classification authority="lcc">MetaLib</mods:classification><mods:classification authority="lcc">Primo</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2016-05-05</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>