I think that script was created by Paul Riggott. You can find his scripts at https://github.com/Paul-Riggott/PS-Scripts  The one you want is Find and Replace.jsx It looks like it has been updated from the version you have. it now allows you to edit metadata in many different fields (your version only changed Description/Caption). ... View more

I found a few problems with the script:   OLD: function processKeyword(Replace,Witha,ddKey){ NEW: function processKeyword(Replace,With,addKey){   OLD: var file=new Thumbnail(items); NEW: var file=new Thumbnail(items[i]);   OLD: xmp.appendArrayItem(XMPConst.NS_DC, "subject", Replace, 0,XMPConst.ARRAY_IS_ORDERED); NEW: xmp.appendArrayItem(XMPConst.NS_DC, "subject", Replace, 0,XMPConst.ARRAY_IS_UNORDERED);   After these changes, I think the script works, but it could use some improvements. #target bridge if( BridgeTalk.appName == "bridge" ) { keyReplace = MenuElement.create("command", "Add-Replace-Remove Keyword", "at the end of tools"); } keyReplace.onSelect = function () { mainReplaceKeyword(); } function mainReplaceKeyword(){ if(app.version.substr(0,app.version.indexOf('.'))==1){ alert("Sorry You Need CS3 or CS4 to run this script!"); return; } var dlg = "dialog{text:'Script Interface',bounds:[100,100,500,310],"+ "panel0:Panel{bounds:[10,10,390,200] , text:'' ,properties:{borderStyle:'etched',su1PanelCoordinates:true},"+ "title:StaticText{bounds:[60,10,350,40] , text:'Add/Replace/Remove Keyword' ,properties:{scrolling:undefined,multiline:undefined}},"+ "panel1:Panel{bounds:[10,40,370,150] , text:'' ,properties:{borderStyle:'etched',su1PanelCoordinates:true},"+ "addKey:Checkbox{bounds:[20,10,160,31] , text:'Add Keyword' },"+ "statictext1:StaticText{bounds:[20,40,119,60] , text:'Replace' ,properties:{scrolling:undefined,multiline:undefined}},"+ "From:EditText{bounds:[120,40,350,60] , text:'' ,properties:{multiline:false,noecho:false,readonly:false}},"+ "statictext2:StaticText{bounds:[20,80,90,97] , text:'With' ,properties:{scrolling:undefined,multiline:undefined}},"+ "To:EditText{bounds:[120,80,350,100] , text:'' ,properties:{multiline:false,noecho:false,readonly:false}}},"+ "button0:Button{bounds:[10,160,180,181] , text:'Ok' },"+ "button1:Button{bounds:[200,160,370,181] , text:'Cancel' }}};"; var win = new Window(dlg,"Replace Keyword"); win.center(); win.panel0.title.graphics.font = ScriptUI.newFont("Times","BOLDITALIC",20); g = win.graphics; b=win.panel0.title.graphics; var myBrush = g.newBrush(g.BrushType.SOLID_COLOR, [0.99, 0.99, 0.20, 1]); g.backgroundColor = myBrush; var myPen =b.newPen (g.PenType.SOLID_COLOR, [0.00, 0.00, 0.99, 1],lineWidth=1); var myPen2 =b.newPen (g.PenType.SOLID_COLOR, [0.99, 0.00, 0.00, 1],lineWidth=1); g.foregroundColor = myPen; b.foregroundColor = myPen2; win.panel0.panel1.From.active=true; win.panel0.panel1.addKey.onClick = function() { if(win.panel0.panel1.addKey.value) { win.panel0.panel1.statictext1.text = "New Keyword"; win.panel0.panel1.From.active=true; win.panel0.panel1.statictext2.visible=false; win.panel0.panel1.To.visible=false; } if(!win.panel0.panel1.addKey.value) { win.panel0.panel1.statictext1.text = "Replace"; win.panel0.panel1.statictext2.visible=true; win.panel0.panel1.To.visible=true; win.panel0.panel1.From.active=true; } } win.center(); var done = false; while (!done) { var x = win.show(); if (x == 0 || x == 2) { win.canceled = true; done = true; } else if (x == 1) { done = true; var result = valiDate(); if(result != true) { alert(result); return; }else{ var Replace = win.panel0.panel1.From.text; var With = win.panel0.panel1.To.text; var addKey = win.panel0.panel1.addKey.value; processKeyword(Replace,With,addKey); } } } function valiDate(){ if(win.panel0.panel1.From.text =='') return "No Keyword Entered!"; return true; } function processKeyword(Replace,With,addKey){ try{ loadXMPScript(); }catch(e){ alert("Can not load XMPScript\r" + e.message); } var items = app.document.selections; for (var i = 0; i < items.length; i++){ var file=new Thumbnail(items[i]); try{ var xmpFile = new XMPFile(file.path, XMPConst.UNKNOWN,XMPConst.OPEN_FOR_UPDATE); }catch(e){ alert("Problem opening xmp for update:-\r" + file.path +"\r" +e.message); return; } try{ var xmp = xmpFile.getXMP(); }catch(e){ alert("Problem opening xmp data:-\r" + e.message); return; } try{ var tmpCount = xmp.countArrayItems(XMPConst.NS_DC, "subject"); }catch(e){ alert("Cannot get count \r" + e.message); } if(addKey){ xmp.appendArrayItem(XMPConst.NS_DC, "subject", Replace, 0,XMPConst.ARRAY_IS_UNORDERED); } if(tmpCount >0 && !addKey){ for (var a =0;a<tmpCount;a++){ var Keyword = xmp.getArrayItem(XMPConst.NS_DC,'subject', a+1); if(Keyword == Replace && With == '') { xmp.deleteArrayItem(XMPConst.NS_DC,'subject', a+1); } if(Keyword == Replace && With != ''){ xmp.setArrayItem(XMPConst.NS_DC,'subject', a+1,With); } } } if (xmpFile.canPutXMP(xmp)) { xmpFile.putXMP(xmp); }else{ alert(e.message); } xmpFile.closeFile(XMPConst.CLOSE_UPDATE_SAFELY); } unloadXMPScript(); } } function loadXMPScript() { var results = new XMPLibMsg("XMPScript Library already loaded", 0, false); if (!ExternalObject.AdobeXMPScript) { try { ExternalObject.AdobeXMPScript = new ExternalObject('lib:AdobeXMPScript'); results.message = "XMPScript Library loaded"; } catch (e) { alert("Could not load AdobeXMPScript \r" + e.message); results.message = "ERROR Loading AdobeXMPScript: " + e; results.line = e.line; results.error = true; } } return results; } function unloadXMPScript() { var results = new XMPLibMsg("XMPScript Library not loaded", 0, false); if( ExternalObject.AdobeXMPScript ) { try { ExternalObject.AdobeXMPScript.unload(); ExternalObject.AdobeXMPScript = undefined; results.message = "XMPScript Library successfully unloaded"; } catch (e) { results.message = "ERROR unloading AdobeXMPScript: " + e; results.line = e.line; results.error = true; } } return results; } function XMPLibMsg (inMessage, inLine, inError) { this.message = inMessage; this.line = inLine; this.error = inError; } ... View more

@karthikeyan.subbiah You might find these custom JSON configuration files useful if you are using that plugin. You can modify the JSON to use only the properties you need. This might be faster than entering properties one at a time in the panel editor. Iptc4xmpCore_properties_view.json will probably have the properties you need.  ... View more

@karthikeyan.subbiah This may not meet your needs exactly, but have a look at the excellent Custom Metadata Panel CEP plugin. It's much more flexible than the Info Panel and it works in Bridge, Photoshop, and Illustrator.   https://exchange.adobe.com/creativecloud.details.103752.html  https://github.com/adobe-dmeservices/custom-metadata    It has an option for a multi dropdown. It doesn't allow you to select multple items at once, but it does allow you to add items one at a time.       ... View more

Oh I see now, at  it's in the "Download resources" link, not the "API Documentation" link. Thanks @Kukurykus    ... View more

@karthikeyan.subbiah My appologies, you are working with an XML extension, but I jumped right into the JavaScript ExtendScript environment. There is more info at https://extendscript.docsforadobe.dev/index.html. You can do a lot more with ExtendScript, but it is much more complicated because you have to code everything - the UI and all functions. Weirdly, Adobe seem to have moved the ExtendScript SDK and examples. The link http://www.adobe.com/devnet/scripting/ redirects to https://www.adobe.io/creative-cloud/ and I can't find any information about ExtendScript there. I'm having trouble navigating the new Adobe developer site, so I can't help you find what you need there.   I don't think you can accomplish what you want with an XML FileInfo extension. It could be done with ExtendScript, but the would a lot more to be added the example I provided and I'm not sure it would work in Illustrator and Photoshop. Adobe would probably like us to use the newer CEP HTML/JavaScript Extensions https://github.com/Adobe-CEP/Getting-Started-guides which I have not yet explored because it is even more complicated.  ... View more

I'm sorry to tell you that the dropdown can only have one selection. You will have to use a list box instead. You might not want a bunch of big list boxes filling up your UI, so you could create a pseudo drop down by setting the listbox height to 0 and using a button that expands it to a larger height revealing the list. On a button click, or some other event, the list box could go back to a height of 0 and save the selected values.   Here is a sample solution, but there are a lot of other possibilities. There is some weirdness in ScriptUI controlls like preferredSize, minimumSize, and maximumSize, so you might have to try different combinations to get the desired display in Windows or Mac.   var win = new Window('palette',"listbox as dropdown", undefined, {closeButton:true}); var keywords = ["one", "two", "three","four","five","six","seven"] list1Grp = win.add('group'); list1Grp.orientation = 'column'; list1Grp.alignChildren = 'left'; list1Grp.spacing = 0; list2Grp = list1Grp.add('group'); list2Grp.orientation = 'row'; list2Grp.alignChildren = 'left'; list2Grp.spacing = 0; list1Txt = list2Grp.add('statictext',undefined,"Select Keywords"); list1Txt.preferredSize=[280,25]; list1Btn = list2Grp.add('button',undefined,":red_triangle_pointed_down: "); list1Btn.preferredSize=[20,20]; var list1 =list1Grp.add ('listbox', undefined, keywords, {multiselect: true}); list1.preferredSize=[280,0]; list2Btn = list1Grp.add('button',undefined,"Add Keywords"); list2Btn.preferredSize=[280,20]; list2Btn.visible = false; list1Btn.onClick=function(){ list1.minimumSize=[280,150]; list1.maximumSize=[280,150]; list2Btn.visible = true; win.layout.layout (true); } list2Btn.onClick=function(){ if(list1.selection == null){ list1Txt.text = "Select Keywords"; } else{ list1Txt.text = list1.selection.join("; ") // Display the list selections. You could use this to write to XMP or put the list selections in an array to write to XMP } list1.minimumSize=[280,0]; list1.maximumSize=[280,0]; list2Btn.visible = false; win.layout.layout (true); } win.show();     ... View more

I am not getting the OpenFile error in Bridge 12.0.0.234   Your script worked, except that I didn't get a value for var des = xmp.getProperty(XMPConst.NS_DC, "description").toString(); so I changed it to this: var des = xmp.getArrayItem(XMPConst.NS_DC, "description",1).toString(); ... View more

Your original method worked for me. The method @Stephen Marsh suggested also worked.   The only difference is that in your screenshot, the current filename is Behandlungen 45 Sek 1:1; Treatments 45 Sec 1:1;.mp4  Is that really the original filename or is it an aboration of the batch rename tool? I wouldn't think it's possible to have that filename in Windows.   ... View more

You can use batch rename with string substitution and regular expression in Bridge to do this. I found a way to do it in two separate operations. Perhaps someone else here can suggest a way to combine them into a single operation. Step 1: remove first 8 characters ^.{8}   Step 2: remove the last 12 characters .{12}$       ... View more

@default855pel8zu0bm I'm sorry to tell you this, but you should not use the XML Metadata Panel extension!   First, I cannot find a way to change the property label in the Metadata Panel. I tried to create a localization file for the labels, and this also failed. Since the label is correct in the File Info Panel, I can only conclude that this is a bug with the Metadata Panel. Your XML code is correct, the problem is with Bridge.   Second, I remembered a big problem with the XML extensions metadata panels - they do not create correct XMP array structures for default namespaces. For example, dc:subject should be a bag list of values, like this: <dc:subject> <rdf:Bag> <rdf:li>KEYWORD 1</rdf:li> <rdf:li>KEYWORD 2</rdf:li> </rdf:Bag> </dc:subject> However, the XML Metadata Panel saves it like this: <dc:subject>KEYWORD 1; KEYWORD 2</dc:subject> This is invalid XMP and will not be readable by other panels or applications. This only seems to happen in an XML metadata panel, the File Info Panel works correctly. I have reported this to Adobe in the past, but apparantly it has not been fixed. This is especially egregious becasue Adobe created the XMP standard and the xmp namespace. They should be the last ones to write invalid XMP!   You should look at the other Custom Metadata Panel I mentioned.    ... View more

@default855pel8zu0bm Thanks. I was able to re-create the extension folder and load the panel. I also see the same problem you do with the property label. I'll see if I can find a solution. ... View more

This looks like an XML extension based on the XMP Metadata UI SDK CC 2014  I have found that these extensions have several bugs and can be tricky. I can look at your extension, if you would be able to share the entire folder /AgendaLiveUp   You might consider an alternative for making custom metadata panels. It is more reliable and has many more features. https://exchange.adobe.com/creativecloud.details.103752.html ... View more

This is uses with(app.document) in your original code: mkFolder() function mkFolder() { var text; var folderName = prompt("New Foder:", "untitled folder"); if(folderName == null) { text = "User canceled operation."; alert(text); } else if (folderName == "") { text = "The field can not be empty."; alert(text); } else { var newFolder = Folder(app.document.presentationPath + "/" +folderName); if(!newFolder.exists) { newFolder.create(); // var files = Folder(newFolder).execute(); // open new folder in system file browser // app.browseTo(newFolder) // open new folder in Bridge workspace with(app.document) thumbnail = newFolder } else { alert("The folder already exists"); } } }   ... View more

Just realized my solution opens a new Bridge window, so it's not ideal. @Kukurykus solution is better. ... View more

Also try this:   app.browseTo(newFolder)   ... View more

This will open the new folder after it is created: mkFolder() function mkFolder() { var text; var folderName = prompt("New Foder:", "untitled folder"); if(folderName == null) { text = "User canceled operation."; alert(text); } else if (folderName == "") { text = "The field can not be empty."; alert(text); } else { var newFolder = Folder(app.document.presentationPath + "/" +folderName); if(!newFolder.exists) { newFolder.create(); // open new folder var files = Folder(newFolder).execute(); } else { alert("The folder already exists"); } } } ... View more

I wish I had the answer, but I'm still learning CEP extensions.   The answer might be found in this Custom Metadata Panel which displays metadata when thumbnail selections are changed. custom-metadata   You can get the source code at  com.adobe.custom-metadata-cep.1.3.0.zxp   Or, install the extension and view the files in \CEP\extensions\com.adobe.custom-metadata-cep\   See selectEvent in this file: host\startupSelection.jsx See SelectEventPlugin (as well as several other Events) in this file: \index.js   ... View more

These are an amazing resource, thanks for shring them @Lumigraphics  ... View more

Try changing the Date Time Original in the Camera Data (Exif) section   ... View more

We'll have to dig into the metadata to find out what is different about the Nikon Z5 files. Are there any photos from the shoot that you can share, either here or directly to me? Since this was from a wedding shoot, that's probably not possible. Perhaps on your next shoot you could take a test shot from both cameras. I know, it would be good to figure this out before your next shoot 🙂   Another option is to read the metadata from a photo from each camera using Jeffrey's Image Metadata Viewer I'm looking for the Date/Time and Time Zone Offset. It would be helpful if you could copy and paste the full metadata viewer results into a document and share that. ... View more

To get a more complete view of the metadata, you might need to use another app. ExifTool is great for this, but it is a command line app and requires a little getting used to. An easier alternitive is an ExifTool-based viewer like Jeffrey's Image Metadata Viewer  It's a web browser tool that allows you to choose a local file to read.       ... View more

This is an interesting problem. I assumed File Info displayed the XMP dates. The trick  now is to figure out what file or metadata property is being displayed, or causing Bridge to adjust the display.   Were the files from both cameras proceesed on the same app and computer? I was reading a post elsewhere about how an app can change the time offset to the system settings when converting files. I'm guessing you did all the processing yourself, so this is an unlikley cause. Still, you might check the dates of thr RAW file in Bridge.   You probably have already checked the dates in the side metadata panel, but just to confirm, are the File Properties Date Created and Camera Data (Exif) Date time Original also incorrect?   ... View more

The screen shot might not have loaded. Here it is again.     ... View more

@jessicamannsphoto I'm not trying to be difficult or waste your time, I'm trying to eliminate possible causes so we can determine why Bridge is displayng a different date than Finder. It's possible Finder is adjusting the date display based on some other metadata parameter or, it might reading a different date properties (there are several).  Knowing what the actual metadata is (not what is displayed by an app) will help in finding a solution.  Could you look at the raw XMP record in the File Info window of a file from your camera and one from the other camera and see what the CreateDate and ModifyDate values are?   ... View more

I think this will work   Find: ^(.{4})(.{2}) Replace: $1-$2- ... View more