Event Search

Introduction

Funnelback includes a number of features to present search results which represent 'events' in an appropriate way. Events, for example, may need to be displayed multiple times within a result page if it spans multiple days, and users may wish to restrict their search to some particular set of days.

Caveats

Combining Faceted Navigation and the Event Search query processing mode is not supported. Faceted navigation performs counts of unique documents URLs, whereas Event Search processing counts date occurrences of those events.

Representing events

Events are represented to Funnelback by documents with some specific metadata which indicate the dates on which the event occurs. For example, the following HTML document represents a user conference event which occurs over three days (the 20th to the 22rd of October, 2010).

    <title>Funnelback User Conference</title>
    <meta name="occurrences" content="20101020 | 20101021 | 20101022">
    Event: Funnelback User Conference

Any HTML <meta> field or XML element may be used for the list of event occurrences, however, the dates must always be specified in the YYYYMMDD format shown above, and be separated by | (pipe) symbols.

After populating the document metadata, this metadata field (or XML field) must be mapped to a metadata class using the standard xml.cfg or metamap.cfg mechanisms. Any free metadata class may be mapped for this purpose and then referenced from within the event query (see below).

Configuring query processing

A query processor option is required for effective events search.

-events=on

This option, when added to the query processor options of a collection, switch query processing into event mode, which adjusts the way results are displayed.

Searching for events

In addition to selecting events which match some textual query, search result pages may be restricted to displaying only events which occur on some specific days, or within a specific date range. the following query, for example, would display only events containing the term 'conference' on the 21st or 22nd of October (assuming the occurrence dates have been mapped to the 'O' metadata class).

conference % O=20101021 O=20101022

Each desired date must be specified in the query, and note that the dates must be specified in order.

As an alternative, a date range may be specified with the following syntax:

conference % O>20101021<20101022

top