Changes

This [[Module Library|XQuery Module]] extends the [httphttps://www.w3.org/TR/xpath-full-text-10 W3C Full Text Recommendation] with some useful functions: The index can be directly accessed, full-text fulltext results can be marked with additional elements, or the relevant parts can be extracted. Moreover, the score value, which is generated by the {{Code|contains text}} expression, can be explicitly requested from items.

All functions and errors in this module are assigned to the {{Code|<code><nowiki>http://basex.org/modules/ft}} </nowiki></code> namespace, which is statically bound to the {{Code|ft}} prefix.<br/>All errors are assigned to the {{Code|http://basex.org/errors}} namespace, which is statically bound to the {{Code|bxerr}} prefix.

{{Mark|Updated with Version 7.3:}} second argument generalized, third parameter added. {|width='100%'

| width='90120' | '''Signatures'''|{{Func|ft:search|$db as item()xs:string, $terms as item()*|text()*}}<br/>{{Func|ft:search|$db as item()xs:string, $terms as item()*, $options as itemmap(*)?|text()*}}

|Returns all text nodes from the full-text index of the [[Database Module#Database Nodes|database node]] {{Code|$db}} that contain the specified {{Code|$terms}}.<br/>The options used for tokenizing the input and building the full-text will also be applied to the search terms. As an example, if the index terms have been stemmed, the search string will be stemmed as well.The {{Code|$options}} argument can be used to overwrite the default control full-text optionsprocessing. It can be specified as* {{Code|element(The following options)}}: {{Code|&lt;options/&gt;}} must be used as root element, and the parameters are specified as child nodes, with supported (the element name representing the key and the text node representing the value:<br /><pre class="brush:xml"><options> <key>value</key> ...</options></pre>* introduction on [[Map Module|map structureFull-Text]]: all parameters can be directly represented as key/value pairs:<br /><code>map { "key" := "value", ... }</code><br/>This variant is more compact, but please note that processing gives you equivalent expressions in the W3C’s specification of maps in XQuery is still work in progress.The following keys are supportedFull-Text notation):* {{Code|mode}}: determines the search mode (also called [http://www.w3.org/TR/xpath-full-text-10/#ftwords AnyAllOption])how tokens are searched. Allowed values are {{Code|any}}, {{Code|any word}}, {{Code|all}}, {{Code|all words}}, and {{Code|phrase}}. {{Code|any}} is the default search mode.* {{Code|fuzzy}}: turns fuzzy querying on or off. Allowed values are an empty string or {{Code|true}}, or and {{Code|false}}. By default, fuzzy querying is turned off.* {{Code|wildcards}}: turns wildcard querying on or off. Allowed values are an empty {{Code|true}} and {{Code|false}}. By default, wildcard querying is turned off.* {{Code|ordered}}: requires that all tokens occur in the order in which they are specified. Allowed values are {{Code|true}} and {{Code|false}}. The default is {{Code|false}}.* {{Code|content}}: specifies that the matched tokens need to occur at the beginning or end of a searched string , or need to cover the entire string. Allowed values are {{Code|start}}, {{Code|end}}, and {{Code|entire}}. By default, the option is turned off.* {{Code|scope}}: defines the scope in which tokens must be located. The option has following sub options:** {{Code|same}}: can be set to {{Code|true}} or {{Code|false}}. It specifies if tokens need to occur in the same or different units.** {{Code|unit}}: can be {{Code|sentence}} or {{Code|paragraph}}. It specifies the unit for finding tokens.* {{Code|window}}: sets up a window in which all tokens must be located. By default, the option is turned off. It has following sub options:** {{Code|size}}: specifies the size of the window in terms of ''units''.** {{Code|unit}}: can be {{Code|sentences}}, {{Code|sentences}} or {{Code|falseparagraphs}}. The default is {{Code|words}}.* {{Code|distance}}: specifies the distance in which tokens must occur. By default, wildcard querying the option is turned off. It has following sub options:** {{Code|min}}: specifies the minimum distance in terms of ''units''. The default is {{Code|0}}.** {{Code|max}}: specifies the maximum distance in terms of ''units''. The default is {{Code|∞}}.** {{Code|unit}}: can be {{Code|words}}, {{Code|sentences}} or {{Code|paragraphs}}. The default is {{Code|words}}.

|{{Error|BXDB0004db:open|Database Module#Errors}} The addressed database does not exist or could not be opened.<br/>{{Error|db:no-index|Database Module#Errors}} the full-text index is not available.<br/>{{Error|BXFT0001options|#Errors}} both the fuzzy and wildcard querying was selectedoption cannot be both specified.

* {{Code|ft:search("DB", "QUERY")}} returns : Return all text nodes of the database {{Code|DB}} that contain the term {{Code|QUERY}}.* Return all text nodes of the database {{Code|DB}} that contain the numbers {{Code|2010}} and {{Code|2020}}:<br/><code>ft:search("DB", ("2010",2011"2020"), map { 'mode':='all' })</code><br/>returns all * Return text nodes of that contain the database terms {{Code|DBA}} that contain the numbers and {{Code|2010B|}} and in a distance of at most 5 words:<syntaxhighlight lang="xquery">ft:search("db", ("A", "B"), map { "mode": "all words", "distance": map {Code|20111 "max": "5", "unit": "words" }}.)</syntaxhighlight>* The last example iterates Iterate over five three databases and returns return all elements containing terms similar to {{Code|Hello World}} in the text nodes:<pre classsyntaxhighlight lang="brush:xquery">

return ft:search($dbname, $terms, map { 'fuzzy': $fuzzy })/..</syntaxhighlight>|} ==ft:contains== {| width='100%'|-| width='120' | '''Signatures'''|{{Func|ft:contains|$input as item()*, $terms as item()*|xs:boolean}}<br/>{{Func|ft:contains|$input as item()*, $terms as item()*, $optionsas map(*)?|xs:boolean}}|-| '''Summary'''|Checks if the specified {{Code|$input}} items contain the specified {{Code|$terms}}.<br/>The function does the same as the [[Full-Text]] expression {{Code|contains text}}, but options can be specified more dynamically. The {{Code|$options}} are the same as for [[#ft:search|ft:search]], and the following ones in addition:* {{Code|case}}: determines how character case is processed.Allowed values are {{Code|insensitive}}, {{Code|sensitive}}, {{Code|upper}} and {{Code|lower}}.By default, search is case insensitive.* {{Code|diacritics}}: determines how diacritical characters are processed. Allowed values are {{Code|insensitive}} and {{Code|sensitive}}. By default, search is diacritical insensitive.* {{Code|stemming}}: determines is tokens are stemmed. Allowed values are {{Code|true}} and {{Code|false}}. By default, stemming is turned off.* {{Code|language}}: determines the language. This option is relevant for stemming tokens. All language codes are supported. The default language is {{Code|en}}.|-| '''Errors'''|{{Error|options|#Errors}} specified options are conflicting.|-| '''Examples'''|* Checks if {{Code|jack}} or {{Code|john}} occurs in the input string {{Code|John Doe}}:<syntaxhighlight lang="xquery">ft:contains("John Doe", ("jack", "john"), map { "mode": "any" })</syntaxhighlight>* Calls the function with stemming turned on and off:<syntaxhighlight lang="xquery">(true(), false()) ! ft:contains("Häuser", "Haus", map { 'stemming': ., 'language':'de' })</presyntaxhighlight>

 {|width='100%'

| width='90120' | '''Signatures'''|{{Func|ft:mark|$nodes as node()*|node()*}}<br />{{Func|ft:mark|$nodes as node()*, $tag name as xs:string|node()*}}

|Puts a marker element around the resulting {{Code|$nodes}} of a full-text index request.<br />The default tag name of the marker element is {{Code|mark}}. An alternative tag name can be chosen via the optional {{Code|$tagname}} argument.<br />Note Please note that :* The full-text expression that computes the token positions must be specified as argument of the <code>ft:mark()</code> function, as all position information is lost in subsequent processing steps. You may need to specify more than one full-text expression if you want to use the XML function in a FLWOR expression, as shown in Example 2.* The supplied node to be transformed must be an internal "database" nodea [[Database Module#Database Node|Database Node]]. The As shown in Example 3, {{Code|update}} or {{Code|transform}} expression can be used to apply the method utilized to convert a main-memory fragment (see example)to the required internal representation.

|* '''Example 1''': The following query returns {{Code|&lt;XML&gt;&lt;mark&gt;hello&lt;/mark&gt; world&lt;/XML&gt;}}, if one text node of the database {{Code|DB}} has the value "hello world":<pre classsyntaxhighlight lang="brush:xquery">

</presyntaxhighlight>'''Example 2''': The following expression loops through the first ten full-text results and marks the results in a second expression:<syntaxhighlight lang="xquery">let $start := 1let $end := 10let $term := 'welcome'for $ft in (db:open('DB')//* [text() contains text { $term }])[position() = $start to $end]return element hit { ft:mark($ft[text() contains text { $term }])}</syntaxhighlight>'''Example 3''': The following expression returns {{Code|<code>&lt;p&gt;xml>hello &lt;b&gt;word&lt;/b&gt;&lt;/pxml&gt;}}</code>:<pre classsyntaxhighlight lang="brush:xquery">copy $p := &lt;p&gt;word&lt;<xml>hello world</p&gt;xml>

return ft:mark($p[text() contains text 'word'], 'b')</presyntaxhighlight>

 {|width='100%'

| width='90120' | '''Signatures'''|{{Func|ft:extract|$nodes as node()*|node()*}}<br />{{Func|ft:extract|$nodes as node()*, $tag name as xs:string|node()*}}<br />{{Func|ft:extract|$nodes as node()*, $tag name as xs:string, $length as xs:integer|node()*}}

|Extracts and returns relevant parts of full-text results. It puts a marker element around the resulting {{Code|$nodes}} of a full-text index request and chops irrelevant sections of the result.<br />The default tag element name of the marker element is {{Code|mark}}. An alternative tag element name can be chosen via the optional {{Code|$tagname}} argument.<br />The default length of the returned text is {{Code|150}} characters. An alternative length can be specified via the optional {{Code|$length}} argument. Note that the effective text length may differ from the specified text due to formatting and readibility issues.<br />For more details on this function, please have a look at [[#ft:mark|ft:mark]].

<pre classsyntaxhighlight lang="brush:xquery">

</presyntaxhighlight>

{|width='100%'

| width='90120' | '''Signatures'''

 {|width='100%'

| width='90120' | '''Signatures'''

{|width='100%'

| width='90120' | '''Signatures'''|{{Func|ft:tokens|$db as item()xs:string|element(value)*}}<br/>{{Func|ft:tokens|$db as item()xs:string, $prefix as xs:string|element(value)*}}

|Returns all full-text tokens stored in the index of the [[Database Module#Database Nodes|database node]] {{Code|$db}}, along with their numbers of occurrences.<br/>If {{Code|$prefix}} is specified, the returned nodes will be refined to the strings starting with that prefix. The prefix will be tokenized according to the full-text used for creating the index.

|{{Error|BXDB0004db:open|Database Module#Errors}} The addressed database does not exist or could not be opened.<br/>{{Error|db:no-index|Database Module#Errors}} the full-text index is not available.|-| '''Examples'''|Returns the number of occurrences for a single, specific index entry:<syntaxhighlight lang="xquery">let $term := ft:tokenize($term)return number(ft:tokens('db', $term)[. = $term]/@count)</syntaxhighlight>

 {|width='100%'|-| width='120' | '''Signatures'''|{{Func|ft:tokenize|$string as xs:string?|xs:string*}}<br/>{{Func|ft:tokenize|$string as xs:string?, $options as map(*)?|xs:string*}}|-| '''Summary'''|Tokenizes the given {{Code|$string}}, using the current default full-text options or the {{Code|$options}} specified as second argument, and returns a sequence with the tokenized string. The following options are available:* {{Code|case}}: determines how character case is processed. Allowed values are {{Code|insensitive}}, {{Code|sensitive}}, {{Code|upper}} and {{Code|lower}}. By default, search is case insensitive.* {{Code|diacritics}}: determines how diacritical characters are processed. Allowed values are {{Code|insensitive}} and {{Code|sensitive}}. By default, search is diacritical insensitive.* {{Code|stemming}}: determines is tokens are stemmed. Allowed values are {{Code|true}} and {{Code|false}}. By default, stemming is turned off.* {{Code|language}}: determines the language. This option is relevant for stemming tokens. All language codes are supported. The default language is {{Code|en}}.The {{Code|$options}} argument can be used to control full-text processing.|-| '''Examples'''|* <code>ft:tokenize("No Doubt")</code> returns the two strings {{Code|no}} and {{Code|doubt}}.* <code>ft:tokenize("École", map { 'diacritics': 'sensitive' })</code> returns the string {{Code|école}}.* <code>declare ft-option using stemming; ft:tokenize("GIFTS")</code> returns a single string {{Code|gift}}.|} ==ft:normalize== {| width='100%'

| width='90120' | '''Signatures'''|{{Func|ft:tokenizenormalize|$input string as xs:string?|xs:string}}<br/>{{Func|ft:normalize|$string as xs:string?, $options as map(*)?|xs:string}}

|Tokenizes Normalizes the given {{Code|$inputstring}} string, using the current default full-text optionsor the {{Code|$options}} specified as second argument. The function expects the same arguments as [[#ft:tokenize|ft:tokenize]].

* {{Code|<code>ft:tokenize("No DoubtHäuser am Meer")}} returns the two strings , map {{Code|no}} and {{Code|doubt'case': 'sensitive' }}.* {{Code|declare ft-option using stemming; ft:tokenize("GIFTS")}} </code> returns a single the string {{Code|giftHauser am Meer}}.

! width="5%110"|Code! width="95%"|Description

|{{Code|BXFT0001options}}

===;Version 7.1===