date:20170124

Re: [Archivesspace_Users_Group] Cataloged note field

2017-01-24 Thread Noah Huffman

Strange.  My cataloged_note content from AT mapped to the Outcome Note field of 
the event record (see screenshot).  But, I migrated from AT to an early version 
of ASpace (1.3?).  I wonder if the mappings have changed since. Let me know 
what you discover.

[cid:image002.jpg@01D2765A.89DDBBB0]

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Adam Jazairi
Sent: Tuesday, January 24, 2017 3:24 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Cataloged note field

Hi Noah,

Thanks for getting back to me. I should've clarified that though we're 
currently running 1.5.2, we used the plugin to migrate to 1.4.2 first. Sorry 
for any confusion.

Our ArchivesSpace instance maps cataloged notes to events, but only partially. 
The events include the date accessioned and the linked record, but not the note 
itself. I wonder if this is an issue with the Archivists' Toolkit migration 
plugin. I'll have a look at the source code and see if anything looks awry.

Adam

--
Adam Jazairi
Digital Library Applications Developer
Boston College Libraries
(617) 552-1404
jaza...@bc.edu

On Tue, Jan 24, 2017 at 2:47 PM, Noah Huffman 
> wrote:
Hi Adam,

It’s recommended that you run the AT migration plugin to ArchivesSpace v.1.4.2 
and then upgrade to ArchivesSpace to 1.5.2.

Even so, I’m not clear on where the cataloged_note field maps.  According to 
the AT migration mapping 
documentation,
 it should map to a collection management record, but I’m not seeing that field 
in collection management.  As part of the 1.4.2 to 1.5.X upgrade, some 
collection management fields were converted to event records.  You might check 
to see if any of your cataloged_note fields from AT now exist as event records 
in ArchivesSpace.  I’m seeing some in my database, so I suspect that is what 
happened.

-Noah

Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
http://library.duke.edu/rubenstein/

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org

[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org]
 On Behalf Of Adam Jazairi
Sent: Tuesday, January 24, 2017 10:13 AM
To: Archivesspace Users Group 
>
Subject: [Archivesspace_Users_Group] Cataloged note field

Hello all,

My institution is in the process of migrating from Archivists' Toolkit to 
ArchivesSpace, and we've noticed that the cataloged note field doesn't seem to 
map. This seems to be intentional, based on the discussion in the following 
ticket: 
https://archivesspace.atlassian.net/browse/AR-827

This is problematic for us because some of our records have important data in 
this field that we don't want to lose. Has anyone else encountered this issue? 
If so, I'd appreciate any advice on how to resolve it.

For reference, we're running ArchivesSpace 1.5.2 and used the AT migration 
plugin
 to migrate our database.

Thanks,

Adam

--
Adam Jazairi
Digital Library Applications Developer
Boston College Libraries
(617) 552-1404
jaza...@bc.edu

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org

[Archivesspace_Users_Group] ARCHON sort titles not migrating

2017-01-24 Thread Teitelbaum, Jesse

We are migrating ARCHON records to  AS 1.4.2 and the collection titles are 
coming over alphabetically by title and not the "sort title."  For example, in 
ARCHON, the "Papers of John Doe" are listed under D for DOE, but when brought 
over to AS, all the collections beginning with "Papers of..." are listed under 
"P."

Does 1.5.2 fix this?  Or is a plug-in required?  Thanks.

Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelb...@pabmc.net
www.house.state.pa.us/BMC/archives


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

Re: [Archivesspace_Users_Group] Cataloged note field

2017-01-24 Thread Adam Jazairi

Hi Noah,

Thanks for getting back to me. I should've clarified that though we're
currently running 1.5.2, we used the plugin to migrate to 1.4.2 first.
Sorry for any confusion.

Our ArchivesSpace instance maps cataloged notes to events, but only
partially. The events include the date accessioned and the linked record,
but not the note itself. I wonder if this is an issue with the Archivists'
Toolkit migration plugin. I'll have a look at the source code and see if
anything looks awry.

