Open nicolasaunai opened 1 year ago
This needs to be discussed, what are you really wanting, and where to store it. (tscat currently has currently no hierarchical relation in catalogues.)
solution could be to add an attribute to catalogs associated to a "path" in the hierarchy, and let the GUI use that information to position the catalog in the tree.
Path Components: fixed attribute - string-list Drag'N'Drop mutliple catalogues and folder - parent is priority Folder representation
What about the trash? Do we present all deleted catalogues in their folder-structure or a flat list. (The Path-element is kept and will used again upon restore)
should users be able to create folders and a kind of tree view for its own local catalogs, as for example exists for distant catalogs on AMDA?