X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Frecordmodel-alvisxslt.xml;h=f9ad32025c8cbae48df8e8fc46fe22e4adf66eb6;hb=91500c092797da8e769f1e63ff0c6bd67aad0fc8;hp=be69601c941735a0eb8cee933b233f8d214bf3e0;hpb=0381d7dc936e74ac2fb55ad217b760c97ace0d5b;p=idzebra-moved-to-github.git diff --git a/doc/recordmodel-alvisxslt.xml b/doc/recordmodel-alvisxslt.xml index be69601..f9ad320 100644 --- a/doc/recordmodel-alvisxslt.xml +++ b/doc/recordmodel-alvisxslt.xml @@ -1,5 +1,5 @@ - + ALVIS XML Record Model and Filter Module @@ -19,7 +19,7 @@ - +
ALVIS Record Filter The experimental, loadable Alvis XML/XSLT filter module @@ -58,7 +58,7 @@ unique, these are the literal schema or element set names used in SRW, - SRU and + SRU and Z39.50 protocol queries. The paths in the stylesheet attributes are relative to zebras working directory, or absolute to file @@ -76,7 +76,7 @@ identifier="http://indexdata.dk/zebra/xslt/1". - +
ALVIS Internal Record Representation When indexing, an XML Reader is invoked to split the input files into suitable record XML pieces. Each record piece is then @@ -89,9 +89,9 @@ you can use this functionality inside the Alvis filter configuration XSLT stylesheets. - +
- +
ALVIS Canonical Indexing Format The output of the indexing XSLT stylesheets must contain certain elements in the magic @@ -113,15 +113,15 @@ z:id="oai:JTRS:CP-3290---Volume-I" z:rank="47896" z:type="update"> - <z:index name="oai:identifier" type="0"> + <z:index name="oai_identifier" type="0"> oai:JTRS:CP-3290---Volume-I</z:index> - <z:index name="oai:datestamp" type="0">2004-07-09</z:index> - <z:index name="oai:setspec" type="0">jtrs</z:index> - <z:index name="dc:all" type="w"> - <z:index name="dc:title" type="w">Proceedings of the 4th + <z:index name="oai_datestamp" type="0">2004-07-09</z:index> + <z:index name="oai_setspec" type="0">jtrs</z:index> + <z:index name="dc_all" type="w"> + <z:index name="dc_title" type="w">Proceedings of the 4th International Conference and Exhibition: World Congress on Superconductivity - Volume I</z:index> - <z:index name="dc:creator" type="w">Kumar Krishen and *Calvin + <z:index name="dc_creator" type="w">Kumar Krishen and *Calvin Burnham, Editors</z:index> </z:index> </z:record> @@ -212,14 +212,10 @@ http://localhost:9999/?version=1.1&operation=scan&x-pScanClause=@attr+1=dc:date+@attr+4=2+a ]]> - See for more information on SRU/SRW - configuration, and or - - the YAZ manual CQL section - for the details - of the YAZ frontend server - CQL - configuration. + See for more information on SRU/SRW + configuration, and or the YAZ + CQL section + for the details or the YAZ frontend server. Notice that there are no *.abs, @@ -227,15 +223,15 @@ filter configuration files involves in this process, and that the literal index names are used during search and retrieval. - - +
+
- +
ALVIS Record Model Configuration - +
ALVIS Indexing Configuration As mentioned above, there can be only one indexing @@ -293,7 +289,7 @@ - + @@ -302,7 +298,7 @@ - + @@ -373,9 +369,9 @@ to suffering and pain, and universal disentigration of your project schedule. - +
- +
ALVIS Exchange Formats An exchange format can be anything which can be the outcome of an @@ -422,9 +418,9 @@ - +
- +
ALVIS Filter OAI Indexing Example The sourcecode tarball contains a working Alvis filter example in @@ -444,9 +440,9 @@ http://www.oaforum.org/tutorial/. - +
- +
@@ -491,7 +487,7 @@ c) Main "alvis" XSLT filter config file: and so on. - in db/ a cql2pqf.txt yaz-client config file - which is also used in the yaz-server CQL-to-PQF process + which is also used in the yaz-server CQL-to-PQF process see: http://www.indexdata.com/yaz/doc/tools.tkl#tools.cql.map