Friendly UI for changing Library path (moving location)

[Teifun2]

Currently it seems impossible to Rename an existing library without having to "re-index" everything.

That means you loose all tags an other Metadata that was already added to the existing models in this library.

It would be greate if there would be a way to

• either rename the folder on disk and then edit the folder Path in the admin tool (which is not working). I also am not sure if this is possible as i am not sure how the metadata is attached to the models, and the folder path might have something to do with it, which would make this much more complicated.
• or give the option to provide a library name that is not related to the Library Path and that can be changed at will. This would be just for better usability in the frontend.
• or give the option to move models from library to library while not using the "organize" path but keep the existing file path relative to the library. <- This would also be a greate improvement if somone would like to restructure their libraries after the fact, without loosing their existing folder structure.

[Floppy]

Great points. I moved a whole load of things from one library to another and accidentally reorganised them at the same time, so I know where you're coming from.

[Floppy]

Now that #860 has added "problems", this is even more useful. A missing library will be flagged as a problem, which then the user could fix if there was an editor for the library.

[mmontminy]

Maybe provide an option to "export" the db to xml or json files in each model's folder with the model specific metadata. A scan would prefer that data if found. This provides a filesystem level backup of the database, as well as making it easier to move a model from one place/library to another without having to re-do all the metadata. This would fit well into the bulk-edit ability. Similar to Organize, have an Export function. You can bulk-edit/export only those models needed. I wouldn't expect the backup file to be automatically kept in sync with the database, it should be a manual export. That way if you made a huge bulk-edit mistake, you'd have the xml/json files to revert from.

[Floppy]

@mmontminy you've read my mind there, that's something I was wondering about too. Very interesting to know it might be something others would find useful.

[ksuquix]

Theoretically all you'd really need is the model id in a file? All the metadata in the database is tied to the model id, so finding a model in a different location is just a matter of repairing the path / library / etc.

Now... if you're moving directories between completely different instances of van_dam, a more complete export would be needed.

[ksuquix]

I think I solved the use-case of renaming libraries with PR #1037

I was able to do this in my libraries mount: mkdir miniatures mv * miniatures

Then in advanced interface, add /miniatures to the path for the library.

All seems to be happy afterwards without any issues.

This is obviously a dangerous operation if you mess it up, but it seems to work.

[Floppy]

So, @ksuquix has enabled library path and name editing in admin, which is one aspect of this. I've separated out the bug with changing path when moving between libraries into #1039, which means this issue can now slim down into a long-term enhancement request for user-friendly way to change the name without using the advanced admin.

[Floppy]

I think given it's possible now and this is just about making a friendlier UI, this issue becomes less urgent?

[ksuquix]

Original request gave 3 potential solutions, #1037 provided one of them.

What about creating a "Friendly UI" low priority enhancement, and also a low priority "give libraries independent names" enhancement, then closing this one?

[Floppy]

That sounds sensible. It's easy to get lost in long issue histories.

[ksuquix]

Tweaked the title a bit, so this issue is now just down to a friendly way of relocating a library (changing the path). #1037 #1039 #1070 address the other aspects.