Possible to convert ASCII

Thanks for an interesting question. I don’t know enough of the specific encoding actions of CS3 and CC to give you an immediate answer.

I can think of two possible fixes. First, there may be a general fix I can add to the MLA software to correct this for all IPTC/EXIF/XMP handling. Second, if a general fix does not make sense I can create a small custom plugin that uses the filters built in to MLA upload and mapping code to give you some relief.

It would be very helpful if you post a link to one or more of the images that show the problem. Would that be possible?

I will be traveling off-road from Saturday March 31 until Monday, April 9. I will have no Internet access during this period, and I will not have any access to my development system. I can investigate further after I return home. Thanks for your understanding and your patience.

Hello,

Are there some e-mail where I can send you those ? They are copyrighted and belong to a customer so I can’t publish them.

Have a nice trip. ??

It was a great trip! If you send me your contact information I will reply with an address where you can send sample images. You can use the Contact Us page at our web site:

Fair Trade Judaica/Contact Us

I look forward to hearing from you.

Thanks for working with me offline to investigate some of your images. The problem you are having is unique to the IPTC data, and I have not found a way to correct the values properly. However, the values you want are present in the EXIF and XMP metadata.

For your mapping rules you would leave the IPTC Value set to “none” and enter a value like this in the EXIF/Template Value:

Copyright or ImageDescription – the EXIF values
template:([+xmp:rights+]) or template:([+xmp:description+]) – the XMP values

You can find some tips on looking at the XMP data in this earlier Support Topic:

“Keywords” to “Description”

You can also use some MLA debugging features to get dumps of the metadata:

1. Navigate to the Settings/Media Library Assistant Debug tab.
2. Scroll down to the “MLA Reporting” text box and enter “0x11”. This will turn on MLA debug logging for metadata extraction.
3. Click the Save Changes button to record your new setting.
4. Optionally, scroll to the bottom of the screen and click “Reset” to clear the error log. You may not want to do this depending on how you manage your error log.

Once that’s done:

1. Navigate to the Media/Assistant admin and click the “Edit” action for the image you want to investigate.
2. On the Media/Edit Media screen click the “Map IPTC/EXIF metadata” link in the “Save” box at the top-right of the screen.

Then, go back to the Debug screen and:

1. Enter “0” in the MLA Reporting text box to turn debug logic off.
2. Scroll down to the Error Log text box and look through the data.
3. You can also scroll to the bottom and click “Download” to get the log content in a text file.

There are lots of tools to look at the metadata in the file, but the above techniques will show you exactly what MLA is seeing and using.

You can also expand your templates to look for values in multiple places. For example:

template:([+exif:Copyright+]|[+xmp:rights+]|[+iptc:2#116+])

That will look first for the exif value, then the xmp value and finally the iptc value and will take the first value it finds.

I hope that gives you more ideas for your own analysis; every image is different. I am marking this topic resolved, but please post an update or follow up with me if you need more specific guidance. Thanks for your interest in the plugin.

Ok, sorry didn’t take time to reply to your last email. I think it would be great if debug was more accessible as it is really helpful to understand how to map data/use template.

Anyway I think I get it all now and using xmp data is the way to do it. I made a donation to thank you for this great an free support. Keep going.

David.

Thanks for confirming that the XMP data was the best source of the data you needed.

Thanks as well for your generous donation to our fair trade work. Donations, reviews and positive feedback are great motivators to keep working on the plugin and supporting its users!