<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hi Channing,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">We have a similar issue at the Bodleian Libraries. Our approach is to have a repository were our published live catalogues are accessible and to then work on another version of the finding aid in
an unpublished repository. This allows us to make necessary re-drafts whilst maintaining access to a published version of the finding aid. We then replace the outdated published version.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Best wishes,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Matthew<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">----------------------------------<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Matthew Neely<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Senior Archivist<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Special Collections<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Bodleian Libraries<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Tel: 01865 287158<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Post: The Weston Library, Broad Street, Oxford, OX1 3BG<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Email: <a href="mailto:matthew.neely@bodleian.ox.ac.uk">
<span style="color:blue">matthew.neely@bodleian.ox.ac.uk</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Web: </span><span style="color:#1F497D"><a href="http://www.bodleian.ox.ac.uk/weston"><span style="color:blue">http://www.bodleian.ox.ac.uk/weston</span></a></span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org>
<b>On Behalf Of </b>Norton, Channing<br>
<b>Sent:</b> 04 April 2023 17:58<br>
<b>To:</b> archivesspace_users_group@lyralists.lyrasis.org<br>
<b>Subject:</b> [Archivesspace_Users_Group] Drafting changes to finding aids<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">All, <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Our institution is looking to adopt the current PUI after using one that was built in house for several years. Right now, our workflow for making large revisions to finding aids is to rely on a feature in our in-house
PUI that allowed us to keep the original versions of finding aids published while making changes without said changes being published. While experimenting with the current PUI, we cannot seem to find such a feature, nor a plugin to provide similar functionality.
Has anyone else run into this need? If so, what solutions, both administrative and technical, have you used to address it?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Any and all help is appreciated,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Channing Norton<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">University of Rochester<o:p></o:p></span></p>
</div>
</body>
</html>