[Digikam-devel] [Bug 280825] New: Option to write metadata to original file/sidecar should be separately configurable for each filetype.

[jm]

https://bugs.kde.org/show_bug.cgi?id=280825

           Summary: Option to write metadata to original file/sidecar
                    should be separately configurable for each filetype.
           Product: digikam
           Version: unspecified
          Platform: unspecified
        OS/Version: MS Windows
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: Metadata
        AssignedTo: digikam-devel at kde.org
        ReportedBy: nutstojunkmail at gmail.com


Version:           unspecified
OS:                MS Windows

It'd be far more flexible to be able to configure individually for each file
type where Digikam should write metadata to, rather than having to tediously
mess around with read-only file attribute. 

For example, something like this in the settings dialog:

Digikam should store metadata to...

jpg [*] file [ ] sidecar [*] sidecar if read-only
cr2 [ ]      [*]         [ ]
nef [ ]      [*]         [ ]
gif [*]      [*]         [ ]
tif [*]      [*]         [ ]

Additionally it might be useful to be able to configure where sidecar files for
each file type are stored:

jpg [ ] in same folder as image [*] in subfolder of image folder
cr2 [*]                         [ ]
nef [*]                         [ ]
etc

perhaps with an additional option to configure the name of the subfolder in
which the sidecar files are stored when that option is selected.

Since a lot of users use different file formats at different stages of their
workflow, and have different needs for each of those formats, a
one-size-fits-all-formats approach quickly becomes counter-productive and so I
hope you will consider my request to make Digikam a bit more configurable for
the needs of an individual's workflow.

Reproducible: Didn't try



Expected Results:  
See details.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.