Bug 481217 - Relocate Title field into Content panel of Edit Metadata windows (instead of Status panel)
Summary: Relocate Title field into Content panel of Edit Metadata windows (instead of ...
Status: RESOLVED DUPLICATE of bug 448125
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Template (other bugs)
Version First Reported In: 8.2.0
Platform: Manjaro Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-11 12:48 UTC by mahikeulbody
Modified: 2024-02-11 13:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mahikeulbody 2024-02-11 12:48:27 UTC
SUMMARY

Relocate Title field into Content panel of Edit Metadata windows (instead of Status panel).

According to iptc.org, Title provides a short human readable name for the picture. It seems much more related to the content of the picture, as Caption or Headline, that to its status.

Moreover that would be more consistent with the fact Right Caption Panel displays Title and Caption, not Headline and Caption. In fact, the best solution would be to have the three fields displayed into both Content panel of Edit Metadata windows and Right Caption Panel.
Comment 1 mahikeulbody 2024-02-11 13:08:35 UTC
Reading many forums, it seems Title is often used to describe a set of pictures, such as "Travel to France" for example, when Caption is used to describe a particular picture. It is more difficult to know how Headline is used (if used, since it is not a field displayed by default in Lightroom, afaik) but we can see as an intermediate level of description.

Anyway, I think it is better to apply the same logic for the three fields ; they should be displayed together in any display where two of them are already displayed (preferentially in the order : Title, Headline, Caption).
Comment 2 Maik Qualmann 2024-02-11 13:21:29 UTC

*** This bug has been marked as a duplicate of bug 448125 ***