[Archivesspace_Users_Group] Loading long CSV files for accessions in ArchivesSpace

Bowers, Kate A. kate_bowers at harvard.edu
Mon Oct 19 09:28:03 EDT 2020

Do you have an idea of what the limit is? That is: what is the largest number of rows you have successfully imported as accessions via spreadsheet?


Kate Bowers
Collections Services Archivist for Metadata, Standards, and Systems
Harvard University Archives
kate_bowers at harvard.edu

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of philip.webster at sheffield.ac.uk
Sent: Monday, October 19, 2020 9:11 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Loading long CSV files for accessions in ArchivesSpace

One thing we have noticed when attempting to batch load accessions using CSV import capability in ArchivesSpace is that there appears to be some sort of limit that prevents us from loading large numbers of items.
I could think of several reasons why this may be the case.

  1.  There may be a hard-coded limit on the number of rows that can be processed in a single background process.
  2.  There may be a relationship between the amount of memory allocated to ArchivesSpace and the number of rows that can be processed.
  3.  There may be a limited amount of time the background process can run for.

Our current workaround is to split the accessions import CSV into multiple files and load them in sequence.
Does anyone on the mailing list know what could be causing the batch process stop before finishing an entire CSV file?

Philip Webster
The University of Sheffield

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20201019/ba6b1bb0/attachment.html>

More information about the Archivesspace_Users_Group mailing list