[Archivesspace_Users_Group] Issues Importing/Rearranging Large Collection

Christine Di Bella christine.dibella at lyrasis.org
Tue Jan 3 09:34:05 EST 2017

Hi Alex,

Thanks for bringing this to our attention. As many people are getting back to work this week, you may see some responses on the list. I’m also going to separately open up a tech support ticket and ask our tech folks to investigate. (You’ll see a separate message directly to you from me about this in a little bit.)


Christine Di Bella
ArchivesSpace Community Outreach Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
cdibella13 (Skype)

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Alexander Duryee
Sent: Wednesday, December 28, 2016 4:02 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Issues Importing/Rearranging Large Collection

We were able to successfully import a large collection (~2000 components) into ArchivesSpace, and imported a set of additions to the collection as well.  However, after importing the additions, we ran into two problems:
1)  After importing the additions via the API, many of the archival objects also have additional "ghost" records in the tree view.  These records are just pointers to the "real" object - clicking them opens the correct object - but they cannot be moved/deleted from the collection.  In addition, these records are exporting in the EAD XML output (as copies of the "real" record).  Most perplexingly, these ghost records don't appear as archival objects in the backend database - only via the frontend and exports.
2) When rearranging archival objects within the collection (via the tree view), the object first appears in the proper location.  However, when refreshing the collection, the component appears 5-10 objects away from where it was dropped.  This is reinforced by the object's position value in the database - for example, drag-and-dropping an object to position 205 will save it at position 198 instead.
Any ideas as to causes/solutions/workarounds would be tremendously appreciated.
Many thanks!

Alexander Duryee
Metadata Archivist
New York Public Library
alexanderduryee at nypl.org<mailto:alexanderduryee at nypl.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170103/ac672778/attachment.html>

More information about the Archivesspace_Users_Group mailing list