After reading the responses I have decided this question should best be posed somewhere else.
Yes
No
You’ve outgrown presets and now you’re entering workflows.
Presets support simple logic and simple controls. Workflows support complex logic and precise control.
The workflow tool for darktable is lua-scripting.
I shoot mostly sports.
From the folder name I can determine if the sport is indoors or outdoors and the venue. Using that I can apply a color calibration preset for the venue if indoors, use the color calibration eye dropper to determine the white balance for one venue which is outdoors and has really bad lights, or stay with as shot.
I use tags when I’m culling for images that are backlit, high contrast, low contrast, etc. and then have processing “recipes” to handle that when the image loads in darkroom.
When an image is loaded into darkroom it is automatically processed to get it to a starting point where I can edit it. My edits are mostly exposure and straightening. Once I’m satisfied, I use a keyboard shortcut to apply the finishing modules.
Or you could start with styles. Programming and scripting are powerful, but not everyone’s idea of fun.
Styles would also allow you to find out how much is actually “fixed” for a group of images. (but you’ll have to do the applying manually or with a script).
Tagging while culling (as @wpferguson describes) may help as well, in that you can quickly select files with a tag and then apply the corresponding style (in lighttable view).
1 Like
Your question was could processing be automated based on the filename and my answer was yes and I talked about how I decoded the path to determine what processing to apply?
Did I misunderstand?
Well, @wpferguson did answer your original question, and the response was “no”.
He then went on to describe a way to (more or less( get what you want through a lua script, describing his workflow.
That answer may not be what you want, but it does reply to the original question.