-<?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
configuration.
-->
-<service>
- <listen port="9004"/>
- <proxy host="localhost" port="80"/>
-</service>
+<!-- thought... right now there is only one global 'service' in the code, but
+ it will be pretty simple to make this repeatable, and I think that should
+ be done at some point (this will eliminate most of the global parameters.
+ But it might be nice to have 'virtual' targets, so differrent sets of
+ configuration could live within one listener (on a single
+ port). -->
+
+<server>
+ <listen port="9004"/>
+ <proxy host="localhost" port="80"/>
+
+ <service>
+ <!-- <metadata name="title"/> -->
+ </service>
+</server>
<!-- Need to figure out where to get ZeeRex records for targets from -->
-<queryprofile/> <!-- Like a CCL profile? Or do these need to be
- dynamically generated from Zeerex?? -->
+<!-- The 'profiles' below are repeatable, and tagged with an ID, so that they
+ can be linked with targets. -->
+
+<!-- They can be generated dynamically using XSLT. -->
+
+<queryprofile/> <!-- Like a CCL profile? What else? -->
+
+<!-- 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>
projects / pazpar2-moved-to-github.git / blobdiff