You must supply a level attribute at the resource level You must supply a title at the resource level You must supply a date at the resource level (including as child of unittitle) You must supply an identifier at the resource level You must supply an extent statement at the resource level. This should be formatted with an extent number and an extent type, like so: "3.25 cubic meters" The extent statement must contain more than just an extent number. If you're making use of the @unit attribute, you would probably be safe in copying that value to the end of the extent's text node (e.g. @unit="Linear Feet", 5... could be changed to @unit="Linear Feet", 5 Linear Feet) The extent statement must start with a number and it must also have at least one space present. (e.g. "5 Linear Feet" is a valid value, but "5items" is not). ArchivesSpace has no concept of an unpublished identifier, yet this component has an internal-only identifier. Please verify that the input file is correct. Woah. Looks like an internal-only AT or Aeon database ID is going to be imported as a published component unique identifier. Those should be removed. The date normalization value for this field needs to be updated. The first date, , is encoded as occurring before the end date, If the value of a level attribute is "otherlevel', then you must specify the value of the otherlevel attribute You must specify a level attribute at every level of description You must specify either a title or a date when describing archival components (this is a requirement enforced by the AchivesSpace data model, not by EAD) The extent statement should contain more than just an extent number since ArchivesSpace will not import any extent attribute values. If you're making use of the @unit attribute, you would probably be safe in copying that value to the end of the extent's text node (e.g. @unit="Linear Feet", 5... could be changed to @unit="Linear Feet", 5 Linear Feet) The ArchivesSpace EAD importer will silently drop note elements. Please convert these to "odd" elements. In order to ensure that your container elements import properly, you should assign id attributes for each container grouping per archival component A container type value ("Box", "Folder", etc.) is required for a container element to be imported. The ArchivesSpace importer won't skip over empty elements, so if you use this value, you must provide a date (either as text or an attribute value)