wish: moving/copying photos in digikam should automatically rename the underlying file if necessary

Bug #411193 reported by N7DR
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
digiKam
Fix Released
Wishlist
digikam (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: digikam

64-bit Kubuntu jaunty; digikam 0.10.0.

It is far too hard to organize one's pictures in digikam if one uses multiple cameras.

The root of the problem lies in the fact that each camera will independently name its image files. So if one imports files from multiple cameras, then the filenames will be duplicated. (The same happens if a camera is reset; often the filenames begin to recycle in that case.) This is not a problem as long as one imports the files into different albums. However, if one has (for example) an album of pictures of flowers, then when one attempts to move a set of images of flowers from camera X into that album, it is frequently the case that many files with the same name from camera Y already exist in the album.

It seems to me that the point of digikam is to organize *photos*, not files, and for many people they will not care about the underlying filename; hence, it would make sense to provide an option so that in the case of a filename conflict, the destination filename can be changed without user interaction (say, by appending "-NNN" where NNN is a number -- that's just a suggestion, though -- to the base filename).

In this scheme, then, if the album "Flowers" already has a file called "DSC0050.jpg" and one attempts to copy/move another image that happens also to be called "DSC0050.jpg" into the album, then digikam would automatically create the file in the "Flowers" album with the name "DSC0050-001.jpg".

This problem is not so bad if one is moving small numbers of files around, but if one is moving hundreds of photos at a time, the current scheme of warning about name conflicts and requiring explicit user involvement is simply impractical.

Revision history for this message
T. Middleton (timtoo) wrote :

There is an option on the import dialog to include the photo timestamp to the filename, as well as adding counter to the end of the filename. The effectively makes it unique in most cases (unless you're shooting with several cameras simultaneously).

I set digikam to rename imported files prefixing them with "photo_" and including a custom format timestamp using the format "yyyyMMddThhmmss". The custom format is the ISO format with punctuation removed. The reason I remove punctuation is that sometimes I have to copy photos to windows and windows won't accept colons in file name.

So my imports end up with filenames that look like this:

photo_20090521T162036-000001.JPG
photo_20090521T162654-000002.JPG
... etc

I like the timestamp in the filename personally; but for users who don't want to set this up, it does seem like a good idea to me to have a simple "auto rename" option that can persist between import sessions... perhaps prompting the user the first time, but once selected never bothers them again (ever).

Revision history for this message
Luka Renko (lure) wrote :

There is already upstream wish for this: have added link to trace it here.

Changed in digikam (Ubuntu):
status: New → Triaged
importance: Undecided → Wishlist
Changed in digikam:
status: Unknown → New
Changed in digikam:
importance: Unknown → Wishlist
Changed in digikam:
status: New → Invalid
Revision history for this message
N7DR (doc-evans) wrote :

Why is this suddenly, nearly two years after filing, deemed invalid? A comment to explain the change of status would have been useful.

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

It is fixed upstream.

Changed in digikam:
importance: Wishlist → Unknown
status: Invalid → Unknown
Changed in digikam:
importance: Unknown → Wishlist
status: Unknown → Fix Released
Rohan Garg (rohangarg)
Changed in digikam (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.