Renaming XSL file

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

diff --git a/etc/pazpar2.cfg b/etc/pazpar2.cfg
index ae8b15f..a640319 100644 (file)
--- a/etc/pazpar2.cfg
+++ b/etc/pazpar2.cfg
@@ -13,26 +13,31 @@
      configuration could live within one listener (on a single
      port). -->
 
-<service>
-    <listen port="9004"/>
-    <proxy host="localhost" port="80"/>
+<server>
+  <listen port="9004"/>
+  <proxy host="localhost" port="80"/>
 
-    <termlist name="subject"/>
-    <termlist name="author"/>
-
-    <metadata name="title"/>
-</service>
+  <service>
+    <!-- <metadata name="title"/> -->
+  </service>
+</server>
 
 <!-- Need to figure out where to get ZeeRex records for targets from -->
 
 <!-- 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>
+  <charset>marc-8</charset>
+  <map type="iso2709" charset="marc-8" format="marcxml"/>
+  <map type="xslt" stylesheet="marc21.xsl"/>
+</retrievalprofile>
 
 </pazpar2>