Metacat

generalize the exception handling because our actions are the same no matter what the specific error is during create - we just notify the CN that the replicate call failed

catch general Exception that may be thrown during MN.replicate() when creating the object locally. There are a few records that keep slipping off our radar with no explanation as to why they remain in "REQUESTED" status.

do not download data at this point

catch errors for each localid we are processing so that they do do prevent other ids from having ORE content generated

additional debug logging for tracking down MN replication errors

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

band-aid for CN-CN replication permOrder issue when access control is embedded in EML and the system metadata is replicated before the EML. we just log the inconsistency and allow the insert to succeed
https://redmine.dataone.org/issues/2583

add comment about returning early when no system metadata can be found.
removed extraneous check on the content type of the SM -- was unused.
formatted indenting

for SystemMetadata events we first check the event for the SM value. If it returns null, we look it up from the shared map. It seems as if we don't always get a value with our events.

comment out: synchronize local system metadata on cn restart