• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • The May 2019 Lightroom updates are now available. There's a brand new slider called Texture, available across the whole family of apps. Lightroom Classic includes a new tool called Flat Field Correction. Lightroom (cloud-based service) has lots of big improvements including cloud trash, invitation-only web galleries, improved chromatic aberration removal and more. The Missing FAQ and Edit Like a Pro eBooks are already updated for the changes. You'll also notice the CC's have disappeared off the end of the names, so we've updated the forum names to match.

custom metadata fields

Michael Gray

New Member
Joined
Jan 18, 2018
Messages
4
Lightroom Experience
Advanced
Lightroom Version
Classic 7
Lightroom Version
Lightroom 6.6 (not online version)
Operating System
macOS 10.13 High Sierra
I have been attempted to set-up Jeffrey Freidl's custom fields plug-in without success.
I have already made adjustments according to the LR feedback.
Using Desktop lightroom 6.

Any suggestions? Is there an alternative?

Michael

12362
 

johnbeardy

Senior Member
Staff member
Moderator
Lightroom Guru
Joined
Oct 8, 2007
Messages
4,987
Location
London
Lightroom Experience
Power User
Lightroom Version
What exactly have you done? Have you been editing files in a text editor? I don't know Jeffrey's plugin and have no idea what you mean by "the LR feedback", but I do know my way around this area. The message means exactly what it says - if you change a setting like its searchability, then you must increment the version too.
 

Wernfried

Active Member
Joined
Jan 31, 2017
Messages
154
Lightroom Experience
Intermediate
Lightroom Version
Classic 7
Is there an alternative?
According exiftool there are 20'000 exif tags defined. I don't know what kind of custom data you are using but I would pick an unused exif tag and put your information there.

For example I use tag "MasterDocumentID" to put the full path of the source file.
 

Wernfried

Active Member
Joined
Jan 31, 2017
Messages
154
Lightroom Experience
Intermediate
Lightroom Version
Classic 7
Actually I would assume for any kind of "custom data" there is already an exif tag.
For example you have tag AcquisitionDateTime , PregnancyStatus, PatientWeight, MilitaryRank, SpectralWidth, Polarity, Occupation, Habitat, Kingdom, etc.
 

PhilBurton

Senior Member
Joined
Nov 16, 2015
Messages
1,659
Location
California, USA
Lightroom Experience
Intermediate
Lightroom Version
Classic 8
Actually I would assume for any kind of "custom data" there is already an exif tag.
For example you have tag AcquisitionDateTime , PregnancyStatus, PatientWeight, MilitaryRank, SpectralWidth, Polarity, Occupation, Habitat, Kingdom, etc.
Wernfried,

