Hi Armin, List, Would a schema like this be helpful to store the operational values in the get_capabilities document?
cat_op_conf (fkey_cat_id,param_type,param_name,param_value) Following would be sample inserts: INSERT INTO cat_op_conf(fkey_cat_id,param_type,param_name,param_value) VALUES (1,get_capabilities,get,http://something/...); VALUES (1,get_capabilities,post_soap,http://something/...); VALUES (1,get_capabilities,post_xml,http://something/...); VALUES (1,get_records,get,http://something/...); VALUES (3,get_capabilities,post,http://something/...); This would be more efficient than storing a part-XML structure, and we can handle the various get,post and soap values - and it would be more efficient to retrieve them. Thoughts are appreciated. Regards Mifan On Fri, 2009-07-10 at 09:31 +0200, Armin Retterath wrote: > good morning mifan, > > the schema i described in part 7 was only a hint ;-). i know that there is a > problem when there are the two bindings http and soap. there are many urls to > handle with. maybe we can split the soap binding from the http and create a > new table 'cat_op_soap' for it? maybe the schema would be something like : > fkey_cat_id, cat_op_getcapabilities, ... > please think about it and check it for usability - in future we have to > integrate the soap binding for wms and wfs in a similar manner. > the second table will make the updates a little bit more complicated - but > this is a problem of the standards and we must handle it on an easy way. > an other possibility is to store the whole xml part: > > <ows:Operation name="GetCapabilities"> > <ows:DCP> > <ows:HTTP> > <ows:Get xlink:href="http://www.portalu.de:80/csw202"/> > <ows:Post xlink:href="http://www.portalu.de:80/csw202";> > <ows:Constraint name="PostEncoding"> > <ows:Value>SOAP</ows:Value> > </ows:Constraint> > </ows:Post> > <ows:Post xlink:href="http://www.portalu.de:80/csw202";> > <ows:Constraint name="PostEncoding"> > <ows:Value>XML</ows:Value> > </ows:Constraint> > </ows:Post> > </ows:HTTP> > </ows:DCP> > </ows:Operation> > > in one column. the problem will be, that we have to parse the information > every time we need them. i would prefer the storing in a relational > structure. but i think you must check it. > > if have further questions - please ask. > cheers > armin > > > Am Freitag 10 Juli 2009 06:13:08 schrieben Sie: > > Hi Armin, > > > > On Thu, 2009-07-09 at 16:44 +0200, Armin Retterath wrote: > > > i am sorry, we need the post urls too, cause the specification demands > > > post for GetRecords and DescribeRecords. > > > > Ok - no worries - will handle the post values as well - is there a > > chance the SOAP values should be stored as well?. I'm just wondering > > whether it is possible to store both values in the schema described in > > Section 7 of the wiki? Or should I have another field to capture the > > post values? > > > > Anyways, I will add this in somewhere. > > > > Thanks > > > > Mifan > > > > > many catalogues would only implement > > > this minimal demands. 'get' is in this two cases only nice too have. > > > please see http://www.mapbender.org/CSW_Requirements point 8. > > > cheers > > > armin > > > > > > Am Donnerstag 09 Juli 2009 07:52:39 schrieb Mifan Careem: > > > > Hi List, > > > > > > > > I've current solved the problem by storing the GET values of the > > > > operations (e.g getrecords) in the main catalog schema itself. I am > > > > currently not storing the other parameter values of the operations - if > > > > this is needed, I can handle this later on, but since currently I just > > > > need the GET URLs, I'll concentrate on this. > > > > > > > > Let me know if there are any suggestions. > > > > > > > > Thanks > > > > > > > > Mifan > > > > > > > > On Tue, 2009-07-07 at 16:05 +0530, Mifan Careem wrote: > > > > > Dear list, > > > > > > > > > > My current schema to store a catalog object is here: > > > > > http://www.mapbender.org/CSW_report_week_3 > > > > > > > > > > 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 > > > > > (2,'getrecords',http_get,http://www.geodata.alterra.nl/excat/csw); > > > > > INSERT INTO cat_op_conf(id,op_name,param_name,param_value) VALUES > > > > > (2,'getrecords','typename','csw:Record'); > > > > > > > > > > etc. > > > > > > > > > > Any suggestions? > > > > > > > > > > > > > > > [1]: <ows:Operation name="DescribeRecord"> > > > > > <ows:DCP> > > > > > <ows:HTTP> > > > > > <ows:Get xlink:href="http://www.geodata.alterra.nl/excat/csw"/> > > > > > <ows:Post xlink:href="http://www.geodata.alterra.nl/excat/csw"/> > > > > > </ows:HTTP> > > > > > </ows:DCP> > > > > > <ows:Parameter name="TypeName"> > > > > > <ows:Value>csw:Record</ows:Value> > > > > > </ows:Parameter> > > > > > <ows:Parameter name="OutputFormat"> > > > > > <ows:Value>application/xml</ows:Value> > > > > > </ows:Parameter> > > > > > <ows:Parameter name="SchemaLanguage"> > > > > > <ows:Value>XMLSCHEMA</ows:Value> > > > > > <ows:Value>http://www.w3.org/XML/Schema</ows:Value> > > > > > </ows:Parameter> > > > > > </ows:Operation> > > > > > > > > > > [2]: > > > > > http://www.geodata.alterra.nl/excat/csw?request=GetCapabilities&servi > > > > >ce=C SW > > > > > > > > > > > > > > > Thanks > > > > > > > > > > Mifan > > > > > > > > _______________________________________________ > > > > Mapbender_dev mailing list > > > > [email protected] > > > > http://lists.osgeo.org/mailman/listinfo/mapbender_dev > > > _______________________________________________ Mapbender_dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapbender_dev
