[Archivesspace_Users_Group] EAD import error: Unexpected Object Type in Queue

[Chris Fitzpatrick]

Hi Jaime,

Yes, that is a rather cryptic error. What I've found is that is usually the case when the importer runs into something that didn't get properly closed, if that makes sense...for example, the importer thinks that it should be back to working on the parent archival_object but the queue just returned a child note_singlepart that wasn't (for whatever reason) properly processed, saved, and moved out of the queue.

You are exactly right about what goes into the note_singlepart.
Would it be possible for you to email me a zipped copy of your EAD so I can test it out?

We are working on improving the error messaging, so hopefully things like this will be more apparent...

thanks! best,chris.





Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org
Developer, ArchivesSpace
http://archivesspace.org/






________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jaime Margalotti <jmargalo at udel.edu>
Sent: Thursday, January 30, 2014 5:06 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] EAD import error: Unexpected Object Type in Queue

I imported all of our EAD finding aids into ArchivesSpace and had numerous errors.  Some I've managed to troubleshoot on my own and some others are still baffling me.

For one failed upload I received the error: "Unexpected Object Type in Queue: expected archival_object got note_singlepart"

According to the Controlled Vale List for note_singlepart_type, this unexpected tag was abstract, langmaterial, materialspec, physdesc, physfacet, or physloc.

We can toss out materialspec, physfacet, and physloc because they do not appear in the finding aid.  The abstract, langmaterial, and physdesc for the collection level were exactly where they were in all of the successfully uploaded finding aids.  The only thing I can assume is that there is some issue with the component physdesc.

Example:
<c02 level="item"><did> <container type="box">1</container>
<container type="folder">F10</container>
<unittitle>Europe, Steichen, Newport<unitdate normal="1897/1945" type="inclusive">undated</unitdate></unittitle> <physdesc>6 leaves</physdesc><dao actuate="onrequest" show="new" linktype="simple" title="PDF of item" href="http://dspace.udel.edu:8080/dspace/bitstream/handle/19716/11737/MSS0149_F10.pdf"><daodesc><p>PDF</p></daodesc></dao></did></c02>

As far as I can tell, there's nothing wrong here either.

Any ideas?

Is there anyplace in the documentation that delves a little more specifically into the meaning of the specific error messages?

Thanks,
Jaime


--

Jaime L. Margalotti
Senior Assistant Librarian
Manuscripts and Archives Department University of Delaware Library
Newark, DE  19717-5267
302-831-0554
jmargalo at udel.edu<mailto:jmargalo at udel.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20140131/128d8337/attachment.html>