Adam

--
Adam Jazairi
Digital Library Applications Developer
Boston College Libraries
(617) 552-1404
jaza...@bc.edu

On Tue, Jan 24, 2017 at 2:47 PM, Noah Huffman  wrote:

> Hi Adam,
>
>
>
> It’s recommended that you run the AT migration plugin to ArchivesSpace
> v.1.4.2 and then upgrade to ArchivesSpace to 1.5.2.
>
>
>
> Even so, I’m not clear on where the cataloged_note field maps.  According
> to the AT migration mapping documentation
> ,
> it should map to a collection management record, but I’m not seeing that
> field in collection management.  As part of the 1.4.2 to 1.5.X upgrade,
> some collection management fields were converted to event records.  You
> might check to see if any of your cataloged_note fields from AT now exist
> as event records in ArchivesSpace.  I’m seeing some in my database, so I
> suspect that is what happened.
>
>
>
> -Noah
>
>
>
> 
>
> Noah Huffman
>
> Archivist for Metadata, Systems, and Digital Records
>
> David M. Rubenstein Rare Book & Manuscript Library
>
> Duke University | 919-660-5982 <(919)%20660-5982>
>
> http://library.duke.edu/rubenstein/
>
>
>
>
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:
> archivesspace_users_group-boun...@lyralists.lyrasis.org] *On Behalf Of *Adam
> Jazairi
> *Sent:* Tuesday, January 24, 2017 10:13 AM
> *To:* Archivesspace Users Group  lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] Cataloged note field
>
>
>
> Hello all,
>
>
>
> My institution is in the process of migrating from Archivists' Toolkit to
> ArchivesSpace, and we've noticed that the cataloged note field doesn't seem
> to map. This seems to be intentional, based on the discussion in the
> following ticket: https://archivesspace.atlassian.net/browse/AR-827
> 
>
>
>
> This is problematic for us because some of our records have important data
> in this field that we don't want to lose. Has anyone else encountered this
> issue? If so, I'd appreciate any advice on how to resolve it.
>
>
>
> For reference, we're running ArchivesSpace 1.5.2 and used the AT
> migration plugin
> 
> to migrate our database.
>
>
>
> Thanks,
>
>
>
> Adam
>
>
> --
>
> Adam Jazairi
>
> Digital Library Applications Developer
>
> Boston College Libraries
>
> (617) 552-1404
>
> jaza...@bc.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] Cataloged note field

2017-01-24 Thread Noah Huffman

Hi Adam,

It’s recommended that you run the AT migration plugin to ArchivesSpace v.1.4.2 
and then upgrade to ArchivesSpace to 1.5.2.

Even so, I’m not clear on where the cataloged_note field maps.  According to 
the AT migration mapping 
documentation,
 it should map to a collection management record, but I’m not seeing that field 
in collection management.  As part of the 1.4.2 to 1.5.X upgrade, some 
collection management fields were converted to event records.  You might check 
to see if any of your cataloged_note fields from AT now exist as event records 
in ArchivesSpace.  I’m seeing some in my database, so I suspect that is what 
happened.

-Noah


Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
http://library.duke.edu/rubenstein/


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Adam Jazairi
Sent: Tuesday, January 24, 2017 10:13 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Cataloged note field

Hello all,

My institution is in the process of migrating from Archivists' Toolkit to 
ArchivesSpace, and we've noticed that the cataloged note field doesn't seem to 
map. This seems to be intentional, based on the discussion in the following 
ticket: 
https://archivesspace.atlassian.net/browse/AR-827

This is problematic for us because some of our records have important data in 
this field that we don't want to lose. Has anyone else encountered this issue? 
If so, I'd appreciate any advice on how to resolve it.

For reference, we're running ArchivesSpace 1.5.2 and used the AT migration 
plugin
 to migrate our database.

