https://bugs.kde.org/show_bug.cgi?id=513884
dede34fr <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from dede34fr <[email protected]> --- Another use case for this, from a slightly different angle: fully unattended photo ingestion. I have a setup where a phone is plugged in over MTP and everything downstream is scripted: files are copied to a staging folder, renamed after the capture date, tagged, and moved into the digiKam collection roots. All of that is already possible without the GUI, because digiKam ships ExifTool (13.58 in 9.1.0), so renaming and writing XMP tags (XMP-digiKam:TagsList) from a script works nicely, and digiKam picks those tags up when it indexes the files. The one link in the chain that cannot be scripted is triggering the maintenance work afterwards. Concretely, two tasks matter most here and are not explicitly mentioned in the original report: 1. Auto-tags assignment (object detection) - the "auto" tag tree 2. Detect and recognize faces Both are configured and working well through Tools > Maintenance, and the settings already live in digikamrc ([Autotags Settings], [Face Management Settings], including model and accuracy). But there is no way to say "run these now, on this album", so newly imported images sit untagged until somebody opens the GUI and starts maintenance by hand. For an otherwise unattended pipeline that is the only remaining manual step. Scanning for new items has the same issue when digiKam is not running: "Album Monitoring" only helps while the application is open. Something like: digikam --maintenance=newitems,autotags,faces [--album=<path>] [--no-gui] reusing the existing digikamrc settings, and exiting with a status code, would be enough - no new configuration surface needed, since the parameters are already persisted by the GUI. Tested with digiKam 9.1.0 on Windows 11 (SQLite database). Happy to test a prototype on Windows if that helps. -- You are receiving this mail because: You are watching all bug changes.
