X-Git-Url: http://git.indexdata.com/?p=idzebra-moved-to-github.git;a=blobdiff_plain;f=doc%2Fquerymodel.xml;h=d7a7f8489ae6cbc385672497dc1fbcea1ecf9aeb;hp=02729663b6e53deeeba3dc08ba7c9bc14023ad84;hb=693a0db94b4b3ac9aee7722572a6b81a86a12e13;hpb=763bf5f4fc8d22feda4784ec7a9db01902902016 diff --git a/doc/querymodel.xml b/doc/querymodel.xml index 0272966..d7a7f84 100644 --- a/doc/querymodel.xml +++ b/doc/querymodel.xml @@ -1,5 +1,4 @@ - Query Model
@@ -143,14 +142,13 @@
-
&acro.rpn; queries and semantics The &acro.pqf; grammar is documented in the &yaz; manual, and shall not be repeated here. This textual &acro.pqf; representation - is not transmistted to &zebra; during search, but it is in the + is not transmitted to &zebra; during search, but it is in the client mapped to the equivalent &acro.z3950; binary query parse tree. @@ -205,7 +203,7 @@ bib-1 Standard &acro.pqf; query language attribute set which defines the semantics of &acro.z3950; searching. In addition, all of the - non-use attributes (types 2-12) define the hard-wired + non-use attributes (types 2-14) define the hard-wired &zebra; internal query processing. default @@ -216,15 +214,6 @@ Extension to the &acro.bib1; attribute set. predefined - @@ -501,7 +490,7 @@ It is possible to search in any silly string index - if it's defined in your - indexation rules and can be parsed by the &acro.pqf; parser. + indexing rules and can be parsed by the &acro.pqf; parser. This is definitely not the recommended use of this facility, as it might confuse your users with some very unexpected results. @@ -528,7 +517,7 @@ string attributes which in appearance resemble XPath queries. There are two problems with this approach: first, the XPath-look-alike has to - be defined at indexation time, no new undefined + be defined at indexing time, no new undefined XPath queries can entered at search time, and second, it might confuse users very much that an XPath-alike index name in fact gets populated from a possible entirely different &acro.xml; element @@ -681,8 +670,8 @@ via ASN.1. Practically no &acro.z3950; clients supports this. Fortunately they don't have to - &zebra; allows retrieval of this information in other formats: - &acro.sutrs;, &acro.xml;, - &acro.grs1; and ASN.1 Explain. + &acro.sutrs;, &acro.xml;, + &acro.grs1; and ASN.1 Explain. @@ -836,7 +825,7 @@
&zebra; general Bib1 Non-Use Attributes (type 2-6) - +
Relation Attributes (type 2) @@ -922,7 +911,7 @@ The relation attributes 1-5 are supported and work exactly as expected. All ordering operations are based on a lexicographical ordering, - expect when the + except when the structure attribute numeric (109) is used. In this case, ordering is numerical. See . @@ -1039,7 +1028,7 @@
- +
Structure Attributes (type 4) @@ -1053,8 +1042,7 @@ The possible values of the structure attribute (type 4) can be defined - using the configuration file - tab/default.idx. + using the configuration file tab/default.idx. The default configuration is summarized in this table. @@ -1152,13 +1140,12 @@ - The structure attribute values Word list (6) is supported, and maps to the boolean AND combination of words supplied. The word list is useful when - google-like bag-of-word queries need to be translated from a GUI + Google-like bag-of-word queries need to be translated from a GUI query language to &acro.pqf;. For example, the following queries are equivalent: @@ -1185,7 +1172,7 @@ Z> find @attr 1=Body-of-text @attr 2=102 @attr 4=105 "bach salieri teleman" - + The structure attribute value Local number (107) @@ -1220,6 +1207,7 @@
+
Truncation Attributes (type = 5) @@ -1407,8 +1395,8 @@ search and scan in index type="p". - The Complete subfield (2) is a reminiscens - from the happy &acro.marc; + The Complete subfield (2) is a reminiscent + from the happy &acro.marc; binary format days. &zebra; does not support it, but maps silently to Complete field (3). @@ -1421,10 +1409,10 @@
-
- +
+
Extended &zebra; &acro.rpn; Features @@ -1531,13 +1519,23 @@ search 2.0.8 - Maximum number of truncated terms (truncmax) 13 search 2.0.10 + + + Specifies whether un-indexed fields should be ignored. + A zero value (default) throws a diagnostic when an un-indexed + field is specified. A non-zero value makes it return 0 hits. + + 14 + search + 2.0.16 + + @@ -1552,7 +1550,7 @@ All ordering operations are based on a lexicographical ordering, - expect when the + except when the structure attribute numeric (109) is used. In this case, ordering is numerical. See . @@ -1645,12 +1643,7 @@ search result. It is a way for a client to name an &acro.apt; part of a query. - + Experimental. Do not use in production code. @@ -1672,14 +1665,14 @@ By setting an estimation limit size of the resultset of the &acro.apt; - leaves, &zebra; stoppes processing the result set when the limit + leaves, &zebra; stops processing the result set when the limit length is reached. Hit counts under this limit are still precise, but hit counts over it are estimated using the statistics gathered from the chopped result set. - Specifying a limit of 0 resuts in exact hit counts. + Specifying a limit of 0 results in exact hit counts. For example, we might be interested in exact hit count for a, but @@ -1758,9 +1751,9 @@ Approximative Limit - 9 + 12 scan - 1.4 + 2.0.20 @@ -1811,9 +1804,9 @@
- &zebra; Extension Approximative Limit (type 11) + &zebra; Extension Approximative Limit (type 12) - The &zebra; Extension Approximative Limit (type 11) is a way to + The &zebra; Extension Approximative Limit (type 12) is a way to enable approximate hit counts for scan hit counts, in the same way as for search hit counts. @@ -2045,7 +2038,7 @@ Numeric use attributes are mapped to the &zebra; internal string index according to the attribute set definition in use. - The default attribute set is &acro.bib1;, and may be + The default attribute set is &acro.bib1;, and may be omitted in the &acro.pqf; query. @@ -2060,7 +2053,7 @@ Z> find @attr 1=BodyOfText serenade Z> find @attr 1=bO-d-Y-of-tE-x-t serenade Z> find @attr 1=1010 serenade - Z> find @attrset &acro.bib1; @attr 1=1010 serenade + Z> find @attrset bib1 @attr 1=1010 serenade Z> find @attrset bib1 @attr 1=1010 serenade Z> find @attrset Bib1 @attr 1=1010 serenade Z> find @attrset b-I-b-1 @attr 1=1010 serenade @@ -2090,7 +2083,7 @@ ignored. The above mentioned name normalization applies. String index names are defined in the used indexing filter configuration files, for example in the - &acro.grs1; + &acro.grs1; *.abs configuration files, or in the alvis filter &acro.xslt; indexing stylesheets. @@ -2105,8 +2098,8 @@ - Finally, &acro.xpath; access points are only - available using the &acro.grs1; filter for indexing. + Finally, &acro.xpath; access points are only + available using the &acro.grs1; filter for indexing. These access point names must start with the character '/', they are not normalized, but passed unaltered to the &zebra; internal @@ -2172,26 +2165,26 @@ numeric (@attr 4=109) ignored - Numeric ('u') + Numeric ('n') Special index for digital numbers key (@attr 4=3) ignored Null bitmap ('0') - Used for non-tokenizated and non-normalized bit sequences + Used for non-tokenized and non-normalized bit sequences year (@attr 4=4) ignored Year ('y') - Non-tokenizated and non-normalized 4 digit numbers + Non-tokenized and non-normalized 4 digit numbers date (@attr 4=5) ignored Date ('d') - Non-tokenizated and non-normalized ISO date strings + Non-tokenized and non-normalized ISO date strings ignored @@ -2501,7 +2494,7 @@ Exhaustive information can be found in the - Section &acro.cql; to &acro.rpn; conversion" + Section &acro.cql; to &acro.rpn; conversion in the &yaz; manual.