https://bugs.kde.org/show_bug.cgi?id=523704
--- Comment #5 from Roland <[email protected]> --- Hi Maik So my view on this is that Digikam is not focused on retaining individual file names or operating against them. So far as I can tell, there is no mechanism by which a file name can be written to metadata during import (i.e. as a comment). But it can do the opposite- replace the filename with a caption, a metadata template. It could be done via ExifTool/scripting, but my point is that the system is far more about structure and metadata for context that a specific file name. And I think that is a good thing. You can search via the Album tree by folder name or tag, but not by filename (that requires the advanced search approach). So again, just sort of a suggestion that content is being managed by structure or tag, not file name. What I find a bit strange about the default F2 behavior for a single file is that this mimics Windows, but you dont leverage this for any other object rename (folder, tag). And likewise, its hard to understand how a filename edit can be perceived as persistent. Bulk renames are almost a requirement, because above a certain file count, its the only way to recover a file's position following an error on merge or drag. Likewise, manual name creation that is just "Roland and John skiing,jpg' is going to create bunch of duplicates across folders, and often, the assuming on a merge is that identical filenames are duplicate images where they arent... So that goes sideways fast. So from a workflow perspective, I see a single file name change as a manually-entered value as the exception, not the default. I dont know if I have ever renamed a file manually in this way EXCEPT when there was a bug in the bulk renamer where it created a name array and ended up creating a file name that already existed in a given folder. And that was an exception to the bulk rename process to begin with, so selecting an alternative naming process actually made more sense. Maybe faster to click the root duplicate image and hit F2, but still, that bug is dead (I think), so Im not sure I have used F2 for a single file rename since- But perhaps this could be a preference setting. There are so many weird scenarios, and Im not sure this needs to be complicated. it is inconsistent, which is a bit of a problem. But the reality is that the need for a specific file rename is going to be far less common than the process of bulk renaming where a folder may have only 1 entity (as a function of deduplication, or folder merging, or whatever) -- You are receiving this mail because: You are watching all bug changes.
