[Archivesspace_Users_Group] "lost" collections after transferring between repositories/upgrades?

Tang, Lydia ltang5 at lib.msu.edu
Tue Mar 13 14:54:39 EDT 2018

I’ve noticed some disturbing behavior…  I was using a separate Data Entry repository for volunteers and less-trained student workers to add data into ArchivesSpace and then would transfer them into the production server.  It seems to me that at some point with our upgrades or somehow, these inventories have been lost(!).  There were some times when I would transfer the collections between repositories that the system seemed to time out.  I had assumed that the collection eventually made it from one repository to another, but I probably should have checked.  Does it seem possible that collections do get lost like this?
Additionally, we have some wonky scenarios where collections seem to be “mostly lost”, but then if I can find a random Top Container, I can edit the record again to have it reindex and show up.  It has happened a couple of times!  During this time, we were on versions 1.5.3 – 2.1.1
Anyone else notice this?  Thanks!
Dr. Lydia Tang, CA, DMA, MLIS
Special Collections Archivist-Librarian
Philosophy, Aesthetics, and Ethics Bibliographer
Michigan State University Libraries
366 W. Circle Drive (DB 6)
East Lansing, MI 48824-1048
Email: ltang5 at msu.edu
Phone: 517-884-8984

More information about the Archivesspace_Users_Group mailing list