I believe the namespaces for CSW-ISO are hard coded in org.geoserver.csw.records.iso.MetaDataDescriptor, though I cannot guarantee that adding it there is all that is needed to resolve your issue. Perhaps it would be interesting making this a configurable thing.
Andrea is mostly right; however one correction: I do not mind at all giving free email support for problems with installation and configuration of the community modules (not for actual dev/depl work of course). However, it is true that it is often necessary to ping me specifically, unfortunately.
I can assure you that the modules do work, since they are in use by several government departments (not all of them deployed by me). It is definitely possible the documentation needs improvement, so it would be great to hear the issues that others are having with it.
It would actually be in the interest of the current users if the modules were used by more users, and they are very aware of that.
On Wed, Jan 5, 2022 at 12:56 PM Mats Elfström <mats.elfstrom@…7245…> wrote:
Hi Friedrich!
I am afraid that the whole geoserver csw and metadata subsystems seem broken (CSW-plugin, the CSW-ISO-plugin, meta-data plugin and the INSPIRE plugin).
The part that is supported is the CSW core with Dublin Core records only. The others are marked as unsupported for a reason 
Since it is a mix of supported and unsupported plugins, no one seems able to even identify what needs to be done.
This is incorrect. There are plenty of people that could, but it would require significant effort, more than can be spent answering a mail.
The ISO plugin was written by Niels Charlier on behalf of Boundless. Boundless is no more, Niels showed no desire to get
involved with user support on the free channels… As a result, nobody can give you the “5 minutes answer”, the only type of
answer that you’ll get on this list, or on stack overflow.
There are other options, but they involve spending money:
- Contact Niels and get a contract to solve your particular problem.
- Contact any commercial support provider involving a core developer. These people can use part of the contract to get up to speed with the module, and provide a fix. This would come with a significant by-product, core developers are answering on this list… meaning you’ll open the path for simple free answers in the future. It does not have to be you, but there needs to be a seed customer that triggers this process.
I have been struggling with this since summer, and I can tell you this: Following the installation and configuring advice in the manual does not work. Perhaps this is the error, and the plugins actually do work. One cannot tell.
Another advice I got is that no one uses these extensions, which may be why no one cares to fix them.
As far as I know, there is just one user (and guess who’s providing support and development to them?).
Same happens for the meta-data module.
Cheers
Andrea
==
GeoServer Professional Services from the experts!
Visit http://bit.ly/gs-services-us for more information. == Ing. Andrea Aime @geowolf Technical Lead
GeoSolutions Group phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928
https://www.geosolutionsgroup.com/
http://twitter.com/geosolutions_it
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail
_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)
Hi Friedrich!
I am afraid that the whole geoserver csw and metadata subsystems seem broken (CSW-plugin, the CSW-ISO-plugin, meta-data plugin and the INSPIRE plugin).
Since it is a mix of supported and unsupported plugins, no one seems able to even identify what needs to be done.
I have been struggling with this since summer, and I can tell you this: Following the installation and configuring advice in the manual does not work. Perhaps this is the error, and the plugins actually do work. One cannot tell.
Another advice I got is that no one uses these extensions, which may be why no one cares to fix them.
This is sad, because Geoserver could be a great platform for publishing geodata AND valid metadata from the same point.
Regards, Mats.E
Den ons 5 jan. 2022 kl 12:13 skrev Friedrich, Heiko <Heiko.Friedrich@…7241…>:
Hello everybody,
I tried wo write that problem to the issue-board ( https://osgeo-org.atlassian.net/jira/software/c/projects/GEOS/issues ) but I can’t login although I have an account. So I trie it here, maybe somebody can help.
We are using the geoserver CSW-plugin, the CSW-ISO-plugin and the meta-data plugin. In one of these plugins the namespaces for the CSW-service is set. I don’t know in which of these.
Unfortunately the srv-namespace is missing ( xmlns:srv=http://www.isotc211.org/2005/srv ). (In CSW-services from other mapservers the srv-namespace is available, e.g.: https://geoportal-hamburg.de/metaver_de/csw?service=CSW&request=GetRecordById&version=2.0.2&outputschema=http:%2F%2Fwww.isotc211.org%2F2005%2Fgmd&elementsetname=full&id=9784D2A9-AEEA-46DF-9FAD-2FA14BFCA00D )
Before we updated to geoserver version 2.20.1 there was also the gml-namespace missing, but know it works… J
Maybe somebody can tell me in which of the plugins the namespace is set, if I can configure it somewhere of if it is a bug and it has to be fixed?
Kind regards!
Heiko Friedrich
PS:
If it helps, the x-path confiugred in the MD_Metadata.properties should look like this:
identificationInfo.SV_ServiceIdentification.serviceType.LocalName.@…7242…=‘test‘
identificationInfo.SV_ServiceIdentification.serviceTypeVersion.CharacterString=‘test‘
identificationInfo.SV_ServiceIdentification.couplingType.SV_CouplingType@…4279…=‘test‘
identificationInfo.SV_ServiceIdentification.containsOperations.SV_OperationMetadata.operationName.CharacterString=‘test‘
identificationInfo.SV_ServiceIdentification.operatesOn.@…7243…=‘test‘
