Bug 512084

Summary: [Feature Request] Implement File Renaming Modifiers 'Range' Logic Into Adjust Time 'File Name Timestamp' Option
Product: [Applications] digikam Reporter: Grant <grantgodfrey>
Component: Plugin-Bqm-TimeAdjustAssignee: Digikam Developers <digikam-bugs-null>
Status: REPORTED ---    
Severity: wishlist CC: metzpinguin
Priority: NOR    
Version First Reported In: 8.8.0   
Target Milestone: ---   
Platform: Other   
OS: Other   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Grant 2025-11-14 15:03:52 UTC 
SUMMARY
It would be really useful if the Adjust Time using the 'File name timestamp' option had the same kind of logic that the file renaming did where I could tell digikam which part of the filename is the year/month/date and then which part is the specific HH:MM:SS, kind of like the file renaming.  Using the existing range modifier option from file renaming is one possibility.  Though it would also be useful if there could be an item separator one where I could tell it, for example, that after the first underscore (_) is always the year, then after the second underscore is the month, etc.  I'm not good enough with programming, but the regex replace might do what I'm thinking of.  So, for example, there could be for each of the different elements of time you could then use a range or regex value to tell digikam where it is in the filename.
Comment 1 Maik Qualmann 2025-11-14 15:12:02 UTC 
No, the goal is to allow digiKam to automatically detect the file date format. This feature has become very popular, even though it was initially programmed simply to see if it was possible. It's now also used as a feature directly in the renaming tool. So, if you have a file date format that digiKam doesn't currently recognize, please post it.

Maik
Comment 2 Grant 2025-11-14 15:22:08 UTC 
Fair enough. It's really good at picking up YYYY_MM_DD in a filename, but filenames I'm trying to pull from then have two underscores, and then HH_MM_SS.

For example, a filename may be [INFORMATION]_[SUB-INFORMATION]_YYYY_MM_DD__HH_MM_SS.  Does that make sense?

e.g. Fall Fotoshoot_Client Name_2025_11_14__14_12_55 which would then be parsed to November 14, 2025 at 14:12:55 on a 24 hour clock.
Comment 3 Maik Qualmann 2025-11-15 07:09:57 UTC 
Your example "Fotoshoot_Client Name_2025_11_14__14_12_55" is already perfectly recognized by digiKam.

Maik