cvs: phpdoc /ja/functions mnogosearch.xml yaz.xml
| From: | Rui Hirokawa | Date: | Mon, 19 Feb 2001 09:57:19 +0000 |
| Subject: | cvs: phpdoc /ja/functions mnogosearch.xml yaz.xml | ||
| Groups: | php.doc | ||
| Request: | Send a blank email to phpdoc+get-969334329@lists.php.net to get a copy of this message | ||
hirokawa Mon Feb 19 01:57:19 2001 EDT
Added files:
/phpdoc/ja/functions mnogosearch.xml
Modified files:
/phpdoc/ja/functions yaz.xml
Log:
added mnogosearch.xml in japanese tree and update translation.
Index: phpdoc/ja/functions/yaz.xml diff -u phpdoc/ja/functions/yaz.xml:1.4 phpdoc/ja/functions/yaz.xml:1.5 --- phpdoc/ja/functions/yaz.xml:1.4 Sun Feb 18 15:29:44 2001 +++ phpdoc/ja/functions/yaz.xml Mon Feb 19 01:57:19 2001 @@ -619,17 +619,16 @@ </funcprototype> </funcsynopsis> <para> - Given a target ID this function returns and array with terms as received - from the target in the last Scan Response. - This function returns an array (0..n-1) where n is the number - of terms returned. Each value is a pair where first item is - term, second item is result-count. - If the <parameter>result</parameter> is given it will be modified to hold - additional information taken from the Scan Response: - <literal>number</literal> (number of entries returned), - <literal>stepsize</literal> (Step-size), - <literal>position</literal> (position of term), - <literal>status</literal> (Scan Status). + ã¿ã¼ã²ããIDãæå®ããããã¨ããã®é¢æ°ã¯ç´è¿ã®ã¹ãã£ã³æã®ã¬ã¹ã + ã³ã¹ã¨ãã¦ã¿ã¼ã²ããããåä¿¡ããé ç®ãé åã¨ãã¦è¿ãã¾ãããã®é¢ + æ°ã¯ãé å(0..n-1)ãè¿ãã¾ãããã ããnã¯è¿ãããé ç®ã®æ°ã§ããå + å¤ã¯ãæåã®å¤ãé ç®ã§ã2çªç®ã®å¤ãçµæã®æ°ã¨ããçµã«ãªã£ã¦ãã¾ãã + <parameter>result</parameter>ãæå®ãããå ´åããã®å¤æ°ã«ã¯ã¹ã㣠+ ã³æã®å¿çããã¨ããã¾ããæ¬¡ã®ãããªè¿½å æ å ±ãä»£å ¥ããã¾ãã + <literal>number</literal> (è¿ãããã¨ã³ããªã®æ°), + <literal>stepsize</literal> (ã¹ããããµã¤ãº), + <literal>position</literal> (é ç®ã®ä½ç½®), + <literal>status</literal> (ã¹ãã£ã³ã¹ãã¼ã¿ã¹) </para> </refsect1> </refentry> @@ -649,38 +648,36 @@ </funcprototype> </funcsynopsis> <para> - This function configures the CCL query parser for a target - with definitions of access points (CCL qualifiers) and their - mapping to RPN. To map a specific CCL query to RPN afterwards - call the <function>yaz_ccl_parse</function> function. - Each index of the array <parameter>config</parameter> is the - name of a CCL field and the corresponding value holds a string - that specifies a mapping to RPN. - The mapping is a sequence of attribute-type, attribute-value - pairs. Attribute-type and attribute-value is separated by an equal - sign (<literal>=</literal>). Each pair is separated by white space. + ãã®é¢æ°ã¯ãã¢ã¯ã»ã¹ãã¤ã³ã(CCLéå®è¾)ãå®ç¾©ããã¿ã¼ã²ããã«é¢ã + ã¦CCLã¯ã¨ãªãã¼ãµã¨RPNã¸ã®ãããã³ã°ãè¨å®ãã¾ããç¹å®ã®CCLã¯ã¨ãª + ãå¾ã§RPNã«ãããããã«ã¯ã<function>yaz_ccl_parse</function>颿° + ãã³ã¼ã«ãã¦ä¸ãããé å<parameter>config</parameter>ã®åæ·»åã¯ã + CCLãã£ã¼ã«ãã®ååã§ããã対å¿ããå¤ã¯RPNã¸ã®ãããã³ã°ãæå®ã + ãæååãä¿æãã¾ãããããã³ã°ã¯å±æ§åããã³å±æ§å¤ã®çµã並ãã + ãã®ã§ãã屿§åã¨å±æ§å¤ã¯ãçå· (<literal>=</literal>)ã§åºåãã + ã¾ããåçµã¯ã空ç½ã§åºåããã¾ãã </para> <para> - <example> - <title>CCL configuration</title> - <simpara> - In the example below, the CCL parser is configured to support - three CCL fields: <literal>ti</literal>, <literal>au</literal> and - <literal>isbn</literal>. Each field is mapped to their BIB-1 - equivalent. It is assumed that variable <literal>$id</literal> is a - target ID. - </simpara> - <programlisting> - $field["ti"] = "1=4"; - $field["au"] = "1=1"; - $field["isbn"] = "1=7"; - yaz_ccl_conf($id,$field); - </programlisting> - </example> + <example> + <title>CCL è¨å®</title> + <simpara> + 以ä¸ã®ä¾ã§ã¯ãCCLãã¼ãµã¯<literal>ti</literal>ã + <literal>au</literal>ã<literal>isbn</literal>ã¨ãã3ã¤ã®CCLãã£ã¼ + ã«ãããµãã¼ãããããã«è¨å®ããã¾ããåãã£ã¼ã«ãã¯ãç価㪠+ BIB-1ã¸ãããããã¾ãã ãã®ä¾ã§ã¯ã<literal>$id</literal>ãã¿ã¼ + ã²ããIDã§ãããã¨ãä»®å®ãã¦ãã¾ãã + </simpara> + <programlisting> + $field["ti"] = "1=4"; + $field["au"] = "1=1"; + $field["isbn"] = "1=7"; + yaz_ccl_conf($id,$field); + </programlisting> + </example> </para> </refsect1> </refentry> - + <refentry id="function.yaz-ccl-parse"> <refnamediv> <refname>yaz_ccl_parse</refname> @@ -697,23 +694,20 @@ </funcprototype> </funcsynopsis> <para> - ãã®é¢æ°ã¯ãCCLãã¼ãµãèµ·åãã¾ãã - This function invokes the CCL parser. It converts a given - CCL FIND query to an RPN query which may be passed to the - <function>yaz_search</function> function to perform a search. - To define a set of valid CCL fields call - <function>yaz_ccl_conf</function> prior to this function. - If the supplied <parameter>query</parameter> was successfully - converted to RPN, this function returns true, and the index - <literal>rpn</literal> of the supplied array - <parameter>result</parameter> holds a valid RPN query. - If the query could not be converted (because of invalid syntax, - unknown field, etc.) this function returns false and three - indexes are set in the resulting array to indicate the cause - of failure: <literal>errorcode</literal>CCL error code (integer), - <literal>errorstring</literal>CCL error string, and - <literal>errorpos</literal>approximate position in query of failure - (integer is character position). + ãã®é¢æ°ã¯ãCCLãã¼ãµãèµ·åãã¾ãããã¼ãµã¯ãæå®ããCCL FINDã¯ã¨ + ãªãæ¤ç´¢ãå®è¡ãã<function>yaz_search</function>颿°ã«æå®å¯è½ãª + RPNã¯ã¨ãªã«å¤æãã¾ããæå¹ãªCCLãã£ã¼ã«ãã®çµãå®ç¾©ããã«ã¯ãã + ã®é¢æ°ã®åã«<function>yaz_ccl_conf</function>ãã³ã¼ã«ãã¾ããæå® + ãã<parameter>query</parameter>ã®RPNã¸ã®å¤æãæåããå ´åããã® + 颿°ã¯trueãè¿ããæå®ããé å<parameter>result</parameter>ã®æ·»å + <literal>rpn</literal>ã¯ãæå¹ãªRPNã¯ã¨ãªãä¿æãã¾ãã(æ§æãç¡ + å¹ã§ãã£ãããåå¨ããªããã£ã¼ã«ãã§ããçã®çç±ã«ããã)ã¯ã¨ãªã + 夿ã§ããªãã£ãå ´åããã®é¢æ°ã¯falseãè¿ãã失æã®åå ã示ããã + ã«è¿ãããé åã«æ¬¡ã®ãããª3ã¤ã®æ·»åãè¨å®ããã¾ãã + <literal>errorcode</literal>CCL ã¨ã©ã¼ã³ã¼ã (æ´æ°)ã + <literal>errorstring</literal>CCLã¨ã©ã¼æååã + <literal>errorpos</literal> ã¨ã©ã¼ãçºçããã¯ã¨ãªã®ããããã®ä½ + ç½®(æ´æ°ã¯æåã®ä½ç½®ãæ´æ°ã§è¡¨ãããã®) </para> </refsect1> </refentry> Index: phpdoc/ja/functions/mnogosearch.xml +++ phpdoc/ja/functions/mnogosearch.xml <reference id="ref.mnogo"> <title>mnoGoSearch 颿°</title> <titleabbrev>mnoGoSearch</titleabbrev> <partintro> <simpara> ããã§ç¤ºã颿°ã«ãããããªã¼ã®æ¤ç´¢ã¨ã³ã¸ã³ mnoGoSearch (æ§å㯠UdmSearch)ã¸ã¢ã¯ã»ã¹ãããã¨ãå¯è½ã¨ãªãã¾ãããããã®é¢æ°ãå©ç¨å¯ è½ã¨ããããã«ã¯ããªãã·ã§ã³ <option role="configure">--with-mnogosearch</option> ã«ãã mnogosearchãµ ãã¼ããæå®ãã¦PHPãã³ã³ãã¤ã«ããå¿ è¦ãããã¾ããmnogosearchã®ã ã¹ãæå®ããã«ãã®ãªãã·ã§ã³ã使ç¨ããå ´åãPHPã¯ããã©ã«ãã§ mnogosearchã/usr/local/mnogosearchã«ãããã®ã¨ãã¦æ¤ç´¢ãè¡ãã¾ãã mnogosearchãä»ã®å ´æã«ã¤ã³ã¹ãã¼ã«ãã¦ããå ´åã«ã¯ã <option role="configure">--with-mnogosearch=DIR</option>ã®ããã«ã ã®ãã¹ãæå®ããå¿ è¦ãããã¾ãã </simpara> <note> <para> PHPã«ã¯ãMySQLã¨ã®æ¥ç¶ã©ã¤ãã©ãªãçµã¿è¾¼ã¾ãã¦ãããMySQLã«ã¢ã¯ã» ã¹ãããã¨ãå¯è½ã§ããmnoGoSearchã¯ããã®çµã¿è¾¼ã¿ã©ã¤ãã©ãªã¨äºæ æ§ããªããé常ã®MySQLã©ã¤ãã©ãªã¨ã®çµåãã§ã®ã¿åä½ãã¾ãããã®ã ããmnoGoSearchãMySQLã¨çµã¿åããã¦ä½¿ç¨ããéã«ã¯ãPHPã® configureã«MySQLãã¤ã³ã¹ãã¼ã«ãããã£ã¬ã¯ããªãæå®ããå¿ è¦ã ããã¾ããããã¯ãmnoGoSearchã«é¢ããè¨å®ã§ä½¿ç¨ãããä¾ãã°ã次㮠ããã«ãªãã¾ãã <option role="configure">--with-mnogosearch --with-mysql=/usr</option> </para> </note> <simpara> ãããã®é¢æ°ã使ç¨ããã«ã¯ã3.1.10以éã®ãã¼ã¸ã§ã³ã®mnoGoSearchã ã¤ã³ã¹ãã¼ã«ããã¦ããå¿ è¦ãããã¾ãã </simpara> <simpara> mnoGoSearchã«é¢ããããè©³ç´°ãªæ å ±ã¯ã<ulink url="&url.mnogo;">&url.mnogo;</ulink>ã«ããã¾ãã </simpara> </partintro> <refentry id="function.udm-alloc-agent"> <refnamediv> <refname>udm_alloc_agent</refname> <refpurpose>mnoGoSearch ã»ãã·ã§ã³ã確ä¿ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_alloc_agent</function></funcdef> <paramdef>string <parameter>dbaddr</parameter></paramdef> <paramdef>string <parameter> <optional>dbmode</optional> </parameter> </paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_alloc_agent</function> returns mnogosearch agent identifier on success, <literal>FALSE</literal> on error. This function creates a session with database parameters. </para> <para> <parameter>dbaddr</parameter> - URL-style database description. Options (type, host, database name, port, user and password) to connect to SQL database. Do not matter for built-in text files support. Format: DBAddr DBType:[//[DBUser[:DBPass]@]DBHost[:DBPort]]/DBName/ Currently supported DBType values are: mysql, pgsql, msql, solid, mssql, oracle, ibase. Actually, it does not matter for native libraries support. But ODBC users should specify one of supported values. If your database type is not supported, you may use "unknown" instead. </para> <para> <parameter>dbmode</parameter> - You may select SQL database mode of words storage. When "single" is specified, all words are stored in the same table. If "multi" is selected, words will be located in different tables depending of their lengths. "multi" mode is usually faster but requires more tables in database. If "crc" mode is selected, mnoGoSearch will store 32 bit integer word IDs calculated by CRC32 algorythm instead of words. This mode requres less disk space and it is faster comparing with "single" and "multi" modes. "crc-multi" uses the same storage structure with the "crc" mode, but also stores words in different tables depending on words lengths like "multi" mode. Format: DBMode single/multi/crc/crc-multi </para> <note> <para> <parameter>dbaddr</parameter> and <parameter>dbmode</parameter> must match those used during indexing. </para> </note> <note> <para> In fact this function does not open connection to database and thus does not check entered login and password. Actual connection to database and login/password verification is done by <function>udm_find</function>. </para> </note> </refsect1> </refentry> <refentry id="function.udm-set-agent-param"> <refnamediv> <refname>udm_set_agent_param</refname> <refpurpose> mnoGoSearch ã¨ã¼ã¸ã§ã³ãã®ã»ãã·ã§ã³ãã©ã¡ã¼ã¿ãè¨å®ãã </refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_set_agent_param</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> <paramdef>int <parameter>var</parameter></paramdef> <paramdef>string <parameter>val</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_set_agent_param</function> returns <literal>TRUE</literal> on success, <literal>FALSE</literal> on error. Defines mnoGoSearch session parameters. </para> <simpara> The following parameters and their values are available: </simpara> <itemizedlist> <listitem> <simpara> UDM_PARAM_PAGE_NUM - used to choose search results page number (results are returned by pages beginning from 0, with UDM_PARAM_PAGE_SIZE results per page). </simpara> </listitem> <listitem> <simpara> UDM_PARAM_PAGE_SIZE - number of search results displayed on one page. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_SEARCH_MODE - search mode. The following values available: UDM_MODE_ALL - search for all words; UDM_MODE_ANY - search for any word; UDM_MODE_BOOL - boolean search. See <function>udm_find</function> for details on boolean search. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_CACHE_MODE - turns on or off search result cache mode. When enabled, the search engine will store search results to disk. In case a similar search is performed later, the engine will take results from the cache for faster performance. Available values: UDM_CACHE_ENABLED, UDM_CACHE_DISABLED. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_TRACK_MODE - turns on or off trackquery mode. Since version 3.1.2 mnoGoSearch has a query tracking support. Note that tracking is implemented in SQL version only and not available in built-in database. To use tracking, you have to create tables for tracking support. For MySQL, use create/mysql/track.txt. When doing a search, front-end uses those tables to store query words, a number of found documents and current UNIX timestamp in seconds. Available values: UDM_TRACK_ENABLED, UDM_TRACK_DISABLED. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_CHARSET - defines local charset. Available values: set of charsets supported by mnoGoSearch, e.g. koi8-r, cp1251, ... </simpara> </listitem> <listitem> <simpara> UDM_PARAM_STOPFILE - Defines name and path to stopwords file. (There is a small difference with mnoGoSearch - while in mnoGoSearch if relative path or no path entered, it looks for this file in relation to UDM_CONF_DIR, the module looks for the file in relation to current path, i.e. to the path where the php script is executed.) </simpara> </listitem> <listitem> <simpara> UDM_PARAM_STOPTABLE - Load stop words from the given SQL table. You may use several StopwordTable commands. This command has no effect when compiled without SQL database support. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_WEIGHT_FACTOR - represents weight factors for specific document parts. Currently body, title, keywords, description, url are supported. To activate this feature please use degrees of 2 in *Weight commands of the indexer.conf. Let's imagine that we have these weights: </simpara> <simpara>URLWeight 1</simpara> <simpara>BodyWeight 2</simpara> <simpara>TitleWeight 4</simpara> <simpara>KeywordWeight 8</simpara> <simpara>DescWeight 16</simpara> <simpara> As far as indexer uses bit OR operation for word weights when some word presents several time in the same document, it is possible at search time to detect word appearance in different document parts. Word which appears only in the body will have 00000010 argegate weight (in binary notation). Word used in all document parts will have 00011111 aggregate weight. </simpara> <simpara> This parameter's value is a string of hex digits ABCDE. Each digit is a factor for corresponding bit in word weight. For the given above weights configuration: </simpara> <simpara>E is a factor for weight 1 (URL Weight bit)</simpara> <simpara>D is a factor for weight 2 (BodyWeight bit)</simpara> <simpara>C is a factor for weight 4 (TitleWeight bit)</simpara> <simpara>B is a factor for weight 8 (KeywordWeight bit)</simpara> <simpara>A is a factor for weight 16 (DescWeight bit)</simpara> <simpara> Examples: </simpara> <simpara> UDM_PARAM_WEIGHT_FACTOR=00001 will search through URLs only. </simpara> <simpara> UDM_PARAM_WEIGHT_FACTOR=00100 will search through Titles only. </simpara> <simpara> UDM_PARAM_WEIGHT_FACTOR=11100 will search through Title,Keywords,Desctription but not through URL and Body. </simpara> <simpara> UDM_PARAM_WEIGHT_FACTOR=F9421 will search through: </simpara> <simpara>Description with factor 15 (F hex)</simpara> <simpara>Keywords with factor 9</simpara> <simpara>Title with factor 4</simpara> <simpara>Body with factor 2</simpara> <simpara>URL with factor 1</simpara> <simpara> If UDM_PARAM_WEIGHT_FACTOR variable is ommited, original weight value is taken to sort results. For a given above weight configuration it means that document description has a most big weight 16. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_WORD_MATCH - word match. You may use this parameter to choose word match type. This feature works only in "single" and "multi" modes using SQL based and built-in database. It does not work in cachemode and other modes since they use word CRC and do not support substring search. Available values: </simpara> <simpara>UDM_MATCH_BEGIN - word beginning match;</simpara> <simpara>UDM_MATCH_END - word ending match;</simpara> <simpara>UDM_MATCH_WORD - whole word match;</simpara> <simpara>UDM_MATCH_SUBSTR - word substring match.</simpara> </listitem> </itemizedlist> </refsect1> </refentry> <refentry id="function.udm-add-search-limit"> <refnamediv> <refname>udm_add_search_limit</refname> <refpurpose>種ã ã®æ¤ç´¢ã®å¶ç´ãè¨å®ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_add_search_limit</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> <paramdef>int <parameter>var</parameter></paramdef> <paramdef>string <parameter>val</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_add_search_limit</function> returns <literal>TRUE</literal> on success, <literal>FALSE</literal> on error. Adds search restrictions. </para> <para> <parameter>agent</parameter> - a link to Agent, received after call to <function>udm_alloc_agent</function>. </para> <para> <parameter>var</parameter> - defines parameter, indicating limit. </para> <para> <parameter>val</parameter> - defines value of the current parameter. </para> <para> Possible <parameter>var</parameter> values: </para> <itemizedlist> <listitem> <simpara> UDM_LIMIT_URL - defines document URL limitations to limit search through subsection of database. It supports SQL % and _ LIKE wildcards, where % matches any number of characters, even zero characters, and _ matches exactly one character. E.g. http://my.domain.__/catalog may stand for http://my.domain.ru/catalog and http://my.domain.ua/catalog. </simpara> </listitem> <listitem> <simpara> UDM_LIMIT_TAG - defines site TAG limitations. In indexer-conf you can assign specific TAGs to various sites and parts of a site. Tags in mnoGoSearch 3.1.x are lines, that may contain metasymbols % and _. Metasymbols allow searching among groups of tags. E.g. there are links with tags ABCD and ABCE, and search restriction is by ABC_ - the search will be made among both of the tags. </simpara> </listitem> <listitem> <simpara> UDM_LIMIT_LANG - defines document language limitations. </simpara> </listitem> <listitem> <simpara> UDM_LIMIT_CAT - defines document category limitations. Categories are similar to tag feature, but nested. So you can have one category inside another and so on. You have to use two characters for each level. Use a hex number going from 0-F or a 36 base number going from 0-Z. Therefore a top-level category like 'Auto' would be 01. If it has a subcategory like 'Ford', then it would be 01 (the parent category) and then 'Ford' which we will give 01. Put those together and you get 0101. If 'Auto' had another subcategory named 'VW', then it's id would be 01 because it belongs to the 'Ford' category and then 02 because it's the next category. So it's id would be 0102. If VW had a sub category called 'Engine' then it's id would start at 01 again and it would get the 'VW' id 02 and 'Auto' id of 01, making it 010201. If you want to search for sites under that category then you pass it cat=010201 in the url. </simpara> </listitem> </itemizedlist> </refsect1> </refentry> <refentry id="function.udm-clear-search-limits"> <refnamediv> <refname>udm_clear_search_limits</refname> <refpurpose> mnoGoSearch æ¤ç´¢ã«é¢ããå ¨ã¦ã®å¶ç´ãã¯ãªã¢ãã </refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_clear_search_limits</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_clear_search_limits</function> resets defined search limitations and returns <literal>TRUE</literal>. </para> </refsect1> </refentry> <refentry id="function.udm-find"> <refnamediv> <refname>udm_find</refname> <refpurpose>æ¤ç´¢ãå®è¡ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_find</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> <paramdef>string <parameter>query</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_find</function> returns result link identifier on success, <literal>FALSE</literal> on error. </para> <para> The search itself. The first argument - session, the next one - query itself. To find something just type words you want to find and press SUBMIT button. For example, "mysql odbc". You should not use quotes " in query, they are written here only to divide a query from other text. mnoGoSearch will find all documents that contain word "mysql" and/or word "odbc". Best documents having bigger weights will be displayed first. If you use search mode ALL, search will return documents that contain both (or more) words you entered. In case you use mode ANY, the search will return list of documents that contain any of the words you entered. If you want more advanced results you may use query language. You should select "bool" match mode in the search from. </para> <simpara> mnoGoSearch understands the following boolean operators: </simpara> <simpara> & - logical AND. For example, "mysql & odbc". mnoGoSearch will find any URLs that contain both "mysql" and "odbc". </simpara> <simpara> | - logical OR. For example "mysql|odbc". mnoGoSearch will find any URLs, that contain word "mysql" or word "odbc". </simpara> <simpara> ~ - logical NOT. For example "mysql & ~odbc". mnoGoSearch will find URLs that contain word "mysql" and do not contain word "odbc" at the same time. Note that ~ just excludes given word from results. Query "~odbc" will find nothing! </simpara> <simpara> () - group command to compose more complex queries. For example "(mysql | msql) & ~postgres". Query language is simple and powerful at the same time. Just consider query as usual boolean expression. </simpara> </refsect1> </refentry> <refentry id="function.udm-get-res-param"> <refnamediv> <refname>udm_get_res_param</refname> <refpurpose>mnoGoSearch çµæãã©ã¡ã¼ã¿ãåå¾ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>string <function>udm_get_res_param</function></funcdef> <paramdef>int <parameter>res</parameter></paramdef> <paramdef>int <parameter>param</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_get_res_param</function> returns result parameter value on success, <literal>FALSE</literal> on error. </para> <para> <parameter>res</parameter> - a link to result identifier, received after call to <function>udm_find</function>. </para> <para> <parameter>param</parameter> - parameter identifier, may have the following values: </para> <itemizedlist> <listitem> <simpara> UDM_PARAM_NUM_ROWS - number of received found links on the current page. It is equal to UDM_PARAM_PAGE_SIZE for all search pages, on the last page - the rest of links. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_FOUND - total number of results matching the query. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_WORDINFO - information on the words found. E.g. search for "a good book" will return "a: stopword, good:5637, book: 120" </simpara> </listitem> <listitem> <simpara> UDM_PARAM_SEARCHTIME - search time in seconds. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_FIRST_DOC - the number of the first document displayed on current page. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_LAST_DOC - the number of the last document displayed on current page. </simpara> </listitem> </itemizedlist> </refsect1> </refentry> <refentry id="function.udm-get-res-field"> <refnamediv> <refname>udm_get_res_field</refname> <refpurpose>mnoGoSearch çµæãã£ã¼ã«ããåå¾ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>string <function>udm_get_res_field</function></funcdef> <paramdef>int <parameter>res</parameter></paramdef> <paramdef>int <parameter>row</parameter></paramdef> <paramdef>int <parameter>field</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_get_res_field</function> returns result field value on success, <literal>FALSE</literal> on error. </para> <para> <parameter>res</parameter> - a link to result identifier, received after call to <function>udm_find</function>. </para> <para> <parameter>row</parameter> - the number of the link on the current page. May have values from 0 to <parameter>UDM_PARAM_NUM_ROWS</parameter>. </para> <para> <parameter>field</parameter> - field identifier, may have the following values: </para> <itemizedlist> <listitem> <simpara> UDM_FIELD_URL - document URL field </simpara> </listitem> <listitem> <simpara> UDM_FIELD_CONTENT - document Content-type field (for example, text/html). </simpara> </listitem> <listitem> <simpara> UDM_FIELD_TITLE - document title field. </simpara> </listitem> <listitem> <simpara> UDM_FIELD_KEYWORDS - document keywords field (from META KEYWORDS tag). </simpara> </listitem> <listitem> <simpara> UDM_FIELD_DESC - document description field (from META DESCRIPTION tag). </simpara> </listitem> <listitem> <simpara> UDM_FIELD_TEXT - document body text (the first couple of lines to give an idea of what the document is about). </simpara> </listitem> <listitem> <simpara> UDM_FIELD_SIZE - document size. </simpara> </listitem> <listitem> <simpara> UDM_FIELD_URLID - unique URL ID of the link. </simpara> </listitem> <listitem> <simpara> UDM_FIELD_RATING - page rating (as calculated by mnoGoSearch). </simpara> </listitem> <listitem> <simpara> UDM_FIELD_MODIFIED - last-modified field in unixtime format. </simpara> </listitem> <listitem> <simpara> UDM_FIELD_ORDER - the number of the current document in set of found documents. </simpara> </listitem> <listitem> <simpara> UDM_FIELD_CRC - document CRC. </simpara> </listitem> </itemizedlist> </refsect1> </refentry> <refentry id="function.udm-free-res"> <refnamediv> <refname>udm_free_res</refname> <refpurpose>mnoGoSearch çµæãéæ¾ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_free_res</function></funcdef> <paramdef>int <parameter>res</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_free_res</function> returns <literal>TRUE</literal> on success, <literal>FALSE</literal> on error. </para> <para> <parameter>res</parameter> - a link to result identifier, received after call to <function>udm_find</function>. </para> <para> Freeing up memory allocated for results. </para> </refsect1> </refentry> <refentry id="function.udm-free-agent"> <refnamediv> <refname>udm_free_agent</refname> <refpurpose>mnoGoSearch ã»ãã·ã§ã³ãéæ¾ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_free_agent</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_free_agent</function> returns <literal>TRUE</literal> on success, <literal>FALSE</literal> on error. </para> <para> <parameter>agent</parameter> - link to agent identifier, received after call to <function>udm_alloc_agent</function>. </para> <para> Freeing up memory allocated for agent session. </para> </refsect1> </refentry> <refentry id="function.udm-errno"> <refnamediv> <refname>udm_errno</refname> <refpurpose>mnoGoSearch ã¨ã©ã¼çªå·ãåå¾ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_errno</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_errno</function> returns mnoGoSearch error number, zero if no error. </para> <para> <parameter>agent</parameter> - link to agent identifier, received after call to <function>udm_alloc_agent</function>. </para> <para> Receiving numeric agent error code. </para> </refsect1> </refentry> <refentry id="function.udm-error"> <refnamediv> <refname>udm_error</refname> <refpurpose>mnoGoSearch ã¨ã©ã¼ã¡ãã»ã¼ã¸ãå¾ã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>string <function>udm_error</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_error</function> ã¯ãmnoGoSearch ã¨ã©ã¼ã¡ãã»ã¼ã¸ã è¿ãã¾ããã¨ã©ã¼ããªãå ´åã«ã¯ãç©ºã®æååãè¿ãã¾ãã </para> <para> <parameter>agent</parameter> ã¯ãã¨ã¼ã¸ã§ã³ãIDã¸ã®ãªã³ã¯ã§ããã <function>udm_alloc_agent</function>ãã³ã¼ã«ããéã«å¾ããããã® ã§ãã </para> <para> ã¨ã¼ã¸ã§ã³ãã¨ã©ã¼ã¡ãã»ã¼ã¸ãå¾ã¾ãã </para> </refsect1> </refentry> </reference> <!-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t sgml-parent-document:nil sgml-default-dtd-file:"../../manual.ced" sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: -->
Index: phpdoc/ja/functions/yaz.xml diff -u phpdoc/ja/functions/yaz.xml:1.4 phpdoc/ja/functions/yaz.xml:1.5 --- phpdoc/ja/functions/yaz.xml:1.4 Sun Feb 18 15:29:44 2001 +++ phpdoc/ja/functions/yaz.xml Mon Feb 19 01:57:19 2001 @@ -619,17 +619,16 @@ </funcprototype> </funcsynopsis> <para> - Given a target ID this function returns and array with terms as received - from the target in the last Scan Response. - This function returns an array (0..n-1) where n is the number - of terms returned. Each value is a pair where first item is - term, second item is result-count. - If the <parameter>result</parameter> is given it will be modified to hold - additional information taken from the Scan Response: - <literal>number</literal> (number of entries returned), - <literal>stepsize</literal> (Step-size), - <literal>position</literal> (position of term), - <literal>status</literal> (Scan Status). + ã¿ã¼ã²ããIDãæå®ããããã¨ããã®é¢æ°ã¯ç´è¿ã®ã¹ãã£ã³æã®ã¬ã¹ã + ã³ã¹ã¨ãã¦ã¿ã¼ã²ããããåä¿¡ããé ç®ãé åã¨ãã¦è¿ãã¾ãããã®é¢ + æ°ã¯ãé å(0..n-1)ãè¿ãã¾ãããã ããnã¯è¿ãããé ç®ã®æ°ã§ããå + å¤ã¯ãæåã®å¤ãé ç®ã§ã2çªç®ã®å¤ãçµæã®æ°ã¨ããçµã«ãªã£ã¦ãã¾ãã + <parameter>result</parameter>ãæå®ãããå ´åããã®å¤æ°ã«ã¯ã¹ã㣠+ ã³æã®å¿çããã¨ããã¾ããæ¬¡ã®ãããªè¿½å æ å ±ãä»£å ¥ããã¾ãã + <literal>number</literal> (è¿ãããã¨ã³ããªã®æ°), + <literal>stepsize</literal> (ã¹ããããµã¤ãº), + <literal>position</literal> (é ç®ã®ä½ç½®), + <literal>status</literal> (ã¹ãã£ã³ã¹ãã¼ã¿ã¹) </para> </refsect1> </refentry> @@ -649,38 +648,36 @@ </funcprototype> </funcsynopsis> <para> - This function configures the CCL query parser for a target - with definitions of access points (CCL qualifiers) and their - mapping to RPN. To map a specific CCL query to RPN afterwards - call the <function>yaz_ccl_parse</function> function. - Each index of the array <parameter>config</parameter> is the - name of a CCL field and the corresponding value holds a string - that specifies a mapping to RPN. - The mapping is a sequence of attribute-type, attribute-value - pairs. Attribute-type and attribute-value is separated by an equal - sign (<literal>=</literal>). Each pair is separated by white space. + ãã®é¢æ°ã¯ãã¢ã¯ã»ã¹ãã¤ã³ã(CCLéå®è¾)ãå®ç¾©ããã¿ã¼ã²ããã«é¢ã + ã¦CCLã¯ã¨ãªãã¼ãµã¨RPNã¸ã®ãããã³ã°ãè¨å®ãã¾ããç¹å®ã®CCLã¯ã¨ãª + ãå¾ã§RPNã«ãããããã«ã¯ã<function>yaz_ccl_parse</function>颿° + ãã³ã¼ã«ãã¦ä¸ãããé å<parameter>config</parameter>ã®åæ·»åã¯ã + CCLãã£ã¼ã«ãã®ååã§ããã対å¿ããå¤ã¯RPNã¸ã®ãããã³ã°ãæå®ã + ãæååãä¿æãã¾ãããããã³ã°ã¯å±æ§åããã³å±æ§å¤ã®çµã並ãã + ãã®ã§ãã屿§åã¨å±æ§å¤ã¯ãçå· (<literal>=</literal>)ã§åºåãã + ã¾ããåçµã¯ã空ç½ã§åºåããã¾ãã </para> <para> - <example> - <title>CCL configuration</title> - <simpara> - In the example below, the CCL parser is configured to support - three CCL fields: <literal>ti</literal>, <literal>au</literal> and - <literal>isbn</literal>. Each field is mapped to their BIB-1 - equivalent. It is assumed that variable <literal>$id</literal> is a - target ID. - </simpara> - <programlisting> - $field["ti"] = "1=4"; - $field["au"] = "1=1"; - $field["isbn"] = "1=7"; - yaz_ccl_conf($id,$field); - </programlisting> - </example> + <example> + <title>CCL è¨å®</title> + <simpara> + 以ä¸ã®ä¾ã§ã¯ãCCLãã¼ãµã¯<literal>ti</literal>ã + <literal>au</literal>ã<literal>isbn</literal>ã¨ãã3ã¤ã®CCLãã£ã¼ + ã«ãããµãã¼ãããããã«è¨å®ããã¾ããåãã£ã¼ã«ãã¯ãç価㪠+ BIB-1ã¸ãããããã¾ãã ãã®ä¾ã§ã¯ã<literal>$id</literal>ãã¿ã¼ + ã²ããIDã§ãããã¨ãä»®å®ãã¦ãã¾ãã + </simpara> + <programlisting> + $field["ti"] = "1=4"; + $field["au"] = "1=1"; + $field["isbn"] = "1=7"; + yaz_ccl_conf($id,$field); + </programlisting> + </example> </para> </refsect1> </refentry> - + <refentry id="function.yaz-ccl-parse"> <refnamediv> <refname>yaz_ccl_parse</refname> @@ -697,23 +694,20 @@ </funcprototype> </funcsynopsis> <para> - ãã®é¢æ°ã¯ãCCLãã¼ãµãèµ·åãã¾ãã - This function invokes the CCL parser. It converts a given - CCL FIND query to an RPN query which may be passed to the - <function>yaz_search</function> function to perform a search. - To define a set of valid CCL fields call - <function>yaz_ccl_conf</function> prior to this function. - If the supplied <parameter>query</parameter> was successfully - converted to RPN, this function returns true, and the index - <literal>rpn</literal> of the supplied array - <parameter>result</parameter> holds a valid RPN query. - If the query could not be converted (because of invalid syntax, - unknown field, etc.) this function returns false and three - indexes are set in the resulting array to indicate the cause - of failure: <literal>errorcode</literal>CCL error code (integer), - <literal>errorstring</literal>CCL error string, and - <literal>errorpos</literal>approximate position in query of failure - (integer is character position). + ãã®é¢æ°ã¯ãCCLãã¼ãµãèµ·åãã¾ãããã¼ãµã¯ãæå®ããCCL FINDã¯ã¨ + ãªãæ¤ç´¢ãå®è¡ãã<function>yaz_search</function>颿°ã«æå®å¯è½ãª + RPNã¯ã¨ãªã«å¤æãã¾ããæå¹ãªCCLãã£ã¼ã«ãã®çµãå®ç¾©ããã«ã¯ãã + ã®é¢æ°ã®åã«<function>yaz_ccl_conf</function>ãã³ã¼ã«ãã¾ããæå® + ãã<parameter>query</parameter>ã®RPNã¸ã®å¤æãæåããå ´åããã® + 颿°ã¯trueãè¿ããæå®ããé å<parameter>result</parameter>ã®æ·»å + <literal>rpn</literal>ã¯ãæå¹ãªRPNã¯ã¨ãªãä¿æãã¾ãã(æ§æãç¡ + å¹ã§ãã£ãããåå¨ããªããã£ã¼ã«ãã§ããçã®çç±ã«ããã)ã¯ã¨ãªã + 夿ã§ããªãã£ãå ´åããã®é¢æ°ã¯falseãè¿ãã失æã®åå ã示ããã + ã«è¿ãããé åã«æ¬¡ã®ãããª3ã¤ã®æ·»åãè¨å®ããã¾ãã + <literal>errorcode</literal>CCL ã¨ã©ã¼ã³ã¼ã (æ´æ°)ã + <literal>errorstring</literal>CCLã¨ã©ã¼æååã + <literal>errorpos</literal> ã¨ã©ã¼ãçºçããã¯ã¨ãªã®ããããã®ä½ + ç½®(æ´æ°ã¯æåã®ä½ç½®ãæ´æ°ã§è¡¨ãããã®) </para> </refsect1> </refentry> Index: phpdoc/ja/functions/mnogosearch.xml +++ phpdoc/ja/functions/mnogosearch.xml <reference id="ref.mnogo"> <title>mnoGoSearch 颿°</title> <titleabbrev>mnoGoSearch</titleabbrev> <partintro> <simpara> ããã§ç¤ºã颿°ã«ãããããªã¼ã®æ¤ç´¢ã¨ã³ã¸ã³ mnoGoSearch (æ§å㯠UdmSearch)ã¸ã¢ã¯ã»ã¹ãããã¨ãå¯è½ã¨ãªãã¾ãããããã®é¢æ°ãå©ç¨å¯ è½ã¨ããããã«ã¯ããªãã·ã§ã³ <option role="configure">--with-mnogosearch</option> ã«ãã mnogosearchãµ ãã¼ããæå®ãã¦PHPãã³ã³ãã¤ã«ããå¿ è¦ãããã¾ããmnogosearchã®ã ã¹ãæå®ããã«ãã®ãªãã·ã§ã³ã使ç¨ããå ´åãPHPã¯ããã©ã«ãã§ mnogosearchã/usr/local/mnogosearchã«ãããã®ã¨ãã¦æ¤ç´¢ãè¡ãã¾ãã mnogosearchãä»ã®å ´æã«ã¤ã³ã¹ãã¼ã«ãã¦ããå ´åã«ã¯ã <option role="configure">--with-mnogosearch=DIR</option>ã®ããã«ã ã®ãã¹ãæå®ããå¿ è¦ãããã¾ãã </simpara> <note> <para> PHPã«ã¯ãMySQLã¨ã®æ¥ç¶ã©ã¤ãã©ãªãçµã¿è¾¼ã¾ãã¦ãããMySQLã«ã¢ã¯ã» ã¹ãããã¨ãå¯è½ã§ããmnoGoSearchã¯ããã®çµã¿è¾¼ã¿ã©ã¤ãã©ãªã¨äºæ æ§ããªããé常ã®MySQLã©ã¤ãã©ãªã¨ã®çµåãã§ã®ã¿åä½ãã¾ãããã®ã ããmnoGoSearchãMySQLã¨çµã¿åããã¦ä½¿ç¨ããéã«ã¯ãPHPã® configureã«MySQLãã¤ã³ã¹ãã¼ã«ãããã£ã¬ã¯ããªãæå®ããå¿ è¦ã ããã¾ããããã¯ãmnoGoSearchã«é¢ããè¨å®ã§ä½¿ç¨ãããä¾ãã°ã次㮠ããã«ãªãã¾ãã <option role="configure">--with-mnogosearch --with-mysql=/usr</option> </para> </note> <simpara> ãããã®é¢æ°ã使ç¨ããã«ã¯ã3.1.10以éã®ãã¼ã¸ã§ã³ã®mnoGoSearchã ã¤ã³ã¹ãã¼ã«ããã¦ããå¿ è¦ãããã¾ãã </simpara> <simpara> mnoGoSearchã«é¢ããããè©³ç´°ãªæ å ±ã¯ã<ulink url="&url.mnogo;">&url.mnogo;</ulink>ã«ããã¾ãã </simpara> </partintro> <refentry id="function.udm-alloc-agent"> <refnamediv> <refname>udm_alloc_agent</refname> <refpurpose>mnoGoSearch ã»ãã·ã§ã³ã確ä¿ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_alloc_agent</function></funcdef> <paramdef>string <parameter>dbaddr</parameter></paramdef> <paramdef>string <parameter> <optional>dbmode</optional> </parameter> </paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_alloc_agent</function> returns mnogosearch agent identifier on success, <literal>FALSE</literal> on error. This function creates a session with database parameters. </para> <para> <parameter>dbaddr</parameter> - URL-style database description. Options (type, host, database name, port, user and password) to connect to SQL database. Do not matter for built-in text files support. Format: DBAddr DBType:[//[DBUser[:DBPass]@]DBHost[:DBPort]]/DBName/ Currently supported DBType values are: mysql, pgsql, msql, solid, mssql, oracle, ibase. Actually, it does not matter for native libraries support. But ODBC users should specify one of supported values. If your database type is not supported, you may use "unknown" instead. </para> <para> <parameter>dbmode</parameter> - You may select SQL database mode of words storage. When "single" is specified, all words are stored in the same table. If "multi" is selected, words will be located in different tables depending of their lengths. "multi" mode is usually faster but requires more tables in database. If "crc" mode is selected, mnoGoSearch will store 32 bit integer word IDs calculated by CRC32 algorythm instead of words. This mode requres less disk space and it is faster comparing with "single" and "multi" modes. "crc-multi" uses the same storage structure with the "crc" mode, but also stores words in different tables depending on words lengths like "multi" mode. Format: DBMode single/multi/crc/crc-multi </para> <note> <para> <parameter>dbaddr</parameter> and <parameter>dbmode</parameter> must match those used during indexing. </para> </note> <note> <para> In fact this function does not open connection to database and thus does not check entered login and password. Actual connection to database and login/password verification is done by <function>udm_find</function>. </para> </note> </refsect1> </refentry> <refentry id="function.udm-set-agent-param"> <refnamediv> <refname>udm_set_agent_param</refname> <refpurpose> mnoGoSearch ã¨ã¼ã¸ã§ã³ãã®ã»ãã·ã§ã³ãã©ã¡ã¼ã¿ãè¨å®ãã </refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_set_agent_param</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> <paramdef>int <parameter>var</parameter></paramdef> <paramdef>string <parameter>val</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_set_agent_param</function> returns <literal>TRUE</literal> on success, <literal>FALSE</literal> on error. Defines mnoGoSearch session parameters. </para> <simpara> The following parameters and their values are available: </simpara> <itemizedlist> <listitem> <simpara> UDM_PARAM_PAGE_NUM - used to choose search results page number (results are returned by pages beginning from 0, with UDM_PARAM_PAGE_SIZE results per page). </simpara> </listitem> <listitem> <simpara> UDM_PARAM_PAGE_SIZE - number of search results displayed on one page. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_SEARCH_MODE - search mode. The following values available: UDM_MODE_ALL - search for all words; UDM_MODE_ANY - search for any word; UDM_MODE_BOOL - boolean search. See <function>udm_find</function> for details on boolean search. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_CACHE_MODE - turns on or off search result cache mode. When enabled, the search engine will store search results to disk. In case a similar search is performed later, the engine will take results from the cache for faster performance. Available values: UDM_CACHE_ENABLED, UDM_CACHE_DISABLED. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_TRACK_MODE - turns on or off trackquery mode. Since version 3.1.2 mnoGoSearch has a query tracking support. Note that tracking is implemented in SQL version only and not available in built-in database. To use tracking, you have to create tables for tracking support. For MySQL, use create/mysql/track.txt. When doing a search, front-end uses those tables to store query words, a number of found documents and current UNIX timestamp in seconds. Available values: UDM_TRACK_ENABLED, UDM_TRACK_DISABLED. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_CHARSET - defines local charset. Available values: set of charsets supported by mnoGoSearch, e.g. koi8-r, cp1251, ... </simpara> </listitem> <listitem> <simpara> UDM_PARAM_STOPFILE - Defines name and path to stopwords file. (There is a small difference with mnoGoSearch - while in mnoGoSearch if relative path or no path entered, it looks for this file in relation to UDM_CONF_DIR, the module looks for the file in relation to current path, i.e. to the path where the php script is executed.) </simpara> </listitem> <listitem> <simpara> UDM_PARAM_STOPTABLE - Load stop words from the given SQL table. You may use several StopwordTable commands. This command has no effect when compiled without SQL database support. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_WEIGHT_FACTOR - represents weight factors for specific document parts. Currently body, title, keywords, description, url are supported. To activate this feature please use degrees of 2 in *Weight commands of the indexer.conf. Let's imagine that we have these weights: </simpara> <simpara>URLWeight 1</simpara> <simpara>BodyWeight 2</simpara> <simpara>TitleWeight 4</simpara> <simpara>KeywordWeight 8</simpara> <simpara>DescWeight 16</simpara> <simpara> As far as indexer uses bit OR operation for word weights when some word presents several time in the same document, it is possible at search time to detect word appearance in different document parts. Word which appears only in the body will have 00000010 argegate weight (in binary notation). Word used in all document parts will have 00011111 aggregate weight. </simpara> <simpara> This parameter's value is a string of hex digits ABCDE. Each digit is a factor for corresponding bit in word weight. For the given above weights configuration: </simpara> <simpara>E is a factor for weight 1 (URL Weight bit)</simpara> <simpara>D is a factor for weight 2 (BodyWeight bit)</simpara> <simpara>C is a factor for weight 4 (TitleWeight bit)</simpara> <simpara>B is a factor for weight 8 (KeywordWeight bit)</simpara> <simpara>A is a factor for weight 16 (DescWeight bit)</simpara> <simpara> Examples: </simpara> <simpara> UDM_PARAM_WEIGHT_FACTOR=00001 will search through URLs only. </simpara> <simpara> UDM_PARAM_WEIGHT_FACTOR=00100 will search through Titles only. </simpara> <simpara> UDM_PARAM_WEIGHT_FACTOR=11100 will search through Title,Keywords,Desctription but not through URL and Body. </simpara> <simpara> UDM_PARAM_WEIGHT_FACTOR=F9421 will search through: </simpara> <simpara>Description with factor 15 (F hex)</simpara> <simpara>Keywords with factor 9</simpara> <simpara>Title with factor 4</simpara> <simpara>Body with factor 2</simpara> <simpara>URL with factor 1</simpara> <simpara> If UDM_PARAM_WEIGHT_FACTOR variable is ommited, original weight value is taken to sort results. For a given above weight configuration it means that document description has a most big weight 16. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_WORD_MATCH - word match. You may use this parameter to choose word match type. This feature works only in "single" and "multi" modes using SQL based and built-in database. It does not work in cachemode and other modes since they use word CRC and do not support substring search. Available values: </simpara> <simpara>UDM_MATCH_BEGIN - word beginning match;</simpara> <simpara>UDM_MATCH_END - word ending match;</simpara> <simpara>UDM_MATCH_WORD - whole word match;</simpara> <simpara>UDM_MATCH_SUBSTR - word substring match.</simpara> </listitem> </itemizedlist> </refsect1> </refentry> <refentry id="function.udm-add-search-limit"> <refnamediv> <refname>udm_add_search_limit</refname> <refpurpose>種ã ã®æ¤ç´¢ã®å¶ç´ãè¨å®ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_add_search_limit</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> <paramdef>int <parameter>var</parameter></paramdef> <paramdef>string <parameter>val</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_add_search_limit</function> returns <literal>TRUE</literal> on success, <literal>FALSE</literal> on error. Adds search restrictions. </para> <para> <parameter>agent</parameter> - a link to Agent, received after call to <function>udm_alloc_agent</function>. </para> <para> <parameter>var</parameter> - defines parameter, indicating limit. </para> <para> <parameter>val</parameter> - defines value of the current parameter. </para> <para> Possible <parameter>var</parameter> values: </para> <itemizedlist> <listitem> <simpara> UDM_LIMIT_URL - defines document URL limitations to limit search through subsection of database. It supports SQL % and _ LIKE wildcards, where % matches any number of characters, even zero characters, and _ matches exactly one character. E.g. http://my.domain.__/catalog may stand for http://my.domain.ru/catalog and http://my.domain.ua/catalog. </simpara> </listitem> <listitem> <simpara> UDM_LIMIT_TAG - defines site TAG limitations. In indexer-conf you can assign specific TAGs to various sites and parts of a site. Tags in mnoGoSearch 3.1.x are lines, that may contain metasymbols % and _. Metasymbols allow searching among groups of tags. E.g. there are links with tags ABCD and ABCE, and search restriction is by ABC_ - the search will be made among both of the tags. </simpara> </listitem> <listitem> <simpara> UDM_LIMIT_LANG - defines document language limitations. </simpara> </listitem> <listitem> <simpara> UDM_LIMIT_CAT - defines document category limitations. Categories are similar to tag feature, but nested. So you can have one category inside another and so on. You have to use two characters for each level. Use a hex number going from 0-F or a 36 base number going from 0-Z. Therefore a top-level category like 'Auto' would be 01. If it has a subcategory like 'Ford', then it would be 01 (the parent category) and then 'Ford' which we will give 01. Put those together and you get 0101. If 'Auto' had another subcategory named 'VW', then it's id would be 01 because it belongs to the 'Ford' category and then 02 because it's the next category. So it's id would be 0102. If VW had a sub category called 'Engine' then it's id would start at 01 again and it would get the 'VW' id 02 and 'Auto' id of 01, making it 010201. If you want to search for sites under that category then you pass it cat=010201 in the url. </simpara> </listitem> </itemizedlist> </refsect1> </refentry> <refentry id="function.udm-clear-search-limits"> <refnamediv> <refname>udm_clear_search_limits</refname> <refpurpose> mnoGoSearch æ¤ç´¢ã«é¢ããå ¨ã¦ã®å¶ç´ãã¯ãªã¢ãã </refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_clear_search_limits</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_clear_search_limits</function> resets defined search limitations and returns <literal>TRUE</literal>. </para> </refsect1> </refentry> <refentry id="function.udm-find"> <refnamediv> <refname>udm_find</refname> <refpurpose>æ¤ç´¢ãå®è¡ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_find</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> <paramdef>string <parameter>query</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_find</function> returns result link identifier on success, <literal>FALSE</literal> on error. </para> <para> The search itself. The first argument - session, the next one - query itself. To find something just type words you want to find and press SUBMIT button. For example, "mysql odbc". You should not use quotes " in query, they are written here only to divide a query from other text. mnoGoSearch will find all documents that contain word "mysql" and/or word "odbc". Best documents having bigger weights will be displayed first. If you use search mode ALL, search will return documents that contain both (or more) words you entered. In case you use mode ANY, the search will return list of documents that contain any of the words you entered. If you want more advanced results you may use query language. You should select "bool" match mode in the search from. </para> <simpara> mnoGoSearch understands the following boolean operators: </simpara> <simpara> & - logical AND. For example, "mysql & odbc". mnoGoSearch will find any URLs that contain both "mysql" and "odbc". </simpara> <simpara> | - logical OR. For example "mysql|odbc". mnoGoSearch will find any URLs, that contain word "mysql" or word "odbc". </simpara> <simpara> ~ - logical NOT. For example "mysql & ~odbc". mnoGoSearch will find URLs that contain word "mysql" and do not contain word "odbc" at the same time. Note that ~ just excludes given word from results. Query "~odbc" will find nothing! </simpara> <simpara> () - group command to compose more complex queries. For example "(mysql | msql) & ~postgres". Query language is simple and powerful at the same time. Just consider query as usual boolean expression. </simpara> </refsect1> </refentry> <refentry id="function.udm-get-res-param"> <refnamediv> <refname>udm_get_res_param</refname> <refpurpose>mnoGoSearch çµæãã©ã¡ã¼ã¿ãåå¾ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>string <function>udm_get_res_param</function></funcdef> <paramdef>int <parameter>res</parameter></paramdef> <paramdef>int <parameter>param</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_get_res_param</function> returns result parameter value on success, <literal>FALSE</literal> on error. </para> <para> <parameter>res</parameter> - a link to result identifier, received after call to <function>udm_find</function>. </para> <para> <parameter>param</parameter> - parameter identifier, may have the following values: </para> <itemizedlist> <listitem> <simpara> UDM_PARAM_NUM_ROWS - number of received found links on the current page. It is equal to UDM_PARAM_PAGE_SIZE for all search pages, on the last page - the rest of links. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_FOUND - total number of results matching the query. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_WORDINFO - information on the words found. E.g. search for "a good book" will return "a: stopword, good:5637, book: 120" </simpara> </listitem> <listitem> <simpara> UDM_PARAM_SEARCHTIME - search time in seconds. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_FIRST_DOC - the number of the first document displayed on current page. </simpara> </listitem> <listitem> <simpara> UDM_PARAM_LAST_DOC - the number of the last document displayed on current page. </simpara> </listitem> </itemizedlist> </refsect1> </refentry> <refentry id="function.udm-get-res-field"> <refnamediv> <refname>udm_get_res_field</refname> <refpurpose>mnoGoSearch çµæãã£ã¼ã«ããåå¾ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>string <function>udm_get_res_field</function></funcdef> <paramdef>int <parameter>res</parameter></paramdef> <paramdef>int <parameter>row</parameter></paramdef> <paramdef>int <parameter>field</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_get_res_field</function> returns result field value on success, <literal>FALSE</literal> on error. </para> <para> <parameter>res</parameter> - a link to result identifier, received after call to <function>udm_find</function>. </para> <para> <parameter>row</parameter> - the number of the link on the current page. May have values from 0 to <parameter>UDM_PARAM_NUM_ROWS</parameter>. </para> <para> <parameter>field</parameter> - field identifier, may have the following values: </para> <itemizedlist> <listitem> <simpara> UDM_FIELD_URL - document URL field </simpara> </listitem> <listitem> <simpara> UDM_FIELD_CONTENT - document Content-type field (for example, text/html). </simpara> </listitem> <listitem> <simpara> UDM_FIELD_TITLE - document title field. </simpara> </listitem> <listitem> <simpara> UDM_FIELD_KEYWORDS - document keywords field (from META KEYWORDS tag). </simpara> </listitem> <listitem> <simpara> UDM_FIELD_DESC - document description field (from META DESCRIPTION tag). </simpara> </listitem> <listitem> <simpara> UDM_FIELD_TEXT - document body text (the first couple of lines to give an idea of what the document is about). </simpara> </listitem> <listitem> <simpara> UDM_FIELD_SIZE - document size. </simpara> </listitem> <listitem> <simpara> UDM_FIELD_URLID - unique URL ID of the link. </simpara> </listitem> <listitem> <simpara> UDM_FIELD_RATING - page rating (as calculated by mnoGoSearch). </simpara> </listitem> <listitem> <simpara> UDM_FIELD_MODIFIED - last-modified field in unixtime format. </simpara> </listitem> <listitem> <simpara> UDM_FIELD_ORDER - the number of the current document in set of found documents. </simpara> </listitem> <listitem> <simpara> UDM_FIELD_CRC - document CRC. </simpara> </listitem> </itemizedlist> </refsect1> </refentry> <refentry id="function.udm-free-res"> <refnamediv> <refname>udm_free_res</refname> <refpurpose>mnoGoSearch çµæãéæ¾ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_free_res</function></funcdef> <paramdef>int <parameter>res</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_free_res</function> returns <literal>TRUE</literal> on success, <literal>FALSE</literal> on error. </para> <para> <parameter>res</parameter> - a link to result identifier, received after call to <function>udm_find</function>. </para> <para> Freeing up memory allocated for results. </para> </refsect1> </refentry> <refentry id="function.udm-free-agent"> <refnamediv> <refname>udm_free_agent</refname> <refpurpose>mnoGoSearch ã»ãã·ã§ã³ãéæ¾ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_free_agent</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_free_agent</function> returns <literal>TRUE</literal> on success, <literal>FALSE</literal> on error. </para> <para> <parameter>agent</parameter> - link to agent identifier, received after call to <function>udm_alloc_agent</function>. </para> <para> Freeing up memory allocated for agent session. </para> </refsect1> </refentry> <refentry id="function.udm-errno"> <refnamediv> <refname>udm_errno</refname> <refpurpose>mnoGoSearch ã¨ã©ã¼çªå·ãåå¾ãã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>int <function>udm_errno</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_errno</function> returns mnoGoSearch error number, zero if no error. </para> <para> <parameter>agent</parameter> - link to agent identifier, received after call to <function>udm_alloc_agent</function>. </para> <para> Receiving numeric agent error code. </para> </refsect1> </refentry> <refentry id="function.udm-error"> <refnamediv> <refname>udm_error</refname> <refpurpose>mnoGoSearch ã¨ã©ã¼ã¡ãã»ã¼ã¸ãå¾ã</refpurpose> </refnamediv> <refsect1> <title>説æ</title> <funcsynopsis> <funcprototype> <funcdef>string <function>udm_error</function></funcdef> <paramdef>int <parameter>agent</parameter></paramdef> </funcprototype> </funcsynopsis> <para> <function>udm_error</function> ã¯ãmnoGoSearch ã¨ã©ã¼ã¡ãã»ã¼ã¸ã è¿ãã¾ããã¨ã©ã¼ããªãå ´åã«ã¯ãç©ºã®æååãè¿ãã¾ãã </para> <para> <parameter>agent</parameter> ã¯ãã¨ã¼ã¸ã§ã³ãIDã¸ã®ãªã³ã¯ã§ããã <function>udm_alloc_agent</function>ãã³ã¼ã«ããéã«å¾ããããã® ã§ãã </para> <para> ã¨ã¼ã¸ã§ã³ãã¨ã©ã¼ã¡ãã»ã¼ã¸ãå¾ã¾ãã </para> </refsect1> </refentry> </reference> <!-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t sgml-parent-document:nil sgml-default-dtd-file:"../../manual.ced" sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: -->