Adjusting file last modified date

[Mark Fraser]

The other day I wanted to change the last modified date of some photos in
digiKam 5.5, but using Image > Adjust Time & Date was no longer an option. I
later found something similar in batch conversion tools, but it doesn't seem
to be working - the last modified date doesn't change and it creates a 2nd
image in the folder.

Am I doing something wrong or am I no longer able to change the last modified
date in digiKam?
--
Registered Linux User #466407 http://counter.li.org

[Martin Burnicki-2]

Mark Fraser wrote:
> The other day I wanted to change the last modified date of some photos in
> digiKam 5.5, but using Image > Adjust Time & Date was no longer an option. I
> later found something similar in batch conversion tools, but it doesn't seem
> to be working - the last modified date doesn't change and it creates a 2nd
> image in the folder.
>
> Am I doing something wrong or am I no longer able to change the last modified
> date in digiKam?

Isn't the "last modified" date just the date from the filesystem, i.e.
the last time the image file was written/updated?

So that date should change to the current date/time whenever you edit
the image and save it, or when you change its meta data and have DK
configured write meta data back to the original file instead of the data
base only.

Martin

[Gilles Caulier-4]

The BQM tool is the old Adjust Date and time tool from KIPI. Some code
adapted to BQM.

The only difference that we need to fix is the capability to preview
the date change in list of file from BQM queue. There is already a
file in bugzilla about this subject.

Gilles Caulier

2017-05-21 11:49 GMT+02:00 Martin Burnicki <[hidden email]>:

> Mark Fraser wrote:
>> The other day I wanted to change the last modified date of some photos in
>> digiKam 5.5, but using Image > Adjust Time & Date was no longer an option. I
>> later found something similar in batch conversion tools, but it doesn't seem
>> to be working - the last modified date doesn't change and it creates a 2nd
>> image in the folder.
>>
>> Am I doing something wrong or am I no longer able to change the last modified
>> date in digiKam?
>
> Isn't the "last modified" date just the date from the filesystem, i.e.
> the last time the image file was written/updated?
>
> So that date should change to the current date/time whenever you edit
> the image and save it, or when you change its meta data and have DK
> configured write meta data back to the original file instead of the data
> base only.
>
> Martin
>

[AndriusWild]

In the meantime, exiftool can do that easily.

exiftool -api quicktimeutc=1 "-FileModifyDate<QuickTime:CreateDate" -overwrite_original FILE 

Change QuickTime:CreateDate to whatever tag you want to copy the info from or to a certain value (date).

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-05-21 4:00 AM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Adjusting file last modified date

The BQM tool is the old Adjust Date and time tool from KIPI. Some code
adapted to BQM.

The only difference that we need to fix is the capability to preview
the date change in list of file from BQM queue. There is already a
file in bugzilla about this subject.

Gilles Caulier

2017-05-21 11:49 GMT+02:00 Martin Burnicki <[hidden email]>:

> Mark Fraser wrote:
>> The other day I wanted to change the last modified date of some photos in
>> digiKam 5.5, but using Image > Adjust Time & Date was no longer an option. I
>> later found something similar in batch conversion tools, but it doesn't seem
>> to be working - the last modified date doesn't change and it creates a 2nd
>> image in the folder.
>>
>> Am I doing something wrong or am I no longer able to change the last modified
>> date in digiKam?
>
> Isn't the "last modified" date just the date from the filesystem, i.e.
> the last time the image file was written/updated?
>
> So that date should change to the current date/time whenever you edit
> the image and save it, or when you change its meta data and have DK
> configured write meta data back to the original file instead of the data
> base only.
>
> Martin
>

[Remco Viëtor]

On dimanche 21 mai 2017 15:15:10 CEST Andrey Goreev wrote:
> In the meantime, exiftool can do that easily.
> exiftool -api quicktimeutc=1 "-FileModifyDate<QuickTime:CreateDate"
> -overwrite_original FILE  Change QuickTime:CreateDate to whatever tag you
> want to copy the info from or to a certain value (date).

But make sure you know which tag you need to overwrite...
In this case, the OP wanted to change the date the file was last /modified/.
Your exemple would change the date the file content was /created/, not the same
thing. I'd even think you wouldn't want to touch that particular item at all,
except when you know the date is wrong and you know the correct creation date.

[AndriusWild]

I am pretty sure that FileModifyDate is the system's "date modified". Windows would have "date created" in addition to it but linux does not store "date created". In the example I sent I copy values from QuickTime Date Created of mp4 file to system's file date modified (I do that because digikam uses date modified (file system) as date created (content) for video files. Works for me)

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Remco Viëtor <[hidden email]>

Date: 2017-05-21 7:43 AM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Adjusting file last modified date

On dimanche 21 mai 2017 15:15:10 CEST Andrey Goreev wrote:
> In the meantime, exiftool can do that easily.
> exiftool -api quicktimeutc=1 "-FileModifyDate<QuickTime:CreateDate"
> -overwrite_original FILE  Change QuickTime:CreateDate to whatever tag you
> want to copy the info from or to a certain value (date).

But make sure you know which tag you need to overwrite...
In this case, the OP wanted to change the date the file was last /modified/.
Your exemple would change the date the file content was /created/, not the same
thing. I'd even think you wouldn't want to touch that particular item at all,
except when you know the date is wrong and you know the correct creation date.