François Van Der Biest

testuser still features an "l" field with an EWKT, was previously used with geofence - but I think this is not relevant anymore. https://github.com/georchestra/georchestra/blob/b166236d8808ff8ed8ab3778f56bf510a11e9c30/ldap/docker-root/georchestra.ldif#L25

When bootstraping a geOrchestra geonetwork, we do not have the same features as an upstream version with the same version. Eg when using https://github.com/geonetwork/geonetwork-ui/blob/main/support-services/docker-compose.yml we get some nice features eg:...

Areas for orgs should be optional

2

This is a pain to configure when there's no use for areas ...

console - Organization a mandatory field ?

1

Even though https://github.com/georchestra/datadir/blob/37e0bcb0be2b9b3b8d372f2939e010b393f20f99/console/console.properties#L142-L145 says that org & orgType are mandatory (by default), the console does not require an Org to be filled in forms, eg  In addition, we should...

header - does not show testadmin's name

1

 tested on master with the docker composition

datafeeder - support non-geo file types

7

CSV being the first one to consider

The documentation on GeoNetwork groups synchronisation (either with geOrchestra roles or geOrchestra orgs) which is located in https://github.com/georchestra/georchestra/blob/master/docs/geonetwork-synchronization.md is outdated, since we now have a dedicated setting to this end:...

Discussed with INRAE / IRD / CIRAD : the sense of "referent" is wider than "manager", and less hierarchical. Makes more sense to them. WDYT ?

defaults.properties has `enableRabbitmqEvents` and `analyticsEnabled` This might require some homogeneization (eg `enableRabbitmqEvents` and `enableAnalytics` or `rabbitmqEventsEnabled` and `analyticsEnabled`) before the 24 release is out.

header - rename the "maps" tab

1

MapStore on /mapstore/#/home offers more than just maps With the recent improvements, there are now stories, dashboards, contexts ... I'd propose to rename the "maps" header tab into "reuses" or...