https://bugs.kde.org/show_bug.cgi?id=521514
Bug ID: 521514
Summary: Would like to add and delete tags from command line.
Classification: Applications
Product: digikam
Version First 9.1.0
Reported In:
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Portability-Interroperability
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
DESCRIPTION
The long and short of the request is wanting to add or delete a tag for a given
file (or a given uniqueHash) from the command line. I'll go a bit into my use
case below though.
EXPECTED RESULT
cli tag manipulation by digikam
SOFTWARE/OS VERSIONS
Windows 11
ADDITIONAL INFORMATION
The company I work for has 10s of thousands of pictures that I'm primarily
using digikam itself to tag with. (Awesome software, btw, thank you for your
hard work!)
To actually consume those files into our workflow I've wrote a custom image
browser which interfaces with digikam's database for tags and paths, though I
treat digikam's db as strictly read only from my side. As I consume I'll
occasionally discover I need to correct something or apply a blacklist tag.
Naturally, that means the cumbersome steps of loading digikam, drilling down to
find the exact file in the album, applying corrections, and manually refreshing
within my image browser. None of those steps are hard, of course, but they are
tedious for one-off operations.
It would be nice if I could send a command to digikam to do very basic tag
manipulation for either a specified file or all known (and existing) locations
of a uniqueHash.
Something sorta like this:
```
digikam --delete-tag "Country/City/Paris" --uniqueHash "abc123"
digikam --add-tag "Country/City/Berlin" --file "c:\pics\Berlin.jpg"
```
The expectation here is that digikam would do all of its normal
database/file/sidecar manipulations that the UI would normally do, with
whatever normally configured settings, but without actually loading the UI.
The other possible solution that would work as an interim solution is a
`digikam --open "file.jpg"` that just opens digikam at that exact file so the
tedium of re-finding the file can at least be skipped.
Thanks in advance!
--
You are receiving this mail because:
You are watching all bug changes.
