An @@@@@@

Thanks @jeanetteclark. setting `names` to NULL for the list that gets assigned to `geographicCoverage` solves the problem. Didn't seem like anything to do with my own list or EML schema,...

@amoeba: I'm working on a [workflow/package](https://github.com/atn38/rMetabase2eml) to take a set of data.frames imported from PostgreSQL views (which will come from a metadata database schema designed for LTER sites), then use...

@jeanetteclark, thank you for the unbelievably quick feature add! Let me know if I got the behavior correct: (1) for a given attribute, the `missingValues` argument takes precedence if there...

I should get into the habit of MREs! Usually lots of moving pieces in workflow. And yes -- more documentation for `set_attributes` would be very helpful for new users --...

Just installed in a fresh project with packrat enabled -- so I'm pretty sure it's your fork -- any way to check definitively? Nothing seems to have changed when above...

Works beautifully now -- thank you!

@cboettig sorry for the late reply. Below is a minimal EML example with the additionalMetadata snippet inserted manually in text editor. This is valid according to [the online EML validator](https://knb.ecoinformatics.org/emlparser/)....

Thanks for the pointer @cboettig, good to understand how `EML` works under the hood more. Great timing on these issues coming up together!

Gotcha, I can see it both ways now. I can always remove the extra ID type columns before feeding it to `set_attributes`, since creating EML is often the last step...

That's the puzzling thing I forgot to include. eml_validate() gives error on a seemingly correct ordered EML list ```[1] "Element 'abstract': This element is not expected. Expected is one of...