Enter Dublin Core XMP in Bridge metadata window

Question

Someone in the general discussion area suggested I cross-post this question here:
I'm trying to find the best way to add some Dublin Core into TIFF files. Basically I'd like to add data to the dc:identifier and dc:relation fields while I'm adding other data in Bridge.  Is there a way to create a tab for Dublin Core in the metadata window?
Currently we're using Bridge and IPTC core was working okay, but now we need to add some metadata that would fit better in Dublin Core.  I know it has a namespace in XMP, but can't figure out a way to use Bridge or Photoshop to enter it.
I have tried to adapt a script created by Paul Riggott in this thread, but have been unable to make it work.
I also tried the "add identifier" script in this thread, but I'm not seeing how it works... probably because it was written for the Mac and I'm working in Windows. Any suggestions?
Thanks.

Answer 1

Sorry, I should probably include the code as I amended it:
// ADOBE SYSTEMS INCORPORATED
// Copyright 2008 Adobe Systems Incorporated
// All Rights Reserved
// NOTICE:  Adobe permits you to use, modify, and distribute this file in accordance with the
// terms of the Adobe license agreement accompanying it.  If you have received this file from a
// source other than Adobe, then your use, modification, or distribution of it requires the prior
// written permission of Adobe.
@fileoverview Shows how to create a TabbedPalette in Bridge with ScriptUI components.
@class Shows how to create a TabbedPalette in Bridge with ScriptUI components.
<h4>Usage</h4>
<ol>
<li>    Run the snippet in the ExtendScript Toolkit (see Readme.txt), with Bridge CS4 as the target.
<li>You should find that a tabbed palette has been added to the Bridge browser window.
</ol>
<h4>Description</h4>
<p>Adds a script-defined tabbed palette to the Bridge browser window. 
<p>The palette is of the "script" type, and contains ScriptUI components,
text fields and buttons. The buttons have event handlers that
change the values in the text fields.
<p>The new palette appears in the default upper-left position in the browser. It can be
  dragged to other positions. <br />
@see SnpCreateWebTabbedPalette
@constructor Constructor.
function SnpCreateTabbedPaletteScriptUI()
     The context in which this snippet can run.
     @type String
    this.requiredContext = "\tExecute against Bridge main engine.\nBridge must not be running";
    $.level = 1; // Debugging level
    this.paletteRefs = null;
Functional part of this snippet. 
Creates the TabbedPalette object, defining the content with
ScriptUI components, and adds the palette to all open Bridge browser windows.
    @return True if the snippet ran as expected, false otherwise. 
    @type Boolean
SnpCreateTabbedPaletteScriptUI.prototype.run = function()
    var retval = true;
    if(!this.canRun())
        retval = false;   
        return retval;
    this.paletteRefs = new Array();
    var wrapper = this;
    // Create and add the TabbedPalette object and its contents.
    function addScriptPalette(doc)
        // Create the TabbedPalette object, of type "script"
        var scriptPalette = new TabbedPalette( doc, "SnpCreateTabbedPaletteScriptUI", "SnpSUIPalette", "script" );
        wrapper.paletteRefs.push(scriptPalette);   
        // Create a ScriptUI panel to be displayed as the tab contents.
        var tbPanel = scriptPalette.content.add('panel', [25,15,255,130], 'The Panel');
        // Add the UI components to the ScriptUI panel
        tbPanel.txtFieldLbl = tbPanel.add('statictext', [15,15,105,35], 'Times Clicked:');
        tbPanel.txtField = tbPanel.add('edittext', [115,15,215,35], '0');
        tbPanel.addBtn = tbPanel.add('button', [15,65,105,85], 'Add');
        tbPanel.subBtn = tbPanel.add('button', [120, 65, 210, 85], "Sub");
        // Define event listeners that implement behavior for the UI components
        tbPanel.addBtn.onClick = function()
