Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

2017-01-25 Thread Bria Lynn Parker 
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, so I could easily purge all the old top containers...

Thanks all for the guidance, though!

On Tue, Jan 24, 2017 at 11:24 AM, Majewski, Steven Dennis (sdm7g) <
sd...@eservices.virginia.edu> wrote:

>
> 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 a mismatch between barcode and barcode_1 — the
> inverse error of the one above: same container, different barcodes.
>
> — Steve.
>
>
>
> On Jan 24, 2017, at 11:10 AM, Bria Lynn Parker  wrote:
>
> 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  wrot
> e:
>
>> Hi all - I'm hoping someone has a tip or hint at where I'm going wrong:
>>
>> We've finished cleaning up/normalizing our EAD (including implementing
>> container attributes and the like for container management). The majority
>> are importing fine, no errors (or, at least no errors I can't find and fix,
>> like bad begin/ends). However, for some of our finding aids, I'm getting
>> the following:
>>
>> indicator_1 : Mismatch when mapping between indicator and indicator_1
>>
>> No other info about location, etc. I've about torn my hair out trying to
>> find *any* mismatch of container data - I've checked every instance's
>> dummy barcode (which is constructed in part from the id), id, and parent
>> against itself, crosschecked with the container indicator, and they all
>> match within themselves. We're importing barcodes in the label attribute,
>> which
>> works (except when it doesn't here?). The error message getting thrown is
>> from this ruby function https://github.com/archivesspa
>> ce/archivesspace/blob/5e1ca66f1f04f142f2695024efb72008250463
>> 25/backend/app/lib/aspace_json_to_managed_container_mapper.rb#L173
>>
>> Help? If someone has encountered this and figured it out, let me know -
>> I'd love some help. If you want to contact me off list, I can sent you a
>> full xml file.
>> Here's an example from my xml:
>>
>>
>>
>> 
>>   
>> Financial Records -- General -- Bound Volumes --
>> Financial Reports
>> 1905-1908
>> 1
>> 1.0
>>   
>> 
>>
>>
>>   
>> Financial Records -- General -- Bound Volumes --
>> Financial Reports
>> 1909
>> 1
>> 2.0
>>   
>> 
>>
>>
>> 
>>   
>> Financial Records -- General -- Bound Volumes --
>> Financial Reports
>> 1910-1911
>> 1
>> 3.0
>>   
>> 
>>
>> (historical background - some of our series restart box numbers at 1, and
>> the container ids reflect that, so 89.1 is the 89th box in the collection,
>> but 1st in the series. This is not causing the error as far as I can tell,
>> since other collections with same numbering style import fine)
>>
>>
>> --
>> Bria L. Parker
>> Metadata Librarian
>> 2200 McKeldin Library
>> University of Maryland
>> College Park, MD 20742-7011
>> (301) 405-9067
>> blpar...@umd.edu
>>
>
>
>
> --
> Bria L. Parker
> Metadata Librarian
> 2200 McKeldin Library
> University of Maryland
> College Park, MD 20742-7011
> (301) 405-9067
> blpar...@umd.edu
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Bria L. Parker
Metadata Librarian

2200 McKeldin Library

University of Maryland

College Park, MD 20742-7011

(301) 405-9067

blpar...@umd.edu
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

2017-01-24 Thread Majewski, Steven Dennis (sdm7g) 

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 a mismatch between barcode and barcode_1 — the inverse error of 
the one above: same container, different barcodes.

— Steve.



On Jan 24, 2017, at 11:10 AM, Bria Lynn Parker 
> wrote:

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 finished cleaning up/normalizing our EAD (including implementing 
container attributes and the like for container management). The majority are 
importing fine, no errors (or, at least no errors I can't find and fix, like 
bad begin/ends). However, for some of our finding aids, I'm getting the 
following:

indicator_1 : Mismatch when mapping between indicator and indicator_1

No other info about location, etc. I've about torn my hair out trying to find 
any mismatch of container data - I've checked every instance's dummy barcode 
(which is constructed in part from the id), id, and parent against itself, 
crosschecked with the container indicator, and they all match within 
themselves. We're importing barcodes in the label attribute, which
works (except when it doesn't here?). The error message getting thrown is from 
this ruby function 
https://github.com/archivesspace/archivesspace/blob/5e1ca66f1f04f142f2695024efb7200825046325/backend/app/lib/aspace_json_to_managed_container_mapper.rb#L173

Help? If someone has encountered this and figured it out, let me know - I'd 
love some help. If you want to contact me off list, I can sent you a full xml 
file.
Here's an example from my xml:





  
Financial Records -- General -- Bound Volumes -- 
Financial Reports
1905-1908
1
1.0
  



   
  
Financial Records -- General -- Bound Volumes -- 
Financial Reports
1909
1
2.0
  



  
Financial Records -- General -- Bound Volumes -- 
Financial Reports
1910-1911
1
3.0
  


(historical background - some of our series restart box numbers at 1, and the 
container ids reflect that, so 89.1 is the 89th box in the collection, but 1st 
in the series. This is not causing the error as far as I can tell, since other 
collections with same numbering style import fine)


--
Bria L. Parker
Metadata Librarian
2200 McKeldin Library
University of Maryland
College Park, MD 20742-7011
(301) 405-9067
blpar...@umd.edu



--
Bria L. Parker
Metadata Librarian
2200 McKeldin Library
University of Maryland
College Park, MD 20742-7011
(301) 405-9067
blpar...@umd.edu
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

2017-01-24 Thread Galligan, Patrick 
Bria,

I can’t tell you where exactly this is happening, but mismatch between 
indicators usually means that you have two different top container indicators 
assigned to the same barcode.

You’d have to look at the barcodes that are already in the system, and any 
indicators associated with the import. I don’t see anything wrong in the 
snippet you sent below, but I also don’t really know what’s already in your 
database.

We had a lot of these errors when we migrated to 1.5.0.

-Patrick Galligan

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[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 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 
<blpar...@umd.edu<mailto:blpar...@umd.edu>> wrote:
Hi all - I'm hoping someone has a tip or hint at where I'm going wrong:

We've finished cleaning up/normalizing our EAD (including implementing 
container attributes and the like for container management). The majority are 
importing fine, no errors (or, at least no errors I can't find and fix, like 
bad begin/ends). However, for some of our finding aids, I'm getting the 
following:

indicator_1 : Mismatch when mapping between indicator and indicator_1

No other info about location, etc. I've about torn my hair out trying to find 
any mismatch of container data - I've checked every instance's dummy barcode 
(which is constructed in part from the id), id, and parent against itself, 
crosschecked with the container indicator, and they all match within 
themselves. We're importing barcodes in the label attribute, which
works (except when it doesn't here?). The error message getting thrown is from 
this ruby function 
https://github.com/archivesspace/archivesspace/blob/5e1ca66f1f04f142f2695024efb7200825046325/backend/app/lib/aspace_json_to_managed_container_mapper.rb#L173

Help? If someone has encountered this and figured it out, let me know - I'd 
love some help. If you want to contact me off list, I can sent you a full xml 
file.
Here's an example from my xml:


  
Financial Records -- General -- Bound Volumes -- 
Financial Reports
1905-1908
1
1.0
  


   
  
Financial Records -- General -- Bound Volumes -- 
Financial Reports
1909
1
2.0
  



  
Financial Records -- General -- Bound Volumes -- 
Financial Reports
1910-1911
1
3.0
  


(historical background - some of our series restart box numbers at 1, and the 
container ids reflect that, so 89.1 is the 89th box in the collection, but 1st 
in the series. This is not causing the error as far as I can tell, since other 
collections with same numbering style import fine)


--
Bria L. Parker
Metadata Librarian

2200 McKeldin Library

University of Maryland

College Park, MD 20742-7011

(301) 405-9067<tel:%28301%29%20405-9067>

blpar...@umd.edu<mailto:blpar...@umd.edu>



--
Bria L. Parker
Metadata Librarian

2200 McKeldin Library

University of Maryland

College Park, MD 20742-7011

(301) 405-9067<tel:%28301%29%20405-9067>

blpar...@umd.edu<mailto:blpar...@umd.edu>
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

2017-01-24 Thread Bria Lynn Parker 
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 finished cleaning up/normalizing our EAD (including implementing
> container attributes and the like for container management). The majority
> are importing fine, no errors (or, at least no errors I can't find and fix,
> like bad begin/ends). However, for some of our finding aids, I'm getting
> the following:
>
> indicator_1 : Mismatch when mapping between indicator and indicator_1
>
> No other info about location, etc. I've about torn my hair out trying to
> find *any* mismatch of container data - I've checked every instance's
> dummy barcode (which is constructed in part from the id), id, and parent
> against itself, crosschecked with the container indicator, and they all
> match within themselves. We're importing barcodes in the label attribute,
> which
> works (except when it doesn't here?). The error message getting thrown is
> from this ruby function https://github.com/archivesspace/archivesspace/
> blob/5e1ca66f1f04f142f2695024efb7200825046325/backend/app/lib/
> aspace_json_to_managed_container_mapper.rb#L173
>
> Help? If someone has encountered this and figured it out, let me know -
> I'd love some help. If you want to contact me off list, I can sent you a
> full xml file.
> Here's an example from my xml:
>
> 
>   
> Financial Records -- General -- Bound Volumes --
> Financial Reports
> 1905-1908
>  "box" id="89.1">1
> 1.0
>   
> 
>
>
>   
> Financial Records -- General -- Bound Volumes --
> Financial Reports
> 1909
>  "box" id="89.1">1
> 2.0
>   
> 
>
>
> 
>   
> Financial Records -- General -- Bound Volumes --
> Financial Reports
> 1910-1911
>  "box" id="89.1">1
> 3.0
>   
> 
>
> (historical background - some of our series restart box numbers at 1, and
> the container ids reflect that, so 89.1 is the 89th box in the collection,
> but 1st in the series. This is not causing the error as far as I can tell,
> since other collections with same numbering style import fine)
>
>
> --
> Bria L. Parker
> Metadata Librarian
>
> 2200 McKeldin Library
>
> University of Maryland
>
> College Park, MD 20742-7011
>
> (301) 405-9067
>
> blpar...@umd.edu
>



-- 
Bria L. Parker
Metadata Librarian

2200 McKeldin Library

University of Maryland

College Park, MD 20742-7011

(301) 405-9067

blpar...@umd.edu
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group