[digikam] [Bug 370553] New: Adjust date - not possible to update "digikam timestamp"

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=370553

            Bug ID: 370553
           Summary: Adjust date - not possible to update "digikam
                    timestamp"
           Product: digikam
           Version: 5.1.0
          Platform: Fedora RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: BatchQueueManager-Tool-TimeAdjust
          Assignee: [hidden email]
          Reporter: [hidden email]

Since version of DK 5.0, it is not possible anymore to update "digikam
timestamp" only.

This tool has been transferred to BQM. The option "update digikam timestamp",
present in DK 4.x, has been removed (see in red in attached picture).
Therefore it is not possible to update digikam timestamp only.

Note: it is however still possible to use digikam timstamp as a time reference
("timestamp used")

Note: other minor problems with new tool in BQM:
 - option "update digikam timestamp" simply removed from UI -> there is a hole
instead. Other options ("EXIF:original", ...) must be shifted upwards.
- TAB key not working very well (should switch between the different options in
the same order than the UI (from "EXIF:original" to "File last Modified")

Reproducible: Always

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=370553

--- Comment #1 from Nicofo <[hidden email]> ---
Created attachment 101543
  --> https://bugs.kde.org/attachment.cgi?id=101543&action=edit
adjust date/time new UI

Digikam Timestamp option removed below

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=370553

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #2 from [hidden email] ---
I recommend to test with 5.2.0

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=370553

Kristian <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #3 from Kristian <[hidden email]> ---
Still missing with digikam 5.2.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=370553

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|5.1.0                       |5.2.0

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=370553

Maik Qualmann <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #4 from Maik Qualmann <[hidden email]> ---
The digiKam timestamp is updated automatically. This option made sense when the
time adjust tool was an external kipi-plugin. When reading the metadata again,
the digiKam timestamp would be reset to the EXIF / XMP metadata anyway.

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=370553

--- Comment #5 from Nicofo <[hidden email]> ---
(In reply to Maik Qualmann from comment #4)
> The digiKam timestamp is updated automatically. This option made sense when
> the time adjust tool was an external kipi-plugin. When reading the metadata
> again, the digiKam timestamp would be reset to the EXIF / XMP metadata
> anyway.

Some thoughts about this:

QUESTION: digiKam timestamp is updated automatically: to which value: EXIF date
? If so, to be fully coherent, this option should also be removed from the UI
in the "Timestamp Used" fields (and not only in the "Timestamp Updated fields")

OK, good point that digiKam timestamp should now updated automatically.
BUT this is not always the case: if you modify externally the date of the
picture (exif or file's date), the timestamp is not updated, and it is not
possible to update it since the option is not present anymore.

MOREOVER: the minor problems of Comment #1 are still valid

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=370553

--- Comment #6 from Maik Qualmann <[hidden email]> ---
(In reply to Nicofo from comment #5)
> QUESTION: digiKam timestamp is updated automatically: to which value: EXIF
> date ?

Direction is first Metadata -> File creation date.

> OK, good point that digiKam timestamp should now updated automatically.
> BUT this is not always the case: if you modify externally the date of the
> picture (exif or file's date), the timestamp is not updated, and it is not
> possible to update it since the option is not present anymore.

Use read Metadata from File or for a automatically update enable the option
"Rescan file when files are modified" for externally modified files.

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=370553

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED
   Version Fixed In|                            |5.4.0

--- Comment #7 from [hidden email] ---
Following the last coment, we can considerate this file as fixed.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=370553

Nicofo <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
   Version Fixed In|5.4.0                       |
         Resolution|FIXED                       |---
            Version|5.2.0                       |5.3.0

--- Comment #8 from Nicofo <[hidden email]> ---
OK, Thanks for the explanations, I agree with you.

But therefore, as DK timestamp is automatically updated to EXIF, there is no
need to keep the possibility to use it as a reference to adjust the date. This
option should be removed from the "Timestamp used" fields (top of screenshot in
comment #2). And so totally disappear from UI ? (it's an internal variable, not
useful for user I think ?)

Note also there are minor problems in the UI: see comment #1

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=370553

--- Comment #9 from Maik Qualmann <[hidden email]> ---
The DK timestamp may make sense for images that have no metadata.

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=370553

--- Comment #10 from Kristian <[hidden email]> ---
I still have regular problems with digikam's internal timestamp. I adjusted the
time of a movie file with the TimeAdjustTool and everything seems to be fine
(file modified date, etc.) apart from digikam's internal timestamp. Even after
updating every single timestamp exiftool is showing, digikam's timestamp
refrains from being updated and I have no idea how to update it.

$ exiftool -time:all -G1 -a *.MOV
======== 20170402T174944-NikonD7200_matchDateTime.MOV
[System]        File Modification Date/Time     : 2017:04:02 18:48:41+02:00
[System]        File Access Date/Time           : 2017:04:05 21:30:12+02:00
[System]        File Inode Change Date/Time     : 2017:04:05 21:30:12+02:00
[QuickTime]     Create Date                     : 2017:04:02 18:48:41
[QuickTime]     Modify Date                     : 2017:04:02 18:48:41
[Track1]        Track Create Date               : 2017:04:02 18:48:41
[Track1]        Track Modify Date               : 2017:04:02 18:48:41
[Track1]        Media Create Date               : 2017:04:02 18:48:41
[Track1]        Media Modify Date               : 2017:04:02 18:48:41
[Track2]        Track Create Date               : 2017:04:02 18:48:41
[Track2]        Track Modify Date               : 2017:04:02 18:48:41
[Track2]        Media Create Date               : 2017:04:02 18:48:41
[Track2]        Media Modify Date               : 2017:04:02 18:48:41
[Nikon]         Create Date                     : 2017:04:02 18:48:41
[Nikon]         Date/Time Original              : 2017:04:02 18:48:41
[Nikon]         Time Zone                       : +01:00
[Nikon]         Daylight Savings                : No
[Nikon]         Date Display Format             : D/M/Y
[XMP-exif]      Date/Time Original              : 2017:04:02 18:48:41
[XMP-xmp]       Create Date                     : 2017:04:02 18:48:41

digikam still displays the old date before adjusting the time be approx. an
hour...

Therefore, the option to update it manually would be nice.

--
You are receiving this mail because:
You are the assignee for the bug.