Read XMP AltTextAccessibility tag from links

[Thorsten Kaltenborn]

Hi there,

is there any way to get the Iptc4xmpCore:AltTextAccessibility tag from a placed file using UXP script or ExtendScript?

The documentation under https://developer.adobe.com/xmp/docs/XMPNamespaces/Iptc4xmpCore/ does not even mention the tag.

Additionally I cannot declare any xmp objects because require("uxp").xmp is always undefined. Do I have to install anything? I tried UXP V. 7.4.2 (ID 2024 19.5.4) and UXP V. 8.1.6 (ID 2025 20.5)

Every hint is appreciated 🙂

[rob day]

Every hint is appreciated

Hi @Thorsten Kaltenborn , In ExtendScript a document has a MetadataPreferences object, which has setProperty and getProperty methods:

https://www.indesignjs.de/extendscriptAPI/indesign-latest/#MetadataPreference.html

var md = app.activeDocument.metadataPreferences;
var ns = "http://ns.adobe.com/xap/1.0/"
var p = "documentWidth"
var v = "8.5"

md.setProperty(ns, p, v);
alert("This Document’s " + p +" property is set to: " + md.getProperty(ns, p))

[Thorsten Kaltenborn]

Hi Rob,

thank you for your answer. But I need the XMP data of a link object. metadataPreferences is a property of the document object only.

[rob day]

With ExtendScript you can get the linkMetadata property from the link, but that is read only—there is getProperty but no setProperty. You might be able to do it by opening the link into Photshop with BridgeTalk and set the metadata property there.

[Dirk Becker]

Hi Rob, let me add a detail:

InDesign stores XMP of linked objects within the document. An old plugin of mine uses that to fix broken XMP without touching the images, add own accounting relevant metadata and so forth during PDF export, and reverts after the export …

You're right though about scripting where this is only relevant because you better update links before looking at their XMP.

[Thorsten Kaltenborn]

Hi Rob,

Thanks for your advice.

I seem to have a general problem with my XMP functions (see below). I'll get back to you when I know more about it.

[Dirk Becker]

Something is wrong with your InDesign + UXP installation.

Using InDesign 20.3.1 for no specific reason,  I'm a bit slow with updates:

 ...

The document "last updated 26.7.2023" does not mention the tag, but according to another thread support was added to photography products only later in December 2023.

https://community.adobe.com/t5/lightroom-classic-ideas/p-support-for-new-iptc-accessibility-metadata...

When looking around in UXP I found much documentation is backed by github. According to the history there of your namespace document that July 2023 change was about broken links and the previous revision is from 2021. Explains the missing items.

https://github.com/AdobeDocs/xmp-docs/blob/main/src/pages/XMPNamespaces/Iptc4xmpCore/index.md

When you get xmp going in principle, I think there is another detail waiting for you - that tag may have language versions.

Happy programming!

[Thorsten Kaltenborn]

Hi Dirk,

Something is wrong with your InDesign + UXP installation.

Using InDesign 20.3.1 for no specific reason,  I'm a bit slow with updates:

Any ideas what's wrong with my UXP and how to fix it?

Like I mentioned I get the same error in both ID versions (on the same Mac). Like you I had 20.3.1 and updated to 20.5 hoping this would fix it.

When you get xmp going in principle, I think there is another detail waiting for you - that tag may have language versions.

I was hoping it does. 🙂

To clarify my problem: I want to read the AltTextAccessibility tag and set the object export options. When I do it manually I only get the "x-default" value (or maybe the first language). I am planning a script that allows you to set the alt text by choosing the right language.

[Dirk Becker]

We're having another XMP discussion in parallel, plus one in the UXP centric creativeclouddeveloper.com forum.

https://community.adobe.com/t5/indesign-discussions/custom-xmp-metadata-not-showing-in-indesign-file...

https://forums.creativeclouddeveloper.com/t/is-there-any-manifest-permission-for-activedocument-file...

My conclusion: If you're within InDesign, prefer the proven InDesign methods.

Beyond that, I can only refer to the typical path when things go wrong:

Name your particular OS (you did not mention Mac or Windows, so I guess you're on Windows. I'm using Mac) . Are there admins around that locked/crippled it down with "enterprise" gradee security software, what used to be antivirus a decade ago. It might show a pattern when others come along for the same problem.

Then take the route with various degrees of reboot in safe mode, use another user account, reinstall, purge preferences, purge more preferences, cleaner script, try another machine with clean OS etc. Look around in other threads, there are lengthy FAQs.

[Dirk Becker]

It just occured to me: when you write "UXP Script" do you mean an .idjs file?

Could be the problem. Try a UXP "plugin" before you rebuild the entire box.

[Dirk Becker · Accepted solution]

After burning a few hours, I can confirm that UXPSCRIPT does not support xmp. At least for now (tried Version 20.3), I filed a bug on it. Digging further via a UXP plugin, with lots of try and error I could also list the language variants of that tag using uxp.xmp, while I haven't even tried to access them via InDesign's own methods (the linkXmp).

My conclusion: both InDesign and the uxp.xmp library still need plenty work. Leaving it at that, back to traditional plug-in programming …

[Thorsten Kaltenborn]

Hi Dirk,

I'm back from vacation. Thanks for digging. So, if I understand you right, I could try to program a plug-in if I need to access the xmp infos. I don't know if I'm ready for that by now. I need more time to learn 🙂

[Thorsten Kaltenborn]

Hi Dirk,

you are right, I only mentioned in a sub-sentence that I work on a Mac. I am more detailed when it comes to bug reports. I wasn't aware that it could be a general bug by now.

I will go on vacation next week so this problem will rest for a while but I will check if the problem persists on my private Mac, too. And I will report after that.

I have seen your other discussion about custom meta data but since I cannot declare xmp generally it didn't help 😉