2 comments

  1. julien says:

    Hi Carl, thanks for this post. I’m learning much more in metadata at the moment and so I can reply your “Copyright URL” into Bridge.

    Actually it comes onto the ‘IPTC (IIM, legacy) ‘Copyright Info URL’

    Best,
    Julien

    • Carl Seibert says:

      HOLY COW! Thank you! What Julien found is that in the Preferences for Adobe Bridge, in Metadata, under a section called “IPTC (IIM, legacy)” you have the option to turn on the CopyrightURL/Web Statement of Rights field. If you tick that option, the field will appear in the interface. I tried it. It does write to and read from the right place, so you should be able to use it to trigger a Licensable tag.

      This is truly very strange. CopyrightURL/Web Statement of Rights is an XMP-only field. It doesn’t have anything to do with the IIM data block. It is, by the way, in the extended schema, even though most developers who subset to the core schema include it. It probably should be in the core in the standard. But that’s seriously inside baseball.

      I don’t understand the “IPTC (IIM, legacy)” section in the prefs. Apart from this field, which clearly doesn’t belong there, it contains a bunch of core fields that you can make appear in the interface under a “IPTC (IIM, legacy)” section heading. Thing is, these are just normal core fields that already appear in the interface in their own section. The ones you can turn on here don’t do anything different from the already existing ones. Both will read and write from and to both the IIM and XMP versions of the fields. I just don’t get it.

      Adobe has been doing some dumb stuff lately, baking in new bugs and breaking UI conventions, among other things. Like making the thumbnails pane in Bridge scroll backwards. Geeez! For 600 bucks a year, I really expect better. As far as Bridge is concerned, if you’re a photographer and you’ve got the funds, Photo Mechanic is a much better alternative.

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.