extent requirements

[fordmadox]

Note, this type of encoding is NOT permitted by the EAD importer (even though it's good, EAD3-like encoding):

<physdesc label="Physical Description"><extent encodinganalog="300" type="cubic feet">10.2</extent></physdesc>

The schematron file will need to check for this, and it should also just go ahead and change the text node to 10.2 cubic feet in this case.

[noahgh221]

Mark, what exactly is not permitted? Does ASpace throw an error on import with this kind of encoding or just not map the type attribute value into the extent type field? Is there a requirement to have some text after the number in the text node?

[fordmadox]

When I tested with version 1.3, the importer threw an error here since it didn't find the extent value (which is tucked away neatly in the @type attribute) and this was the only physdesc element provided at the collection level. So yeah, the text node would need to change to 10.2 cubic feet in this case (unless the importer were to change).