Closed dwins closed 11 years ago
It's likely that this is an omission on the GeoNode side - GeoServer probably has separate fields for these other metadata links and we aren't populating them. The fix might be for GeoServer to include the WMS metadata links in the WFS and WCS metadata listings... but I'm not sure what the factors were in organizing things the way they currently are.
Could be, but in the GeoServer UI for layers there's only one field for configuring the 'metadata links'. If I were a user just of that GUI I'd assume that filling that out for my layer would have it show up in all the right places.
But internally it very well me that there are separate fields for each, but it looks like there's no way to access them.
I agree with Chris's comment.
This sounds like a bug in geoserver, can someone file it there and then link to it here and close this one?
Closing this as GeoNetwork is no longer applicable, and issue #761 may be similar but more current.
In WFS 1.1 there is a 'MetadataURL' field for each featureType that we leave blank, and in WCS there is an OWS metadata link that we don't populate, we just say:
We do however populate it properly for WMS, using the link to geonetwork's metadata record. And looking at the GeoServer admin console it looks like it's properly filled out there.
So sounds like this is most likely just a bug in the capabilities documents of WFS and WCS in GeoServer.