indexing.additional-metamap-source.[key_name]

Background

This setting controls where additional metadata mappings for a collection are defined. Mappings in the listed files will be combined with the data sources’s own metadata mappings to produce the final list of mappings to be used.

The format allows for setting several sources to be defined, each with a key name (allowing data sources to override the defaults).

indexing.additional-metamap-source.(key_name)=(file_path)

The format of the given file is expected to be either identical to the format described for metamap.cfg or to be identical to the format returned within the data section of JSON in the response of the API:

GET https://FUNNELBACK_ADMIN_SERVER:PORT>/admin-api/metadata-mapping/v1/collections/DATA_SOURCE_ID

When metadata mappings are combined external metadata mappings may add to but not override any metadata mapping or source already defined for a collection. For example:

  • if the data source already defines metadata class price as NUMERIC then an external additional metadata file will not be able to override its type.

  • if the data source already defines a source e.g. /root/price for XML, the external additional metadata file will not be able to change which class that source is mapped to.

Setting the key

Set this configuration key in the search package or data source configuration.

Use the configuration key editor to add or edit the indexing.additional-metamap-source.[key_name] key, and set the value. This can be set to any valid String value.

Default value

indexing.additional-metamap-source.content-auditor=$SEARCH_HOME/conf/metamap.cfg.content-auditor

This default setting provides a set of custom metadata mappings to reserved classes for the use of content auditor.

Examples

The following adds metadata mapping from a search package to the component data source in question.

indexing.additional-metamap-source.customer-shared=$SEARCH_HOME/conf/SEARCH_PACKAGE_ID/metadata-mappings.cfg

See also