Paul,

I agree with you that the exception reporting is insufficient. Did you- 
as I suggested last time - create a JIRA issue for this and the other 
bug (wrong order)?
Suggestions for improvements or new features can also be put on JIRA. I 
will look at these issues when I get the chance, bugs having highest 
priority of course.

However; I don't think the CSW module is being funded by anyone at the 
moment. If you want large improvements in the short term for your 
project that is maybe something you can help with.

Regards
Niels

On 08/24/2015 02:46 PM, Paul van Genuchten wrote:
> Hi list, I would like to discuss some potential optimisations to the csw
> server implementation in geoserver. I wanted to use the csw endpoint in
> a geoserver training, however I noticed some challenges in the
> implementation. For me having a csw service in geoserver makes sense,
> because in that case data and metadata are managed in the same system,
> things like last update date, title, abstract, contact are always in
> sync between wms/wfs-getcapabilities and metadata.
>
> @nielscharlier: Thank you for your suggestion about the metadata
> language (on a thread some weeks ago), indeed the metadata language was
> the one causing the error (although i still think the error should
> indicate which element causus the issue).
>
> A challenge I have with the current implemetation is that I noticed all
> metadata elements are in some random order, and this breaks the xsd. How
> is the order of the elements applied? Something might be wrong in my
> md_metadata.properties, although I think it's a bug in the implemetation.
>
> my md-response has:
>
> <gmd:MD_Metadata>
>       <gmd:referenceSystemInfo>...
>       <gmd:dataQualityInfo>...
>       <gmd:fileIdentifier>...
>       <gmd:distributionInfo>...
>       <gmd:language>...
> ...
>
> Another optimisation to discuss might be to allow to create a
> md_metadata.properties per workspace, because in quite some cases layers
> in workspace do share some metadata.
>
> Another option I would suggest is to add an option "use internal csw for
> metadata links" on the service or workspace level. In that case the
> metadata url field will either not be visible, or filled with a default
> in the layer-management-form
>
> A last optimisation I would suggest is related to customisation of the
> getcapabilities response itself, can it be an option to add a similar
> approach as md_metadata.properties to the getcapabilities response?
> (INSPIRE requires some custom elements in the getcapabilities response,
> and this might be an approach to add them)
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Geoserver-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users


------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to