X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Frecord_transform.xml;h=c490d56d1d1b322161e2a9b504c931c10834b095;hb=88907efa4d22cad39f1545525c95289d8aa1226a;hp=e298a406048915341dddbc8798e705d33ef368b9;hpb=915efbba95f2a46ef5abf35e8fe85f2d0d0567ea;p=metaproxy-moved-to-github.git
diff --git a/doc/record_transform.xml b/doc/record_transform.xml
index e298a40..c490d56 100644
--- a/doc/record_transform.xml
+++ b/doc/record_transform.xml
@@ -1,4 +1,4 @@
-
@@ -15,7 +15,7 @@
3mp
Metaproxy Module
-
+
record_transform
Metaproxy Module that performs record transformations
@@ -30,35 +30,54 @@
syntax and elementset name according to the rules specified, to fetch
only existing record formats, and transform them on the fly to requested
record syntaxes.
-
+
- The allowed record present syntax and
+ The allowed record present syntax and
element name are described in multiple
- <retrieval> elements inside the
+ <retrieval> elements inside the
<retrievalinfo>
element. The syntax attribute is mandatory, but
the name attribute
- may be omitted, in which case any
+ may be omitted, in which case any
element name is accepted. An additional
identifier attribute can be added to explicitly
describe the Z39.50 identifier string.
The <retrieval> element and the content
- is described in the
+ is described in the
Retrieval Facility section
of the YAZ manual.
+
+ From Metaproxy version 1.3.26 and onwards the backend conversion ma
+ also use USEMARCON.
+ If USEMARCON is enabled, the backend may include
+ a usemarcon element with two attributes:
+ stage1 and stage2 that points to
+ conversion files as interpreted by USEMARCON. One or both must be given.
+
-
+
SCHEMA
-
-
+
+ Schema is in two parts.. One for the filter itself and one for the
+ retrieval info.
+
+
+
+
+
+
+
-
+
EXAMPLES
A typical configuration looks like this:
@@ -84,13 +103,18 @@
+
+
+
+
+
]]>
-
-
+
+
SEE ALSO
@@ -99,7 +123,7 @@
-
+
©right;