GeoNetwork 3.99.0 codesprint April 2020

This sprint will focus on making the first release of GeoNetwork based on Elasticsearch. The version will be named 3.99.0. See https://github.com/geonetwork/core-geonetwork/pull/2830

Where?

• Remote
• Discussion on https://gitter.im/geonetwork/core-geonetwork
• Working place https://github.com/geonetwork/core-geonetwork/tree/es

When?

Monday 20 to Wednesday 22 April 2020

Who?

• Jose Garcia
• Francois Prunayre
• Arnaud De Groof
• Pierre Mauduit
• Anyone else ?

Agenda

• Docker
• Testing and roadmap
• 3.99.0 release

Work summary

Testing & listing missing functionalities (define roadmap for next steps - All)

Build & deploy

• Docker composition for easy deployment (Pierre) https://github.com/geonetwork/docker-geonetwork/tree/es/3.99.0
• Data directory / Copy index definition while initializing external data dir (Francois)
• Prefix for module https://github.com/geonetwork/core-geonetwork/pull/4310 (Jose)
• Schema plugins / Update version to 4.0 (they are not backward compatible with 3.x anymore) (Jose).
• Kubernetes config (Arnaud & Pierre)

Searches

• CSW / Checks (Jose)
• CSW / results_with_summary drop, displayinfo drop
• ES / Index / Temporal coverage using date range type (see https://www.elastic.co/guide/en/elasticsearch/reference/current/range.html) (Francois)

• ES / suggestion / current filter apply (Francois)
• ES / sort / Most recent (to easily find latest created) (Francois)
• Search / Response / Remove op* (Jose)

Index

• Performance improvement : only update fields when no need to reindex all the records (eg. privileges, category, rating, ...)

UI

• Batch editing facet and search
• Associated record / Fix multiple UUID search & fix dataset search
• Style / Search / Facet / Long value not truncated properly (eg. in contact) / relates to .text-ellipsis (Arnaud) https://github.com/geonetwork/core-geonetwork/pull/4616
• UI / Check configuration for facets (Arnaud)
• Style / Search / Results / Button with long links not truncated (Arnaud)
• UI / Check association - service/dataset/parent/source/... (Arnaud)
• Prevent displaying the index not available panel while the page is loaded (Jose)
• Facet, search with nested aggregation (resourceType/format) is down (query is made only with the codelist_hierarchyLevel_text param)

Dashboards

• Dashboard / Restore and improve KB dashboards (Arnaud) - Create a space, Update export.json to new format https://github.com/geonetwork/core-geonetwork/blob/es/es/es-dashboards/data/export.json

If we have time ...

• Add facet on datestamp
• Cleaning & removal of deprecated stuffs (Jose & Francois)
• Hide INSPIRE Themes panel in home page if INSPIRE setting is disabled (https://github.com/geonetwork/core-geonetwork/blob/es/web-ui/src/main/resources/catalog/views/default/templates/home.html#L84) (Jose)
• INSPIRE / Indexing / Turn if off if INSPIRE settings is off. see https://github.com/geonetwork/core-geonetwork/blob/es/schemas/iso19139/src/main/plugin/iso19139/index-fields/index.xsl#L378-L446

Doc

• Documentation for installation (All)

  • https://github.com/geonetwork/doc/blob/3.99.x/source/overview/change-log/version-3.99.0.rst
  • https://github.com/geonetwork/doc/blob/3.99.x/source/maintainer-guide/installing/installing-from-war-file.rst

Release

• Change version to 3.99.x, db migration check, link to doc
• CVF
• Release a GeoNetwork 3.99.0

Questions

Index structure & facet translation?

In GN3 we are using:

• server side translations (eg. codelistTranslator, thesaurusTranslator)
• client side translations

With the move to ES, should we store translations and make aggregations on it?

• • this allows KB to make dashboard on real value and not key

Transifex / How to have resources for 2 versions?

See Juan info about API but no clue how to do this in the UI.

CFV to rename branch es to 3.99.x ?

To be done on Wednesday for PSC approval.

Docker: how does the process to generate and publish images onto the docker official library work ?

GeoNetwork went some time ago through the process to be listed in Docker Hub official images. Once a new proposal was accepted, the author is responsible for keeping their images up-to-date and responding to user feedback. The Official Repositories team becomes responsible for publishing the images and documentation on Docker Hub. Updates to the Official Image follow the same pull request process, though with less review. The Official Images team ultimately acts as a gatekeeper for all changes, which helps mitigate the risk of quality and security issues from being introduced.

About new release:

• Create a new folder for the version in GeoNetwork's official images repo.
• Dockerfiles are updated to get the WAR for that version and tags in generate-stackbrew-library.sh are updated to match the release.
• Once changes are committed generate-stackbrew-library.sh is used to generated the file that Docker official library uses to build the images.
• Create a Pull Request to https://github.com/docker-library/official-images to update https://github.com/docker-library/official-images/blob/master/library/geonetwork with the output from generate-stackbrew-library.sh.
• Docker official images team review the pull request and merge it if all looks fine.
• Docker Hub automatically builds and publishes the new image.

Roadmap

• Level 3 ...
• Harvester / ArcSDE / Set thumbnail using FileStore (Jeeves service removed)
• Search / Statistics (index.search.slowlog?)
• Multilingual support

Funding

The following organizations have provided funding or in-kind contributions towards this activity.

• EEA
• Metawal
• titellus
• Ifremer
• camptocamp
• GeoCat
• Spacebel

If you are interested in financially supporting this activity via OSGeo: PayPal Donation or Sponsorship is appropriate. The OSGeo treasurer can provide invoice for your records.