X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Fbook.xml;h=58e9ca6da36de1707880354a304f71bcf3972bb1;hb=4aa368ef32545c581183ea8de5ef92980351b850;hp=9df32a53aee44d90ebdfb8a2f9e67e6c71221fdc;hpb=940409f4617e6e3668a7184c42552ed16b2d9d8f;p=pazpar2-moved-to-github.git
diff --git a/doc/book.xml b/doc/book.xml
index 9df32a5..58e9ca6 100644
--- a/doc/book.xml
+++ b/doc/book.xml
@@ -585,18 +585,17 @@
The intermediate, internal representation of the record looks like
this:
+
- The Shining
+ The Shining
- King, Stephen
+ King, Stephen
- ebook
-
-
-
- ]]>
+ ebook
+
+
+]]>
As you can see, there isn't much to it. There are really only a few
important elements to this file.
@@ -630,12 +629,13 @@
Pazpar2 1.6.37 and later also allows already clustered records to
be ingested. Suppose a database already clusters for us and we would like
to keep that cluster for Pazpar2. In that case we can generate a
- pz:cluster wrapper element that holds individual pz:record elements.
+ cluster wrapper element that holds individual
+ record elements.
Cluster record example:
+ The ShiningKing, Stephen
@@ -646,8 +646,7 @@
King, Stephenaudio
-
-
+
]]>
@@ -859,6 +858,14 @@
tf[i] = tf[i] / cluster_size;
relevance += 100000 * tf[i] / idf[i];
]]>
+
+ For controlling the ranking parameters, refer to the
+ rank element of the
+ service definition.
+ Refer to the rank attribute
+ of the metadata element for how to control ranking for individual
+ metadata fields.
+