Externalization of the catalog metadata template

[mattiagiupponi]

Externalization of the catalog metadata template

Overview

At the moment the catalog XML template is hardcoded and requires a manual change in order to change the template.
This proposal, meant to externalize the metadata XML as a configuration variable in order to let the user change the template without touch the code

Proposed By

@mattiagiupponi

Assigned to Release

This proposal is for GeoNode 3.x.

State

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

Motivation

The benefits include letting the user/developer change the catalog metadata XML without touch the code, by changing an environment variable

Proposal

A new settings variable has been added in the settings.py named CATALOG_METADATA_TEMPLATE. By default, it takes the full_metadata.xml template in order to keep the backward compatibility
In settings.py this line has been added

CATALOG_METADATA_TEMPLATE = os.getenv("CATALOG_METADATA_TEMPLATE", "catalogue/full_metadata.xml")

The code can be easily called with

settings.CATALOG_METADATA_TEMPLATE

The catalog variable is available also in the context_processor in order to let also the template read the value from the variable.
Example from transaction_insert.xml

{% include CATALOG_METADATA_TEMPLATE %}

Backwards Compatibility

Since the default value is the old template, is totally compatible

Future evolution

Explain which could be future evolutions.

Feedback

Update this section with relevant feedbacks, if any.

Voting

Project Steering Committee:

• Alessio Fabiani:
• Francesco Bartoli:
• Giovanni Allegri:
• Simone Dalmasso:
• Toni Schoenbuchner:
• Florian Hoedt:

Links

• Pull Request