Hi Niels! Aim high, hit low.
There seems to be no disagreement on your original proposal, and I also
believe that the bug here lies in the documentation. And trust me, I'd be
happy to contribute a working setup if I could manage to put one together.
My goal is to publish geodata on Geoserver and add a little more metadata
to the CSW than the simple WMS provides when harvested to Geonetwork. And I
think CSW-ISO would do the trick. But this line in the mapping file stops
the harvester:
$dateStamp.Date= if_then_else ( isNull("metadata.date") , 'Unknown',
"metadata.date")
Since I cannot figure out how to populate metadata.date the returned date
will be 'Unknown' which Geonetwork refuses to accept.
The Creation date would do fine, but I would like to add a Revision date as
well since the underlying PostGIS data will change.
I have asked for help on several mailing lists to no avail. If these
parameters are documented, please link me to that. I should not be that
hard to figure out.
Regards, Mats.E
Den mån 11 apr. 2022 kl 09:43 skrev Niels Charlier via Ge
Coserver-devel <geoserver-devel@lists.sourceforge.net>:
> Hello Mats and Richard,
>
> Thank you for your feedback. I hear two signals from you:
>
> (1) there is demand for the functionality of these modules;
> (2) they are currently too hard to deploy and configure, or in other
> words there is demand for better support.
>
> Considering these points I think it would be good to get more
> discussion/questions on here and jira issue tracking going on for these
> modules. I am absolutely willing to respond to your questions/problems,
> if I have missed anything that was sent to this ML I do apologize. I
> also hope that with the promotion of the modules we will make progress
> in this department.
>
> I can assure that the modules do work and have been put to use by
> different people. If there are issues with initial deployment, they are
> probably easy to solve if reported (I often work directly from custom
> builds, so that is why I might not be aware). But the modules should not
> be merged; they each have use cases separate from each other and serve
> different purposes. Perhaps their build could be combined into a single
> zip file, but I doubt that would be such a time saver.
>
> I do agree that the configuration is really a very big bottleneck, and
> that is harder to solve:
>
> - for CSW, the so-called "mapping file" is an absolute disaster for
> ISO/inspire. The system was created (by me, I admit) as it was an easy,
> quick and convenient way to set-up very basic, simple metadata in Dublin
> Core. But for ISO/inspire the mapping file becomes a monster that is
> extremely hard to set up and maintain. I believe CSW needs a new
> configuration system, using templates that are more intuitive and
> maintainable. So if anyone would fund me writing that, I would give much
> applause.
>
> - for the metadata module, I am quite happy with the configuration
> system. Yes, it is also quite complicated, but that complication is a
> necessary consequence of the advanced customization that is possible. So
> it might be necessary for a new user to familiarize themselves with the
> module and all its possibilities. If people can't figure it out, I would
> say it must be a problem of documentation, so perhaps feedback and issue
> reporting could help to improve that.
>
> Kind Regards
>
> Niels
>
>
> On 09/04/2022 11:55, Richard Duivenvoorde wrote:
> > Hi List,
> >
> > My 1c: fully agree with Mats, being somebody getting cold when hearing
> > 'metadata' and 'csw' in one sentence, I was still eager to try to test
> > this in geoserver, hoping I could make this work as csw in QGIS...
> >
> > But I failed miserably too (even asked mr Geonetwork for help),
> > because of our inexperience with all the metadata lingua (profiles,
> > mappings to fields, several xml files to edit etc etc) and just the
> > inability to add some custom fields.
> >
> > I hope this proposal would make this a little easier :-)
> >
> > Regards,
> >
> > Richard
> >
> > On 4/9/22 11:10, Mats Elfström wrote:
> >> Hi! My 2c on this proposal.
> >> I have been struggling trying to make use of Geoserver as a metadata
> >> repository and source for published geodata. With no success. Even a
> >> vanilla installation, using unaltered sample configuration files,
> >> fails to generate any output that Geonetwork harvester will accept.
> >> The geoserver subsystem for metadata involves 4 extensions, two of
> >> which are community and two are supported extensions. Promoting the
> >> two community modules is a good start. Maybe this will ensure that
> >> these four modules will work together as expected.
> >> But I would like to propose an even bolder approach. To me, CSW,
> >> Metadata and ISO-INSPIRE are parts of a whole and would perhaps be
> >> easier to install, configure and maintain if combined into a single
> >> extension? If I may be so bold? And even further, made part of
> >> Geoserver core.
> >> Metadata is the most important single factor for the availability and
> >> useability of geodata, and Geoserver is an important player in this
> >> field. Given that PostGIS lacks a built-in metadata function,
> >> Geoserver could fill that void, even if only for published data.
> >> Some have suggested that the lack of interest in the csw-metadata
> >> parts of Geoserver is due to the fact that very few use it. But is
> >> that because it is not needed, or because it is too hard to set up
> >> and configure?
> >> Best regards, Mats.E
> >>
> >> Den fre 8 apr. 2022 kl 14:28 skrev Niels Charlier via Geoserver-devel
> >> <geoserver-devel@lists.sourceforge.net
> >> <mailto:geoserver-devel@lists.sourceforge.net>>:
> >>
> >> Hi Simone,
> >>
> >> Thanks for your vote. Yes I am available for all questions
> >> regarding the modules and general maintenance as required or
> >> requested by the PSC .
> >>
> >> Kind Regards
> >>
> >> Niels
> >>
> >> On 06/04/2022 15:49, Simone Giannecchini wrote:
> >>> Hi Niels,
> >>> I'd say +1 as we use at least CSW quite a lot ourselves.
> >>>
> >>> I am assuming you are also stepping up to supporting people's
> >>> questions on the ML and keeping the modules following the general
> >>> GeoServer development.
> >>>
> >>> Regards,
> >>> Simone Giannecchini
> >>> ==
> >>> Professional Support for GeoNode, GeoServer and MapStore from
> >>> the experts!
> >>> Visit http://bit.ly/gs-services <http://bit.ly/gs-services> for
> >>> more information.
> >>> ==
> >>> Ing. Simone Giannecchini
> >>> @simogeo
> >>> Founder/Director GeoSolutions Italy
> >>> President GeoSolutions USA
> >>>
> >>> phone: +39 0584 962313
> >>> fax: +39 0584 1660272
> >>> mob: +39 333 8128928
> >>> US: +1 (845) 547-7905
> >>>
> >>> http://www.geosolutionsgroup.com <http://www.geosolutionsgroup.com
> >
> >>> http://twitter.com/geosolutions_it
> >>> <http://twitter.com/geosolutions_it>
> >>>
> >>> -------------------------------------------------------
> >>> 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.
> >>>
> >>>
> >>> On Tue, Apr 5, 2022 at 5:43 AM Jody Garnett
> >>> <jody.garn...@gmail.com <mailto:jody.garn...@gmail.com>> wrote:
> >>>
> >>> Hey Niels!
> >>>
> >>> Not quite sure I understand the CLA question; if you did the
> >>> work on behalf of a particular government department and had their
> >>> permission/authority to donate to OSGeo then you should be good. If
> >>> you are really interested in being careful you could ask the manager
> >>> (whoever paid you or authorized the work) to sign a "Corporate
> >>> contributor license
> >>> <https://www.osgeo.org/wp-content/uploads/corporate_contributor.pdf>",
>
> >>> and name the body of the work (metadata and csw-iso) as the
> >>> contributed work in "Schedule B" at the bottom of the document.
> >>>
> >>> Although it says "corporate" it is really:
> >>>
> >>>> "You" (or "Your") shall mean the copyright owner or legal
> >>>> entity authorized by the copyright owner that is making this
> >>>> Agreement with the Foundation. "You" (or "Your") shall mean the
> >>>> copyright owner or legal entity authorized by the copyright owner
> >>>> that is making this Agreement with the Foundation.
> >>>
> >>> So a government should be able to sign it.
> >>> --
> >>> Jody Garnett
> >>>
> >>>
> >>> On Apr 4, 2022 at 4:49:08 AM, Niels Charlier via
> >>> Geoserver-devel <geoserver-devel@lists.sourceforge.net
> >>> <mailto:geoserver-devel@lists.sourceforge.net>> wrote:
> >>>> Hello,
> >>>>
> >>>> I have written up two proposals to promote community
> >>>> modules "metadata"
> >>>> and "csw-iso" to extensions.
> >>>>
> >>>> https://github.com/geoserver/geoserver/wiki/GSIP-311
> >>>> <https://github.com/geoserver/geoserver/wiki/GSIP-311>
> >>>>
> >>>> https://github.com/geoserver/geoserver/wiki/GSIP-312
> >>>> <https://github.com/geoserver/geoserver/wiki/GSIP-312>
> >>>>
> >>>> I believe stability, test coverage, users, are all okay.
> >>>> Please discuss.
> >>>>
> >>>> One question about copyrights though: the metadata module
> >>>> was mostly
> >>>> written by me (who signed CLA) as part of a contract
> >>>> particular
> >>>> government department. I believe they technically have
> >>>> copyrights, and
> >>>> agreed to open source it. What would be required though?
> >>>> Should they
> >>>> sign CLA for businesses?
> >>>>
> >>>> Kind Regards
> >>>>
> >>>> Niels
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> 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>
> >>> _______________________________________________
> >>> 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>
> >>>
> >> _______________________________________________
> >> 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>
> >>
> >>
> >>
> >> --
> >>
> >> *
> >> *
> >>
> >> *GisKraft*, Geodatakonsult
> >>
> >> Mats Elfström, Marsvinsholms stationsväg 80, 271 93 Ystad, Sweden
> >> tel: +46 70 595 39 35 / www.giskraft.se <http://www.giskraft.se>
> >>
> >>
> >>
> >> _______________________________________________
> >> Geoserver-devel mailing list
> >> Geoserver-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
> >
> >
> >
> > _______________________________________________
> > Geoserver-devel mailing list
> > Geoserver-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
--
*GisKraft*, Geodatakonsult
Mats Elfström, Marsvinsholms stationsväg 80, 271 93 Ystad, Sweden
tel: +46 70 595 39 35 / www.giskraft.se
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
