Skip to content

GeoNetwork 3.99.0 codesprint April 2020

josegar74 edited this page May 25, 2020 · 75 revisions

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?

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

Searches

  • 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

Dashboards

Cleaning & removal of deprecated stuffs

If we have time ...

Service(8)
service(2)

Selecting the first one doesn't return results, while the second one returns 10 results. Seem an issue of the value indexed (the text value of the codelist). Proposal to index the text value, but using the codelistValue to extract the translation from codelist.xml file, so the indexed value is unified.

Doc

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 this week 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:

Roadmap

https://github.com/geonetwork/doc/blob/4.0.x/source/overview/change-log/version-4.0.0-alpha.1.rst#whats-new

Funding

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

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.

Clone this wiki locally