Help Center

Menu

metamap.cfg

This feature is deprecated and will be removed in a future version. Please update any existing implementations to use supported features.

metamap.cfg was previously used to define the metadata class mappings for a data source.

The metamap.cfg file is no longer in use and metadata should now be configured using the metadata configuration interface instead.

Syntax

The metamap.cfg consists of a mapping, one per line

metamap.cfg
class,content,tag name

where:

class

is the Funnelback metadata class.

content

uses one of the content flags (below)

tag name

is the name or property value of the <meta> tag, or an HTML tag (in angle brackets). Lines beginning with a hash (#) are treated as comments and ignored.

Content flags

The content flag can be set to the following values:

0

do not index this metadata as part of the document’s content. Only searchable through explicit use of the metadata field operator.

1

index this metadata as part of the document’s content. A general search will also match occurrences of the keyword within this metadata field.

2

sets the field as geospatial search data. This feature is available from Funnelback version 7.

all collections that are part of a meta collection must share common type 2 metadata fields. For example if x is defined as type 2 metadata in one collection all other collections that are part of the meta collection must also have the x field defined as type 2.
3

sets the field as a numerical metadata field.

all collections that are part of a meta collection must share common type 3 metadata fields. For example if N is defined as type 3 metadata in one collection all other collections that are part of the meta collection must also have the N field defined as type 3.
4

sets the field as a lock string for early binding document level security.

Example

If a web page contained the following <meta> tags:

<meta name="Title" content="My dummy website">
<meta name="Description" content="An example for metamap.cfg">
<meta name="Keywords" content="shakespeare casear romeo juliet">
<meta name="Date" content="25/07/2006">
<meta property="og:image" content="http://example.com/example.gif">

The following metamap.cfg would map each of those meta tags to classes

metamap.cfg
t,1,title
c,1,description
d,0,date
image,0,og:image
keyword,1,keywords

If a web page contained the following HTML in the body:

<h2>This is some heading text</h2>

The following metamap.cfg configuration could be used to put "This is some heading text" into meta class 'header2'.

metamap.cfg
header2,1,<h2>

See also