Metacat

only attempt to generate OREs for objects that we know not to have them already. https://projects.ecoinformatics.org/ecoinfo/issues/6061

check for null archived flag in ORE SM
https://redmine.dataone.org/issues/3046

utility methods to update/reserialize existing ORE maps that were generated with older foresite (and included bad dateTime strings).
https://redmine.dataone.org/issues/3046

include dataone.ore.downloaddata as a configurable property in case MNs (like LTER) want to have the process download externally-stored data files described in an EML data package.

instead of generating SM and ORE maps during dataone configuration/MN registration, moved this all to the replication admin screen where we can target generation for specific nodes. That way it's more controlled as to when and where we generate DataONE required content....

include all EML versions (had been only eml 2.1 for testing)

expose serverLocation parameter to run GenerateSystemMetadata for different replication parters as needed.
https://redmine.dataone.org/issues/2740

only generate system metadata for original objects.
https://redmine.dataone.org/issues/2721

do not download data at this point

only 2.1.0 EML docs for ORE generation right now...