This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:indexing:powersearch:custom [2012/01/30 21:56] doc |
admin:indexing:powersearch:custom [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 19: | Line 19: | ||
| Usages are essential to the customization of PowerSearch. The POWERSEARCH option instructs Omnidex to evaluate the columns referenced in the WHERE clause of the SELECT statement, and matches their USAGE clauses with the preconfigured instructions for each USAGE. These instructions describe actions such as using synonyms, checking for misspelling, or even doing geographic searches. | Usages are essential to the customization of PowerSearch. The POWERSEARCH option instructs Omnidex to evaluate the columns referenced in the WHERE clause of the SELECT statement, and matches their USAGE clauses with the preconfigured instructions for each USAGE. These instructions describe actions such as using synonyms, checking for misspelling, or even doing geographic searches. | ||
| + | |||
| + | |||
| + | === The Usages File Layout === | ||
| These preconfigured instructions can be customized or expanded to meet the needs of each application. The usage instructions exist in a tab-delimited file with six columns. It can be modified using a text editor such as 'Notepad' on Windows or 'vi' on UNIX. It can also be created in a spreadsheet program such as Microsoft Excel, which allows a file to be saved as a Tab-Delimited File. | These preconfigured instructions can be customized or expanded to meet the needs of each application. The usage instructions exist in a tab-delimited file with six columns. It can be modified using a text editor such as 'Notepad' on Windows or 'vi' on UNIX. It can also be created in a spreadsheet program such as Microsoft Excel, which allows a file to be saved as a Tab-Delimited File. | ||
| Line 55: | Line 58: | ||
| * %CRITERIA% - This token is replaced with the criteria passed in the WHERE clause for this column. | * %CRITERIA% - This token is replaced with the criteria passed in the WHERE clause for this column. | ||
| - | Typically, the replacement string uses a $CONTAINS clause that applies synonyms, misspellings or other Omnidex features. The use of a $CONTAINS clause is not required, though. While not all SQL can be applied, administrators can try applied varied SQL clauses in this section, including complex, parenthesized, Boolean predicates, nested queries, etc. | + | Typically, the replacement string uses a [[dev:sql:functions:contains|$CONTAINS]] clause that applies synonyms, misspellings or other Omnidex features. The use of a $CONTAINS clause is not required, though. While every SQL construct cannot be supported, administrators can use a wide variety of SQL clauses in this section, including complex, parenthesized, Boolean predicates, nested queries, etc. |
| == $COMMENTS == | == $COMMENTS == | ||
| - | Comments that are useful to the administrator to document this usage.. | + | Comments that are useful to the administrator to document this usage. |