I would be thrilled to know if there are EXIF tags for the subject area of railroad and rail transit photography. For example:

  • System name (e.g. BNSF or DB or Transport for London)
  • Division name (e.g. Western)
  • Route Name (e.g. Piccadily Line or Blue Line)
  • Route Number (on the New York City subway system could be a number or a letter)
  • Station Name (e.g. Lexington Avenue or King's Cross)
  • Rollling stock type (passenger, freight, boxcar, goods wagon, flatcar)
  • Rolling stock manufacturer (e.g. Pullman Standard, Metro Camwell, Alsthom)
  • Rolling stock series name (e.g. GP 35, R29,)
  • Locomotive wheel arrangement (4-8-4 (US) 2-4-2 (Europe), BB)
  • Rolling stock number (e.g. 61097) Or capture an entire UIC number, as in this photograph:
12363


I had always assumed that I wold need to define custom metadata fields for this information. That was before I started to investigate DAM solutions, including Lightroom, and discovered almost no support for custom metadata fields. After a while I came to the conclusion that I would have to use groups of keywords as a barely acceptable substitute. I'm not happy about this situation, but that's the reality I have to work with.

Phil Burton
 

Wernfried

Active Member
Joined
Jan 31, 2017
Messages
154
Lightroom Experience
Intermediate
Lightroom Version
Classic 7
I would be thrilled to know if there are EXIF tags for the subject area of railroad and rail transit photography. For example:

I had always assumed that I wold need to define custom metadata fields for this information. That was before I started to investigate DAM solutions, including Lightroom, and discovered almost no support for custom metadata fields.
Ok, for such complex data a DAM solution seems to be needed.

I would say items like wheel arrangement or route number are not a property of an image but the image is just one property out of a "railroad and rail transit" data set.
 

PhilBurton

Senior Member
Joined
Nov 16, 2015
Messages
1,659
Location
California, USA
Lightroom Experience
Intermediate
Lightroom Version
Classic 8
Ok, for such complex data a DAM solution seems to be needed.

I would say items like wheel arrangement or route number are not a property of an image but the image is just one property out of a "railroad and rail transit" data set.
Perhaps, but for railroad photography, that might be just as important as other parts of the subject description such as geo-coordinates.

Phil Burton
 

PhilBurton

Senior Member
Joined
Nov 16, 2015
Messages
1,659
Location
California, USA
Lightroom Experience
Intermediate
Lightroom Version
Classic 8
Check this Plug-in, maybe it works for you:


Franz
Franz,

For me the issue is explained clearly in the description for this plug-in:

These custom fields are stored in the Lightroom catalogue and are never written to images themselves or to exported files. That is both good and bad. It means that they can be used for information which you do not want others to see, but it also means the information is locked inside Lightroom and only a plug-in can access the fields.

If/when/ever this limitation is removed, then I will gladly use this plug-in.

Phil Burton
 

Wernfried

Active Member
Joined
Jan 31, 2017
Messages
154
Lightroom Experience
Intermediate
Lightroom Version
Classic 7
For me the issue is explained clearly in the description for this plug-in:

These custom fields are stored in the Lightroom catalogue and are never written to images themselves or to exported files. That is both good and bad. It means that they can be used for information which you do not want others to see, but it also means the information is locked inside Lightroom and only a plug-in can access the fields.

If/when/ever this limitation is removed, then I will gladly use this plug-in.
Perhpas you can use Jeffrey Friedl's Run Any Command

Have a look at "PluginProperty=field" or The Special {LUA=...} Token, it might be possible to access the custom metadata from the Search and Replace Plugin.

"PluginProperty" allows you to access the per-image custom metadata kept by a plugin, where field is the plugin's id and the metadata field id, joined with a dot. [...] with PluginProperty, you can reference any plugin data for which you know the plugin id and field name. You can get these from the plugin author, or try digging around the plugin's Info.lua for the plugin id and a reference to its LrMetadataProvider, where you can find field ids.

When you check the code with a HEX editor then the filed names should be "uk.co.beardsworth.findreplace.custom01" to "uk.co.beardsworth.findreplace.custom16" and/or "uk.co.beardsworth.findreplace.jbParse01" to "uk.co.beardsworth.findreplace.jbParse05"
 

johnbeardy

Senior Member
Staff member
Moderator
Lightroom Guru
Joined
Oct 8, 2007
Messages
4,987
Location
London
Lightroom Experience
Power User
Lightroom Version
Just don't come to me for support on this!

Sure, a plugin such as Jeffrey's can read any other plugin's custom metadata and could therefore write it to the original or to a sidecar. However, what benefit does this really have? As backup? Well, the backup is the catalogue. Then are you going to take this metadata to another app? Which? Because none (of any significance) is coded to read custom metadata. So are you going to bring it back into LR? OK. But one plugin can't write another plugin's metadata, so you can't write it back to Search and Replace's fields. This means you are going to need another plugin which can both read from the originals and has custom metadata. Phil, you and I have gone over this a few times.... and you're best off with the course you've taken.
 

PhilBurton

Senior Member
Joined
Nov 16, 2015
Messages
1,659
Location
California, USA
Lightroom Experience
Intermediate
Lightroom Version
Classic 8
Just don't come to me for support on this!

Sure, a plugin such as Jeffrey's can read any other plugin's custom metadata and could therefore write it to the original or to a sidecar. However, what benefit does this really have? As backup? Well, the backup is the catalogue. Then are you going to take this metadata to another app? Which? Because none (of any significance) is coded to read custom metadata. So are you going to bring it back into LR? OK. But one plugin can't write another plugin's metadata, so you can't write it back to Search and Replace's fields. This means you are going to need another plugin which can both read from the originals and has custom metadata. Phil, you and I have gone over this a few times.... and you're best off with the course you've taken.
John,

I think we are in total agreement. I completely agree with your reasoning.

It's a darn shame that Adobe won't support their own XMP standard, but I don't see any real value in custom metadata fields that can't be shared with others.

Phil Burton
 

johnbeardy

Senior Member
Staff member
Moderator
Lightroom Guru
Joined
Oct 8, 2007
Messages
4,987
Location
London
Lightroom Experience
Power User
Lightroom Version
It's a shame, Phil, but it's been going downhill for more than 10 years. I guess I am moving to the view that one should focus on the stuff that will survive machine learning, like keywords and "rich" captions, and not spend too much time structuring metadata in a purist way.

John
 
Last edited:
Top