Dear Michael, (My assumption is that you're referring to batch importing EADs. If this is for something else, please let us know.)
There are a number of users here who have a great deal of experience with batch importing EADs in ArchivesSpace. I know that the folks at Harvard specifically have put together a suite of tools for checking and batch processing EADs and presented on this at the ArchivesSpace Member Forum in August. The files from their presentation are at http://bit.ly/2a4VvgV and this document - https://docs.google.com/document/d/1S6fgCYnEPnyPPhqscx5O2iSW9nvl9Tc7WeHc8dnsIBA/edit - has explanations and links to some of their tools. They or some of our other power EAD importers can likely give you more guidance on diagnosing problem files within a larger batch. Christine Christine Di Bella Community Outreach Manager christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org> 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [cid:image003.png@01CE734E.FD759D30] From: archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of Michael Ridderbusch Sent: Friday, September 16, 2016 3:32 PM To: archivesspace_users_group@lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] batch importation -- identifying problem records If a background job for a batch importation fails due to a record or two, how can I easily identify the problem records?
_______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
