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 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
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.
@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
User Story
In order to transform ISO19115-2 documents into DCATUS using mdtranslator, datagov wants to add processing for
Language
Acceptance Criteria
Language
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
Language
should be transformed from ISO19115-2 to DCATUSBackground
Security Considerations (required)
None
Sketch
The text was updated successfully, but these errors were encountered: