To enable any Swish searching, modify your interchange.cfg to add:

Require module Vend::Swish
AddDirective Swish hash
Variable swish Vend::Swish

To configure your catalog to use Swish, modify the appropriate catalog.cfg and add:

Swish command /usr/bin/swish-e
Swish index products/swish-e.db

Simple search for the term Swish:

swish-e -w Swish

Same search with specifying the index file:

swish-e -w Swish -f db/xmldocs

You can include properties in the output:

swish-e -w Swish -f db/xmldocs -p purpose

Or search within a property:

swish-e -w purpose=LWP -f db/xmldocs

Indexing web sites is pretty easy. Swish provides a spider script, which is simply called with the parameters default starting_URL. Create a configuration file similar to the following:

IndexFile db/icdevgroup
IndexDir /usr/local/lib/swish-e/spider.pl
SwishProgParameters default http://www.icdevgroup.org/docs/

Now you can start indexing with swish-e -S prog -c icdevgroup.conf.

escape non-alphanumeric characters in search specification.

base directory in which to look up text files to search (related option fi).

Directory paths can be absolute, provided that the pathname is equal to the MV_SEARCH_FILE variable, or a scratch variable of the same name is 1. To enable searching in say, /etc/dict, use either [calcn]$Variable->{MV_SEARCH_FILE} = '/etc/dict'; return[/calcn] or [tmp /etc/dict]1[/tmp].

the search string matches only at the beginning of a column.

not intended for common use. When more tag is used, this option automatically provides a pointer to the search reference.

case sensitive search.

operation to perform to check field for a match.

For tq and aq matching using Text::Query module, see Q: .

the so-called "coordinated" search allows for multiple search options to be stacked on top of each other.

If the number of search fields (sf options) equals the number of search specs (se options), the search will return items that match all or one of the field-specification blocks (controlled with mv_orsearch). When the two numbers do not match, coordinated mode will be automatically and silently turned off. To force a coordinated search, see mv_force_coordinate.

When coordinated searching is used, case sensitivity, substring matching, negation and other options can be specified multiple times and work on a field-by field basis, according to the following rules:

Make dictionary matching case-insensitive. Ignored unless mv_dict_look is set.

Make dictionary matching follow dictionary order, where only word characters and whitespace matter. Ignored unless mv_dict_look is set.

delimiter for counting records in search index files. The default, a newline, works well for most line-based index files.

require that search field matches the search specification exactly (as opposed to the default word-based matching, or substring matching with su). Search specification will behave as it was enclosed in quotes.

force coordinated search (enabled with mv_coordinate).

Normally, coordinated mode is automatically turned off when the number of search specifications does not match the number of search fields. With this option, however, instead of disabling coordinated mode, Interchange ensures the number of search specifications does match the number of fields by filling the missing specifications with the last one specified, or by discarding extras.

This option is useful when you want to search for one string in multiple fields with different options.

specify filename containing a single line with the list of database fields, separated by TABs. This is used when you are searching databases without the "field header" on the first line, but you would still want to refer to fields by their names.

tables and/or text files to be searched.

return search results from the specified result number onwards. When this option is set, Interchange will return search results starting from the match number specified even if there is only one page of results. If set to a value greater than the total number of matches, it will act as if no matches were found.

number of lines to skip at the beginning of a search index or text file. Interchange normally skips one line for text-based searches (st=text) to exclude the header line.

delimiter for counting fields in search index files. The default, a TAB character, works well for most line-based index files.

perform search similar to SQL "LIKE" functionality. When defined, mv_like_spec is required as well.

string to search for in mv_like_field. The behaviour of the % character and case-sensitivity depends upon your SQL implementation.

maximum number of records (search results) to return from a search. When all the results are displayed on a single page, this option is equivalent to mm. When the more tag is used to display results multi-page, then this option determines the number of results per page. To specify unlimited, use none or all, not 0.

final, maximum number of records (search results) to return from a search (related option ml).

minimum size of a search string for a search operation.

search operator will perform numeric (instead of string) comparison.

return all records

(specification of :* indicates "all fields").

the one and only match from the search will be the value of the mv_searchspec itself. Useful in testing, or yes/no confirmation whether the search string was found

for text-based searches (st=text only), this option specifies the SQL query to run over the lines in the file. This is not the same as an external SQL database search.

Furthermore, the SQL_Query undergoes a little modification before it is used. Here's a practical example:

Artist: <input name="artist" />
Title:  <input name="title"  />
<input type="hidden" name="mv_sql_query" value="
  SELECT  code FROM products
  WHERE artist LIKE artist
  AND    title LIKE title
" />

If the right-hand side of every part of expression is an alphanumeric, unquoted word, then it is replaced with the appropriate form variable value. (Or if it's a one-click search, scratch variables are used instead). Quoted right-hand side values are taken literally.

If the left-hand side of every part of expression is a quoted word, the behavior is reversed. That part is replaced with the appropriate form variable value. (Or if it's a one-click search, scratch variables are used instead). Unquoted left-hand side values are taken literally.

Here's an example that allows users to select whether they want to search in title or artist fields:

Search for: <input name="searchstring" /><br />
Search in   <input type="radio" name="column" value="title"  /> title
            <input type="radio" name="column" value="artist" /> artist

<input type=hidden name="mv_sql_query" value="
  SELECT code    FROM products
  WHERE 'column' LIKE searchstring
" />

Just for a reference, here's what the two above examples would look like when coded "manually":

[page search="
  co=yes
  sf=artist
  op=rm
  se=[value artist]
  sf=title
  op=rm
  se=[value title]
"]
Search for [value artist], [value title]
</a>


[page search="
  co=yes
  sf=[value column]
  op=rm
  se=[value searchstring]
"]
Search for [value searchstring] in [value column]
</a>

select search type. glimpse uses the Glimpse search engine (see Glimpse), db (or the equivalent sql) iterate over every row in the SQL database, text searches corresponding database text source files, and ref iterates over the results from some previous, already-performed search (related option lb).

match on substrings as well as whole words. This is typically set in dictionary-based searches.

determine sort order of the returned data. It is possible to refer to columns by both using their names (if the search is such that column names are known) and their indices, starting from 0.

removes duplicate records from the result set. Duplicates are determined by comparing the value of the first search return field (set with rf).

assign value to a value variable. This is exactly what happens with normal variables in search profiles when you use the variable_name=value syntax, so you should use this option only where variables cannot be set directly (i.e. in one-click searches):

[page
  href=scan
  arg="se=Renaissance
       se=Impressionists
       va=category_name=Renaissance and Impressionist Paintings
       os=yes"
]Renaissance and Impressionist Paintings<a>