Metacat

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)

Append more information such as user name and group to the validating session response.

remove exception from method decl - was not matching the interface def and not compiling.

add "Generate System Metadata" button to the replication server list display. When clicked, we generate SM for records belonging to that source server. This is only enabled when DataONE has been configured.
https://redmine.dataone.org/issues/2762

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

handle authorization for delete() differently for CN vs MN.
On the CN, only the CN (or tbd admin user) can call it.
On the MN, both the CN (or admin user) and the same MN can call it.

add Session-less archive() method

only admin users can call MN/CN.delete(). This is limited to any CN and only the MN that is calling itself