[Archivesspace_Users_Group] location woes

Elizabeth Dunham Elizabeth.Dunham at asu.edu
Wed Sep 14 15:18:24 EDT 2016

Hi Lydia,

Is SQL an option for you?  I had a much smaller version of this problem a few months ago when one of my curators unintentionally batch created about 1,500 meaningless location records.  She was trying to create two sets of locations with different identifiers, but ended up with one set of locations containing both identifiers.  Fortunately, that composition and the fact that nothing was linked to those locations (seeing as it's physically impossible to put something on the referenced shelf space) made them easy to target and eliminate using a SQL "delete" statement.

By way of disclaimer, SQL is the only language I'm confident enough in to do this sort of work, so I tend to use it for everything.  As such, someone else may have a much more elegant solution.

I hope this information helps, and good luck!


Assistant Archivist
Arizona State University Libraries
Archives and Special Collections
Tempe, AZ 85287-1006
Elizabeth.Dunham at asu.edu

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia
Sent: Wednesday, September 14, 2016 11:56 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] location woes

Hello everyone,

I’ve definitely learned to try out my more ambitious projects in our test instance after this location snafu.  We tried to roll back the instance to a backup last night, reindexed everything, and the bad locations were all still there!  If any of you know of a way to target mass delete the locations (nearly 6500 location entries), please let me know!


Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org

More information about the Archivesspace_Users_Group mailing list