GeoNetwork UI and microservices codesprint October 2020

When & Where?

• 12th to 16th October (or a couple of days depending on your availability)
• The sprint will be remote but some of us on Tuesday/Wednesday (Olivier, Florent, Christophe, Francois) join at the farm (https://latitferme.bio/), 321, Route de la Mollière, Saint-Pierre-de-Genebroz, Chambéry, Savoie, Auvergne-Rhône-Alpes, France

Who?

• Francois - full week
• Florent - Tuesday, Wednesday
• Olivier - Tuesday, Wednesday
• Christophe - Tuesday, Wednesday
• Michel - Tuesday, Wednesday
• Jose - Tuesday, Wednesday

Sponsors

• EEA https://sdi.eea.europa.eu/

Agenda

The overall idea:

2 topics to make progress on

• https://github.com/geonetwork/geonetwork-microservices
• https://github.com/geonetwork/geonetwork-ui

Microservices

The focus here is to design the organization of the infrastructure (gateway, config), make the project easy to work with (docker container?) and focus on some of the main components:

• Searching app (Elasticsearch endpoint + OGC API Record endpoint)
• Authorizing app
• Formatting app
• Indexing app

The roadmap will be defined in: https://github.com/geonetwork/geonetwork-microservices/projects/1

GeoNetwork UI

Current objective here is to be able to embed easily GeoNetwork in third party application using WebComponents.

<script src=”gn-ui.min.js”/>
<gn-ui-records-list filter=”tag=COPERNICUS” sortBy=”changeDate” size=”10”/>

The work planned is:

• Global requirements (i18n)
• Mockup of the following UC
• UC 1 / Simple list of records
• UC 2 / Search box
• UC 3 / Category entry page (one facet/one icon/one number <> list of records)

Questions:

• Can we webcomponent create a popup over the entire page?
• How to make 2 webcomponent interact (eg. facet list/record list)

The roadmap is defined in: https://github.com/geonetwork/geonetwork-ui/wiki/Roadmap

GeoNetwork UI2

When splitting in microservices, e.g. Public UI, Editor, Admin, Harvesting, Login/personal profile. We want to share common layout aspects between applications. Some applications are based on clientside Angular, some on serverside html generation. Can we adopt a templating technology which can run on client and serverside?

Technologies

• Angular applications
• Generic error pages 403,404,500, html representation should include geonetwork header/footer.
• html-representation of OpenAPI-Records (aka landing pages / no-js interface)

Technology options

• Embed Angular widgets in a serverside rendered html page including header-footer
• Serverside Angular
• Duplicate header/footer
• ...