The error you're seeing is actually an informational warning; ie. ICA-AtoM is letting you know that it cannot validate the imported EAD file, but it should still successfully import the data it contains. In this case, the EAD generated by Steady uses XML schema (XSD) instead of DTD, which isn't handled by the current version of ICA-AtoM.
Can you verify whether the content of the EAD file was actually imported? When the import is complete, there should be a button linking to the newly-created description, which will be in draft status. If your data is not being imported, then we have a different issue to track down.
By the way, thanks for pointing us at Steady -- we are working on CSV import at the moment for several migrations and as a new feature in the upcoming 1.2 release, so the approach Steady uses will be very useful for us to ensure better interoperability.
Hope this helps,
MJ
> --
> You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
> To post to this group, send email to ica-ato...@googlegroups.com.
> To unsubscribe from this group, send email to ica-atom-user...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/ica-atom-users?hl=en.
>
Google Code is read-only this morning, but I will file an issue for this to correct validation for both DTD and XSD-based import in the next release.
In the meantime, the easiest way to get EAD generated by Steady to import into ICA-AtoM is to:
1) On the second line of the XML file (after the <?xml ... declaration), add:
<!DOCTYPE ead PUBLIC "-//Society of American Archivists//DTD ead.dtd (Encoded Archival Description (EAD) Version 1.0)//EN" "http://www.loc.gov/ead/ead.xsd">
2) Remove the attributes in the <ead> element on the following line, ie. replace:
<ead xmlns:ns2="http://www.w3.org/1999/xlink" xmlns="urn:isbn:1-931666-22-9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:isbn:1-931666-22-9 http://www.loc.gov/ead/ead.xsd">
Simply with: <ead>
MJ
Yes, the first three lines of your XML file should look like this:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!DOCTYPE ead PUBLIC "-//Society of American Archivists//DTD ead.dtd (Encoded Archival Description (EAD) Version 1.0)//EN" "http://www.loc.gov/ead/ead.xsd">
<ead>
... with the rest of the content following. I've attached a copy of the sample EAD file for reference, hopefully Google Groups will handle it gracefully.
MJ
Hm, a 500 internal error is a bit more difficult to diagnose. The easiest way is to replace index.php in the URL with qubit_dev.php , eg. import using this URL:
http://localhost/icaatom-1.1/qubit_dev.php/;object/importSelect
Alternatively, if you're familiar with the Apache log on your system, it should provide some more detailed information around what's causing an error 500.
Are you getting these errors with the file I provided as well as the one from Steady?
I use my desktop email client (Mail.app on Mac OSX) to read this mailing list, so I just attach files like "regular" email. I'm not sure if something similar is possible through the Google Groups web interface.
MJ
Fatal error: Class 'XSLTProcessor' not found in C:\wamp\www
\icaatom-1.1\lib\QubitXmlImport.class.php on line 179