You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@gannebamm
is this still relevant?
are you able to share a public GeoNode URL that I may use as a harvest test target where I can reproduce the problem?
Hi @ricardogsilva
Sorry, I was busy with getting our instance publicly available and will not have time to test this before next week. The URL https://atlas.thuenen.de will provide some datasets as 3.3.x GeoNode instance beginning at 01.04 (this Friday).
Expected Behavior
If I define a GeoNode Unified Harvester to copy resources:

these resources will be accessible by my node.
Actual Behavior
Some resources are not able to get copied and throw keyword errors:

The other resources´ metadata are copied (ResourceBase objects) but the content itself is not present:

Layer resources are not loaded properly as well:

Even though they are part of GeoServer:

But there is an additional
geonode_
in the layers name.Steps to Reproduce the Problem
Specifications
There are many PRs and ISSUEs targeting the new harvester feature (https://github.com/GeoNode/geonode/pulls?q=is%3Apr+harvest ; https://github.com/GeoNode/geonode/issues?q=is%3Aissue+harvester). It was first discussed as part of the GNIP-89 (#7664). Some of the issues I encountered were addressed before (#7947 (review)) but should be fixed by now. I would encourage other users and admins to test this feature more thorough.
The text was updated successfully, but these errors were encountered: