Version 4.0.2

GeoNetwork 4.0.2 release is a minor release but adds a better multilingual support which may require some changes in your installations:

Database migration

With the possibility to restore deleted record, catalog maintainer has to update the database with the following migration SQL script.

Index migration

Index migration is only required if you created custom facets configuration in the admin or created custom Kibana dashboards. Changes are related to name or structure changes in index fields due to the improvement made for multilingual record support. The changes affect the following type of fields:


codelist_ is now cl_ and is an object composed of:

So characterSet was:

codelist_characterSet: [
codelist_characterSet_text: [
codelist_characterSet_text_langeng: [

and is now:

cl_characterSet: [{
  key: "utf8",
  default: "UTF8",
  langeng: "UTF8",
  link: ""

So if using codelist_characterSet_text in a facet, use cl_characterSet.default with this new version.


The allKeywords field is now only used for rendering (not for query) to limit the total number of field and avoid some errors on large catalogues.

Use the per thesaurus fields which were named thesaurus_geonetwork+external/local+type+thesaurusid and are now th_thesaurusid. The field is also an object composed of:

thesaurus_geonetworkthesaurusexternalthemeeeatopics: [
  "Land use",
  "Biodiversity - Ecosystems",

and is now:

th_eea-topics: [{
  default: "Biodiversity - Ecosystems",
  langeng: "Biodiversity - Ecosystems",
  link: ""
  default: "Policy instruments",
  langeng: "Policy instruments",
  link: ""

Topic category

topic is renamed to cl_topic and has the same structure as a codelist.


geotag is now stored in the template field for keyword types ie. keywordType-place

For more details check Configuring search fields and Configuring faceted search.