|
|
Chapter 6. Subsections
6.1. TagsTag is a special parameter which can be given for a set of documents. The main purpose of tags is to join a number of documents into one group and then while doing search to select a group of documents to search through. You can use Tag command of indexer.conf to give some tag value for a server or server subset. While doing search you can specify tag value to search through documents which tag matches given parameter with t=xxx parameter, which can be passed from HTML form. Take a look into Section 6.1.1, indexer.conf-dist and search.htm-dist for explanation and examples. 6.1.1. Tag commandTag <string> Use this field for your own purposes. For example for grouping some servers into one group, etc... During search you'll be able to limit URLs to be searched through by their tags. Can be set multiple times before Server command and takes effect till the end of config file or till next Tag command. Default values is an empty string. 6.1.2. TagIf commandTagIf <tag> [Match|NoMatch] [NoCase|Case] [String|Regex] <section> <arg> [<arg> ... ] Mark document by <tag> tag, if the value of section match the arg pattern given. The meaning of first three optional parameters are exactly the same as for the Allow command (see Section 3.10.14). Example TagIf Docs regex Title Manual 6.1.3. Tags in SQL versionTag type is CHAR. CHAR type allows to use some nice features. You can use '_' and '%' LIKE wildcards in tag parameter when doing search. It makes possible that tag, like a category, does support an idea of nesting. For example, documents with tag value "AB" can be found with both "A%" and "AB" tag limits. Tags also give a way to make an URL a member of multiple tag selections. Playing with LIKE wildcards you can easily create two or more groups. For example, tag "ABCDE" is the member of at least these selections: _BCDE A_CDE AB_DE ABC_E ABCD_
|