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

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


On Tue, Mar 13, 2018 at 2:54 PM, Tang, Lydia <> 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:
> Phone: 517-884-8984
> _______________________________________________
> Archivesspace_Users_Group mailing list
Archivesspace_Users_Group mailing list

Reply via email to