X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Fzoom.xml;h=e86924d2a14a2a9a97d95c402c3b8c80b8e12a19;hb=b8550b672196ca7e6fe11a8cba7155beb8794286;hp=b80df073130548b33af924fc2fcedd3cfdb3f15a;hpb=30006392c5d236b5da322842855bd246b2ccfdd8;p=metaproxy-moved-to-github.git diff --git a/doc/zoom.xml b/doc/zoom.xml index b80df07..e86924d 100644 --- a/doc/zoom.xml +++ b/doc/zoom.xml @@ -56,9 +56,10 @@ CONFIGURATION - The configuration consists of five parts: torus, + The configuration consists of six parts: torus, fieldmap, cclmap, - contentProxy and log. + contentProxy, log + and zoom. torus @@ -71,15 +72,34 @@ attribute url - URL of Web service to be used to fetch target profile - for a given database (udb). The special sequence - %db of the URL is replaced by the - actual database specified as part of Search. + URL of Web service to be used when fetch target profiles from + a remote service (Torus normally). + + + The sequence %query is replaced with a CQL + query for the Torus search. The special sequence %realm is replaced by value of attribute realm or by realm DATABASE argument. + + The special sequence %db is replaced with + a single database while searching. Note that this sequence + is no longer needed, because the %query can already + query for a single database by using CQL query + udb==.... + + + + + attribute content_url + + + URL of Web service to be used to fetch target profile + for a given database (udb) of type content. Semantics otherwise like + url attribute above. + @@ -134,6 +154,16 @@ + attribute explain_xsl + + + Specifies a stylesheet that converts one or more Torus records + to ZeeExplain records. The content of recordData is assumed to be + holding each Explain record. + + + + element records @@ -234,6 +264,26 @@ + + + zoom + + The zoom element controls settings for the + ZOOM. + + + + attribute timeout + + + Is an integer that specifies, in seconds, how long an operation + may take before ZOOM gives up. Default value is 40. + + + + + + QUERY HANDLING @@ -300,11 +350,12 @@ - authentication + authentication Authentication parameters to be sent to the target. For Z39.50 targets, this will be sent as part of the - Init Request. + Init Request. Authentication consists of two components: username + and password, separated by a slash. If this value is omitted or empty no authentication information is sent. @@ -336,7 +387,7 @@ - cfProxy + cfProxy Specifies HTTP proxy for the target in the form host:port. @@ -352,7 +403,7 @@ - + contentConnector Specifies a database for content-based proxy'ing. @@ -469,6 +520,16 @@ + sruVersion + + Specifies the SRU version to use. It unset, version 1.2 will be + used. Some servers do not support this version, in which case + version 1.1 or even 1.0 could be set it. + + + + + transform Specifies a XSL stylesheet filename to be used if record @@ -494,19 +555,20 @@ The value of this field is a string that generates a dynamic link based on record content. If the resulting string is non-zero in length a new field, metadata with attribute - type="generated-url". + type="generated-url" is generated. The contents of this field is the result of the URL recipe conversion. The urlRecipe value may refer to an existing metadata element by ${field[pattern/result/flags]}, which will take content of field and perform a regular expression conversion using the pattern given. For example: ${md-title[\s+/+/g]} takes - metadadata element title and converts one or more + metadata element title and converts one or more spaces to a plus character. - If the contentConnector + If the contentConnector setting also defined, the resulting value is - augmented with a session string as well as the content proxy server. + augmented with a session string as well as host name of the + content proxy server. @@ -525,7 +587,7 @@ DATABASE parameters - Extra information may be carried in the Z39.50 Datbase or SRU path, + Extra information may be carried in the Z39.50 Database or SRU path, such as authentication to be passed to backend etc. Some of the parameters override TARGET profile values. The format is @@ -535,16 +597,22 @@ Where udb is the unique database recognised by the backend and parm1, value1, .. are parameters to be passed. The following describes the - supported parameters. + supported parameters. Like form values in HTTP the parameters and + values are URL encoded. The separator, though, between udb and parameters + is a comma rather than a question mark. What follows question mark are + HTTP arguments (in this case SRU arguments). user - Specifies user to be passed to backend. If this parameters is + Specifies user to be passed to backend. If this parameter is omitted, the user will be taken from TARGET profile setting - authentication. + + authentication + + . @@ -554,7 +622,10 @@ Specifies password to be passed to backend. If this parameters is omitted, the password will be taken from TARGET profile setting - authentication. + + authentication + + . @@ -562,9 +633,12 @@ proxy - Specifies proxy to be for backend. If this parameters is + Specifies one or more proxies for backend. If this parameter is omitted, the proxy will be taken from TARGET profile setting - cfProxy. + + cfProxy. + The parameter is a list of comma-separated host:port entries. + Bost host and port must be given for each proxy. @@ -578,6 +652,15 @@ + nocproxy + + + If this parameter is specified, content-proyxing is disabled + for the search. + + + + realm @@ -631,6 +714,7 @@ + ]]>