Update path name of nested collections when parent collection is renamed

[grb]

OK. Personally, I don’t really see how it would be possible to implement the other feature request without also implementing the functionality that you have asked for — otherwise, there would have to be a way (other than the path name) for a nested child collection

oldTopCollectionName/childCollection

to know that is should inherit access permissions from a renamed top collection now named

newTopCollectionName

For now, I will leave your feature request stand as a separate topic; however, I have modified the title to make it more clear what you are asking for (old title: “Feature Request – Hierarchical Collection Management”; new title: “Update path name of nested collections when parent collection is renamed”). I also changed the topic’s “app” tag frmo “app:browser” to “app:all”.

 

@jeanp

At a minimum, it should be possible to select and move multiple collections under a master collection to easily restore or reorganize the hierarchy.

Bulk reassignment of organization items from one collection to another is already possible, although perhaps not in the way that you envision. The following feature request should be relevant, though:

Drag and Drop vault items/entries/folders/collections

I have changed the topic title (from “Drag and Drop vault items/entries” to “Drag and Drop vault items/entries/folders/collections”) to reflect the fact that the feature request scope has expanded through the course of discussion (and as a result of previous thread mergers).