MDTranslator ISO19115-2 to DCATUS: Spatial

[Jin-Sun-tts]

User Story

In order to transform ISO19115-2 documents into DCATUS using mdtranslator, datagov wants to add processing for Spatial

Acceptance Criteria

• GIVEN the DCATUS Spatial field
  AND how the DCATUS writer expects to find the data within the internal metadata object
  WHEN the associated ISO19115-2 reader ruby modules are created
  THEN Spatial should be transformed from ISO19115-2 to DCATUS

Background

• related to #4862
• We process 291017 ISO19115-2 datasets. We want all our datasets to be in DCATUS.
• This reader is not intended to be feature complete according to the ISO19115-2 standard. All we're looking to read is as much as the DCATUS writer expects.
• ISO19115-3 development workflow

Security Considerations (required)

None

Sketch

• field mapping relationship ISO19115-2 -> MDJSON -> DCATUS
  • .//gmd:MD_DataIdentification//gmd:extent//gmd:EX_Extent//gmd:geographicElement//gmd:EX_GeographicBoundingBox
  • intObj[:metadata][:metadataInfo][:extents][:geographicExtents][:boundingBox]
  • Spatial
• add processing in resourceInfo to read keywords from gmd:MD_DataIdentification
• create a transformation test demonstrating how the value went from the ISO19115-2 document into the DCATUS json
• create a response object message test verifying when required elements are missing