Version 4.0.0

GeoNetwork 4.0.0 release is the first version of GeoNetwork using Elasticsearch as search engine!

By moving from Lucene to Elasticsearch GeoNetwork 4.0.0 offers:

• shared index across catalogs (clustering)
• Improved search experience
• Improved performance for searching and indexing
• Opportunity to add dashboards with Kibana
• Simplify the geonetwork codebase

The Elasticsearch engine supports GeoNetwork core functionality: user can search, edit records and manage the catalogue as usual. Only the searches (and all related protocols) are affected by the change to Elasticsearch. The editor and admin application remains the same.

Before you start:

• Installing the application require to install an Elasticsearch instance (see Installing search platform).

Release highlights:

• The GeoNetwork 4.0.0 release is aligned with GeoNetwork 3.10.4 (see Version 3.10.4).

• The user search experience has been greatly improved.

  For more infromation see the description in Version 4.0.0-alpha.1 and Version 4.0.0-alpha.2.

• Search / Exact match support

  

• Record view / Use timeline to render resource events, temporal extent and vertical extent

  

• Map / Add mouse position

• Indexing / Improvements

• API / Retrieve any extents

• Improve ISO19110 support

• Restrict access to Elasticsearch API

See 4.0.0 issues and pull requests for full details.

Removed features

There remains opportunities to help:

• A number of features that you enjoy in GeoNetwork 3 may not yet be available.
• Multilingual editing is the same, but multilingual search is not yet fully operational.

Read carefully the list of missing features before migrating.

• Search API - RDF (replaced with use CSW with DCAT output format)
• Search API - Z39.50
• Search API - SRU
• Search API - OpenSearch
• Search API - OAI-PMH

• GeoNetwork API features:

• ReportUploads

• XLink: Remove directory entry used in other record

• Lucene: Lucene is no longer available, migrated scripts to Elastisearch API

• Index

• Search on bounding polygons, currently only the geometry is indexed but not used in search

• Admin

• Information about the index - not needed, can be replaced by Kibana admin?

• Schematron rules (See SchematronCriteriaGroupServiceIntegrationTest)

• Search / Statistics and search stat dashboards

• Security

• ECAS not tested

• Harvester

• GeoNetwork 4 can not be harvested using GeoNetwork protocol by GeoNetwork 3 version.

  Mitigation: Use CSW Harvester instead.