X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Frecordmodel-alvisxslt.xml;h=d067622033c19d54946fa2e83a65bdf9fc671895;hb=c33ea56e3771c3b80ba66ef8fda3a09cad171ebb;hp=df73cb99294b3c825d75034b45802144cf37609f;hpb=43b4d8d93cd567284f4e48731119f3da2a1daedf;p=idzebra-moved-to-github.git
diff --git a/doc/recordmodel-alvisxslt.xml b/doc/recordmodel-alvisxslt.xml
index df73cb9..d067622 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
@@ -187,19 +187,55 @@
the same character normalization map w.
+ Finally, this example configuration can be queried using PQF
+ queries, either transported by Z39.50, (here using a yaz-client)
+
+ open localhost:9999
+ Z> elem dc
+ Z> form xml
+ Z>
+ Z> f @attr 1=dc:creator Kumar
+ Z> scan @attr 1=dc:creator adam
+ Z>
+ Z> f @attr 1=dc:title @attr 4=2 "proceeding congress superconductivity"
+ Z> scan @attr 1=dc:title abc
+ ]]>
+
+ or the proprietary
+ extentions x-pquery and
+ x-pScanClause to
+ SRU, and SRW
+
+
+
+ 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.
+
+
Notice that there are no *.abs,
*.est, *.map, or other GRS-1
- filter configuration files involves in this process.
+ 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
@@ -337,9 +373,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
@@ -386,9 +422,31 @@
-
+
+
+
+ ALVIS Filter OAI Indexing Example
+
+ The sourcecode tarball contains a working Alvis filter example in
+ the directory examples/alvis-oai/, which
+ should get you started.
+
+
+ More example data can be harvested from any OAI complient server,
+ see details at the OAI
+
+ http://www.openarchives.org/ web site, and the community
+ links at
+
+ http://www.openarchives.org/community/index.html.
+ There is a tutorial
+ found at
+
+ http://www.oaforum.org/tutorial/.
+
+
-
+
@@ -433,7 +491,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