Changes

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

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

=Database Functions=

{{Mark|Updated with Version 7.2.2:}} second argument generalized, third parameter added. {|width='100%'|-| valign='"top' "| width='90120' | '''SignaturesSignature'''|<code><bpre>ft:search</b>( $db as item(), $terms as item()*) as text()*</code><br/><code><b>ftxs:search</b>($db as item()string, $terms as item()*, $options as itemmap(*)? := map { }) as text()*</codepre>|-valign="top"

|Returns all text nodes from the full-text index of the [[Database Module#Database Nodesdatabase {{Code|database node]] <code>$db</code> }} that contain the specified {{MonoCode|$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 {{MonoCode|$options}} argument can be used to overwrite the default control full-text optionsprocessing. It can be specified as* {{Mono|element(options)}}: <code>&lt;The following options/&gt;</code> 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):* {{MonoCode|mode}}: determines determine the search mode (also called [http://www.w3.org/TR/xpath-full-text-10/#ftwords AnyAllOption])how tokens are searched. Allowed values are {{MonoCode|any}}, {{MonoCode|any word}}, {{MonoCode|all}}, {{MonoCode|all words}}, and {{MonoCode|phrase}}. {{MonoCode|any}} is the default search mode.* {{MonoCode|wildcards}}: turn wildcard querying on or off. Allowed values are {{Code|true}} and {{Code|false}}. By default, wildcard querying is turned off.* {{Code|fuzzy}}: turns turn fuzzy querying on or off. Allowed values are an empty string or {{MonoCode|true}}, or and {{MonoCode|false}}. By default, fuzzy querying is turned off.* {{MonoCode|wildcardserrors}}: turns wildcard control the maximum number of tolerated errors for fuzzy querying on or off. By default, {{Code|0}} is assigned (see [[Full-Text#Fuzzy_Querying|Fuzzy Querying]] for more details).* {{Code|ordered}}: indicate if all tokens must occur in the order in which they are specified. Allowed values are an empty {{Code|true}} and {{Code|false}}. The default is {{Code|false}}.* {{Code|content}}: specify 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.* {{MonoCode|scope}}: define 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}}: set up a window in which all tokens must be located. By default, the option is turned off. It has following sub options:** {{Code|size}}: specify the size of the window in terms of ''units''.** {{Code|unit}}: can be {{Code|sentences}}, {{Code|sentences}} or {{MonoCode|paragraphs}}. The default is {{Code|words}}.* {{Code|falsedistance}}: specify the distance in which tokens must occur. By default, wildcard querying the option is turned off. It has following sub options:** {{Code|min}}: specify the minimum distance in terms of ''units''. The default is {{Code|0}}.** {{Code|max}}: specify 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}}.|-valign="top"

|'''[[{{Error|db:get|Database Module#Errors}} The addressed database does not exist or could not be opened.<br/>{{Error|db:no-index|BXDB0004]]''' is raised if Database Module#Errors}} the full-text index is not available.<br/>'''[[XQuery Errors{{Error|options|#BaseX Errors|BASX0022]]''' is raised if both }} the fuzzy and wildcard querying has been selectedoption cannot be both specified.|-valign="top"

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

return ft:search($dbname, $terms, map { 'fuzzy': $optionsfuzzy })/..

==ft:marktokens== {|width='100%'|-| valign='"top' "| width='90120' | '''SignaturesSignature'''|<code><bpre>ft:mark</b>tokens( $nodes db as node()*) as node()*</code><br /><code><b>ftxs:mark</b>($nodes as node()*string, $tag prefix as xs:string := ()) as nodeelement(value)*</codepre>|-valign="top"

|Puts a marker element around the resulting <code>$nodes</code> of a Returns all full-text tokens stored in the index request.<br />The default tag name of the marker element is <code>mark</code>. An alternative tag name can be chosen via the optional <code>database {{Code|$tag</code> argumentdb}}, along with their numbers of occurrences.<br />Note that If {{Code|$prefix}} is specified, the XML node returned nodes will be refined to the strings starting with that prefix. The prefix will be transformed must be an internal tokenized according to the full-text used for creating the index.|- valign="top"| '''Errors'''|{{Error|db:get|Database Module#Errors}} The addressed database" nodedoes not exist or could not be opened. The <code>transform<br/code> expression can be used to apply {{Error|db:no-index|Database Module#Errors}} the method to a mainfull-memory fragment (see example)text index is not available.|-valign="top"

|* The following query returns <code>&lt;XML&gt;&lt;mark&gt;hello&lt;/mark&gt; world&lt;/XML&gt;</code>Returns the number of occurrences for a single, if one text node of the database <code>DB</code> has the value "hello world"specific index entry:<pre classlang="brush:'xquery"'>let $term := ft:marktokenize($term)return number(dbft:opentokens('DBdb', $term)//*[text() contains text 'hello'. = $term]/@count)

=General Functions= ==ft:extractcontains== {|width='100%'|-| valign='"top' "| width='90120' | '''SignaturesSignature'''|<code><bpre>ft:extract</b>contains( $nodes input as nodeitem()*) as node()*</code><br /><code><b>ft:extract</b>(, $nodes terms as nodeitem()*, $tag as xs:string) options as nodemap(*)*</code><br /><code><b>ft? :extract</b>($nodes as node(= map { })*, $tag as xs:string, $length as xs:integer) as node()*boolean</codepre>|-valign="top"

|Extracts and returns relevant parts of full-text results. It puts a marker element around Checks if the resulting <code>specified {{Code|$nodes</code> of a full-text index request and chops irrelevant sections of input}} items contain the resultspecified {{Code|$terms}}.<br />The default tag name of function does the same as the marker element is <code>mark</code>. An alternative tag name [[Full-Text]] expression {{Code|contains text}}, but options can be chosen via specified more dynamically. The {{Code|$options}} are the same as for {{Function||ft:search}}, and the optional <code>$tag</code> argumentfollowing ones exist:* {{Code|case}}: determines how character case is processed. Allowed values are {{Code|insensitive}}, {{Code|sensitive}}, {{Code|upper}} and {{Code|lower}}.<br />The By default length of the returned text , search is <code>150</code> case-insensitive.* {{Code|diacritics}}: determines how diacritical charactersare processed. Allowed values are {{Code|insensitive}} and {{Code|sensitive}}. By default, search is diacritical insensitive. An alternative length can be specified via * {{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 optional <code>$length</code> argumentlanguage. This option is relevant for stemming tokens. All language codes are supported. The default language is {{Code|en}}. Note that the effective text length may differ from the |- valign="top"| '''Errors'''|{{Error|options|#Errors}} specified text due to formatting and readibility issuesoptions are conflicting.|-valign="top"

* The following query may return <code>&lt;XML&gt;...&lt;b&gt;hello&lt;/b&gt;...&lt;XML&gt;</code> Checks if a text node of {{Code|jack}} or {{Code|john}} occurs in the database input string {{Code|John Doe}}:<codepre lang='xquery'>DBft:contains("John Doe", ("jack", "john"), map { "mode": "any" })</codepre> contains * Calls the string "hello world"function with stemming turned on and off:<pre classlang="brush:'xquery"'>ft:extract(db:opentrue('DB')//*[text, false() ) ! ft:contains text ("Häuser", "Haus", map { 'hellostemming']: ., 'blanguage', 1:'de' })

 {|width='100%'|-| valign='"top' "| width='90120' | '''SignaturesSignature'''|<code><bpre>ft:count</b>( $nodes as node()*) as xs:integer</codepre>|-valign="top"

|-valign="top"

* <code>{{Code|ft:count(//*[text() contains text 'QUERY'])</code> }} returns the <code>{{Code|xs:integer</code> }} value <code>{{Code|2</code> }} if a document contains two occurrences of the string "QUERY".

 {|width='100%'|-| valign='"top' "| width='90120' | '''SignaturesSignature'''|<codepre>ft:score( $item as item()*) as xs:double*<b/pre>|- valign="top"| '''Summary'''|Returns the score values (0.0 - 1.0) that have been attached to the specified items. {{Code|0}} is returned a value if no score was attached.|- valign="top"| '''Examples'''|* {{Code|ft:score('a' contains text 'a')}} returns the {{Code|xs:double}} value {{Code|1}}.|} ==ft:tokenize== {| width='100%'|- valign="top"| width='120' | '''Signature'''|</bpre>ft:tokenize( $item string as xs:string?, $options as itemmap(*)*? := map { }) as xs:doublestring*</codepre>|-valign="top"

|Returns Tokenizes the score 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 (0are {{Code|true}} and {{Code|false}}.0 - 1By default, stemming is turned off.0) that have been attached to * {{Code|language}}: determines the specified itemslanguage. This option is relevant for stemming tokens. All language codes are supported. <code>0</code> The default language is returned a value if no score was attached{{Code|en}}.The {{Code|$options}} argument can be used to control full-text processing.|-valign="top"

* <code>ft:scoretokenize('a' contains text 'a'"No Doubt")</code> returns the two strings {{Code|no}} and {{Code|doubt}}.* <code>xsft:tokenize("École", map { 'diacritics':double'sensitive' })</code> value returns the string {{Code|école}}.* <code>1declare ft-option using stemming; ft:tokenize("GIFTS")</code>returns a single string {{Code|gift}}.

==ft:tokensnormalize== {|width='100%'|-| valign='"top' "| width='90120' | '''SignaturesSignature'''|<pre>ft:normalize( $string as xs:string?, $options as map(*)? := map {}) as xs:string</pre>|- valign="top"| '''Summary'''|Normalizes the given {{Code|$string}}, using the current default full-text options or the {Mono{Code|$options}} specified as second argument. The function accepts the same arguments as {{Function||ft:tokenize}}; special characters and separators will be preserved.|- valign="top"| '''Examples'''|* <bcode>ft:tokensnormalize("Häuser am Meer", map { 'case': 'sensitive' })</bcode> returns the string {{Code|Hauser am Meer}}.|} ==ft:thesaurus== {| width='100%'|- valign="top"| width='120' | '''Signature'''|<pre>ft:thesaurus( $db node as itemnode()) , $term as xs:string, $options as elementmap(value*)? := map { })as xs:string*}}<br/pre>|- valign="top"| '''Summary'''|Looks up a {{Code|$term}} in a [[Full-Text#Thesaurus|Thesaurus Structure]] supplied by {{Code|$node}}. The following {{Code|$options}} exist:* {{Code|relationship}}: determines the relationship between terms* {{Code|levels}}: determines the maximum number of levels to traverse|- valign="top"| '''Examples'''| Returns {{Code|happy}} and {{MonoCode|lucky}}:<bpre lang='xquery'>ft:tokensthesaurus( <thesaurus> <entry> <term>happy</term> <synonym> <term>lucky</term> <relationship>RT</relationship> </synonym> </entry> </bthesaurus>, 'happy')</pre>|} =Highlighting Functions= ==ft:mark== {| width='100%'|- valign="top"| width='120' | '''Signature'''|<pre>ft:mark( $db nodes as itemnode()*, $prefix name as xs:string := ()) as elementnode(value)*}}</pre>|-valign="top"

|Returns all Puts a marker element around the resulting {{Code|$nodes}} of a full-text request.<br/>The default name of the marker element is {{Code|mark}}. An alternative name can be chosen via the optional {{Code|$name}} argument.<br/>Please note that:* The full-text tokens stored in expression that computes the index 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 function in a FLWOR expression, as shown in Example 2.* The supplied node must be a [[Database Module#Database NodesNode|database nodeDatabase Node]] <code>$db</code>. As shown in Example 3, along with their numbers of occurrences.<br/>If {{MonoCode|update}} or {{Code|$prefixtransform}} is specified, the returned nodes will can be refined utilized to the strings starting with that prefix. The prefix will be tokenized according convert a fragment to the full-text used for creating the indexrequired internal representation.|-valign="top"| '''ErrorsExamples'''|'''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 lang='xquery'>ft:mark(db:get('DB')//*[[Database Module#Errors|BXDB0004]text() contains text 'hello'])</pre>'''Example 2''' is raised if : The following expression loops through the first ten full-text index is not availableresults and marks the results in a second expression:<pre lang='xquery'>let $start := 1let $end := 10let $term := 'welcome'let $test := function($node) { $node/text() contains text { $term } }for $ft in (db:get('DB')//*[$test(.)])[position() = $start to $end]return ft:mark($ft[$test(.)])</pre>'''Example 3''': The following expression returns <code>&lt;xml>hello &lt;b&gt;word&lt;/b&gt;&lt;/xml&gt;</code>:<pre lang='xquery'>copy $p := <xml>hello world</xml>modify ()return ft:mark($p[text() contains text 'word'], 'b')</pre>

==ft:tokenizeextract== {|width='100%'|-| valign='"top' "| width='90120' | '''SignaturesSignature'''|{{Mono|<bpre>ft:tokenize</b>extract( $input nodes as node()*, $name as xs:string := () , $length as xs:stringinteger := ()) as node()*}}</pre>|-valign="top"

|Tokenizes Extracts and returns relevant parts of full-text results. It puts a marker element around the given resulting {{MonoCode|$inputnodes}} string, using of a full-text index request and chops irrelevant sections of the result.<br/>The default element name of the marker element is {{Code|mark}}. An alternative element name can be chosen via the current optional {{Code|$name}} argument.<br/>The default full-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 optionsdue to formatting and readibility issues.<br/>For more details on this function, please have a look at {{Function||ft:mark}}.|-valign="top"

* <code>ft:tokenize("No Doubt")</code> returns the two strings The following query may return {{MonoCode|no&lt;XML&gt;...&lt;b&gt;hello&lt;/b&gt;...&lt;XML&gt;}} and if a text node of the database {{MonoCode|doubtDB}}.contains the string "hello world":* <codepre lang='xquery'>declare ft-option using stemming; ft:tokenizeextract(db:get('DB')//*[text("GIFTS")contains text 'hello'], 'b', 1)</codepre> returns a single string |} =Errors= {| class="wikitable" width="100%"! width="110"|Code|Description|- valign="top"|{{MonoCode|giftoptions}}|Both wildcards and fuzzy search have been specified as search options.

===; Version 79.2===6* Added: {{Function||ft:thesaurus}}* Updated: {{Function||ft:search}}, {{Function||ft:contains}}: new {{Code|errors}} option. ; Version 9.1* Updated: {{Function||ft:tokenize}} and {{Function||ft:normalize}} can be called with empty sequence. ;Version 9.0* Updated: error codes updated; errors now use the module namespace ;Version 8.0* Added: {{Function||ft:contains}}, {{Function||ft:normalize}}* Updated: Options added to {{Function||ft:tokenize}}

;Version 7.8* UpdatedAdded: [[#{{Function||ft:searchcontains}}* Updated: Options added to {{Function||ft:search]] (second argument generalized, third parameter added)}}

===;Version 7.1===7* Updated: the functions no longer accept [[Database Module#Database Nodes|Database Nodes]] as reference. Instead, the name of a database must now be specified.

;Version 7.2* AddedUpdated: [[#ft:tokens{{Function||ft:tokens]]search}} (second argument generalized, [[#ft:tokenize|ft:tokenize]]third parameter added)

[[Category;Version 7.1* Added:XQuery]]{{Function||ft:tokens}}, {{Function||ft:tokenize}}