<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta content="text/html; charset=utf-8">
</head>
<body>
<div>Ben,</div>
<div><br>
</div>
<div>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.
</div>
<div><br>
</div>
<div>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. <a href="https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asAutoReplaceContainers.py">
https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asAutoReplaceContainers.py</a></div>
<div><br>
</div>
<div>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.
<a href="https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asReplaceContainers.py">
https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asReplaceContainers.py</a></div>
<div><br>
</div>
<div>There should be documentation in the repo, but let me know if you get stuck.
</div>
<div><br>
</div>
<div>-Patrick Galligan </div>
<br>
Sent with BlackBerry Work<br>
(www.blackberry.com)<br>
<br>
<div class="gw_quote" style="border-top:#b5c4df 1pt solid; padding-top:6px; font-size:14px">
<div><b>From: </b><span>Ben Goldman <<a href="mailto:bmg17@psu.edu">bmg17@psu.edu</a>></span></div>
<div><b>Date: </b><span>Thursday, Jun 29, 2017, 3:52 AM</span></div>
<div><b>To: </b><span>Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>></span></div>
<div><b>Subject: </b><span>[Archivesspace_Users_Group] merging/fixing duplicate top containers</span></div>
</div>
<br>
<div>
<div style="font-family:georgia,serif; font-size:10pt; color:#000000">
<div>Hello,</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div><img src="cid:0adb6e00e3d922e8cd87529d47fe6d5a6e97f6b0@zimbra"></div>
<div><br>
Thanks much,</div>
<div>Ben</div>
<div><br>
</div>
<div>
<div><strong>Ben Goldman</strong><br>
Digital Records Archivist & <br>
Sally W. Kalin Early Career Librarian for Technological Innovations<br>
Penn State University Libraries</div>
</div>
</div>
</div>
</body>
</html>