X-Git-Url: http://jsfdemo.indexdata.com/?a=blobdiff_plain;f=doc%2Fpazpar2_conf.xml;h=d7de16fd944949dcc80fd39d1e0e5ae46e5070c1;hb=fef6f115619637faeec3e3c34e30a31e1419dbaf;hp=bea66c239744b794211e58b8a47c6880d8f6ee63;hpb=2b4eb014c7252177ca1a4400a226182e8db4fb2e;p=pazpar2-moved-to-github.git

diff --git a/doc/pazpar2_conf.xml b/doc/pazpar2_conf.xml
index bea66c2..d7de16f 100644
--- a/doc/pazpar2_conf.xml
+++ b/doc/pazpar2_conf.xml
@@ -262,17 +262,33 @@
 	     Specifies that this element is to be used to
 	     help rank 
 	     records against the user's query (when ranking is
-	     requested). The value is an integer, used as a
+	     requested). 
+	     The valus is of the form 
+	     <literallayout>
+	      M [F N]
+	     </literallayout>
+	     where M is an integer, used as a
 	     multiplier against the basic TF*IDF score. A value of
-	     1 is the base, higher values give additional
-	     weight to 
+	     1 is the base, higher values give additional weight to
 	     elements of this type. The default is '0', which
 	     excludes this element from the rank calculation.
 	    </para>
 	    <para>
+	     F is a CCL field and N is the multipler for terms
+	     that matches those part of the CCL field in search.
+	     The F+N combo allows the system to use a different
+	     multipler for a certain field. For example, a rank value of
+	     "<literal>1 au 3</literal>" gives a multipler of 3 for
+	     all terms part of the au(thor) terms and 1 for everything else.
+	    </para>
+	    <para>
 	     For Pazpar2 1.6.13 and later, the rank may also defined
 	     "per-document", by the normalization stylesheet. 
 	    </para>
+	    <para>
+	     The per field rank was introduced in Pazpar2 1.6.15. Earlier
+	     releases only allowed a rank value M (simple integer).
+	    </para>
 	   </listitem>
 	  </varlistentry>
 	  
@@ -343,6 +359,28 @@
 	  </varlistentry>
 	  
 	  <varlistentry>
+	   <term id="metadata_limitmap">limitmap</term>
+	   <listitem>
+	    <para>
+	     Specifies a default limitmap for this field. This is to avoid mass 
+	     configuring of targets. However it is important to review/do this on a per
+	     target since it is usually target-specific. See limitmap for format. 
+	    </para>
+	   </listitem>
+	  </varlistentry>
+	  
+	  <varlistentry>
+	   <term id="metadata_facetmap">facetmap</term>
+	   <listitem>
+	    <para>
+	     Specifies a default facetmap for this field. This is to avoid mass 
+	     configuring of targets. However it is important to review/do this on a per
+	     target since it is usually target-specific. See facetmap for format. 
+	    </para>
+	   </listitem>
+	  </varlistentry>
+	  
+	  <varlistentry>
 	   <term>setting</term>
 	   <listitem>
 	    <para>
@@ -525,7 +563,71 @@
 	 </para>
 	</listitem>
        </varlistentry>
-       
+
+       <varlistentry>
+	<term>ccldirective</term>
+	<listitem>
+	 <para>
+	  Customizes the CCL parsing (interpretation of query parameter
+	  in search).
+	  The name and value of the CCL directive is gigen by attributes
+	  'name' and 'value' respectively. Refer to possible list of names
+	  in the
+	  <ulink 
+	      url="http://www.indexdata.com/yaz/doc/tools.html#ccl.directives.table">
+	   YAZ manual
+	   </ulink>.
+	 </para>
+	</listitem>
+       </varlistentry>
+
+       <varlistentry>
+	<term>rank</term>
+	<listitem>
+	 <para>
+	  Customizes the ranking (relevance) algorithm.
+	  Attribute 'cluster' is a boolean
+	  that controls whether Pazpar2 should boost ranking for merged
+	  records. Is 'yes' by default. A value of 'no' will make
+	  Pazpar2 average ranking of each record in a cluster.
+	 </para>
+	 <para>
+	  This configuration was added in pazpar2 1.6.18.
+	 </para>
+	</listitem>
+       </varlistentry>
+
+       <varlistentry id="sort-default">
+	<term>sort-default</term>
+	<listitem>
+	 <para>
+	  Specifies the default sort criteria (default 'relevance'),
+	  which previous was hard-coded as default criteria in search. 
+	  This is a fix/work-around to avoid re-searching when using 
+	  target-based sorting. In order for this to work efficient, 
+	  the search must also have the sort critera parameter; otherwise 
+	  pazpar2 will do re-searching on search criteria changes, if
+	  changed between search and show command.
+	 </para>
+	 <para>
+	  This configuration was added in pazpar2 1.6.20.
+	 </para>
+	</listitem>
+       </varlistentry>
+
+<!--       
+       <varlistentry>
+	<term>set</term>
+	<listitem>
+	 <para>
+	  Specifies a variable that will be inherited by all targets defined in settings
+	  <screen>
+	   &lt;set name="test" value="en"..&lt;set>
+	  </screen>
+	 </para>
+	</listitem>
+       </varlistentry>
+-->   
        <varlistentry>
 	<term>settings</term>
 	<listitem>
@@ -587,7 +689,7 @@
              type="year" merge="range" termlist="yes"/>
    <metadata name="author" brief="yes" termlist="yes"
              merge="longest" rank="2"/>
-   <metadata name="subject" merge="unique" termlist="yes" rank="3"/>
+   <metadata name="subject" merge="unique" termlist="yes" rank="3" limitmap="local:"/>
    <metadata name="url" merge="unique"/>
    <icu_chain id="relevance" locale="el">
     <transform rule="[:Control:] Any-Remove"/>