[Geoserver-devel] geonetwork sync solutions

Hello,

I am looking in to the different ways to synchronise metadata between geonetwork and geoserver. The only possible way I can find is using harvesters, either from the CSW of geoserver or the OGC services directly. The issue with that is that this makes it impossible to edit the records in geonetwork (even if you forced this, it would be removed with the next harvest), which means in practice that you are limited to the metadata fields that exist in geoserver.

I was wondering if there are any solutions already in existence for situations where you do want to keep your metadata in sync, but still want to take advantage of the additional fields in geonetwork (for example, upload related files to geonetwork). I see two possible ways this could be done:
(1) sync only the fields that exist in geoserver, and leave the rest untouched in geonetwork.
(2) sync from geonetwork to geoserver rather than the other way around

This might lead to some new development in geoserver, so I am also wondering, if there is any solution for this problem that could be to benefit of others?

Thanks for your advise.

Kind Regards

Niels

Hi Niels,

(1) sync only the fields that exist in geoserver, and leave the rest
untouched in geonetwork.

I guess that (1) could be the best solution. GeoNetwork is strongly targeted
at manipulating XML documents, so I guess that the metadata merging should be
done by it.
When GN harvests a resource from an WxS service, it uses an XSL for
transforming the resource returned by the WxS service into a 19139 metadata.

What could be implemented quite easily in GN is, during the harvesting,
creating an XML document holding both the old metadata (if it exists) and the
fresh harvested resource metadata, and then transform this new XML with the
XSL.
The XSL can then be customized so that the output XML (the ISO19139 record
that will be saved into GN) will be created taking info from both the old
metadata (probably the info that you know have been edited in GN, bc the WxS
service does not handle them) and from the harvested resource.

Just my 2¢.

   Cheers,
   Emanuele

Alle 11:02:10 di Wednesday 8 March 2017, Niels Charlier ha scritto:

Hello,

I am looking in to the different ways to synchronise metadata between
geonetwork and geoserver. The only possible way I can find is using
harvesters, either from the CSW of geoserver or the OGC services
directly. The issue with that is that this makes it impossible to edit
the records in geonetwork (even if you forced this, it would be removed
with the next harvest), which means in practice that you are limited to
the metadata fields that exist in geoserver.

I was wondering if there are any solutions already in existence for
situations where you do want to keep your metadata in sync, but still
want to take advantage of the additional fields in geonetwork (for
example, upload related files to geonetwork). I see two possible ways
this could be done:
(1) sync only the fields that exist in geoserver, and leave the rest
untouched in geonetwork.
(2) sync from geonetwork to geoserver rather than the other way around

This might lead to some new development in geoserver, so I am also
wondering, if there is any solution for this problem that could be to
benefit of others?

Thanks for your advise.

Kind Regards

Niels

---------------------------------------------------------------------------
--- Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

Emanuele,

Thanks for your tip. That makes a lot of sense.

A downside to this scenario is that if changes need to be made, for some fields they need to happen in geoserver (if they exist there, because in geonetwork they will be overwritten) while for others they need to happen in geonetwork (if they don't exist in geoserver).

A third alternative I didn't mention yet, is to expand the metadata possibilities of geoserver. We already have a metadata map for resources with unlimited metadata fields written in the catalog, and the ability to map them to the internal CSW. All that is missing really is a GUI for this. A geoserver plugin could add an extra tab page to the layers where additional metadata fields can be edited. A configuration file would specify which additional fields should be exposed and what their type is (file, url, etc...). All of these fields can then be harvested by geonetwork through CSW.

Regards

Niels

On 08-03-17 19:33, Emanuele Tajariol wrote:

Hi Niels,

(1) sync only the fields that exist in geoserver, and leave the rest
untouched in geonetwork.

I guess that (1) could be the best solution. GeoNetwork is strongly targeted
at manipulating XML documents, so I guess that the metadata merging should be
done by it.
When GN harvests a resource from an WxS service, it uses an XSL for
transforming the resource returned by the WxS service into a 19139 metadata.

What could be implemented quite easily in GN is, during the harvesting,
creating an XML document holding both the old metadata (if it exists) and the
fresh harvested resource metadata, and then transform this new XML with the
XSL.
The XSL can then be customized so that the output XML (the ISO19139 record
that will be saved into GN) will be created taking info from both the old
metadata (probably the info that you know have been edited in GN, bc the WxS
service does not handle them) and from the harvested resource.

Just my 2¢.

    Cheers,
    Emanuele

Alle 11:02:10 di Wednesday 8 March 2017, Niels Charlier ha scritto:

Hello,

I am looking in to the different ways to synchronise metadata between
geonetwork and geoserver. The only possible way I can find is using
harvesters, either from the CSW of geoserver or the OGC services
directly. The issue with that is that this makes it impossible to edit
the records in geonetwork (even if you forced this, it would be removed
with the next harvest), which means in practice that you are limited to
the metadata fields that exist in geoserver.

I was wondering if there are any solutions already in existence for
situations where you do want to keep your metadata in sync, but still
want to take advantage of the additional fields in geonetwork (for
example, upload related files to geonetwork). I see two possible ways
this could be done:
(1) sync only the fields that exist in geoserver, and leave the rest
untouched in geonetwork.
(2) sync from geonetwork to geoserver rather than the other way around

This might lead to some new development in geoserver, so I am also
wondering, if there is any solution for this problem that could be to
benefit of others?

Thanks for your advise.

Kind Regards

Niels

---------------------------------------------------------------------------
--- Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

On Thu, Mar 9, 2017 at 5:58 PM, Niels Charlier <niels@anonymised.com> wrote:

A third alternative I didn't mention yet, is to expand the metadata
possibilities of geoserver. We already have a metadata map for resources
with unlimited metadata fields written in the catalog, and the ability
to map them to the internal CSW. All that is missing really is a GUI
for this. A geoserver plugin could add an extra tab page to the layers
where additional metadata fields can be edited. A configuration file
would specify which additional fields should be exposed and what their
type is (file, url, etc...). All of these fields can then be harvested
by geonetwork through CSW.

Yep, I'd love to see that. Maybe with some configuration file to lay out
the editing UI... there are several examples around, one example here:
https://geopaparazzi.github.io/geopaparazzi/forms.html

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------