Metacat

stack trace the HZ put exception during CN-CN replication

additional debugging statements for CONCURRENT_MAP_PUT error during CN-CN replication.

include eml2.0.0beta4 DTD during Metacat build so that we can continue to accept (and validate) beta4 documents.
This arose when testing Metacat as DataONE Coordinating Node where legacy documents are being housed in the CN.

encode '/' and ':' in the DOI used for the resolve URL

Don't set the replication status to failed for an object when it is called by a public user. Just throw the NotAuthorized exception. This prevents this node from being de-prioritized because of public calls to the method.

include revisions table in the initial temp table population.
use the "first" creator listed in the EML (either org or person).
use other reasonable default values as needed to fully populate the spreadsheet columns
https://redmine.dataone.org/issues/2815

add columns: publisher and pub_date. include default values for all columns - even data files should have title.
still a few todos but closer.
https://redmine.dataone.org/issues/2815

script to generate DOI registration spreadsheet
https://redmine.dataone.org/issues/2815

share the same dbConnection when inserting and then updating SystemMetadata objects in the backing store.
any errors encountered during the update will rollback the entire transaction and the SM record will not exist, even in part.

Do not loadAllKeys() for SystemMetadataMap when Metacat first starts up. hzIdentifiers will be populated with a simple SQL statement rather than the serial loading of every single SystemMetadata object. It will remain in synch using the usual entryXXX() methods as before....