X-Git-Url: http://jsfdemo.indexdata.com/?a=blobdiff_plain;f=doc%2Fbook.xml;h=f3c82351fa375e4f8b8c35c2f10983f889858102;hb=b6b190610799a920163200fd5920406adcc3f6c0;hp=e71bc694eeef77de366ae069093a468a83ffeac7;hpb=14074ecf20d86518ccedc0c9617a49949ec19779;p=pazpar2-moved-to-github.git diff --git a/doc/book.xml b/doc/book.xml index e71bc69..f3c8235 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. @@ -625,6 +624,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 + cluster wrapper element that holds individual + record elements. + + + Cluster record example: + + + The Shining + King, Stephen + ebook + + + The Shining + King, Stephen + audio + + + ]]> +
@@ -651,7 +675,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.