Here is a proposal to make a first release of version 4.0.0. This version has been tested a lot since its first alpha release in April 2020 mainly in the context of 2 projects: EEA and Metawal which have been the main supporters of this work. Also other organizations like BRGM, Ifremer, JRC started tests on this version and probably others … It is already used in production systems since early September and supports the main user needs with significant improvements on the search and its configuration. Users can search/map/edit/manage the catalog and use the core schemas dublin-core/ISO19139/19110/19115-3.
So this proposal is about:
Release a first 4.0.0 version
Clearly highlight that some of GeoNetwork 3 features are not supported (see https://github.com/geonetwork/core-geonetwork/issues/4727). So before migrating, users should check the list if they have specific needs. Search protocols and multilingual support are probably the main limitations for now.
I think it is a good idea and a first step to move forward to the microservices architecture.
For a while, while the missing features are implemented in version 4.0, it will be required to maintain 3.10 (or release 3.12). But releasing 4.0.0 I think it will be beneficial to get support to implement the missing features.
Something to check, in case it’s not done yet, it’s to provide a Docker composition integrating ElasticSearch and some update the schema documentation about the changes required for the new version (afaik it’s mostly related to the indexing).
I think it is a good idea and a first step to move forward to the microservices architecture.
For a while, while the missing features are implemented in version 4.0, it will be required to maintain 3.10 (or release 3.12). But releasing 4.0.0 I think it will be beneficial to get support to implement the missing features.
Something to check, in case it’s not done yet, it’s to provide a Docker composition integrating ElasticSearch and some update the schema documentation about the changes required for the new version (afaik it’s mostly related to the indexing).
Here is a proposal to make a first release of version 4.0.0. This version has been tested a lot since its first alpha release in April 2020 mainly in the context of 2 projects: EEA and Metawal which have been the main supporters of this work. Also other organizations like BRGM, Ifremer, JRC started tests on this version and probably others … It is already used in production systems since early September and supports the main user needs with significant improvements on the search and its configuration. Users can search/map/edit/manage the catalog and use the core schemas dublin-core/ISO19139/19110/19115-3.
So this proposal is about:
Release a first 4.0.0 version
Clearly highlight that some of GeoNetwork 3 features are not supported (see https://github.com/geonetwork/core-geonetwork/issues/4727). So before migrating, users should check the list if they have specific needs. Search protocols and multilingual support are probably the main limitations for now.
I’m happy to vote +1 for releasing version 4, provided we do maintain a 3.x branch until 4 contains all the missing features.
All the best
Jo
···
Jo Cook
t:+44 7930 524 155/twitter:@archaeogeek
Please note that currently I do not work on Friday afternoons. For urgent responses at that time, please visit support.astuntechnology.com or phone our office on 01372 744009
Thanks for the proposal! To facilitate progress and involvement from other users it can indeed be a good idea to make a v4.0.0. Indeed it wil very important that the limitations are highlighted (as well as the benefits) so users can make a proper selection. These things should be prominent in the download page and in the release notes I think.
Here is a proposal to make a first release of version 4.0.0. This version has been tested a lot since its first alpha release in April 2020 mainly in the context of 2 projects: EEA and Metawal which have been the main supporters of this work. Also other organizations like BRGM, Ifremer, JRC started tests on this version and probably others … It is already used in production systems since early September and supports the main user needs with significant improvements on the search and its configuration. Users can search/map/edit/manage the catalog and use the core schemas dublin-core/ISO19139/19110/19115-3.
So this proposal is about:
Release a first 4.0.0 version
Clearly highlight that some of GeoNetwork 3 features are not supported (see https://github.com/geonetwork/core-geonetwork/issues/4727). So before migrating, users should check the list if they have specific needs. Search protocols and multilingual support are probably the main limitations for now.
I strongly encourage this release, this is a great step forward, and it’s working very well.
It’s mandatory to move forward with Elastic Search support, hopefully the release will create a good momentum for people to use it, test it and fund missing features.
This is going along with all the work we are doing with geonetwork-ui and geonetwork-microservices so it makes clear sense to me.
I think it is a good idea and a first step to move forward to the microservices architecture.
For a while, while the missing features are implemented in version 4.0, it will be required to maintain 3.10 (or release 3.12). But releasing 4.0.0 I think it will be beneficial to get support to implement the missing features.
Something to check, in case it’s not done yet, it’s to provide a Docker composition integrating ElasticSearch and some update the schema documentation about the changes required for the new version (afaik it’s mostly related to the indexing).
Here is a proposal to make a first release of version 4.0.0. This version has been tested a lot since its first alpha release in April 2020 mainly in the context of 2 projects: EEA and Metawal which have been the main supporters of this work. Also other organizations like BRGM, Ifremer, JRC started tests on this version and probably others … It is already used in production systems since early September and supports the main user needs with significant improvements on the search and its configuration. Users can search/map/edit/manage the catalog and use the core schemas dublin-core/ISO19139/19110/19115-3.
So this proposal is about:
Release a first 4.0.0 version
Clearly highlight that some of GeoNetwork 3 features are not supported (see https://github.com/geonetwork/core-geonetwork/issues/4727). So before migrating, users should check the list if they have specific needs. Search protocols and multilingual support are probably the main limitations for now.
Very huge rework, thank you and to all the ones involved in this!
As noted by Jeroen anyway, differences between 3.x and 4 should be clearly pointed out.
Cheers,
Emanuele
···
Regards,
Emanuele Tajariol
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.
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.
+1 from me - reading through the alpha docs, this is a bunch of impressive improvements bringing many useful new features and enhancements. I know organisations who will be keen to get these new features into their catalogues to help users find what they need.
Here is a proposal to make a first release of version 4.0.0. This version has been tested a lot since its first alpha release in April 2020 mainly in the context of 2 projects: EEA and Metawal which have been the main supporters of this work. Also other organizations like BRGM, Ifremer, JRC started tests on this version and probably others … It is already used in production systems since early September and supports the main user needs with significant improvements on the search and its configuration. Users can search/map/edit/manage the catalog and use the core schemas dublin-core/ISO19139/19110/19115-3.
So this proposal is about:
Release a first 4.0.0 version
Clearly highlight that some of GeoNetwork 3 features are not supported (see https://github.com/geonetwork/core-geonetwork/issues/4727). So before migrating, users should check the list if they have specific needs. Search protocols and multilingual support are probably the main limitations for now.
+1 from me - reading through the alpha docs, this is a bunch of impressive improvements bringing many useful new features and enhancements. I know organisations who will be keen to get these new features into their catalogues to help users find what they need.
Here is a proposal to make a first release of version 4.0.0. This version has been tested a lot since its first alpha release in April 2020 mainly in the context of 2 projects: EEA and Metawal which have been the main supporters of this work. Also other organizations like BRGM, Ifremer, JRC started tests on this version and probably others … It is already used in production systems since early September and supports the main user needs with significant improvements on the search and its configuration. Users can search/map/edit/manage the catalog and use the core schemas dublin-core/ISO19139/19110/19115-3.
So this proposal is about:
Release a first 4.0.0 version
Clearly highlight that some of GeoNetwork 3 features are not supported (see https://github.com/geonetwork/core-geonetwork/issues/4727). So before migrating, users should check the list if they have specific needs. Search protocols and multilingual support are probably the main limitations for now.