Thanks,

Adam

--
Adam Jazairi
Digital Library Applications Developer
Boston College Libraries
(617) 552-1404
jaza...@bc.edu
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] interpreting import error messages - problem creating agent person

2017-01-24 Thread Julie Swierczek

I have a large batch of MARCXML files to import.  I keep getting error
messages such as "Error: #RetryTransaction: Problem creating
'agent_person': RetryTransaction".

Is there some way to figure out which agent is causing the problem?  The
MARCXML record has thirty-three 700 fields, not to mention other agent
fields, so using trial-and-error to find the problem is not a good use of
time.  I don't see any obvious problems, such as unusual characters in the
fields.

I have copied the agent fields and the complete error message below.

Julie

Agent fields:


Committee on Militarism in Education
(U.S.)


Committee on Militarism in Education
(U.S.)
Archives.

Sayre, John Nevin
1884-1977


Thomas, Norman
1884-1968


Wilson, E. Raymond
Edward Raymond
1896-1987


Sayre, John Nevin
1884-1977
fast
(OCoLC)fst00271556


Thomas, Norman
1884-1968
fast
(OCoLC)fst2998


Wilson, E. Raymond
Edward Raymond
1896-1987
fast
(OCoLC)fst00018322


Committee on Militarism in Education
(U.S.)
fast
(OCoLC)fst00659515.


United States.
Army.
Reserve Officers' Training
Corps.
fast
(OCoLC)fst00541024.

 
Barnes, Roswell P.
Roswell Parkhurst
1901-1949
correspondent


Allen, Devere
1891-1955
correspondent


Armstrong, Eunice B.
correspondent


Atkinson, Henry A.
correspondent


Baldwin, Roger N.
Roger Nash
1884-1981
correspondent


Boss, Charles F.
Charles Frederick
1888-
correspondent


Brinton, Ellen Starr
1886-1954
correspondent


Bromley, Dorothy Dunbar
1896-1986
correspondent


Catt, Carrie Chapman
1859-1947
correspondent


Coe, George Albert
1862-1951
correspondent


Detzer, Dorothy
1893-1981
correspondent


Forbes, Rose Dabney
1864-1947
correspondent


Johnson, Edwin C.
correspondent


Kirkpatrick, William
1757-1812
correspondent


Lane, Winthrop D.
Winthrop David
1887-1962
correspondent


Libby, Frederick J.
Frederick Joseph
1874-1970
correspondent


Moore, Alfred S.
correspondent


Morgan, Laura Puffer
1874-1962
correspondent


Newton, Ray
correspondent


Olmsted, Mildred Scott
1890-1990
correspondent


Page, Kirby
1890-1957
correspondent


Pharo, Florence M.
correspondent


Rankin, Jeannette
1880-1973
correspondent


Sayre, John Nevin
1884-1977
correspondent


Thomas, Norman
1884-1968
correspondent


Tinker, Wellington H.
correspondent


Van Kirk, Walter W.
Walter William
1891-1956
correspondent


Villard, Oswald Garrison
1872-1949
correspondent


Walser, Kenneth E.
correspondent


Wilson, E. Raymond
Edward Raymond
1896-1987
correspondent


Wilson, Theresa L.
correspondent


Wing, Andrew S.
correspondent


Wohlforth, Robert
correspondent


Error message:

==
tester_19046123.xml
==
1. STARTED: Reading JSON records
1. DONE: Reading JSON records
2. STARTED: Validating records and

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 
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 
> 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

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

Re: [Archivesspace_Users_Group] Cataloged note field

[Archivesspace_Users_Group] ARCHON sort titles not migrating

Re: [Archivesspace_Users_Group] Cataloged note field

Re: [Archivesspace_Users_Group] Cataloged note field

[Archivesspace_Users_Group] interpreting import error messages - problem creating agent person

Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

8 matches

Site Navigation

Mail list logo

Footer information