MetadataExplorer refactor and GeoNode API service integration

[allyoucanmap]

MIP - MetadataExplorer refactor and GeoNode API service integration

Please check out the MapStore contributing rules at:
https://github.com/geosolutions-it/MapStore2/wiki/Contributing-to-MapStore

Overview

This proposal focuses on the refactor of the MetadataExplorer plugin components to review:

• name of plugin, proposed name Catalog
• layout of the plugin, using resources catalog components as much as possible
• support of GeoNode API as new service

Proposed By

Stefano Bovio (@allyoucanmap)

Assigned to Release

This proposal is for MapStore 2026.01.00.

State

• Under Discussion
• In Progress
• Completed
• Rejected
• Deferred

Motivation

At the moment, MapStore has a catalog plugin called MetadataExplorer with an outdated style and theme that could be refactored and reviewed to be more customizable to be used by MapStore and the GeoNode client. This proposal takes the introduction of the GeoNode API service as an opportunity to review the layout and functionalities. In addition we could remove the custom catalog in GeoNode taking advantage of the MapStore one

Proposal

The refactor of the current layers catalog plugin should maintain the current features:

• Support registration of multiple services (WMS, WFS, WMTS, TMS, …)
• Advanced configuration of the services settings
• Managing multiple services (add/remove/update actions)

Additional functionalities will be included after the refactor of the core layers catalog plugin:

• Style and theme improvement based on the current homepage grid system components
• Configurable layout as a side panel or dialog component
• Introduction of the GeoNode API catalog as an official service type
• Search system improvement with filtering support only for specific service types, initially only for the GeoNode API catalog
• Configurable side section with a JSON file to represent the category tree. The category tree can have nested folders, with leaves acting as catalog filters. These filters will be combined with the filters selected at the top of the main area.

MockUps

The following figures represent preliminary mockups of the layers catalog. The structure and components' position may change during the initial design phase and/or during the development, based on the needs of the different services supported.

Preliminary notes about the UI/UX:

• A section to manage additional services should be included. A button on the top right side of the header could allow the user to access this section
• Filters management could be implemented reusing the existing panel component used in the main catalog
• Card layout and related actions can be enhanced and extended, taking into account that some catalogs could include a dataset with multiple OGC services. In particula,r selection and add actions will be reviewed during the development

Screenshots inside MapStore:

• Panel list layout in MapStore

• Search filter will show a clear button when text is entered

• Allow to select multiple layers and add them

• It would be possible to show full content of text using the card options menu list

• The split button will be presented when multiple type of layers can be included from a single record

• The dialog layout will be available via configuration (localConfig or context cfg)

Screenshots with GeoNode API integrations:

• Dialog layout composed using MapStore catalog components

• Dialog layout showing the filter panel open

Backwards Compatibility

The new plugin will replacing the MateadataExplorer and for this reason checks to migrate the existing context will be included if needed.
The migration guidelines will include additional information in case the localConfig.json configuration will introduce changes for the plugin

Future evolution

This refactor will ensure to keep the capabilities extension of catalog allowing to add additional services in the future.

Feedback

Update this section with relevant feedbacks, if any.

Voting

Project Steering Committee:

• @tdipisa: +1
• @offtherailz: +1
• @allyoucanmap: +1
• @MV88: +1
• @giohappy: +1

Links

Remove unused links below.

• Email Discussion
• Pull Request
• Linked Issue

[tdipisa]

+1

I really like it @allyoucanmap but sections like Backwards Compatibility and Future evolution shouldn't be left blank. I imagine that some quick reference text can be provided for them.

[MV88]

+1
maybe we can consider to click on the card to select the layer to add then to the map instead of checkbox or in addition to it.

[offtherailz]

+ 1

here some suggestions

The dialog layout will be available via configuration (localConfig or context cfg).

For this instead of a configuration, I'd prefer an "expand" button. Is more testable and useful for several cases. We can configure initial view if needed, but if not needed, I'd choose one. Let's avoid alternative flags when not stictly necessary

• GeoNode Integration (if not reproducing an existing layout that have to be maintained).
  • Categories UI should be better uniformed with filter UI. I can suggest a left panel with only category browser and + "Advanced search" button below in the panel that adds the other features.
  • Is it possible to apply similar advanced filters also to WMS (e.g. keyworkds ....)?

[giohappy]

+1

The requirements for the left panel have not been clearly identified. We're gathering use cases from users, and one, for example, will probably need a generic Tree of labels where certain nodes (not only leaves) can act as filter values to be combined with the filters available in the main area.
How filters from the sidebar and the main will be combined should probably be configurable (AND or OR).

The tree in the left bar should probably be built from a URL serving the (static or dynamically generated) configuration.

[allyoucanmap]

+1 maybe we can consider to click on the card to select the layer to add then to the map instead of checkbox or in addition to it.

@MV88 yes, clicking on the card is like clicking the checkbox