Bug 207944

Summary: new renaming of pictures
Product: [Applications] digikam Reporter: Michael <Michael.NoSpam>
Component: AdvancedRename-fileAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: wishlist CC: caulier.gilles, languitar
Priority: NOR    
Version: 1.2.0   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In: 2.0.0
Sentry Crash Report:

Description Michael 2009-09-20 08:13:14 UTC 
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Just now I have read that you are going to redesign the renaming functionality for pictures within digikam. Thus I use my chance to ask for a minor enhancement:

Within my workflow I use a simple minded picture naming - only the date plus an appended sequence number like e,g, 2009-08-03_01.jpg (spread among subdirectories YYYY/MM/DD like db/2009/2009-08/2009-08-03/2009-08-03_01.jpg). The directories are created during download from camera. My first step after download is to delete bad/ugly pictures. Then I rename all pictures of the "current" day to get the final filename like 2009-08-03_01.jpg. Now my problem: If - after a while - I'd like to drop or add pictures into that scheme then current renaming fails since it cannot handle renaming if the target filename already exists. E.g. if I delete ..._04.jpg I'd like to get
*_01.jpg --> *_01.jpg
*_02.jpg --> *_02.jpg
*_03.jpg --> *_03.jpg
*_05.jpg --> *_04.jpg
...
Right now one gets error messages that the target files are already existing.

A possible solution idea: Do such renaming in two steps. Within the first step you append some additional string like *_01.jpg.RENAMING onto all files. Within the second step you drop that suffix.

That would solve my "problem" with bulk file renaming. Probabely it's not that easy since you also have to consider abortion during renaming.


Thanks for considering my suggestion,

Michael
Comment 1 Andi Clemens 2009-11-09 12:01:25 UTC 
Yes, aborting is one problem, the other is speed :-) Renaming for example 300 images twice can be slow in digiKam, since the database needs to be updated.
Anyway you are right, we need to manage something like your problem, and I have the same issue sometimes, too.
Comment 2 Andi Clemens 2009-11-09 12:19:58 UTC 
Actually this is more of an general issue, not AdvancedRename. AdvancedRename only delivers the new filenames, but the renaming is done in the background by either KIO slaves (or something on our own in the future?).
The same renaming issue can be found in BQM, AlbumUI and CameraUI, and partially when renaming folders I guess (although we can not rename multiple folders in batch).
So I will change the component to "general"...
Comment 3 caulier.gilles 2011-07-03 13:55:49 UTC 
Andi,

This entry is fixed with 2.0.0 ?

Gilles Caulier
Comment 4 Andi Clemens 2011-07-23 22:32:08 UTC 
Yes this should be fixed, I'll close the bug.