+--- 2.0.20 2007/12/19
+
+Added experimental support for faceted results. This is implemented
+as a special retrieval on a result set and is triggered using element
+set name zebra::facet::f1:t1,f2,t2,.. which will return terms and
+hit counts for field f1, type t1, field f2, type t2, .. The returned
+data is packed as XML or SUTRS depending on record syntax.
+
+Added support for Unicode-based indexing using ICU. This allows
+locale specific scanning, sorting. The implementation is based on
+the ICU utility part of YAZ 3.0.16 and later. See the manual as well
+as the examples/marcxml for an example of the use of ICU.
+
--- 2.0.18 2007/09/19
Fixed bug with scan and staticrank enabled. Bug introduced in 2.0.16.
<chapter id="architecture">
- <!-- $Id: architecture.xml,v 1.25 2007-09-18 19:21:32 adam Exp $ -->
+ <!-- $Id: architecture.xml,v 1.26 2007-12-19 13:35:39 adam Exp $ -->
<title>Overview of &zebra; Architecture</title>
<section id="architecture-representation">
<literal>zebra::snippet</literal>
</entry>
<entry>
- Get snippet for record. This includes a phrase from the original
+ Get snippet for record for one or more indexes (f1,f2,..).
+ This includes a phrase from the original
record at the point where a match occurs (for a query). By default
give terms before - and after are included in the snippet. The
matching terms are enclosed within element
<literal><s></literal>. The snippet facility requires
Zebra 2.0.16 or later.
</entry>
+ <entry>&acro.xml; and &acro.sutrs;</entry>
+ </row>
+ <row>
+ <entry>
+ <literal>zebra::facet::</literal><replaceable>f1</replaceable>:<replaceable>t1</replaceable>,<replaceable>f2</replaceable>:<replaceable>t2</replaceable>,..
+ </entry>
+ <entry>
+ Get facet of a result set. The facet result is returned
+ as if it was a normal record, while in reality is a
+ recap of most "important" terms in a result set for the fields
+ given.
+ The facet facility first appeared in Zebra 2.0.20.
+ </entry>
<entry>&acro.xml;</entry>
</row>
</tbody>
<chapter id="fields-and-charsets">
- <!-- $Id: field-structure.xml,v 1.13 2007-12-19 09:30:29 adam Exp $ -->
+ <!-- $Id: field-structure.xml,v 1.14 2007-12-19 13:35:39 adam Exp $ -->
<title>Field Structure and Character Sets
</title>
</para>
<para>
- Zebra 1.3 and Zebra 2.0 series require that the field type is
- a single character, e.g. <literal>w</literal> (for word), and
- <literal>p</literal> for phrase. Zebra 2.1 allows field types to
- be any string. This allows for greater flexibility - in particular
+ Zebra 1.3 and Zebra versions 2.0.18 and earlier required that the field
+ type is a single character, e.g. <literal>w</literal> (for word), and
+ <literal>p</literal> for phrase. Zebra 2.0.20 and later allow field types
+ to be any string. This allows for greater flexibility - in particular
per-locale (language) fields can be defined.
</para>
<chapter id="introduction">
- <!-- $Id: introduction.xml,v 1.50 2007-05-24 13:44:09 adam Exp $ -->
+ <!-- $Id: introduction.xml,v 1.51 2007-12-19 13:35:39 adam Exp $ -->
<title>Introduction</title>
<section id="overview">
</row>
<row>
<entry>Facetted browsing</entry>
- <entry>partial</entry>
- <entry>&zebra; supports <literal>scan inside a hit
- set</literal> from a previous search, thus reducing the listed
- terms to the
- subset of terms found in the documents/records of the hit
- set.</entry>
+ <entry>available</entry>
+ <entry>Zebra 2.1 and allows retrieval of facets for
+ a result set.
+ </entry>
<entry><xref linkend="querymodel-zebra-attr-scan"/></entry>
</row>
<row>