Version: (using KDE KDE 3.5.1) Installed from: Ubuntu Packages I store both my RAW files and JPG in the same directory. It would be nice if there was a way to let digikam know that the RAW and JPG represent the same image and that when setting tags, making albums, etc, to ignore the RAW image. Also, by doing something like this, if I do go back and regenerate the JPG (which sadly is not as flexible with any Linux program as it is with my Canon software) digikam could know (or ask) to reapply the tags, comments, etc. that are on the RAW image to the newly generated JPG.
I would generalize this whish to have an option to propagate all annotations (i.e., comment, rating and tags) from the JPG to the RAW and vice versa. Currently, I have to annotate both versions of a photo one after the other, and therefore I have to view both in the main view, which consumes a lot of screen real estate and CPU. It would be nice to be able to filter an album to view only the JPGs, and yet have digikam add the edited metadata to RAW also. This is related to Bug 151228, but with a twist: rather than turn off RAW processing, do "smart" automated processing of the RAW when annotating the corresponding JPG (or the other way around). Of course, this smart behavior is not without potential issues. We might not always want to have identical annotations for the different formats of a photo. Hence, the request to make it an option, such as "propagate [or copy] annotations between RAW and JPG versions of a photo".
As part of the mime type quick filter from the status bar, a NoRAWFile filter has been added that allows to hide raw file from all views quickly. Gerhard
A new NoRAWFile was just added: http://bugs.kde.org/show_bug.cgi?id=147427 Together with this filter and an option to apply any changes to the tags/comments of a jpg/png etc., automatically to the corresponding raw file (if it exists) this would solve this wish (Though only in the jpg/png->raw direction). We only have to be careful that when moving files around: also the corresponding raw files should be moved. And this is maybe the place where things get tricky. A more general, saver solution, would be the grouping of images, http://bugs.kde.org/show_bug.cgi?id=121310 RAWs/JPGs could be automatically put into one group and marked as "Share metadata". Personally I would like this approach better. However, this can only be done for digikam >=0.10 as it requires a change in the database.
Ooh, I do like the image grouping idea... I indeed often have a series of photos shot over a short period of time that would have the same comment and tags... except that they might get different ratings (e.g., one is a keeper and the rest are not quite that good), and so in that case, then they would't share all metadata. Still, the default for a group could be to share metadata, to save most of intitial duplicate annotation, and then one could override specific instances of the metadata.
*** This bug has been marked as a duplicate of 151228 ***
Fixed with bug #151228