Improvements on resource cloning

[mattiagiupponi]

Actual Behavior

When cloning, the additional information are not cloned (keywords, perms, regions, metadata etc...) ideally the resource should take with itself all this information.

Expected behaviour

Cloning creates a new, fully independent resource. It gets its own UUID, its own permissions record, and, for a Dataset, its own copy of the data on the GIS backend. Ownership of the clone is transferred to whoever triggers it, regardless of who owned the source.

What is carried over from the source:

• Metadata: title, abstract, category, license, and every other descriptive field
• Keywords, regions, and thesaurus keywords
• Contacts and their roles (point of contact, metadata author, and so on)
• Geographic access limits (per-user and per-group)
• Permissions: the clone starts with the same permission spec as the source, not the default permissions a newly created resource would get
• Linked resources (e.g. a Map's linked Datasets)
• Type-specific data: a Dataset's attribute table, a Map's layers, and the underlying files/assets

What does not carry over:

• The owner, which becomes the user who triggered the clone
• The featured flag, always reset to off on the clone

Because the clone owns its own copy of everything above rather than sharing rows with the source, deleting the source resource afterward does not affect the clone.

Specifications

• GeoNode version: master / 5.1.x
• Installation type (vanilla, geonode-project):
• Installation method (manual, docker):
• Platform:
• Additional details: