In last TF (https://github.com/orgs/zalf-rdm/discussions/5) we agreed on a way to handle related projects in GN. We agreed on a centralized location (in GeoNode related projects table) to store related projects within our infrastructure. This related projects can be edited or appended via the admin interface of GN and other IT services can interact with this list via the GN rest API.
To reduce manual work on integrating zalf projects, we agreed on using the zalf project database maintained by ITS. To reduce failure potential we decided to integrate the data from the zalf project table using an asynchronous task repeatedly update our project table from the zalf table using the GN build in asynchronous execution environment celery.
depends on: #134
In addition to implement the synchronization this tasks needs to be monitored, which is also part of this issue, if not so create a new issue for that before closing this one
Task Description
In last TF (https://github.com/orgs/zalf-rdm/discussions/5) we agreed on a way to handle related projects in GN. We agreed on a centralized location (in GeoNode related projects table) to store related projects within our infrastructure. This related projects can be edited or appended via the admin interface of GN and other IT services can interact with this list via the GN rest API.
To reduce manual work on integrating zalf projects, we agreed on using the zalf project database maintained by ITS. To reduce failure potential we decided to integrate the data from the zalf project table using an asynchronous task repeatedly update our project table from the zalf table using the GN build in asynchronous execution environment celery.
depends on: #134
In addition to implement the synchronization this tasks needs to be monitored, which is also part of this issue, if not so create a new issue for that before closing this one