X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Frecord_transform.xml;h=6465b423d6436aa6f342f3d6b4706b9a6a884192;hb=eb2f36fbec12a2063183d5ae4a9568c55e28acdc;hp=5ec12a0e493ebe1016b1ee4d60c0e19c3ecb0511;hpb=e2f76f7d5f800b51b2a153f83433d9654e384ba3;p=metaproxy-moved-to-github.git diff --git a/doc/record_transform.xml b/doc/record_transform.xml index 5ec12a0..6465b42 100644 --- a/doc/record_transform.xml +++ b/doc/record_transform.xml @@ -1,28 +1,34 @@ - + + %idcommon; ]> - - + + + Metaproxy + Index Data + + record_transform 3mp - Metaproxy Module - + Metaproxy Module + record_transform - Z3950 present package record transformation + Metaproxy Module that performs Z39.50 presentResponse record transformations DESCRIPTION This filter acts only on Z3950 present requests, and let all other types of packages and requests pass untouched. It's use is - twofold: blocking Z3950 present requests, which the backend - server does not understand and can not honour, and transforming + twofold: blocking Z3950 present requests, which the backend + server does not understand and can not honor, and transforming the present syntax and elementset name according to the rules - specified, to fetch only exisitng record formats, and transform + specified, to fetch only existing record formats, and transform them on the fly to requested record syntaxes. @@ -33,71 +39,53 @@ element. The syntax attribute is mandatory, but the name attribute may be omitted, in which case any - element name is accepted. An additonal - identifier attribute can be added to explicetly + element name is accepted. An additional + identifier attribute can be added to explicitly describe the Z3950 identifier string. - Record transformations are invoked when the optional attributes - backendsyntax and backendname - as well as the <convert> element are specified. - Record conversions come in two flavours: - <marc> binary conversions between different - binary MARC formats and MarcXML formats, and - <xslt> stylesheet transformations performed - on any kind of XML records. These conversions can be stacked in any - order, and are performed linearly in file order. - - - The binary MARC record transformations - <marc> are defined using the following - attributes: inputformat, outputformat, - inputcharset and outputcharset. - - - XML <xslt> transformation instructions - accept only one mandatory stylesheet attribute, - which is either an absolute path, or a relative path from the - working directory of metaproxy to the location - of the requested XSLT stylesheet. + The <retrieval> element and the content + is described in the + Retrieval Facility section + of the YAZ manual. + SCHEMA + + + + EXAMPLES A typical configuration looks like this: - - - - - - + + + + - + + - - - - + + + + + - - - - - + + + - + ]]>