mnoGoSearch 3.2.33 reference manual: Full-featured search engine software
Prev |  | Next

# Chapter 8. Searching documents

# Using search front-ends

## Performing search

Open your preferred front-end in you web browser:

    http://your.web.server/path/to/search.cgi
    or
    http://your.web.server/path/to/search.php3
    or
    http://your.web.server/path/to/search.pl

To find something just type words you want to find and press the SUBMIT button. For example, "`mysql odbc`". You should not use any quotes " in your query, they are written here only to separate a query from other text. mnoGoSearch will find all documents that contain the word "mysql" and/or the word "odbc". Best documents having bigger weights will be displayed first.

## Search parameters

mnoGoSearch front-ends support the following parameters given in CGI query string. You may use them in the HTML form on the search page.

Table 8-1. Available search parameters

q | text parameter with search query
s | characters sequence, specifying results sorting order. Small caps specify ascendant sorting, upper caps - descendant. Following characters can be used: R or r - for sorting by relevancy, P or p - for sorting by PopularityRank, D or d - for sorting by last modified date. U or u - for sorting by URL. S or s - for sorting by section (see "su" parameter). Default value: RP.
su | section name to sort results. This parameter must be used with "s=S|s".
sl.* | section limits. You can limit searches with defined section value. E.g.: sl.title=Top
ps | page size, number of search results displayed on one page, 10 by default.
np | page number, 0 by default (first page)
m | search mode. Currently "all","any" and "bool" values are supported.
wm | word match. You may use this parameter to choose word match type. There are "wrd", "beg", "end" and "sub" values which respectively mean whole word, word beginning, word ending and word substring match.
t | tag limit. Limits search through documents with given tag only. This parameter has the same effect with -t indexer option
cat | Category limit. Take a look into the Section called Categories in Chapter 6 for details.

ul

URL limit, URL substring to limit search through subsection of database. It supports SQL % and _ LIKE wildcards. This parameter has the same effect than -u indexer option. If relative URL is specified `search.cgi` inserts % signs before and after "ul" value when compiled with SQL support. It allows to write the URL substring in HTML form to limit search, for example <OPTION VALUE="/manual/"> instead of VALUE="%/manual/%". When full URL with schema is specified `search.cgi` adds % sign only after this value. For example for <OPTION VALUE="http://localhost/"> `search.cgi` will pass http://localhost/% in SQL LIKE comparison.

wf | Weight factors. It allows changing different document sections weights at a search time. Should be passed in the form of hex number. Check the explanation below.
g | Language limit. Language abbreviation to limit search results by url.lang field.
tmplt | Template filename (without path). To specify template file other standard `search.htm`.
type | Content-Type limit. Content-type to limit search results by url.content_type field. For cache mode storage this should be exact match. For SQL-modes it may be SQL-like pattern.
sp | Words forms limit. =1, if you need search all forms for entered words. =0, if you need search only entered words. Default value is 1.
sy | Synonyms limit. =1, if you need add synonyms for entered words. =0, do not use synonyms. Default value is 1.

dt

Limit by time. Three types are supported.

If dt is set to back, that means you want to limit result to recent pages, and you should specify this recentness in variable dp.

If dt is set to er, that means the search will be limited to pages newer or older than the date given. Variable dx is newer/older flag (1 means newer or after, -1 means older or before). Date is specified in variables dy, dm, dd.

If dt is set to range, that means search withing given range of dates. Variables db and de are used here and stand for beginning and end date.

> All times in cached mode are measured with a one hour precision.

dp

Limit by recentness, if dt value is back. It should be specified in xxxA[yyyB[zzzC]] format. Spaces are allowed between xxx and A and yyy and so on). xxx, yyy, zzz are numbers (can be negative!), A, B, C can be one of the following (the letters are the same as in strptime/strftime functions): s - second, M - minute, h - hour, d - day, m - month, y - year. Examples:

      4h30m 	  - 4 hours and 30 minutes
      1Y6M-15d        - 1 year and six month minus 15 days
      1h-60m+1s       - 1 hour minus 60 minutes plus 1 second

dx | is newer/older flag (1 means newer or after, -1 means older or before), if dt value is er.
dm | Month, if dt value is er. 0 - January, 1 - February, ... 11 - December.
dy | Year, if dt value is er. Four digits. For example, 1999 or 2001.
dd | Day, if dt value is er. 1...31.
db | Beginning date, if dt value is range. Each date is a string of the form dd/mm/yyyy, where dd is the day, mm is the month and yyyy is a four-digits year.
de | End date, if dt value is range. Each date is a string of the form dd/mm/yyyy, where dd is the day, mm is the month and yyyy is a four-digits year.

## Changing different document parts weights at search time

