MDTranslator ISO19115-2 to DCATUS: theme

[Jin-Sun-tts]

User Story

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

Acceptance Criteria

• GIVEN the DCATUS theme 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 theme 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:descriptiveKeywords//gmd:MD_Keywords//gmd:thesaurusName
  • intObj[:metadata][:resourceInfo][:keywords][:thesaurus][:title]
  • theme
• 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

[Jin-Sun-tts]

in the iso19115-2.xml example:

 <gmd:thesaurusName>
        <gmd:CI_Citation>
          <gmd:title>
            <gco:CharacterString>ISO 19115 Topic Category</gco:CharacterString>
          </gmd:title>

In dcat_us_theme.rb, we see the condition:

if keyword_group[:thesaurus][:title] == "ISO Topic Categories"

Questions: Should the thesaurusName title always be expected to have the value ISO Topic Categories?