X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Fsru_z3950.xml;h=2f9e121b362a2bbca4766334c8892702739db3db;hb=45d155e02c30dff521e54975952148ff72db9a9a;hp=8c23ff1025549be169abcd87bf15d2fb5bf38009;hpb=a96413b9df8d1409a227405b488d1aaa8c8bfeb4;p=metaproxy-moved-to-github.git diff --git a/doc/sru_z3950.xml b/doc/sru_z3950.xml index 8c23ff1..2f9e121 100644 --- a/doc/sru_z3950.xml +++ b/doc/sru_z3950.xml @@ -1,9 +1,10 @@ + + %idcommon; ]> - - + sru_z3950 3mp @@ -12,17 +13,39 @@ sru_z3950 - transforming SRU web service requests to Z3950 metaproxy packages + Metaproxy Module transforming SRU web service requests to Z3950 Metaproxy packages DESCRIPTION - The sru_z3950 metaproxy filter transforms valid - SRU/GET or SRU/SOAP requests to Z3950 requests, and wraps the + The sru_z3950 Metaproxy filter transforms valid + SRU GET/POST/SOAP requests to Z3950 requests, and wraps the received hit counts and XML records into suitable SRU response messages. - It supports only the SRU searchRetrieve operation, which + Multiple database elements defining the names of the accepted + databases are allowed in the configuration file. Each + of them must contain their own explain record, or must be empty. + Notice that explain + records come in SRU and Z39.50 flavors, and this filter requires + the SRU version. See the + ZeeReX Explain + standard pages and the + SRU Explain pages + for more information. + + + All Z39.50 packages and all HTTP packages that do not resolve to + one configured database name are passed unaltered to the next + filters on the route. + + + The SRU explain operation is supported, + returning either the absolute minimum required by the standard, or + a full pre-defined ZeeReX explain record. + + + It supports the SRU searchRetrieve operation, which is transformed into successive Z3950 init, search and present requests. @@ -30,25 +53,47 @@ The SRU scan operation is not supported. - The SRU explain operation is not supported. - A configuration for a full SRU server needs to prepend the - zeerex_explain filter in front of this - sru_z3950 to serve explain requests. This filter - still needs to be implemented. - - This filter does not handle CQL-to-PQF translations. In case that - the backends do not understand CQL, you need to prepend the - cql_pqf metaproxy filter. This filter - still needs to be implemented. - + the backends do not understand CQL, you need to append the + cql_pqf metaproxy filter. + + + This module supports the following SRU extra parameters: + + + x-target + + + Specifies backend Z39.50 target. + + + + + x-max-sockets + + + Specifies maximum number of sockets to use for a Z39.50 backend + client (for one given target host/db). + + + + + EXAMPLES A typical configuration looks like this: + + + + ... + + + + + ]]>