Funnelback logo



External metadata


External metadata is metadata which can be applied to pages in a web collection, without actually modifying the pages in any way. For example, it is possible to make all pages in a particular website match the query c:partner by adding a single line to the external metadata file. c:partner

Targets of the metadata are identified by their URL as supplied by the webserver when the page was originally crawled. Note: The external metadata mechanism was designed for use only with collections containing URL data (i.e. web collections).

Metadata information can be supplied for any of the allowable metadata classes (a-z, A-Z, 0-9), but care should be taken if reusing classes which have special behaviour (i.e. d is used for dates).

Activate External Metadata

To activate the external metadata for a collection, create the file external_metadata.cfg in the collection's conf subdirectory. The file can be created through the Funnelback administration interface using the file-manager.

When indexing commences external_metadata.cfg is checked for validity and data structures are set up to enable efficient lookup. If an error is detected, an appropriate error message will be printed, scanning of the file will cease and the documents will be indexed without external metadata. (See Step-Index.log using the "Browse Log Files" option in the administration interface.)

External metadata file format

The external metadata file must be a text file delimited into lines by linefeed (octal 012) characters. Each line consists of a URL-prefix followed by a list of metadata elements which apply to all URLs which start with that prefix (unless overridden by a more specific URL-prefix).

URL prefixes must include a full hostname. It is permissible to commence the prefix with "http://". If no protocol is specified then "http://" is assumed.

Each metadata element consists of a metadata field specifier (a single lowercase letter followed by a colon) followed by a word or a string of text in double quotes. Metadata elements are separated by whitespace. Punctuation should only be present within quoted strings. eg. s:"Publications Record" p:CSIRO. t: metadata will be used as the document title.

Here is an example of an external metadata file: w:ACT x:knowledge x:science x:chemistry x:"knowledge science physics" y:external y:funding x:knowledge x:science x:chemistry

These records have the effect that:

  1. Any page within the site, eg. or will be indexed with act_w,
  2. Any page within, eg. or will be indexed with knowledge_x, science_x and chemistry_x (as well as act_w).
  3. Any page within, eg. will inherit act_w from the first record, knowledge_x, science_x and chemistry_x from the fourth and external_y and funding_y from the third. It will NOT inherit physics_x from the third record because the x metadata from the third record has been over-ridden by the x metadata in the fourth.

Note: If multiple lines in the metadata file start with an identical prefix, only the first will be effective.

Default page handling

URL default pages (e.g. index.html) will be stripped from both the prefix given in the external metadata file and the URL being checked from the collection. When a URL prefix is stripped exact matching will be applied, hence would match any default page on, but would not match other pages or sub directories on Default pages are defined as any page called index, welcome, home, default or main followed by a dot and a three or four character extension (e.g. htm or html).

External Metadata Date Format

Two types of date metadata can be applied using the external metadata mechanism: document date ('d' field) and document expiry date ('X' field). Dates must be specified as 8 digit integers in the format YYYYMMDD. For example: d:20040101 X:20041231

specifies that documents in the nominated web directory were all published on 01 Jan 2004 and cease to be valid on 01 Jan 2005.

Profile-based external metadata

It is possible to create external_metadata.cfg files per profile, rather than in the collection conf directory, however these files won't be processed by the indexer. To have them processed they need to be concatenated and written into conf/external_metadata.cfg prior to indexing.

This operation can be automated using the validation tool described below.

Validation and concatenation tool provides a task to validate an external metadata file, as well as concatenating per-profile files into a single collection one. This task can process per-profile external metadata files, and concatenate only valid lines into the collection's conf/external_metadata.cfg file, discarding malformed lines.

The task name is ValidateExternalMetadata, it takes the following parameter:

ID of the collection containing the external metadata file to validate or concatenate
Either check to only check an existing file for errors, or concatenate to check and concatenate per-profile files
Percentage of errors (expressed as a floating number between 0 and 1) to tolerate before exiting with an error code. For example, using errorThreshold=0.7 will tolerate up to 70% of errors in external metadata files before aborting.

The common use case is to configure this task in the update workflow using a pre_index_command:

 pre_index_command=$SEARCH_HOME/linbin/ActivePerl/bin/perl $SEARCH_HOME/bin/ ValidateExternalMetadata collection=$COLLECTION_NAME mode=concatenate

If there are more errors than the configured threshold, the task will fail with a non-zero exit code, causing the update to fail before indexing.

A log of the validation is produced under the collection log folder: $SEARCH_HOME/data/<collection>/log/external_metadata.cfg-validation.log.

See also

top ⇑