[digikam] [Bug 196672] Add new option to setup global preference about default album dating

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com
 Status|CONFIRMED   |RESOLVED
   Version Fixed In||8.0.0
 Resolution|--- |FIXED

--- Comment #9 from Maik Qualmann  ---
There is now an option when importing whether to use the oldest, newest or
average album date. With Bug 461069, the album date is now updated depending on
the setting when copying, moving or deleting images.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 196672] Add new option to setup global preference about default album dating

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|setup   |Setup-Views

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 196672] Add new option to setup global preference about default album dating

[Jaakko Luttinen]

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

--- Comment #8 from Jaakko Luttinen  ---
I just came up with a very simple solution that would be sufficient for me.
Instead of needing to modify anything about album date framework, just add a
few options to View -> Sort Albums:

-> By Oldest Image Date
-> By Average Image Date
-> By Newest Image Date

in addition to the existing options:

-> By Folder
-> By Category
-> By (Album) Date

And if the choice is persistent between sessions, that would be just the
sufficient and perfect solution for me. Thus, this would still keep album date
system as it is now, but still allows users to "ignore" that value and sort
based on the album contents. What do you think?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 196672] Add new option to setup global preference about default album dating

[Jaakko Luttinen]

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

--- Comment #7 from Jaakko Luttinen  ---
I don't see the complexity of determining image dates as a part of this issue.
If we assume that digikam assigns dates to images somehow, determining album
date automatically from that info is trivial. And because determining image
dates is something that digikam has to do (and does) anyway regardless of this
feature, I think it can be assumed. For instance, when the images are sorted by
date, there is already some mechanism to figure out what date to use for each
image. Just use the same mechanism here. How are missing timestamps handled
when sorting images by date? Use the same result here. If an album is empty or
none of its images has a date, then the album has no date and that's ok.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 196672] Add new option to setup global preference about default album dating

[bugzilla_noreply]

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

--- Comment #6 from caulier.gil...@gmail.com ---
This is the complexity of this kind of task : introduce changes which do not
have side effect with all workflow already used by DK users.

Typically the album date must be estimated, depending of the album contents.
Automatized date computation can fail in some cases. For ex :

- image has no date => we use file time stamp instead image metadata.
- album has video => currently Exiv2 video metadata do not work has expected.
We will return always the FS time stamp in this case.
- album has XMP sidecar => date can be extracted from this container and if
option is turned on from DK config pannel.
- ... and i forget certainly some other cases here...

So to compute the date album average can be complicated and can give a false
value. Batch processing this kind of task can introduce wrong date in album
properties from database.

To resume : it's not simple task. This is why this entry exist since a very
long time in bugzilla.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 196672] Add new option to setup global preference about default album dating

[Simon]

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

--- Comment #5 from Simon  ---
@Jaakko
I didn't consider the totally dynamic case and that's not what it is today. It
is an actual property, not just caching of something derived from the album
content. I do see your point, such completely dynamic behaviour would actually
be fine by me. However it is a much more intrusive change, and I made bad
experiences with assuming a "normal" workflow - people do all kinds of things.
You could also call adding images with a completely different date later on
"not typical" (at least I never do that).

Well I guess it is moot to discuss this in more detail until someone picks this
up and does it - I added it to my list of things to do when time permits, but
that can mean anything.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 196672] Add new option to setup global preference about default album dating

[bugzilla_noreply]

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

--- Comment #4 from caulier.gil...@gmail.com ---
Simon,

The idea some good too from my viewpoint...

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 196672] Add new option to setup global preference about default album dating

[Jaakko Luttinen]

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

--- Comment #3 from Jaakko Luttinen  ---
One point of the "dynamic" date is that the album shouldn't have any date as
such, only the images have dates. And then, the date of the album is just
computed from the images (oldest, newest or average). If I add/remove images,
the date of the album should change accordingly. This is what Shotwell does and
I think it's intuitive. For me, it is very confusing that an album has a date
and it can (and by default is) something very different from the photo dates.
In my thinking, the images have dates and the "album date" just reflects that
somehow.

I understand that for efficiency reasons the album date is stored in the
database and thus it needs to be updated automatically whenever the image
collection changes in the album. Thus, the album date in the database isn't
"user data" but rather just cached date. Therefore, I don't see any violation
of the principle. :) And of course, this wouldn't have to be a default option.

Also, I understand that sometimes people might want to put dates on albums so
that it has nothing to do with the dates of the images, but I think that is not
a typical case. At least I have never had any use for such a feature.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 196672] Add new option to setup global preference about default album dating

[Simon]

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

Simon  changed:

   What|Removed |Added

 Ever confirmed|0   |1
Version|0.10.0  |5.6.0
 CC||freisi...@gmail.com
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Simon  ---
Archeology going on :D

I support this idea, with slight modifications:
Provide all options in the album creation/modification dialog and remember the
one that was last chosen. There can still be a setting for automatically added
albums (i.e. picked up by scanning), but I think there should be a direct
choice in the dialog. No need to set it again if you don't want to, as it
remembers the previous choice. Otherwise one has to know about some option
hidden in the configuration, that's not good user experience.

Changing the dates retrospectively could be a maintenance option, but certainly
can't happen automatically. This violates the "least surprising and invasive
behaviour" principle (which I just made up). Changing the users data
automatically due to a new feature is never an option in my opinion.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 196672] Add new option to setup global preference about default album dating

[Jaakko Luttinen]

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

Jaakko Luttinen  changed:

   What|Removed |Added

 CC||jaakko.lutti...@iki.fi

--- Comment #1 from Jaakko Luttinen  ---
Any news on this after 8 years?

I'd be happy with a very simple solution: Add one global option whether to
determine the album date automatically or manually. That is, somewhere in
settings, there'd be "Determine album date from" with options:

- oldest image date
- average image date
- newest image date
- manually specified date (this is the current solution)

If the album dates are stored in the database, then changing this option to
oldest/avg/newest could update all the album dates in the database (thus, one
loses any manually set album dates). Also, the date choosing in album
properties and album creation would be disabled/removed when not in "manually
specified date" mode.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 196672] Add new option to setup global preference about default album dating

[via KDE Bugzilla]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Severity|normal  |wishlist

-- 
You are receiving this mail because:
You are watching all bug changes.