|
a/src/doc/user/usermanual.xml |
|
b/src/doc/user/usermanual.xml |
|
... |
|
... |
| 3792 |
<literal>rclcat</literal>) is the <emphasis>only</emphasis>
|
3792 |
<literal>rclcat</literal>) is the <emphasis>only</emphasis>
|
| 3793 |
field with an <literal>OR</literal> default. You do need to use
|
3793 |
field with an <literal>OR</literal> default. You do need to use
|
| 3794 |
<literal>OR</literal> with <literal>ext</literal> terms for
|
3794 |
<literal>OR</literal> with <literal>ext</literal> terms for
|
| 3795 |
example.</para> </note>
|
3795 |
example.</para> </note>
|
| 3796 |
|
3796 |
|
|
|
3797 |
<sect2 id="RCL.SEARCH.LANG.RANGES">
|
|
|
3798 |
<title>Range clauses</title>
|
|
|
3799 |
|
|
|
3800 |
<para>&RCL; 1.24 and later support range clauses on fields which
|
|
|
3801 |
have been configured to support it. No default field uses them
|
|
|
3802 |
currently, so this paragraph is only interesting if you modified
|
|
|
3803 |
the fields configuration and possibly use a custom input
|
|
|
3804 |
handler.</para>
|
|
|
3805 |
|
|
|
3806 |
<para>A range clause looks like one of the following:</para>
|
|
|
3807 |
<programlisting><replaceable>myfield</replaceable>:<replaceable>small</replaceable>..<replaceable>big</replaceable>
|
|
|
3808 |
<replaceable>myfield</replaceable>:<replaceable>small</replaceable>..
|
|
|
3809 |
<replaceable>myfield</replaceable>:..<replaceable>big</replaceable>
|
|
|
3810 |
</programlisting>
|
|
|
3811 |
|
|
|
3812 |
<para>The nature of the clause is indicated by the two dots
|
|
|
3813 |
<literal>..</literal>, and the effect is to filter the results for
|
|
|
3814 |
which the <replaceable>myfield</replaceable> value is in the
|
|
|
3815 |
possibly open-ended interval.</para>
|
|
|
3816 |
|
|
|
3817 |
<para>See the section about the <link
|
|
|
3818 |
linkend="RCL.INSTALL.CONFIG.FIELDS">
|
|
|
3819 |
<filename>fields</filename> configuration file</link> for the
|
|
|
3820 |
details of configuring a field for range searches.</para>
|
|
|
3821 |
|
|
|
3822 |
|
|
|
3823 |
</sect2>
|
|
|
3824 |
|
| 3797 |
<sect2 id="RCL.SEARCH.LANG.MODIFIERS">
|
3825 |
<sect2 id="RCL.SEARCH.LANG.MODIFIERS">
|
| 3798 |
<title>Modifiers</title>
|
3826 |
<title>Modifiers</title>
|
| 3799 |
|
3827 |
|
| 3800 |
<para>Some characters are recognized as search modifiers when found
|
3828 |
<para>Some characters are recognized as search modifiers when found
|
| 3801 |
immediately after the closing double quote of a phrase, as in
|
3829 |
immediately after the closing double quote of a phrase, as in
|
|
... |
|
... |
| 4636 |
|
4664 |
|
| 4637 |
<para>A field can be either or both indexed and stored. This and
|
4665 |
<para>A field can be either or both indexed and stored. This and
|
| 4638 |
other aspects of fields handling is defined inside the
|
4666 |
other aspects of fields handling is defined inside the
|
| 4639 |
<filename>fields</filename> configuration file.</para>
|
4667 |
<filename>fields</filename> configuration file.</para>
|
| 4640 |
|
4668 |
|
|
|
4669 |
<para>Some fields may also designated as supporting range queries,
|
|
|
4670 |
meaning that the results may be selected for an interval of its
|
|
|
4671 |
values. See the <link linkend="RCL.INSTALL.CONFIG.FIELDS">
|
|
|
4672 |
configuration section</link> for more details.</para>
|
|
|
4673 |
|
| 4641 |
<para>The sequence of events for field processing is as follows:
|
4674 |
<para>The sequence of events for field processing is as follows:
|
| 4642 |
<itemizedlist>
|
4675 |
<itemizedlist>
|
| 4643 |
<listitem><para>During indexing,
|
4676 |
<listitem><para>During indexing,
|
| 4644 |
<command>recollindex</command> scans all <literal>meta</literal>
|
4677 |
<command>recollindex</command> scans all <literal>meta</literal>
|
| 4645 |
fields in HTML documents (most document types are transformed
|
4678 |
fields in HTML documents (most document types are transformed
|
|
... |
|
... |
| 6210 |
installation. In a nutshell: extension prefixes should be all
|
6243 |
installation. In a nutshell: extension prefixes should be all
|
| 6211 |
caps, begin with XY, and short. E.g. XYMFLD.</para>
|
6244 |
caps, begin with XY, and short. E.g. XYMFLD.</para>
|
| 6212 |
</listitem>
|
6245 |
</listitem>
|
| 6213 |
</varlistentry>
|
6246 |
</varlistentry>
|
| 6214 |
<varlistentry>
|
6247 |
<varlistentry>
|
|
|
6248 |
<term>[calues]</term>
|
|
|
6249 |
<listitem><para>Fields listed in this section will be stored as
|
|
|
6250 |
&XAP; <literal>values</literal> inside the index. This makes
|
|
|
6251 |
them available for range queries, allowing to filter results
|
|
|
6252 |
according to the field value. This feature currently supports
|
|
|
6253 |
string and integer data. See the comments in the file for more
|
|
|
6254 |
detail</para>
|
|
|
6255 |
</listitem>
|
|
|
6256 |
</varlistentry>
|
|
|
6257 |
<varlistentry>
|
| 6215 |
<term>[stored]</term>
|
6258 |
<term>[stored]</term>
|
| 6216 |
<listitem><para>A field becomes stored (displayable inside
|
6259 |
<listitem><para>A field becomes stored (displayable inside
|
| 6217 |
results) by having its name listed in this section (typically
|
6260 |
results) by having its name listed in this section (typically
|
| 6218 |
with an empty value).</para>
|
6261 |
with an empty value).</para>
|
| 6219 |
</listitem>
|
6262 |
</listitem>
|