-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pitfalls for metadata providers regarding expected mapping of distributions , digitaltransfers from ISO19115/19139 metadata to GeoDCAT-AP #123
Comments
@uvoges The situation you describe is the result of the GeoDCAT-AP ISO to DCAT-AP mapping - since the links are not mapped to DCAT-AP Distributions, they are not displayed as distributions in data.europa.eu. |
in this issues I would like to collect pitfalls for metadata providers regarding distributions , digitaltransfers when mapping ISO19115/ISO19139 tdigitaltransferoptions (as provided in INSPIRE) to GeoDCAT-AP which is e.g. upon harvesting.....
The links defined in the ISO19115 md:distributionInfo/gmd:MD_Distribution/gmd:transferOptions are mapped to different GeoDCAT-AP distribution resources with different fields in the DCAT-AP representation of the metadata depending on the codeListValue defined in the gmd:function element. Only gmd:transferOptions with the codeListValues 'download', 'offlineAccess' or 'order' are mapped to dcat distributions. gmd:transferOptions with the codeListValues 'information' or 'search' are mapped as foaf:page if no gmd:function element is defined the links are mapped as dcat:landingPage. These links still exist in the metadata but are not displayed as distributions e.g. in the data.europa.eu portal.
The following ISO metadata will be mapped to a distribution:
The text was updated successfully, but these errors were encountered: