A basic record search requires two separate request parameters, Ntk and Ntt. This topic describes them and contains examples of valid record search queries that use Ntk and Ntt .
Ntk=<search_key>. The search key parameter, Ntk, specifies which property or dimension is going be evaluated when searching. You specify a property or dimension as a value for this parameter. (You can also specify a search interface as a value for the Ntk parameter.)
Ntt=<search_term>. The keyword parameter, Ntt, specifies the actual search terms that are submitted.
Record search parameters must accompany a standard navigation request, even if that basic navigation request is empty. This is because a record search actually acts as a custom filter on a basic navigation request.
For example, a request is considered invalid if only the property key (Ntk), and keyword (Ntt) are specified, without specifying a Navigation value (N).
Likewise, only records currently returned by the basic navigation request (N) are considered when performing a record search.
Record search terms and navigation dimension values together form an AND Boolean request.
Rec ID | Dimension value (Wine Type) | Name property | Description property |
---|---|---|---|
1 |
Red (Dim Value 101) |
Antinori Toscana Solaia |
Dark ruby in color, with extremely ripe... |
2 |
Red (Dim Value 101) |
Chateau St. Jean |
Dense, rich, and complex describes this California... |
3 |
White (Dim Value 103) |
Chateau Laville |
Dense and vegetal, with celery, pear, and spice flavors... |
4 |
Other (Dim Value 103) |
Jose Maria da Fonseca |
Big, ripe, and generous, layered with honey... |
<application>?N=0&Ntk=Description&Ntt=Ripereturns records 1 and 4, because the navigation request is empty (N=0).
<application>?N=101&Ntk=Description&Ntt=Ripe
returns only record 1, because the navigation request (N=101) is already filtering the record set to records 1 and 2.
<application>?Ntk=Description&Ntt=Ripe