Added XSLT support. Configuration file (e.g. etc/pazpar2.cfg) must now be specified

[pazpar2-moved-to-github.git] / etc / pazpar2.cfg

diff --git a/etc/pazpar2.cfg b/etc/pazpar2.cfg
index 97a5bdd..e63a98c 100644 (file)
--- a/etc/pazpar2.cfg
+++ b/etc/pazpar2.cfg
@@ -1,5 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<pazpar2 xmlns="http://www.indexdata.com/pazpar2/1.0">
+<?xml version="1.0" encoding="UTF-8"?> <pazpar2 xmlns="http://www.indexdata.com/pazpar2/1.0">
 
 <!-- NOTE: This is not yet a functional config file. It's meant as a scratchpad/
      discussion area to figure out just how the heck to structure this kind of
@@ -18,9 +17,6 @@
   <proxy host="localhost" port="80"/>
 
   <service>
-    <termlist name="subject"/>
-    <termlist name="author"/>
-
     <!-- <metadata name="title"/> -->
   </service>
 </server>
@@ -30,11 +26,16 @@
 <!-- The 'profiles' below are repeatable, and tagged with an ID, so that they
      can be linked with targets. -->
 
-<!-- Oooh!!! They can be generated dynamically using XSLT. I just peed in my pants. -->
+<!-- They can be generated dynamically using XSLT. -->
+
+<queryprofile/>  <!-- Like a CCL profile? What else? -->
 
-<queryprofile/>  <!-- Like a CCL profile? Or do these need to be 
-                       dynamically generated from Zeerex??  -->
+<!-- Select by target ID (pattern). What else???   -->
 
-<retrievalprofile/>   <!-- Specify what stylesheets to use to normalize records?? -->
+<retrievalprofile>
+  <requestsyntax>marc21</requestsyntax>
+  <nativesyntax name="iso2709" format="marc21" encoding="marc-8" mapto="marcxml"/>
+  <map type="xslt" stylesheet="marc21.xsl"/>
+</retrievalprofile>
 
 </pazpar2>