[Archivesspace_Users_Group] Deleting Empty Top Containers

Custer, Mark mark.custer at yale.edu
Sun Sep 17 14:09:48 EDT 2017


Hi, Suzanne.


Yep, that's exactly the way to do it, and exactly why the "unassociated" option was added.


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.


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).


Mark

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Stasiulatis, Suzanne <sustasiula at pa.gov>
Sent: Saturday, September 16, 2017 1:55:14 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers

Hello,

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.

In Manage Top Containers, you can choose Yes for Unassociated containers 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?

[cid:image001.png at 01D32EEF.C216EC60]

Thanks!

Suzanne

Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090
www.phmc.pa.gov/Archives<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=>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170917/fc1da9b1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 52962 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170917/fc1da9b1/attachment.png>


More information about the Archivesspace_Users_Group mailing list