<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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-US" link="blue" vlink="purple">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>Hi, Suzanne.</p>
<p><br>
</p>
<p>Yep, that's exactly the way to do it, and exactly why the "unassociated" option was added. </p>
<p><br>
</p>
<p>Since top containers are scoped to repositories, though, if you have multiple repositories in your installation, then you'll need to perform this action within each repository. We've assigned this cleanup task as something that our repository managers should
do on a periodic basis. </p>
<p><br>
</p>
<p>We haven't decided to automate this task yet, however, which I guess gives us the opportunity to make sure that everything looks okay before activating the bulk delete option. That said, I think that automating this on a periodic basis outside of normal
business hours could be the way to go. We had originally hoped that orphaned top containers could never be created in the staff application, but given that they can be associated with different resource, accession, and archival object records, it would be
a bit tricky to do that, so orphaned, or unassociated, top containers will be created if an entire resource record is deleted, for instance. Same thing happens right now for digital object records; the only difference there is that digital objects can also
be created as stand-alone records in the staff interface, whereas you can't do that with top containers (without using the API). </p>
<p><br>
</p>
<p>Mark</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Stasiulatis,
Suzanne <sustasiula@pa.gov><br>
<b>Sent:</b> Saturday, September 16, 2017 1:55:14 PM<br>
<b>To:</b> archivesspace_users_group@lyralists.lyrasis.org<br>
<b>Subject:</b> [Archivesspace_Users_Group] Deleting Empty Top Containers</font>
<div> </div>
</div>
<div>
<div class="WordSection1">
<p class="MsoNormal">Hello,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am working in ArchivesSpace version 1.5.4. I’d like to delete all of our empty top containers through the staff interface. By empty, I mean top containers that aren’t linked to any archival objects. I believe we created containers in
the archival object page and then unlinked them at some point. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In <u>Manage Top Containers</u>, you can choose <u>Yes</u> for
<u>Unassociated containers</u> and leave all other fields blank. This gives us a very long list. Can anyone confirm that this list includes all of our empty top containers and only our empty top containers?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><img width="874" height="479" style="width:9.1041in;height:4.9895in" id="Picture_x0020_1" src="cid:image001.png@01D32EEF.C216EC60"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Suzanne<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy">Suzanne Stasiulatis
</span></b><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy">| Archivist II<br>
Pennsylvania Historical and Museum Commission<b> </b>| Pennsylvania State Archives<br>
350 North Street | Harrisburg, PA 17120-0090<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.phmc.pa.gov_Archives&d=DwMFAg&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=p6DgPzipKtHj5MNdBWmiUC7F9PxIagbI68ckkTxVYSQ&s=L5_6KoOslchLuYAG4MlU2hUAyE1KmI2Y-fkbpZn5N5o&e="><span style="color:blue">www.phmc.pa.gov/Archives</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#17365D"><a href="mailto:sustasiula@pa.gov"><span style="color:blue">sustasiula@pa.gov</span></a></span><u><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:blue"><o:p></o:p></span></u></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>