- </screen>
- where the indexing type is defined after the
- literal <literal>':'</literal> character.
- Any value from the standard configuration
- file <filename>default.idx</filename> will do.
- Finally, any
- <literal>text()</literal> node content recursively contained
- inside the <literal><z:index></literal> element, or any
- element following a <literal>index</literal> processing instruction,
- will be filtered through the
- appropriate char map for character normalization, and will be
- inserted in the named indexes.
- </para>
- <para>
- Finally, this example configuration can be queried using &acro.pqf;
- queries, either transported by &acro.z3950;, (here using a yaz-client)
- <screen>
- <![CDATA[
- Z> open localhost:9999
- Z> elem dc
- Z> form xml
- Z>
- Z> find @attr 1=control @attr 4=3 11224466
- Z> scan @attr 1=control @attr 4=3 ""
- Z>
- Z> find @attr 1=title program
- Z> scan @attr 1=title ""
- Z>
- Z> find @attr 1=title @attr 4=2 "How to program a computer"
- Z> scan @attr 1=title @attr 4=2 ""
- ]]>
- </screen>
- or the proprietary
- extensions <literal>x-pquery</literal> and
- <literal>x-pScanClause</literal> to
- &acro.sru;, and &acro.srw;
- <screen>
- <![CDATA[
- http://localhost:9999/?version=1.1&operation=searchRetrieve&x-pquery=@attr 1=title program
- http://localhost:9999/?version=1.1&operation=scan&x-pScanClause=@attr 1=title ""
- ]]>
- </screen>
- See <xref linkend="zebrasrv-sru"/> for more information on &acro.sru;/&acro.srw;
- configuration, and <xref linkend="gfs-config"/> or the &yaz;
- <ulink url="&url.yaz.cql;">&acro.cql; section</ulink>
- for the details or the &yaz; frontend server.
- </para>
- <para>
- Notice that there are no <filename>*.abs</filename>,
- <filename>*.est</filename>, <filename>*.map</filename>, or other &acro.grs1;
- filter configuration files involves in this process, and that the
- literal index names are used during search and retrieval.
- </para>
- <para>
- In case that we want to support the usual
- <literal>bib-1</literal> &acro.z3950; numeric access points, it is a
- good idea to choose string index names defined in the default
- configuration file <filename>tab/bib1.att</filename>, see
- <xref linkend="attset-files"/>
- </para>
-
- </section>
+ </screen>
+ where the indexing type is defined after the
+ literal <literal>':'</literal> character.
+ Any value from the standard configuration
+ file <filename>default.idx</filename> will do.
+ Finally, any
+ <literal>text()</literal> node content recursively contained
+ inside the <literal><z:index></literal> element, or any
+ element following a <literal>index</literal> processing instruction,
+ will be filtered through the
+ appropriate char map for character normalization, and will be
+ inserted in the named indexes.
+ </para>
+ <para>
+ Finally, this example configuration can be queried using &acro.pqf;
+ queries, either transported by &acro.z3950;, (here using a yaz-client)
+ <screen>
+ <![CDATA[
+ Z> open localhost:9999
+ Z> elem dc
+ Z> form xml
+ Z>
+ Z> find @attr 1=control @attr 4=3 11224466
+ Z> scan @attr 1=control @attr 4=3 ""
+ Z>
+ Z> find @attr 1=title program
+ Z> scan @attr 1=title ""
+ Z>
+ Z> find @attr 1=title @attr 4=2 "How to program a computer"
+ Z> scan @attr 1=title @attr 4=2 ""
+ ]]>
+ </screen>
+ or the proprietary
+ extensions <literal>x-pquery</literal> and
+ <literal>x-pScanClause</literal> to
+ &acro.sru;, and &acro.srw;
+ <screen>
+ <![CDATA[
+ http://localhost:9999/?version=1.1&operation=searchRetrieve&x-pquery=@attr 1=title program
+ http://localhost:9999/?version=1.1&operation=scan&x-pScanClause=@attr 1=title ""
+ ]]>
+ </screen>
+ See <xref linkend="zebrasrv-sru"/> for more information on &acro.sru;/&acro.srw;
+ configuration, and <xref linkend="gfs-config"/> or the &yaz;
+ <ulink url="&url.yaz.cql;">&acro.cql; section</ulink>
+ for the details or the &yaz; frontend server.
+ </para>
+ <para>
+ Notice that there are no <filename>*.abs</filename>,
+ <filename>*.est</filename>, <filename>*.map</filename>, or other &acro.grs1;
+ filter configuration files involves in this process, and that the
+ literal index names are used during search and retrieval.
+ </para>
+ <para>
+ In case that we want to support the usual
+ <literal>bib-1</literal> &acro.z3950; numeric access points, it is a
+ good idea to choose string index names defined in the default
+ configuration file <filename>tab/bib1.att</filename>, see
+ <xref linkend="attset-files"/>
+ </para>
+
+ </section>