[Qgis-developer] MetaSearch 0.3.0 released

Tom Kralidis tomkralidis at gmail.com
Thu Sep 4 04:09:13 PDT 2014



On Thu, 4 Sep 2014, Blumentrath, Stefan wrote:

> Date: Thu, 4 Sep 2014 08:00:06 +0000
> From: "Blumentrath, Stefan" <Stefan.Blumentrath at nina.no>
> To: Tom Kralidis <tomkralidis at gmail.com>,
>     Alexander Bruy <alexander.bruy at gmail.com>
> Cc: qgis-developer <qgis-developer at lists.osgeo.org>
> Subject: AW: [Qgis-developer] MetaSearch 0.3.0 released
> 
> Hi Tom,
>
> if you allow me a user-question here:
>
>> Having said this, what about the Layer properties dialog's Metadata section? There
>> is almost enough there for a fulsome enough metadata record.  Adding
>> a CSW publishing client ('Publish Metadata') would be straightforward.
>
> Such a feature would be very much appreciated. Would you think of shipping a CSW server (e.g. pyCSW) with a QGIS installation / make that a dependency for a plugin or do you think of an interface to Metadata catlogue software like (from the group of OSGeo tools) GeoNetwork. The latter - which probably would be comparable with this solution in the proprietary world: https://www.geocat.net/bridge/ - would be nice, because it would a) improve interoperability between OSGeo projects, and b) help in central metadata management of an organisation (while the former is probably mor beneficial for smaler companies or single users which do not operate something like GeoNetwork)!
> Otherwise, a way to get metadata from QGIS published (e.g. in GeoNetwork), would be XML-import...
>

Optionally both.  The default could be loosely coupled using the CSW endpoint and all is done via CSW-T.  A user could manage/publish their metadata with a selected CSW of their choosing/configuration.

The other option would be to ship pycsw as the QGIS CSW server to allow users to easily stand up their own CSW.  pycsw is Python and can be embedded seamlessly into downstream apps with Python support (like QGIS).

..Tom


More information about the Qgis-developer mailing list