[Archivesspace_Users_Group] batch import of ead

[Kottman, Miloche]

The imports of EADs has worked this way since at least version 1.00.  If any EAD fails ArchivesSpace validation, the entire job fails.

I second the suggestion of calling this a bug.  I would expect the “good” records to load and would love to see the validation errors for any and all EADs that were unable to load.

--Miloche Kottman
University of Kansas


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Nathan Stevens
Sent: Monday, January 12, 2015 9:14 AM
To: Vandermillen, Michael
Cc: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] batch import of ead

Can you forward this message to the mailing list (archivesspace_users_group at lyralists.lyrasis.org<http://lyralists.lyrasis.org>) since it may be a bug other users have seen.

On Fri, Jan 9, 2015 at 4:05 PM, Vandermillen, Michael <michael_vandermillen at harvard.edu<mailto:michael_vandermillen at harvard.edu>> wrote:
Hi Nathan,
Do you know what the state of batch EAD import is? If I select multiple finding aids (36 in my case), I see them all appear in my import job queue, but then I get a failure message. I’m working with a set of Finding Aids in which I know some will load successfully but some won’t. I was assuming the bad would fail and the good would load, but seems to abort immediately.
Thanks-
Michael



--
Nathan Stevens
Programmer/Analyst
Digital Library Technology Services
New York University

1212-998-2653
ns96 at nyu.edu<mailto:ns96 at nyu.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150112/522012b7/attachment.html>