MDTranslator ISO19115-2 to DCATUS: License

[Jin-Sun-tts]

User Story

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

Acceptance Criteria

• [ ] GIVEN the DCATUS license 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 license 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

[rshewitt]

iso19115-3 has 3 constraints: common, legal, and security. if these are present in -2 then you should probably create all 3. reference in the constraint is a citation in -3. dcatus only pulls the title from that reference/citation so there shouldn't need to be an update to the citation module because title is already processed

[Jin-Sun-tts]

In the current DCAT-US writer, the license is derived from resourceInfo -> constraints -> reference -> title.

ISO19115-3 
<mri:resourceConstraints>
    <mco:MD_Constraints>
           <mco:reference>
               <cit:CI_Citation>
                  <cit:title>

However, in ISO19115-2, MD_Constraintsunder resourceConstraints does not include a reference element.

 <gmi:MI_Metadata
   <gmd:identificationInfo>
     <gmd:MD_DataIdentification>
       <gmd:resourceConstraints> 
          <gmd:MD_Constraints>
             <gmd:useLimitation>

need guidance on how to locate the corresponding license information in ISO19115-2.