Support » Plugin: Media Library Assistant » Mapping Lightroom IPTC to WordPress Fields ADVICE

  • Resolved timothyselvage


    I’m trying to remap Lightrooms IPTC data fields to WP Fields but can not decide whether this is the best way. Any better suggestions for suitable remapping. It seems that where I’ve set up the WP field Caption to be 2#122 (lightrooms ‘description writer) it has a low number of characters available.

    FIELD | IPTC value | REPLACE
    1) Title: 2#105 [REPLACE]
    2) Name/slug: None [REPLACE]
    3) ALT Text: 2#005 [REPLACE]
    4) Caption: 2#122 [REPLACE]
    5) Description: 2#120 [REPLACE]
    6) Att. tags: 2#025 [REPLACE]

    This uses the lightroom fields:
    1) Headline
    2) none
    3) Title
    4) Description writer
    5) Caption
    6) Keyword

    I would be interested in how other Lightroom users have mapped the IPTC fields to allow easy and effective managements of data.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author David Lingren


    Thank you for taking the time to write up your current mapping rules in support of your question. I use PhotoShop to annotate my images, not Lightroom, but the general advice should be similar.

    Regarding your comment about IPTC field 2#122, here is what the IPTC Standard says:

    2:122 Writer/Editor
    Repeatable, maximum 32 octets, consisting of graphic characters plus spaces.
    Identification of the name of the person involved in the writing, editing or correcting the objectdata or caption/abstract.

    As you can see, the field is limited to 32 characters and is intended to store a person’s name. You might find another field is better for more general Caption purposes. You might also find a more useful field in the EXIF meta data values.

    You can use Content Templates to combine metadata elements, supply defaults for missing values and so on. You could build up a Caption from several IPTC fields. Here’s an example Content Template you would put in the “EXIF/Template” text box on the IPTC/EXIF page:

    template:([+iptc:object-name+] — ([+iptc:sub-location+], )([+iptc:city+], )([+iptc:province-or-state+], )([+iptc:country-or-primary-location-name+]))

    All those parentheses are optional; they ensure that missing values are quietly ignored along with their punctuation. For example, if the sub-location wasn’t filled in, the comma and space after it would also be dropped. You can find more information about templates in the “Content Templates” section of the Settings/Media Library Assistant Documentation tab.

    You can use the special “ALL_IPTC” or “ALL_EXIF” pseudo values to discover which IPTC/EXIF fields are populated in your images.

    You can quickly see the data available in your images by coding something like:

    [mla_gallery ids=272 mla_caption=”{+exif:ALL_IPTC+}” columns=1]
    [mla_gallery ids=272 mla_caption=”{+exif:ALL_EXIF+}” columns=1]

    The ALL_IPTC and ALL_EXIF pseudo values will dump all of the information in the image so you can see what’s in there. In this example, ids=272 is a quick way to select a specific attachment for the gallery; you can use any data selection parameters that you like.

    You can also use the pseudo values in the EXIF/Template textbox of an IPTC/EXIF mapping rule or code [+exif:ALL_IPTC+] as a Template Data Source for a Custom Fields mapping rule.

    I put your question out to a couple of Lightroom users and one of them sent this response:

    I’m assuming this person wants to ingest metadata from images into WP that was written to the images by Lightroom. The biggest challenge is going to be figuring out how to get access to every one of the available metadata fields that Lightroom writes to the image. Sometimes fields are stored in IPTC headers (Core or Extended), sometimes EXIF, other times XMP, and sometimes even more than one. There’s also Dublin Core, but I’m not sure if Lightroom uses it. And sometimes fields in one metadata standard don’t cleanly map to fields in another standard. For example, Copyright, Description, Creator, and Date & Time are all mapped differently between IPTC, EXIF, and XMP. (See: I’m sure there are other instances of this type of inconsistency.

    Essentially there are 5-6 major metadata ‘standards’ – EXIF, DCF (Dublin Core), ITPC Core, IPTC Extended, and XMP. Then Adobe has its own extensions. And each maps various metadata fields in different ways even though there are supposed to be standards for the various field mappings.

    To my knowledge Adobe doesn’t provide any documentation as to how one would extract the metadata that Lightroom writes to the image via various tools like PHP or other languages, or how Lightroom’s metadata fields would map to “standard” IPTC, IPTC Extended, EXIF, or XMP fields.

    If I were doing this I would first try to fill every possible metadata field in Lightroom with some text, then export the image from LR with all metadata intact. Then I would try to extract every single one of those metadata fields via PHP or other tools in an attempt to determine how Lightroom is storing the various metadata fields in the images. From there it’s just a matter of deciding how one wants to map & insert those fields into WordPress.

    XMP & PHP:

    IPTC & PHP:

    EXIF & PHP:

    In a quick search I can’t find any guidance on how to access Dublin Core metadata via PHP (it may be that Dublin Core isn’t used for image metadata…)

    Hope that helps.

    The current MLA version does not support access to XMP meta data in images (although it does for PDF documents). If you find a compelling reason for using XMP meta data in your images, let me know and I will consider developing support in MLA.

    I hope that gets you closer to the mapping results you want. I am marking this topic resolved, but please update it if you have problems or further questions about accessing IPTC/EXIF meta data in MLA. Thanks for your interest in the plugin.

    First of all I want to say that I really appreciate your work. Great plugin, that makes media management much more comfortable. Above all I love meta data processing, particularly the mapping of IPTC and EXIF tags. It is so powerful that it took me a while to figure out how to use it in an optimal way. The good news, one even can apply the mapping later in a batch process. Only drawback, that does not work for me, since almost all of my images were only populated with XMP tags. Thus I can’t do the mapping anymore. That only works for new uploads, when I generate additional IPTC tags before uploading the image.

    The big advantage of XMP over (old plain) IPTC, it allows any character and not only ASCII ones. That is why I preferred using XMP. German and Spanish for instance have quite a few character that are not in the ASCII character set.

    I hope this is a “compelling reason for using XMP” and you might consider developing XMP support in MLA.

    Plugin Author David Lingren


    Thank you for the positive feedback and for your suggestion, which comes at an opportune time. Have a look at this recent support topic:

    Truncated Title/Alt Text

    I will be working on XMP support and posting an update when I have a Development Version to try out. Thanks for adding your voice to the process!

    Plugin Author David Lingren


    I have uploaded a new Development Version that adds XMP support for mapping rules and the [mla_gallery] shortcode.

    For IPTC EXIF mapping rules you can access XMP data in the EXIF/Template text box. For example, the full title can be accessed as “template:([+xmp:Title+])“. More information can be found in the “Field-level prefix values” section of the Settings/Media Library Assistant Documentation tab.

    You can find step-by-step instructions for using the Development Version in this earlier topic:

    MLA errors when using plugin

    It would be great if you can try extracting XMP data from as many images as you can.

    If you get a chance to try the Development Version, let me know if it meets your needs. Thanks for your interest in the plugin.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Mapping Lightroom IPTC to WordPress Fields ADVICE’ is closed to new replies.