Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

Well, so it turns out the issue wasn't so much with my data, but that I did not realize that deleting a resource does not also delete the top containers created when importing a resource and associated with that resource. So my own testing was my downfall! Thankfully this was all on a test server,

Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

I was getting that error on 1.5.2 migration ( see other email thread ) and that one turned out to be due to an erroneous duplicate barcode assigned to different containers with different indicators. In the other cases, where there were trailing spaces in one of the barcodes, the message was

Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of Bria Lynn Parker Sent: Tuesday, January 24, 2017 11:10 AM To: Archivesspace Users Group <Archivesspace_Users_Group@lyralists.lyrasis.org> Subject: Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch I should add: I'm running

Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

I should add: I'm running 1.5.2, and I have checked for sneaky whitespaces within any of these attributes and have found none. On Tue, Jan 24, 2017 at 11:06 AM, Bria Lynn Parker wrote: > Hi all - I'm hoping someone has a tip or hint at where I'm going wrong: > > We've