[Mapbender-dev] Catalog Schema and Storing Op values

Mifan Careem mifan at opensource.lk
Tue Jul 7 06:35:37 EDT 2009

Dear list,

My current schema to store a catalog object is here:

I currently provide an Admin function to 'Load a Catalog'. In this, I
need to store Operation[1] values from the OperationsMetadata section of
the Catalog's GetCapabilities[2] document. What would the best way be to
store these operations sections (getrecords,describerecords etc.),
considering that I have to make use of the GET/POST values often to make
a CSW search?

Currently, I thought of this:

- Store normal catalog information in the cat table
- store Parameter names and values of the Operations in a seperate
table, like this:
INSERT INTO cat_op_conf(id,op_name,param_name,param_value) VALUES
INSERT INTO cat_op_conf(id,op_name,param_name,param_value) VALUES


Any suggestions?

[1]: <ows:Operation name="DescribeRecord">
<ows:Get xlink:href="http://www.geodata.alterra.nl/excat/csw"/>
<ows:Post xlink:href="http://www.geodata.alterra.nl/excat/csw"/>
<ows:Parameter name="TypeName">
<ows:Parameter name="OutputFormat">
<ows:Parameter name="SchemaLanguage">




More information about the Mapbender_dev mailing list