Lightroom: You should swap Headline with Title

  • 5
  • Problem
  • Updated 4 years ago
  • (Edited)
Meatadata panel in Lightroom seems to ignore basic IPTC rules.

As is stated in the IPTC core:

"Headline
A headline is a brief publishable synopsis/summary of the contents of the photograph.
The Headline term should not be confused with the Title term."

"Title
This field can be used as a shorthand reference for the image or "photograph" - primarily for identification. The title of an image may take several forms; for photographers this might be the filename of their original scan or digital camera file, for news organizations it might be the name of the story for which it's to be used.
The Title term should not be confused with the Headline term, which is a short synopsis of the content of the photograph."

So, in reality Headline should be used as a title for an image. The way Metadata promotes now in the Default view, is:

1. Title
2. Caption

so users will assume that "Title" should be the title of the image.

To be correct the IPTC field "Headlne" should be promoted in "Title" place.

This can be an issue with many online web services, galleries, etc.
Please consider fixing.
Photo of g k

g k

  • 14 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 5
Photo of john beardsworth

john beardsworth

  • 736 Posts
  • 94 Reply Likes
"Meatadata panel in Lightroom seems to ignore basic IPTC rules. "

So does the world. Most systems use title - better to acknowledge reality?
Photo of g k

g k

  • 14 Posts
  • 0 Reply Likes
@john beardsworth

I do not agree. Many websites and photographers mention that this is a mistake.
Many users may not be aware of it, until it is too late. Wouldn't it be better if Adobe could help them use an industry standard, instead of promoting the wrong way to do it?

I mean really, it can't be hard at all to switch them around, can it?
Photo of john beardsworth

john beardsworth

  • 736 Posts
  • 94 Reply Likes
Realistically, that battle was lost long ago (probably when people confused "product" and "title"), and there's enough wiggle room in the standard to allow title to be used as most people prefer. Might not Adobe's effort be better spent modernising the standard?

As it is, you can create your own metadata panels quite easily - just adding text files in a folder called Metadata Field Lists. Just a *.lrtemplate file like this:

return {
version = 1, -- format this file is in (format version #1)
title = "Pedantic IPTC",
id = "www.beardsworth.co.uk.1",
type = "MetadataFieldList",

items = {
"com.adobe.filename",
"com.adobe.headline",
"com.adobe.caption",
}
}



The format is shown in p76 onwards in the SDK http://www.adobe.com/devnet/photoshop... (you don't need to create a plugin - just the above text file)

So it wouldn't be too difficult for Adobe to do - if they ever thought it worthwhile.
Photo of g k

g k

  • 14 Posts
  • 0 Reply Likes
That is a great hack, but I fear that the majority of users will not use it. Solving it for me only, is not my goal here.I strongly feel that they should fix it. That is why I made this report in the first place.

Besides, there are other issues here. If I choose to follow the correct path and use "Headline" to title my photos, then in the Book module for example, there is simply no way to show the "Headline" on the photos. So, as you can see there are more involved here.

I would hate to have Headlined all of my photos, only to realise afterwards that these headlines are useless for the Book module.
Photo of Dorin Nicolaescu-Musteață

Dorin Nicolaescu-Musteață, Champion

  • 703 Posts
  • 36 Reply Likes
Agree. With both of you.

The problem is that you cannot use the Headline field even if you're pedantic and populating it. So, the real solution, perhaps, would be to add the Headline to the list of available fields in all appropriate places.

And not only the Headline. What the heII!
Photo of john beardsworth

john beardsworth

  • 736 Posts
  • 94 Reply Likes
That's not really an effect of Adobe preferring title - more a surprising design limitation in the Book module. If you look at Print's Page panel / Photo Info you'll see there's already a perfectly good UI element that allows the user to choose from a larger selection of fields, including Headline.
Photo of Dorin Nicolaescu-Musteață

Dorin Nicolaescu-Musteață, Champion

  • 703 Posts
  • 36 Reply Likes
That's what I meant.

For the record, I personally miss it in smart collections (i.e. Headline is empty).
Photo of john beardsworth

john beardsworth

  • 736 Posts
  • 94 Reply Likes
There's a lot we miss in smart collections - like most of the data in the catalogue
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 349 Reply Likes
TextMeta supports headline field for smart collections, if you're serious...

http://www.robcole.com/Rob/ProductsAn...
Photo of g k

g k

  • 14 Posts
  • 0 Reply Likes
@john beardsworth
@Dorin Nicolaescu-Musteață

John is right. Most other modules are quite versatile. It is the Book module that lacks this functionality.

But I really, really want to be pedantic about it ;)
Headline should be in the place of Title.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 349 Reply Likes
I think simply swapping headline with title would be a bad idea at this point, since that would put all Lightroom users who depend on the title field out in the cold.

But having options for field inclusion in book module etc, and native support for user editable metadata tagset views seem like really good ideas to me.

Note: Jeffrey Friedl has a *very* nice plugin for creating these metadata views. Only shortcoming is - it doesn't handle dynamic plugin metadata, like ExifMeta's - granted, ExifMeta has a built-in way to create these metadata views, but it's not much friendlier than hand-editing Metadata Field List files.
Photo of g k

g k

  • 14 Posts
  • 0 Reply Likes
@Rob Cole

Don't you think it would be possible for Adobe to copy "Title" to "Headline" optionally for the user and make it correct for everyone?

I do agree though, that options should be richer in other modules. That would "sort of" fix it for me.

Thing is, why do it wrong in the first place?
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 349 Reply Likes
Well, there is probably more than one possible solution, which could be done by Adobe, and/or you. I'm not qualified to say what should have happened way back when.

But, if you want to copy/swap fields around, there are some plugins that will do it.

Cheers,
Rob
Photo of john beardsworth

john beardsworth

  • 736 Posts
  • 94 Reply Likes
This is how I would do it with my Search and Replace plugin