After changing metadata of nonSpatial Dataset its converted to geo Dataset

[mwallschlaeger]

When uploading a dataset as non spatial dataset and editing the metadata of the dataset. The dataset is converted to a spatial dataset

[gannebamm]

@ridoo @matthesrieke please check if this is still valid

[ridoo]

@gannebamm I expected such tickets to appear here: https:/orgs/GeoNodeUserGroup-DE/projects/1/views/4

I will have a look at them once everything from 4.1.0 has been merged, and will add bugfixes if the issue is still valid

[ridoo]

Investigation result: The non-spatial dataset is not converted to a spatial one. The link back to the dataset is using the /dataset route instead using the /tabular one. The metadata editor seems to be using the old Django templates.

[ridoo]

Correction .. it is indeed converted to spatial-dataset, The /tabular route works for normal /datasets so it appeared to me to be a routing issue on the first glimpse. I will have a deeper look.

[ridoo]

The issue is caused by the default resource_manager which is called from layers/views.py#dataset_metadata. The non-spatial importer handler creates a custom resource manager by intent, to avoid conflicting steps when GeoNode tries to sync/handle spatial resources at GeoServer (tiles, styles, gwc, ..).

@gannebamm @matthesrieke It seems that the metadata editor was not tested thoroughly (at least by me), and turns out to be a blind spot for further integration issues.

[ridoo]

Note: I have hidden off-topic comments with regard transferring the issues to this repository