DashboardUsingES

Date	12 June 2017	Contacts	Francois Prunayre
Status	Motion passed - Done	Release	3.4
Source code	PR 1966 & PR 2023
Supported by	metawal, ifremer

Proposal Type:

• Type: UI, Server
• Module: UI, Server

Voting History

• Vote Proposed: 14 June 2017
• +1 from Jose, Francois

Main goal

This proposal help users to analyze the content and usages of the catalog by adding the capability to create custom dashboards and embed them to the admin console. Main motivations are that current dashboards in the admin console are not usable when having too many records or search requests. Eg. legend with truncated label, browser freeze due to too many series.

For this, an Elasticsearch index is used to:

• index catalog content
• index search statistics. and Kibana is used to create dashboards.

The Elasticsearch node used can be the same as the one used for WFS harvesting.

This proposal fix a number of issues discovered in the search statistics module:

• CSW and q services search were not logged since drilldown queries are used (ie. hierarchical facet)
• Excluded fields property was not used (eg. it was logging all _op* privileges criteria)

See PR for details:

• Catalog content dashboard https://github.com/geonetwork/core-geonetwork/pull/1966
• Search statistics https://github.com/geonetwork/core-geonetwork/pull/2023
• https://www.youtube.com/watch?v=bJl9stYMsG0&t=12s