Opened 15 years ago

Closed 15 years ago

Last modified 13 years ago

#3121 closed enhancement (fixed)

Add title, abstract and keywordlist for root layer in wms getcapabilities response

Reported by: mschulz Owned by: tomkralidis
Priority: normal Milestone: 6.0 release
Component: WMS Server Version: 5.4
Severity: normal Keywords:
Cc: assefa, dmorissette, mko

Description

The root layer of a wms corresponds to the map level settings of the mapfile, but it is currently not possible to set some wms metadata (title, abstract, keywords) for the root layer, separately from the service section. The web metadata settings of the mapfile are used in the service section of the getcapabilities response and not at the root layer level.

One possible solution would be to create new metadata keywords in the web metadata object, e.g. wms_rootlayer_title, wms_rootlayer_abstract and wms_rootlayer_keywordlist.

Attachments (2)

mstrac-3121.patch (7.5 KB ) - added by tomkralidis 15 years ago.
mstrac-3121_abstract.patch (1 byte ) - added by mko 13 years ago.
removed

Download all attachments as: .zip

Change History (8)

comment:1 by tomkralidis, 15 years ago

Cc: assefa dmorissette added
Owner: changed from mapserverbugs to tomkralidis
Status: newassigned

Dan/Assefa: any comments, etc. before I implement this?

comment:2 by assefa, 15 years ago

Tom, I don't see any issues with this. Note that the current behavior is a bit inconsistent in the sense that wms/ows_title form the web object is used for the root's element title but wms/ows_abstract and wms/ows_keywordlist are not used. Could you please specify that we are keeping the current behavior if wms_root_xxx are not set or should we use the web level metadata for abstract and keyword when the wms_root_xxx are not available.

in reply to:  2 comment:3 by tomkralidis, 15 years ago

Replying to assefa:

Tom, I don't see any issues with this. Note that the current behavior is a bit inconsistent in the sense that wms/ows_title form the web object is used for the root's element title but wms/ows_abstract and wms/ows_keywordlist are not used. Could you please specify that we are keeping the current behavior if wms_root_xxx are not set or should we use the web level metadata for abstract and keyword when the wms_root_xxx are not available.

I think we should be consistent and use wms/ows_abstract and wms_ows_keywordlist for the root Layer item as well, along with wms/ows_title, if the wms/ows_rootlayer_* metadata is not set.

In addition, many CSW harvesting approaches split off (and then associate) the service metadata with the content metadata, so content metadata would be there for the root element when someone does a content search.

If none or wms/ows_rootlayer_* is set, then the web level title/abstract/keywordlist is printed out.

See attached patch. Any objections / anything I missed?

by tomkralidis, 15 years ago

Attachment: mstrac-3121.patch added

comment:4 by tomkralidis, 15 years ago

Resolution: fixed
Status: assignedclosed

Committed to trunk in r9300. Thanks for Assefa for reviewing the patch.

comment:5 by mko, 13 years ago

Cc: mko added

Great this issue is solved. But I think 'rootlayer' is somehow inaccurate as it's the service section, not a layer. The map->metadata.abstract previously shown in the service section could now appear in the root layer - sorry - the first real layer.

by mko, 13 years ago

Attachment: mstrac-3121_abstract.patch added

removed

in reply to:  5 comment:6 by mko, 13 years ago

Replying to mko:

Great this issue is solved. But I think 'rootlayer' is somehow inaccurate as it's the service section, not a layer. The map->metadata.abstract previously shown in the service section could now appear in the root layer - sorry - the first real layer.

The patch works fine. Sorry, my fault using a buggy mapfile for testing.

Note: See TracTickets for help on using tickets.