Feature Branch Status

[ridoo]

Tracks status of feature branches developed in GeoNode SEP 2023.

• Map Layer Infos, LB 2.1.2.3
  • Ticket: Thuenen-GeoNode-Development/Sprints#10
  • PR geonode-mapstore-client: Adds layer info button to map view geonode-mapstore-client#22
  • thuenen_atlas: 6efe1ef
  • Upstream Ticket: Showing metadata per layer in map GeoNode/geonode-mapstore-client#1616
  • Upstream PR: Added table of content to open layer details in map view. GeoNode/geonode-mapstore-client#1661
• Compliant GDI-DE, LB 2.1.1.4
  • Ticket: Thuenen-GeoNode-Development/Sprints#6
  • PR: GDI-DE compliance issues resolved #7
  • thuenen_atlas: 06a5a1f
  • Upstream PR
  • PR for non-local decimals in template
• Copied Metadata, LB 2.1.1.5
  • Ticket: Thuenen-GeoNode-Development/Sprints#7
  • PR: Allows metadata upload to dataset having different UUID  geonode#1
  • thuenen_4.x image build (docker-compose pull 52north/geonode_thuenen:4.x needed)
  • Upstream PR: Allow uploading ISO metadata when UUID is different GeoNode/geonode#11903
• Patch Layer Infos, LB 2.1.1.5 (see also Copied Metadata)
  • Ticket: Thuenen-GeoNode-Development/Sprints#14
  • PR: Patching the attribute set  geonode#4
  • thuenen_4.x image build (docker-compose pull 52north/geonode_thuenen:4.x needed)
  • Upstream Ticket: GNIP 93: Allowing changes to the dataset attributes table via REST API  GeoNode/geonode#10873
  • Upstream PR: @kilichenko-pixida create an upstream PR
• DataCite Download, LB 2.1.1.3
  • Ticket: Thuenen-GeoNode-Development/Sprints#5
  • PR Added DataCite metadata using PyCSW's latest version. geonode#3
  • PR Added datacite metadata download feature. geonode-mapstore-client#27
  • thuenen_4.x image build (docker-compose pull 52north/geonode_thuenen:4.x needed):
    • @ahmdthr wait for pycsw PR to be merged and new alpha version released (contact community for this)
    • @ridoo update submodule once finished
  • Upstream PR: ❓
• Groups Facet, LB 2.1.2.4
  • Postponed as of Implement the Group facet API GeoNode/geonode#11853 (will be part of upstream 4.3.0)
  • Ticket: Thuenen-GeoNode-Development/Sprints/issues/11
  • thuenen_atlas: ❓
  • Upstream PR: ❓
• Push GeoNode Instance
  • Thuenen-GeoNode-Development/Sprints#17
  • thuenen_atlas: ❓
  • Upstream PR

[gannebamm]

With the release v4.2 (https://github.com/GeoNode/geonode/releases/tag/4.2.0), I want to discuss the effort to set this as our target branch/version. With that, we do not have to track master, which is volatile. @ridoo what do you think?

[ridoo]

We are not tracking master but "stable" v4.1.x. However, targeting 4.2.0 definitely makes sense.

Hard to say how much effort this would take without having a deeper look first. GeoSolutions made changes to configuration and structure, and in the end moved things to a different repository using a different versioning scheme for their images. So tracking all the changes will not be straight-forward this time.

I see these todos:

1. Updating 52n repository containing the GeoNode forks (having version tags under our control)
2. Updating the GeoNode blueprint
3. Updating the thuenen_atlas

As you can see, 52n has also things to do here for our own repos (unrelated to thuenen context).

52n could start updating things we would have to do anyway, learn about the change impact, and then doing an update for thuenen related stuff. I would follow a "break and fix" strategy here as of the aforementioned reasons. Do you have a max budget for this in mind? Perhaps it will not be that big issue, after updating our stuff and we can do this by effort.

/cc @matthesrieke
/cc @gannebamm

[ridoo]

@ridoo Postpone https://github.com/Thuenen-GeoNode-Development/Sprints/issues/17 and start with upgrading to 4.2.0

[gannebamm]

Thünen has deployed the latest version (tisdar.dev) and is starting the review process @vineetasharma105 @hvwaldow

[ridoo]

Let me know in case you need help