Metacat

force replication for newly-registered system metadata

Merged in the D1_0_6_2_BRANCH changes that include the transition from ObjectFormat calls to ObjectFormatCache calls.

include System Metadata forced replication - just need to figure out when to call it!

handle timed replication of system metadata. there are still a few outstanding issues:
-track server location of system metadata-only entries
-replication policy flag for system metadata-only entries?
-locking for replicated entries?
-forced replication of entries

transfer full System Metadata (as XML) during document and data replication

-remove system metadata guid -> local id mapping (there is no document for system metadata now)
-include system metadata elements when replicating data objects (TODO: transfer all system metadata structures with the docinfo request).
TODO: remove docid+rev from the systemMetadata table definition

do not use XML files for storing SystemMetadata - use DB tables only.

use update method to update the mapping between local and guid (d1) when we get a force replication request that is an "update

use "object_format" element consistently so that it is replicated across instances
https://redmine.dataone.org/issues/1514

insert/update documents with null user and null group to circumvent access control restrictions then update the user_owner and user_updated values to reflect what exists on the originating server (pisco)