[Archivesspace_Users_Group] Import Error Message Suggestion

[Custer, Mark]

Hi Jaime,

Completely agreed, and I'd love to hear more about your process of migrating to ArchivesSpace.  I'm just starting on a similar project, but I don't think that we'll be ingesting too much EAD directly into ArchivesSpace at this point, so I'm still very unfamiliar with that process.

In the meantime, if you're importing EAD files into ArchivesSpace, do you also have an XML editor like oXygen?  If so, then you could validate these documents against a Schematron file that would tell you exactly where those errors occur.

I have honestly never written a Schematron file until just now (but I was very inspired at the EAD Hackathon!), but using the following example file (which I just hastily put together) with oXygen will show you exactly where those problems occur:

<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2">
    <ns uri="urn:isbn:1-931666-22-9" prefix="ead"/>
    <pattern>
        <rule context="ead:unitdate[contains(@normal, '/')]">
            <assert test="number(substring-after(@normal, '/')) gt number(substring-before(@normal, '/'))">Date normalization is invalid (end date occurs before begin date)</assert>
        </rule>
    </pattern>
</schema>

In this case, I'm assuming that you have schema-valid EAD files, but if you're using the DTD instead, you should be able to just delete that "ead:" piece of text or replace it with "*:".

I hope this might help.  Obviously you could turn this example into a much more robust Schematron file, and test for a lot of other things, too.
Mark


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Steven Majewski
Sent: Wednesday, February 05, 2014 4:48 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Import Error Message Suggestion



... or if not the line number, at least the enclosing element or some context to indicate where the missing item is missing from.

We're getting lots of errors ( on validated EAD) like:


Error: #<:ValidationException: {:errors=>{"dates"=>["one or more required (or enter a Title)"], "title"=>["must not be an empty string (or enter a Date)"]}}>

It seems to be saying it's expecting a date or title somewhere but it doesn't indicate where.


( If it's difficult to get this context info on import, an acceptable alternative would be to provide
a tighter version of the EAD schema that more closely corresponds to what the ArchivesSpace
importer accepts.  )

- Steve Majewski


On Feb 5, 2014, at 4:16 PM, Jaime Margalotti <jmargalo at udel.edu<mailto:jmargalo at udel.edu>> wrote:


The error message currently driving me crazy is "archival_object/dates/0/ end must not be before begin."  I understand what it means, but finding the single incorrectly typed normalized date in the container list of a long finding aid is nearly impossible.  If error messages could include which line in the finding aid caused them to fail to import, it would be an enormous help.
Many 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/20140205/bd770d07/attachment.html>