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
The specific domains for several elements of Project Open Data Metadata Schema v1.1 differ from the typical domains for the corresponding metadata element in ISO or FGDC metadata. Geoportal Server could allow defining a mapping between the values found in the geospatial metadata to values to be used in Project Open Data Metadata Schema v1.1.
For example, FGDC CSDGM records with secclass values “Medium Confidentiality” and “No Confidentiality” are currently mapping to “non-public”.
A suggested approach is to include mapping in dcat-mappings.xml that use a regex to find values in the source metadata and map those to a target value to be included in the output json file.
The text was updated successfully, but these errors were encountered:
dcat-mappings.xml allows to define domain values mappings. For each string field it is possible to include <map from="" to=""/> collection of nodes. Each "from" is a regular expression matching input value (coming from the index) and "to" is output value printed to the DCAT json. Also, "to" might have value of "*" to indicate to pass original input value right to the output. Example:
The specific domains for several elements of Project Open Data Metadata Schema v1.1 differ from the typical domains for the corresponding metadata element in ISO or FGDC metadata. Geoportal Server could allow defining a mapping between the values found in the geospatial metadata to values to be used in Project Open Data Metadata Schema v1.1.
For example, FGDC CSDGM records with
secclass
values “Medium Confidentiality” and “No Confidentiality” are currently mapping to “non-public”.A suggested approach is to include mapping in
dcat-mappings.xml
that use a regex to find values in the source metadata and map those to a target value to be included in the output json file.The text was updated successfully, but these errors were encountered: