Verified in TEST1, that this is the case.
TEST1 uses a deploy configuration that does not override either harvester.harvesting.heritrix.archiveFormat or harvester.harvesting.metadata.metadataFormat
Verified in TEST1, that this is the case.
TEST1 uses a deploy configuration that does not override either harvester.harvesting.heritrix.archiveFormat or harvester.harvesting.metadata.metadataFormat