Thanks for looking through the Change Log and spotting this new MLA feature. You can find more information in the Settings/Media Library Assistant Documentation tab.
- The “IPTC & EXIF Processing Options” section has an example of adding a mapping rule for the WordPress Standard Fields, taxonomy terms or custom fields.
- The “Field-level Substitution Parameters” section describes the “xmp” prefix used to specify that the data you want is in the item’s XMP metadata.
- The “Content Templates” section tells you how to take data from multiple places, test for blank values and so forth.
- The “IPTC/EXIF Mapping for PDF Documents” section has some examples that can be adapted for XMP data. Simply replace the “pdf:” prefix with “xmp:”
I regret that the information you need is scattered throughout the Documentation, but I will help you get the results you need.
You may have seen these earlier topics:
Mapping XMP from images to Att. Tag
Truncated Title/Alt Text
The first one may be of interest, if by “WP tags” you mean you want to assign terms in the “Att. Tags” or WordPress “Tags” taxonomy. You might find that the xmp:Keywords data source will work for the images you have. If not, post a link or two to your images and I can look through them to see where in the XMP data you might find what you need.
That should get you started. Experiment a bit and let me know how it goes. Any additional information you can give me will let me be more specifically helpful. Thanks for your interest in the plugin and the new XMP metadata features.
Thanks a lot for your quick response. I read the documentation but did not understand that I would have to replace pdf with xmp. Did it now and it (almost) works perfectly. I use the following mappings:
IPTC EXIF/Template Value Priority
ALT Text object-name template:([+xmp:Title+]) EXIF
Caption object-name template:([+xmp:Title+]) EXIF
Description caption-or-abstract template:([+xmp:Subject+]) EXIF
Keywords keywords template:([+xmp:Keywords,array+]) EXIF
For IPTC it works fine. But if there are XMP tags Caption is the same as Description. I would expect it to be the “Headline”. Thus I think you map the same XMP tag to Title and Subject or at least tags holding the same values in my case. The XMP tag holding the value I expect to be the Title in my case is Xmp.photoshop.Headline.
Thanks for your update with the good news regarding your progress.
You wrote ‘For IPTC it works fine. But if there are XMP tags Caption is the same as Description. I would expect it to be the “Headline”.‘
I used Photoshop CS6 to test out one of my images. In the “File Info…” dialog box I filled in the IPTC Headline text box. The “Raw Data” tab shows <photoshop:Headline>IPTC Headline</photoshop:Headline> – which implies that the XMP data comes from the IPTC data. If the IPTC Headline text box is empty, the XMP value is missing. MLA does not use the XMP value because the IPTC value is the same.
The MLA [+xmp:Title+] field is set from the “dc” namespace “title” field, and the [+xmp:Subject+] field is set from the “dc” namespace “description” field. If your images do not have xmp:dc.description, you may be seeing the default WordPress value, which is the same as the item’s WordPress “Title”.
You could try changing your “Description” template to something like:
template:([+xmp:photoshop.Headline+]|[+xmp:Subject+])
If you find an image where the IPTC and XMP photoshop values are different, post a link and I will have a look.
Sorry for my delayed reply. I was out of town over the holidays.
But now I come back with good news. Eventually I found a mapping, that works fine:
Field Title IPTC Value EXIF/Template Value Priority
ALT Text object-name template:([+xmp:Title+]) IPTC
Caption object-name template:([+xmp:Title+]) IPTC
Description caption-or-abstract template:([+xmp:Subject+]) IPTC
Keywords keywords template:([+xmp:Keywords,array+]) IPTC
If there are both sets, IPTC and XMP, present the correct values are assigned. After deleting all IPTC tags the same. But if I set Priority to EXIF and delete all XMP instead of the IPTC tags wrong values get assigned. But since it works fine with IPTC priority I do not care.
BTW, I use Digikam, a data base program running under Linux, to archive my photos. Digikam writes IPTC tags as well as XMP tags into the pictures. Older versions only wrote IPTC tags. That is why I still got loads of pictures without XMP tags.
The title I assign to my pictures is written by Digikam to these fields:
Xmp.dc.title
Iptc.Application2.ObjectName
What I wrote about the “Headline” was wrong. I confused it with Title because Title was hidden in a different tab when I examined the pictures using another program.
Thanks a lot for your great plugin.
Knut
I hope you enjoyed your holidays! Thank you for your update with the good news on your progress. I am happy to hear that all the values you need are stored in the IPTC fields.
I am marking this topic resolved, but please update it if you have problems or further questions regarding mapping values from your image files to the WordPress standard fields and taxonomies. Thanks for your interest in the plugin.
It is okay to mark this topic resolved. But I would like to make on last remark. I would prefer to set Priority to EXIF to have the XMP tags read before the IPTC tags. That is why the character set for IPTC tags is limited to ASCII according to the standard and thus sometimes – not always – there appear funny characters in the fields.
As I wrote above, if Priority is IPTC and there are no IPTC tags in the pictures MLA falls back to XMP. But if Priority is set to EXIF and there are no XMP tags MLA does not fall back to IPTC. In this case there are no Keywords and no Description assigned and Caption looks like Description. I would expect, that MLA searches the IPTC tags first before falling back to WP default values.
Anyhow, if I delete all XMP and IPTC tags Caption looks like Description too. Maybe that is caused by Exif.Image.ImageDescription which holds the the same description as the respective IPTC and XMP tags.
Thank you for following up and expanding on your issue with “Priority: EXIF”. I regret that I did no understand your earlier post well enough.
In fact, you uncovered an MLA defect; thank you! I have fixed it and uploaded a new Development Version dated 20150519. You can find step-by-step instructions for using the Development Version in this earlier topic:
MLA errors when using plugin
I will mark this topic unresolved until the new feature is released in the next MLA version. If you have some time to try the new Development Version, let me know if it resolved your problem. Thanks for your help with this topic and for alerting me to the defect.
Hey David,
thanks for your quick reply.
Well I’d love to test the Development Version. But unfortunately I can’t find it. What is the “Developers tab of the Media Library Assistant entry in the Repository”? Do you mean this page: wordpress.org/plugins/media-library-assistant? I do not see ana Developers Tab an this page.
Cheers Knut
That’s great news – thanks for offering the time to test the update.
You are not the first to have trouble with the instructions. Here is a recent topic with some additional instructions:
Polylang Media Translation
In short, you can find the Development Version here:
https://wordpress.org/plugins/media-library-assistant/developers/
Let me know if that works for you.
Knut,
Thanks for your update with the good news. It looks like you meant to post your update here. It says:
Knut.Hildebrandt
Member
Posted 5 hours ago #
Great, now it works like a charm.
Thanks a lot for introducing reading out XMP tags.
I am happy to hear the problem is corrected, and I will mark this topic resolved when the fix goes out in the next MLA version. Thanks for your persistence and your help.
David,
sorry for posting in the wrong thread. After jumping from one to the other I eventually confused them.
Anyhow, thanks again for your excellent plugin. I’ll continue exploring it’s usage and if I come across more inconsistencies I’m happy to report them.
Knut
I have released MLA version 2.11. It contains the XMP fixes required to resolve your issues.
I am marking this topic resolved, but please update it if you have any problems or further questions regarding XMP support in MLA. Thanks for your interest in the plugin.
Well, as much as I could see every think worked fine. If In stumble upon any problem I let you know.
Thanks for your effort and sorry for the late response.
Thanks for the update with your good news. If there is anything else I can do, let me know.
