<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div><div>I can now batch import a large majority of our 4074 EAD files into ArchivesSpace. </div><div>( I’ve only samples and tested a portion of other Virginia Heritage institutions 6000+ files. ) </div><div><br></div><div>All but 21 files parse and produce json files with my batch import parser. </div><div>Not all of those json files import with POST /repositories/$ID/batch_imports: several hundred fail,</div><div>usually with Java memory errors returned. In the one instance I’ve tried, I was able to import </div><div>the file successfully using the frontend web import job upload form. </div><div><br></div><div>The remaining error messages are:</div><div><br></div><div><br></div><div><font face="Courier"> 1 #<:ValidationException: {:errors=>{"instances/0/container/type_1"=>["Property is required but was missing"]}}><br> 1 #<:ValidationException: {:errors=>{"record"=>["Can't unambiguously match {:reference_text=>\"(In non correspondence -legal)\"} against schema types: [\"JSONModel(:note_index_item) object\"]. Resolve this by adding a 'jsonmodel_type' property to {:reference_text=>\"(In non correspondence -legal)\"}"]}}><br> 1 Invalid schema given: string<br> 2 #<:ValidationException: {:errors=>{"notes/7/subnotes/0/content"=>["Must be 65000 characters or fewer"]}}><br> 16 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"]}}><br></font><br></div><div><br></div><div>I will continue to investigate these errors, but in the mean time, it seemed we could import a sufficient number to go on to </div><div>evaluating the rest of the system. </div><div><br></div><div>Here is the stylesheet I’m using to fix some of these import problems. In some cases, the “fix” is just papering over a problem</div><div>to get the guide imported. For example, we’re inserting “1 arbitrary_unit” for missing <extent> elements; or arbitrarily truncating</div><div>the <eadid> at 255 characters. The desired plan would be to get all of the collections imported into ArchivesSpace and review</div><div>and correct them there (rather than editing EAD xml files). But we need a good way of tagging the elements that need review</div><div>and correction. I don’t know if the xml comments I’ve inserted will prove to be a useful solution to that. </div><div><br></div><div>Here, I believe Archivist’s Toolkit solution was to import files even when it didn’t meet it’s requirements, but then you could not</div><div>publish or expand the hierarchy of the guide until you had gone thru and corrected the issues, which were hilighted in the edit</div><div>form. This would be the ideal, but I would at least like to figure out how to tag elements as needing review. </div><div><br></div><div><br></div><div>( BTW: What is the difference between not-published & suppressed ? ) </div><div><br></div><div><br></div><div></div></body></html>