[Archivesspace_Users_Group] merging/fixing duplicate top containers

Ben Goldman bmg17 at psu.edu
Thu Jun 29 10:29:54 EDT 2017

Thanks, Patrick. 

asReplaceContainers.py looks especially useful in our case. Can you tell me whether it retains Child Type and Child Indicator when it replaces a Top Container? 


Ben Goldman 
Digital Records Archivist & 
Sally W. Kalin Early Career Librarian for Technological Innovations 
Penn State University Libraries 

From: "Galligan, Patrick" <PGalligan at rockarch.org> 
To: "Archivesspace Users Group" <archivesspace_users_group at lyralists.lyrasis.org> 
Sent: Wednesday, June 28, 2017 3:03:00 PM 
Subject: Re: [Archivesspace_Users_Group] merging/fixing duplicate top containers 


So, uh, we had some of the same issue. We generally identified that you need at least one barcode to realistically do it in our case. We have two scripts. 

1. This one is for resources where the Box numbers don't restart at 1 every series. It won't work if you have two separate box 1s. We know the script is a little messy, but we haven't had the chance to test a refactor. It basically matches based on logic around our barcodes. You could change this to match around other logic as necessary. Like you might be able to split your indicators and match based off of those. We did barcodes because we had faux codes after migration and it was the easiest way to identify the "real" container. [ https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asAutoReplaceContainers.py | 
https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asAutoReplaceContainers.py ] 

2. This you can use on resources that restart numbers. It's pretty manual, and you have to create a Csv first, but it gets the job done. [ https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asReplaceContainers.py | 
https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asReplaceContainers.py ] 

There should be documentation in the repo, but let me know if you get stuck. 

-Patrick Galligan 

Sent with BlackBerry Work 

From: Ben Goldman < [ mailto:bmg17 at psu.edu | bmg17 at psu.edu ] > 
Date: Thursday, Jun 29, 2017, 3:52 AM 
To: Archivesspace Users Group < [ mailto:archivesspace_users_group at lyralists.lyrasis.org | archivesspace_users_group at lyralists.lyrasis.org ] > 
Subject: [Archivesspace_Users_Group] merging/fixing duplicate top containers 


Without realizing it, we migrated a considerable number of poorly encoded instances into ASpace 1.5 and its new container model. We're trying to figure out how best to deal cases like the one in the screenshot below, where historical practice has found us encoding box and folder numbers in a single instance, with values separated by a slash. Until a merge feature is implemented, it looks like we may have to do this through the API, and I'm wondering if anyone has tackled something similar and can possibly share a solution. 

Thanks much, 

Ben Goldman 
Digital Records Archivist & 
Sally W. Kalin Early Career Librarian for Technological Innovations 
Penn State University Libraries 

Archivesspace_Users_Group mailing list 
Archivesspace_Users_Group at lyralists.lyrasis.org 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170629/2c188863/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-06-28 at 1.48.32 PM.png
Type: image/png
Size: 104679 bytes
Desc: Screen Shot 2017-06-28 at 1.48.32 PM.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170629/2c188863/attachment-0001.png>

More information about the Archivesspace_Users_Group mailing list