https://bugs.kde.org/show_bug.cgi?id=523759
--- Comment #3 from Roland <[email protected]> --- Hey guys My post wasnt worded as flexibly as it could have been. I didnt mean- please create a symbolic link creation/destruction engine. Im talking about similar functionality leveraging tech you already use in other contexts. So a better description might be: user-managed album pins: lightweight, database-only shortcuts to existing albums, shown in a dedicated workspace tree (e.g. near the top of Albums). So core functionality would be: Create/tear down pins freely; pins do not alter the filesystem. Click a pin → view target album contents. Drop onto a pin → move/copy into the target album (same as dropping on the real album). Optional local pin label; cannot rename the real album via the pin. Delete pin ≠ delete album/files. “Go to real album” action. The core problem is that Saved Searches/Tags are read/filter oriented and sit outside the Album drop model that filing workflows require. With anything like larger collections, the trees are always going to be large and will see 3-5 layers (i.e Sports\Football\NFL\Teams\Broncos and then a slew of folders at that level which themselves could have a bunch (i.e. \Players could have 100 folders under it, per team). Categorizing/filing an imported batch of content from a gameday is a HUGE pain right now. I end up having to create sort of manual versions of this- where there might be a \Broncos\_New Content for source folder. But even there, if one photo is a generic practice day image, an another is a player that is nested under Players\100 folders, its more difficult that it should be. it is dramatically faster to sort/file content into specific categories before tagging, and then, if needed, deconstructing the folder structure (i.e. players can be combined, or merged into Eras, since the player name can be assigned as a tag or Description, along with a year or etc etc. -- You are receiving this mail because: You are watching all bug changes.