It is possible to pass the "wf" HTML form variable to `search.cgi`. "wf" variable represents weight factors for specific document parts. Currently body, title, keywords, description, url parts, crosswords as well as user defined META and HTTP headers are supported. Take a look in the "Section" part of `indexer.conf-dist`.

To be able to use this feature, it is recommended to set different section IDs for different document parts in the "Section" command of `indexer.conf`. Currently up to 256 different sections are supported.

Imagine that we have these default sections in `indexer.conf`:

      Section body        1  256
      Section title       2  128
      Section keywords    3  128
      Section description 4  128

"wf" value is a string of hex digits ABCD. Each digit is a factor for corresponding section's weight. The most right digit corresponds to section 1. For the given above sections configuration:

D is a factor for section 1 (body)
C is a factor for section 2 (title)
B is a factor for section 3 (keywords)
A is a factor for section 4 (description)

Examples:

wf=0001 will search through body only.
wf=1110 will search through title,keywords,description but not
through the body.
wf=F421 will search through:
Description with factor 15 (F hex)
Keywords with factor 4
Title with factor 2
Body with factor 1

By default, if "wf" variable is omitted in the query, all sections factors are 1, it means all sections have the same weight.

## Using front-end with an shtml page

When using a dynamic shtml page containing SSI that calls `search.cgi`, i.e. `search.cgi` is not called directly as a CGI program. It is necessary to override Apache's SCRIPT_NAME environment attribute so that all the links on search pages lead to the dynamic page and not to `search.cgi`.

For example, when a shtml page contains a line <--#include virtual="search.cgi">, SCRIPT_NAME variable will still point to `search.cgi`, but not to the shtml page.

To override the SCRIPT_NAME variable, we implemented a UDMSEARCH_SELF variable that you may add to Apache's `httpd.conf` file. Thus `search.cgi` will check UDMSEARCH_SELF variable first and then SCRIPT_NAME. Here is an example of using UDMSEARCH_SELF environment variable with SetEnv/PassEnv Apache's `httpd.conf` command:

    SetEnv UDMSEARCH_SELF /path/to/search.cgi
    PassEnv UDMSEARCH_SELF

## Using several templates

It is often required to use several templates with the same `search.cgi`. There are several ways to do it. They are given here in the order `search.cgi` detects the template name.

1. `search.cgi` checks the environment variable UDMSEARCH_TEMPLATE. So you can put a path to the desired search template in UDMSEARCH_TEMPLATE.

2. `search.cgi` also supports Apache's internal redirect. It checks REDIRECT_STATUS and REDIRECT_URL environment variables. To activate this way of template usage you may add these lines in Apache `srm.conf`:

       AddType text/html .zhtml
       AddHandler zhtml .zhtml
       Action zhtml /cgi-bin/search.cgi

   Put `search.cgi` into your `/cgi-bin/` directory. Then put the HTML template into your site's directory structure under any name with .zthml extension, for example template.zhtml. Now you may open the search page: http://www.site.com/path/to/template.zhtml You may use any unused extension instead of .zthml, of course.

3. `search.cgi` also checks URL part after "search.cgi", available in the PATH_INFO environment variable. `search.cgi?search1.html` uses `search1.htm` as its template, `search.cgi?search2.html` uses `search2.htm`, and so on.

4. If the above three ways didn't work, search.cgi opens a template which has the same name than the script being executed using SCRIPT_NAME environment variable. `search.cgi` will open a template `ETC/search.htm`, `search1.cgi` will open `ETC/search1.htm` and so on, where ETC is mnoGoSearch's /etc directory (usually `/usr/local/mnoGoSearch/etc`). So, you can use the same `search.cgi` with different templates without having to recompile it. Just create one or several hard or symbolic links for `search.cgi` or copy it and put the corresponding search templates into /etc directory of the mnoGoSearch installation.

   Take a look also into Making multi-language search pages section

## Advanced boolean search

If you want more advanced results, you may use the query language. You should select "bool" match mode in the search form.

mnoGoSearch understands the following boolean operators:

`&` - logical AND. For example, "mysql & odbc". mnoGoSearch will find any URLs that contain both "mysql" and "odbc". You can also use `+` for this operator.

`|` - logical OR. For example "mysql|odbc". mnoGoSearch will find any URLs that contain the word "mysql" or the word "odbc".

`~` - logical NOT. For example "mysql & ~odbc". mnoGoSearch will find URLs that contain the word "mysql" and do not contain the word "odbc" at the same time. Note that ~ just excludes the given word from the results. Query "~odbc" will not find anything!

`()` - group command to compose more complex queries. For example "(mysql | msql) & ~postgres". Query language is simple and powerful at the same time. Just consider the query as a usual boolean expression.

## How search handles expired documents

Expired documents are still searchable with their old content.

Prev | Home | Next
Multilingual servers support |  | How to write search result templates