MDTranslator ISO19115-2 to DCATUS: Language

[Jin-Sun-tts]

User Story

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

Acceptance Criteria

• GIVEN the DCATUS Language 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 Language 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:resourceConstraints//gmd:MD_Constraints//gmd:useLimitation
  • intObj[:metadata][:metadataInfo][:defaultMetadataLocale][:languageCode] + [:otherMetadataLocales][:languageCode]
  • language
• 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]

dcatus writer looking for[:metadata][:metadataInfo][:defaultMetadataLocale][:languageCode]and optional [:otherMetadataLocales][:languageCode]

ISO19115-2 doesn't include default and other metadata locales:

<gmi:MI_Metadata
  <gmd:locale>
    <gmd:PT_Locale>
      <gmd:languageCode>
        <gmd:LanguageCode 

need suggestions on how to mapping this situation.

[btylerburton]

would setting a default in dcat-us writer be the way to go, @rshewitt?

[rshewitt]

@btylerburton iso19115-3 has 2 kinds of locales: mdb:defaultLocale and mdb:otherLocale. iso19115-2 appears to only have 1 type of locale: gmd:locale. one path forward is to use the first locale as the default and the remaining ones as others. this would bypass editing the dcat-us language module and instead be handled within module_locale of the iso19115-2 reader. frankly, i don't feel confident enough to run with that decision so we should bounce it off of chris

[FuhuXia]

looking at XML we have on catalog, it is predominately

<gmi:MI_Metadata>
    <gmd:language>
    <gco:CharacterString>eng</gco:CharacterString>
    </gmd:language>