Copy / clone resource should clone also the dynamic model about geonode-importer HOT 2 CLOSED

@etj @giohappy
I'm thinking about the cloning of a resource coming from a geo package.
I implemented a clone() method inside the handler which will call an async task that takes care of the work.

There are few issues with the cloning since the actual resource_manager implementation uses the "concrete_manager" to create the geoserver resource and is actually something we cannot do because:

• is not sure that the original file is still there since the option "store_spatial_file" can be set to FALSE and the file is deleted once the upload is finished
• and even if the original file is there, geoserver is not able to load a geo package from the importer and it raises an exception in geonode since is not part of the accepted format

So, actually, we can easily ignore the existence of the gpkg since we can just copy the actual, but we should:

• change the resource_manager so it can skip the call on the concrete manager and set up the resource and have a new alternate

once we have the alternate we can:

• clone the dynamic_model Shema
• clone the dynamic_model fields
• write some SQL to clone the entire table and rename it with the new alternate provided by the creating

My only concern is, The community will accept that the calling of the concrete manager in the resource_manager.copy() will be optional? (activated by default)

from geonode-importer.

As agreed by chat, let's move forward with the proposed changes.

from geonode-importer.