Bug 192024 - Smart sidecard files handling
Summary: Smart sidecard files handling
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Sidecar (show other bugs)
Version: 1.0.0
Platform: Debian stable Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-08 12:28 UTC by Michal Thoma
Modified: 2020-08-30 15:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.1.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Thoma 2009-05-08 12:28:06 UTC
Version:           0.10 (using KDE 4.2.2)
OS:                Linux
Installed from:    Debian stable Packages

Most raw conversion tools used nowdays creates sidecard files where the conversion parameters are stored (i.e. RawTherapee, UFRaw).

Unfortunately all image cataloguing tools including Digikam ignores these sidecards so when the image is copied or moved to another location via Digikam, developement parameters are lost in the process.

It would be fancy to have possibility to define sidecard files which will be treated as the part of the image file and moved&copied with that.

Naming pattern for sidecards is invariably rather simple - for "imgp001.dng" the sidecars would be "imgp001.xxx" or "imgp001.dng.xxx". So in fact only extension matters (PP2 for RAWTherapee and so on.)

Also displaying some icon as an indication that image has sidecard would be fancy.

Right now I defined my RawThreapee sidecard as image file so at least I can see it's there, though having smart sidecard handling would be much easier.
Comment 1 Mikolaj Machowski 2009-05-10 21:45:09 UTC
In terms of organization it depends on Bug 126149 but this report is less specific. Bug 126149 is precisely about RAW+JPEG and this is about all files with the same name and different extensions. Note: this is different than photo-stacks where user should be able to group similar photos.
Comment 2 caulier.gilles 2010-06-07 10:03:16 UTC

*** This bug has been marked as a duplicate of bug 220545 ***
Comment 3 caulier.gilles 2020-08-30 15:40:37 UTC
Fixed with bug #220545