MDTranslator ISO19115-2 to DCATUS: rights

[rshewitt]

User Story

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

Acceptance Criteria

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

the dcatus rights writer relies on use-constraint data stored in :releasability which is only found in ISO19115-3. use-constraints exists in ISO19115-2 but only have useLimitation as child elements.

here's the data access in the rights writer

  statement = constraint.dig(:releasability, :statement)
  disseminationConstraints = constraint.dig(:releasability, :disseminationConstraint)

ISO19115-2 use-constraints don't have a releasability element to populate so the build method needs to be refactored. in the short term, the approach can just be compatible with ISO19115-2 but in the long term it should be able to process all 3 spatial metadata types (related ticket)