Invalid unmatched <additionalMetadata> produced at end of some EML documents

[gremau]

I find this: <additionalMetadata/>

At the end of some of the EML documents I create using MetaEgress, but not with all. This tag is not matched by any other additionalMetadata elements in the document and is invalid. The pattern I see is that it only happens when I make EML that has all otherEntities, and no dataTables. Can't explain why yet but will investigate.

[gastil]

My first guess would be to look at the Annotation. Perhaps some Annotation is put in for dataTable but not otherEntity. The kind of annotation that goes into the additionalMetadata. Just a wild guess.

…

On Tue, Aug 16, 2022 at 2:37 PM Greg Maurer ***@***.***> wrote: I find this: At the end of some of the EML documents I create using MetaEgress, but not with all. This tag is not matched by any other additionalMetadata elements in the document and is invalid. The pattern I see is that it only happens when I make EML that has all otherEntities, and no dataTables. Can't explain why yet but will investigate. — Reply to this email directly, view it on GitHub <#70>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGTM6FTVKCR6HUB5MPMJDPTVZQC2TANCNFSM56XKMOTA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[atn38]

Huh, I wonder if it's because MetaEgress always expects at least one dataTable and preemptively creates an additionalMetadata tag to deal with the units. That would be my guess.