// This only works on bridge!!
loadXMPLib();
// Here put the namepace and the prefix (you can create also your own new namespace and prefix)
// In this case, it uses the Dublin Core Properties
var psNamespace = "http://purl.org/dc/elements/1.1/";
var psPrefix = "dc:";
XMPMeta.registerNamespace(psNamespace, psPrefix);
// Here you have to choose 1, 2, or multiple thumbnails. In this case it chooses all tiff files found on content pane.
var sels = app.document.visibleThumbnails;
for (var b in sels) {
    // Here I choose tif files, but you can set (cr2|raw|dng|nef/jpg) for raw and jpg files leave it empty for any file except folders
    if (sels[b].spec instanceof File && sels[b].name.match(/\.(cr2|raw|dng|nef)$/i)) {
        var xmp = new XMPMeta(sels[b].synchronousMetadata.serialize());      
        // I can create new Properties in Dublin Core and add values to them
        xmp.setProperty(psNamespace, "MyProp01", 'some text here');
        xmp.setProperty(psNamespace, "MyProp02", 'false');
        xmp.setProperty(psNamespace, "MyProp03", '32895665');
        xmp.setProperty(psNamespace, "MyProp04", 'label2');
        // Or, you can use the DublinCore native properties.
        // In this case, I want to ADD some text to 'Descrition' existing text ('Description is a 'langAlt' property)
        // First, I read any Descrition value and add it to a var
        var Description =  xmp.getArrayItem(XMPConst.NS_DC, "description",1);
        // Then I add may new tex to that existing value:
        // (I wanted to put the return '\r' (or new line '\n') to add new paragraphs in the middle of text: "\rline2\rline3")
        xmp.setLocalizedText(XMPConst.NS_DC, "description", null, "x-default", Description + "\rlinha2\nlinha3");
        // If you want to delete any existing value and create new value directly use this instead:
        // xmp.setLocalizedText(XMPConst.NS_DC, "description", null, "x-default", "Nota");
        var updatedPacket = xmp.serialize(XMPConst.SERIALIZE_OMIT_PACKET_WRAPPER | XMPConst.SERIALIZE_USE_COMPACT_FORMAT);
        sels[b].metadata = new Metadata(updatedPacket);
unloadXMPLib();
// Functions needed:
function loadXMPLib() {
    if( xmpLib == undefined ) {
          if( Folder.fs == "Windows" ) {
              var pathToLib = Folder.startup.fsName + "/AdobeXMPScript.dll";
          } else {
              var pathToLib = Folder.startup.fsName + "/AdobeXMPScript.framework";
          var libfile = new File( pathToLib );
          var xmpLib = new ExternalObject("lib:" + pathToLib );
function unloadXMPLib() {
    if ( ExternalObject.AdobeXMPScript ) {
        try {
            ExternalObject.AdobeXMPScript.unload();
            ExternalObject.AdobeXMPScript = undefined;
        }catch (e) { }
        tbPanel.subBtn.onClick = function()
            var txt = tbPanel.txtField;
            txt.text = parseInt(txt.text) - 1;
    // Add the palette to all open Bridge browser windows
    for(var i = 0;i < app.documents.length;i++)
        addScriptPalette(app.documents[i]);
    return retval;
  Determines whether snippet can be run given current context.  The snippet
  fails if these preconditions are not met:
  <ul>
  <li> Must be running in Bridge
  </ul>
  @return True is this snippet can run, false otherwise
  @type boolean
SnpCreateTabbedPaletteScriptUI.prototype.canRun = function()
    // Must run in Bridge
    if(BridgeTalk.appName == "bridge")
        return true;       
    // Fail if these preconditions are not met. 
    // Bridge must be running,
    $.writeln("ERROR:: Cannot run SnpCreateTabbedPaletteScriptUI");
    $.writeln(this.requiredContext);
    return false;
"main program": construct an anonymous instance and run it
  as long as we are not unit-testing this snippet.
if(typeof(SnpCreateTabbedPaletteScriptUI_unitTest) == "undefined") {
    new SnpCreateTabbedPaletteScriptUI().run();