X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;ds=sidebyside;f=doc%2Fbook.xml;h=9df32a53aee44d90ebdfb8a2f9e67e6c71221fdc;hb=940409f4617e6e3668a7184c42552ed16b2d9d8f;hp=e71bc694eeef77de366ae069093a468a83ffeac7;hpb=52aadcb28792d5d0e199520b2ca40ac0d910925f;p=pazpar2-moved-to-github.git
diff --git a/doc/book.xml b/doc/book.xml
index e71bc69..9df32a5 100644
--- a/doc/book.xml
+++ b/doc/book.xml
@@ -625,6 +625,31 @@
in the retrieval record ultimately drives merging, sorting, ranking,
the extraction of browse facets, and display, all configurable.
+
+
+ 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 record example:
+
+
+ The Shining
+ King, Stephen
+ ebook
+
+
+ The Shining
+ King, Stephen
+ audio
+
+
+
+ ]]>
+
@@ -651,7 +676,7 @@
search. You start a new search using the 'search' command. Once the
search has been started, you can follow its progress using the
'stat', 'bytarget', 'termlist', or 'show' commands. Detailed records
- can be fetched using the 'record' command.
+ can be fetched using the 'record' command.