Emanuele Tajariol

@afabiani is there a way to fix the existing maps? I guess that a script would be useful here.

I see that `ResourceBase` already contains lots of "big" metadata fields that are seldom used. Being `ResourceBase` one of the main classes in the whole model, it is often queried,...

@bhavin2897 since it's quite difficult to create a unit test for such an error, I guess the best way to deal with the possibile fix is to apply it in...

Also the trees of `LOCALE_PATHS` are put in the backup zip and then restored.

Also `static_dirs` and `static_root` should be excluded.

> Does the proposal prevent users from changing metadata if the original metadata was uploaded and preserved? No:  Part of the proposal is about to only notify the user...

Some comments from another issue referencing this topic: - https://github.com/GeoNode/geonode/issues/11494#issuecomment-1723335481 by @giohappy > @gannebamm at the moment the idea is just to implement the simple relationship model. We can extend...

I would move back the label from `feature` to `bug` since `dc:subject` is one of the core CSW queriables. Pls note that GeoNode [declares `dc:subject` as a queryable](https://development.demo.geonode.org/catalogue/csw?request=GetCapabilities&service=CSW&version=2.0.2); having GeoNode/pyCSW...

This is still open, since the initial tests showed that the REST packets were serialized in a completely different format using the 2 different libraries.

Some options here: - replace the current GUI with an adapted version of the mapstore GUI for editing GeoFence rules; - remove the GUI, and make GeoFence standalone available via...