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

[Tang, Lydia]

Thanks for the context, Jason.  My IT person loaded a database backup from the summer and I was able to download the collection’s EAD and import it into our production database.  Even then, a few random objects showed up and I had to edit and save the collection in order for the Resource record to show up.  I think we lost our earlier attached Subjects and Agents but at least we have the inventory.  Luckily with only 600 collections, I could check everything else (however tedious), but I would be worried if I had a much larger collection and wouldn’t be able to know what might have been lost!
Crisis averted for now.  ;)
Lydia
From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jason Loeffler <j at minorscience.com>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Tuesday, March 13, 2018 at 3:11 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] "lost" collections after transferring between repositories/upgrades?

In 1.5.1 there was a major issue with "losing" connections between repositories and digital objects when digital objects were transferred between repositories.

https://archivesspace.atlassian.net/projects/AR/issues/AR-1405

But what you describe may be an indexing issue. Brute force approach, but have you rebuilt the index from scratch?

Jason

On Tue, Mar 13, 2018 at 2:54 PM, Tang, Lydia <ltang5 at lib.msu.edu<mailto:ltang5 at lib.msu.edu>> wrote:
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!
Lydia
--
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<mailto:ltang5 at msu.edu>
Phone: 517-884-8984<tel:517-884-8984>
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group