You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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 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
User Story
In order to transform ISO19115-2 documents into DCATUS using mdtranslator, datagov wants to add processing for
license
Acceptance Criteria
license
fieldAND 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 DCATUSBackground
Security Considerations (required)
None
Sketch
The text was updated successfully, but these errors were encountered: