[Archivesspace_Users_Group] Import problem resolved

[De Catanzaro, Christine D]

Hi everyone,

Just wanted to follow up on the importing problem we were experiencing at Ga. Tech. Thanks to some great work by Chris Fitzpatrick, and Chris Helms here at Tech, we were able to locate the problem in the <descrules> element. Apparently an error is thrown due to the actual XML being injected into the code which is not handled properly. The bug has been reported: https://www.pivotaltracker.com/story/show/76051320.

I'm happy to report that everything imports just fine when I remove the <descrules> element prior to import.

Thanks so much,
Christine

----- Forwarded Message -----
From: "Christine D De Catanzaro" <christine.decatanzaro at library.gatech.edu>
To: "archivesspace users group" <archivesspace_users_group at lyralists.lyrasis.org>
Sent: Thursday, July 10, 2014 3:48:59 PM
Subject: Import and export problems

Hi everyone,

We archivists at Georgia Tech are in the midst of testing various functions of ArchivesSpace, and we have run across several issues.

One problem is that none of us can import EAD documents, either created in XMetal as an EAD DTD or created as a schema export from Archivists' Toolkit. (The migration of all of our records worked just fine; these are "one-off" attempts that we're making, with new or revised finding aids, mostly.) We consistently get this error message: "Error: wrong number of arguments (10 for 4)." This is one of those cryptic messages that others have written about previously. None of the finding aids we were trying to import were duplicates. Our XMetal documents import to AT just fine.

Chris F. recently noted: "A big problem is that schema valid EAD is sometimes not compliant to the AS model. There's a big range of variance that is allowed in the EAD schema, so we're still working on getting all the import mappings right." Is this at the root of the problem? Perhaps what's needed is a master schema describing what AS thinks is valid EAD? Or showing the problematic nodes would help immensely.

A second, maybe related, problem is that we also can't export EAD files from AS. This failed, mostly, although a couple of us had some success with exporting small EAD docs. These can't be re-imported into AS, however. All of the files we try to export give similar errors. Attached is a screenshot of one of our recent failures, in case that helps.

Thanks for any help you can offer,

Christine

-- 
Christine D. de Catanzaro, Ph.D., M.L.I.S.
Access Archivist
Subject Librarian - Music

Georgia Tech Archives
Library & Learning Excellence
Georgia Institute of Technology
266 4th Street, NW
Atlanta, GA 30332-0900

Phone: 404-385-0107
Fax: 404-894-9421

E-mail: decatanzaro at gatech.edu 

-- 
Christine D. de Catanzaro, Ph.D., M.L.I.S.
Access Archivist
Subject Librarian - Music

Georgia Tech Archives
Library & Learning Excellence
Georgia Institute of Technology
266 4th Street, NW
Atlanta, GA 30332-0900

Phone: 404-385-0107
Fax: 404-894-9421

E-mail: decatanzaro at gatech.edu 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: AS-Export.jpg
Type: image/jpeg
Size: 677154 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20140801/fb11065d/attachment.jpg>