Access to Memory (AtoM)

Import a description with multiple <extent>, <genreform>, <dimensions>, or <physfacet> nested inside. Example:

 <physdesc>
     <extent encodinganalog="1.5B1">63,48 m de documents textuels</extent>
     <extent encodinganalog="1.5B1">7195 photographie(s)</extent>
     <extent encodinganalog="1.5B1">15 dessin(s)</extent>
     <extent encodinganalog="1.5B1">2 gravure(s)</extent>
     <extent encodinganalog="1.5B1">1 plan(s)</extent>
     <extent encodinganalog="1.5B1">1 dessin(s) d&apos;architecture</extent>
     <extent encodinganalog="1.5B1">327 vidéo(s)</extent>
     <extent encodinganalog="1.5B1">150 bande(s) magnétique(s)</extent>
     <extent encodinganalog="1.5B1">12 objet(s)</extent>
 </physdesc>

• The first nested element is added to its corresponding definition list (e.g. extent - in the example above, "63,48 m de documents textuels" is added to the extent label)
• All subsequent fields are imported, but they do not appear as extent

See attached screenshot.

Expected result
Extent label appears ONCE, with all related elements (e.g. other extent information) appearing beneath the same extent label. We should not need to repeat the extent label for every <extent> element.

Note that this should be true for all nested elements - <genreform>, <dimensions>, <extent> and <physfacet> are the primary candidates we are making sure import. Data in other allowed nested elements (e.g. <name> and other name tags, <occupation>, <function>, <subject>, etc.) SHOULD import, but it is not necessary to keep the EAD tags.