Locked History Actions

deegree3/WorkspaceConfiguration/ServicesConfiguration/DataMetadataCoupling

Data / Metadata Coupling

This page describes the coupling between data and metadata using deegree webservices. Currently there is the possibility to couple data served by deegree featureServices (through FeatureTypes) and deegree mapServices (through layers) with corresponding metadata. This results in the generation of MetadataURL elements within the Capabilities documents.

The configuration of the data / metadata coupling happens within the specific webservices configuration files.

A global MetadataURLTemplate element provides a template for generating URLs of ISO metadata records. In the example below, this is a KVP-encoded GetRecordById request template to a CSW instance. Every layer (for WFS: feature type) in the configuration can carry a MetadataSetId element to define the actual metadata record identifier (usually a UUID). This allows deegree mapServices to generate the MetadataURL element in the GetCapabilities response.

1. Detailed Configuration

1.1. Example for data / metadata coupling within a deegree mapService configuration

<deegreeWMS [...]>
  <MetadataURLTemplate>http://discovery.eu/csw?service=CSW\
    &amp;request=GetRecordById&amp;version=2.0.2&amp;id=${metadataSetId}\
    &amp;outputSchema=http://www.isotc211.org/2005/gmd\
    &amp;elementSetName=full
  </MetadataURLTemplate>
  [...]
  <RequestableLayer>
    <Name>AU.AdministrativeUnit</Name>
    <Title>Administrative unit</Title>
    <Abstract>...</Abstract>
    [...]
    <MetadataSetId>550e8400-e29c-11d4-a716-446655440000
    </MetadataSetId>
    [...]
  </RequestableLayer>
  [...]
</deegreeWMS>

CategoryDeegree3 CategoryWorkspaceConfiguration