| Summary: | Writing metadata control panel in configuration dialog | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | anttiah |
| Component: | Setup-Metadata | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | caulier.gilles, fest.in, krege, mystra.x64 |
| Priority: | NOR | ||
| Version: | 2.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed In: | 6.2.0 | |
*** Bug 277512 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 265880 *** Fixed with #265880 and not reproducible with 6.2.0 *** Bug 214708 has been marked as a duplicate of this bug. *** |
Version: 2.3.0 (using KDE 4.7.2) OS: MS Windows If I choose "Write to XMP sidecar only" setting in digiKam configuration dialog, I still have to enable: - Save image tags as "Keywords" tags in metadata embedded in files [X] - Save metadata template as metadata embedded in files [X] - and so on... to get these data to be embedded in SIDECARS. HOWEVER disabling option "Write Metadata to RAW files (experimental) [ ]" doesn't disable writing metadata into RAW-file's sidecar. Isn't this a bit unlogical. I mean that, if I have "Write to XMP sidecar" enabled, option "Write Metadata to RAW files" doesn't have any effect! For CLEARER configuration settings couldn't you make a "table" which would have three columns like: 1) Digikam's Database, 2)Embedded in Media file, 3) Embedded in Sidecar file. User could then enable/disable every metadata item for these three files (database, media file or sidecar). So the table would be like this: 1 2 3 - Save image tags as "Keywords" tags... [ ] [ ] [ ] - Save metadata template as metadata... [ ] [ ] [ ] - Save image captions and title in metadata... [ ] [ ] [ ] - Save image timestamps in metadata... [ ] [ ] [ ] and so on... If every data has to be stored in digiKam's database the first column is of course kind of useless. However it makes it superclear for novice Digital Asset Management users in which places every piece of data is actually stored. So it could be left there as "greyed out but enabled", if database storage can't be disabled for any of these metadata settings. This table to fine tune your metadata storage locations could be further evolved by adding tabs for every file type. So user could fine tune metadata settings for every file type (JPG, RAW, MOV, AVI,...) IF he/she wants to! Software settings should be so bullet proof and clear, that a novice user would immediately know where the data goes and what files are modified! I personally don't like if I have to read manual and run several test runs on temporary image files, before I can safely start to use a program. Just my two cents! Reproducible: Didn't try Steps to Reproduce: Start digiKam --> Settings-menu --> Configure digiKam --> Metadata (on the left bar) --> Behavior-tab Actual Results: - Expected Results: - -