You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found another class of errors that is not caught by schematron rules.
A number of our EAD guides were created from templates, and so we often have empty elements that have not been filled in. I did try to remove empty elements in my preprocessing, but some that are not completely empty are still empty of content.
And example of the sort of import errors generated:
The following errors were found:
notes/3/content : At least 1 item(s) is required
notes/7/subnotes/0/content : Property is required but was missing
Ditto for other elements, like an empty container element (so, not just notes, it doesn't look like). We should raise a warning for a defined set of elements (head, p, container, etc.) that don't pass the [not(normalize-space()] test.
I found another class of errors that is not caught by schematron rules.
A number of our EAD guides were created from templates, and so we often have empty elements that have not been filled in. I did try to remove empty elements in my preprocessing, but some that are not completely empty are still empty of content.
And example of the sort of import errors generated:
And these are caused by EAD like this:
I need to find all of the elements that map to JSONModel notes and figure out a test that catches these errors.
The text was updated successfully, but these errors were encountered: