Metadata Scripting

Good Morning, I hope someone out there can help.....
I am having trouble saving all the metadata info using Bridge.
I've tried filling in the sections both in Bridge, and 'file info' in PS, and saving the metadata template, and for some reason, all saves ok, except the copyright status, and copyright info url sections. I have checked these check boxes are ticked before I save and close the file, and when I reopen the image, again, both these fields are empty.
This happens regardless of if I use 'append metadata' or 'replace metadata', or select all in Bridge and set the metadata via the file info option.
The information will only save if I apply to each individual file via photoshop, which is very time consuming, even if I automate an action...
Adobe Technical Support have advised me to ask on the forum if there is a known script...please help!
many thanks
amanda

I sensed that, and thought they'd misadvised you. Scripting's not for everyone.
In Bridge, select a file, right click it, select File Info, and enter some copyright info. Before you close the File Info dialog, there's a triangle menu at the top right that allows you to Append and Replace, but also lets you save the template. Notice as well that it has a Show option.
Save the template, and it writes an xmp file. Then use the Show option to open the templates' folder in Finder/Explorer. You can then open your xmp file in a text editor. Basically you need to delete stuff that's not relevant to copyright. If you've ever looked at HTML you'll find it familiar.
John

Similar Messages

Script to automatically enter document metadata

I need to enter document info as metadata into all of my Indesign documents as they are posted on the web as pdf docs so I wanted a script that would automaticaly enter the data once the document has been saved. I only need 3 fields to be filled.
My document is saved as "1234.1234 Document Name_D1" and the 3 fields I need are:
Document Title: only the wording after the code and before the underscore "Document Name"
Author: Is always "Company Name"
Keywords: only the "1234.1234" before the doc name
I'm not sure if this is at all possible so if it can be done automatically using only the whole document name then I'll take that instead.
Thanks,

Dear RinaPatch,
Can you please try the below JS code? May be it will help to you.
var myDocument = app.activeDocument;
with (myDocument.metadataPreferences){
    author = "Adobe";
    copyrightInfoURL = "http://www.adobe.com";
    copyrightNotice = "This document is copyrighted.";
    copyrightStatus = CopyrightStatus.yes;
    description = "Example of xmp metadata scripting in InDesign CS";
    documentTitle = "XMP Example";
    jobName = "XMP_Example_2003";
    keywords = ["animal", "mineral", "vegetable"];
    var myNewContainer = createContainerItem("http://ns.adobe.com/xap/1.0/", "email");
    setProperty("http://ns.adobe.com/xap/1.0/", "email/*[1]", "[email protected]");
Otherwise, please provide the details clearly.
thx,
csm_phil

Copy GPS Metadata Back into Photoshop TIFFs with Bridge Scripting

I've published a sample script on the Bridge blog about metadata scripting with Bridge and AdobeXMPScript -- specifically the script deals with GPS metadata and automation that synchronizes work done by both Bridge and Photoshop.
Here is the link:
http://blogs.adobe.com/bridge/2009/01/copy_gps_metada_1.html
Enjoy!
-David

I couldn't read all through your post as I am jetting out of here.
Buy this:
http://www.fastpictureviewer.com/codecs/
and install it. It's relatively cheap. Screen shot is from Windows Explorer.
Handles ID, PSD, etc., files as well. Though the preview uses greeked text for the most part for the ID files.
Take care, Mike

How can I export metadata to a csv file in CS4?

Help please, I used Workflow Automation Scripts on CS3 but it doesn't seem to work on CS4.

OK,
after combing through these posts and trying various 'solutions' I have found that the Barred Rock export metadata script is the only one I have been able to get to work in CS4, kinda. It is a superior script to the original workflow automation script that edo75 refers to, as it does not seem to have the comma issue encountered by jesse and others, where if there are any commas in your metadata it creates a new column and your excel file becomes nonsensical and disorganized. There is a way to avoid this by the way, simply by opening a new file in excel and importing the csv file as text, you then tell excel to read the data the right way by selecting various delimiter combinations. It is not a perfect solution but I have found that by doing this it places most of my metadata in the proper columns, and I end up doing a minimal amount of editing. The barred rock version, which I assume is a modified version of the original script available from adobe as the interface is exactly the same, does not seem to have this issue with commas at all, I am unsure why. If B. Stucky is still reading these posts he may be able to answer, as I think he wrote this script?
Anyhow I was able to get the script to load in CS4 and then I had to tweek the script to recognize my custom metadata schema, which I was able to do. Now however there is an issue with it recognizing the actual metadata in the image files. I suspect it is a mynamespace issue, that is, I do not have the right path for it to locate the actual metadata for export.
here is where I suspect the problem lay, where this "http://NPSAlaskaImageStandard" is incorrect.
new MdNs.MetadataNamespace( "NPS Alaska Image Standard", "http://NPSAlaskaImageStandard", "NPSAlaskaImageStandard" );
I am a total novice with this stuff so this may not be it at all, however this is my best guess, anyone know the answer?

Error while importing : /metadata/iam-features-ldap-sync/LDAPUser.xml

Hi,
I am unable to import modified Oracle Identity Manager metadata. I am using OIM 11.1.1.5 on Windows Server 2007 EE.
I am trying to use the import/export functionality via EM.
I am able to export the LDAPUser.xml file from */metadata/iam-features-ldap-sync/LDAPUser.xml,* have made changes to it but when I am importing it back I am getting the error :
Error occurred while executing operation.
MDS-00001: exception in Metadata Services layer
MDS-01059: document with the name /metadata/iam-features-ldap-sync/LDAPUser.xml missing in the source metadata store
The values of the parameters in the import MDS operations are :
fromLocation : E:/MDS/import/ +(On the physical server hosting the OIM)+
docs : */metadata/iam-features-ldap-sync/LDAPUser.xml*
restrictCustTo:
excludeAllCust: false
excludeBaseDocsan : false
excludeExtendedMetadata : false
cancelOnException : true
I have tried using the command line script as well, It runs without a hitch but when I try and import back, it gives me the same old unedited document.
Has anyone been successful with this approach ?
Regards,

Yes, I have. But still the same issue. It seem to run fine using the weblogicImportmetadata.bat fine but when I export and check the updated file, I still get back the original.
Here's what I get on runnung the weblogicImportmetadata.bat file
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Starting import metadata script ....
Please enter your username :weblogic
Please enter your password :
+Please enter your server URL [t3://localhost:7001] :t3://localhost:7001+
Connecting to t3://localhost:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'OIM
+1'.+
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Location changed to domainRuntime tree. This is a read-only tree with DomainMBea
n as the root.
For more help, use help(domainRuntime)
Disconnected from weblogic server: AdminServer
End of importing metadata script ...
Exiting WebLogic Scripting Tool.
C:\Oracle\Middleware1\Oracle_IDAM\server\bin>
Edited by: 810367 on Aug 21, 2012 6:45 PM

Error while exporting metadata file /iam-features-ldap-sync/LDAPUser.xml

Hi All,
i am trying to export /iam-features-ldap-sync/LDAPUser.xml metadata file with the weblogic properties mentioned below
# Weblogic Server Name on which OIM application is running
wls_servername=oim_server1
# If you are importing or exporting any out of box event handlers, value is oim.
# For rest of the out of box metadata, value is OIMMetadata.
# If you are importing or exporting any custom data, always use application name as OIMMetadata.
application_name=OIMMetadata
# Directory location from which XML file should be imported.
# Lets say I want to import User.xml and it is in the location /scratc/asmaram/temp/oim/file/User.xml,
# I should give from location value as /scratc/asmaram/temp/oim. Make sure no other files exist
# in this folder or in its sub folders. Import utility tries to recursively import all the files under the
# from location folder. This property is only used by weblogicImportMetadata.sh
metadata_from_loc=@metadata_from_loc
# Directory location to which XML file should be exported to
metadata_to_loc=D:/MDS
# For example /file/User.xml to export user entity definition. You can specify multiple xml files as comma separated values.
# This property is only used by weblogicExportMetadata.sh and weblogicDeleteMetadata.sh scripts
metadata_files=/metadata/iam-features-ldap-sync/LDAPUser.xml
# Application version
application_version=11.1.1.3.0
i get the following error
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Starting export metadata script ....
Please enter your username [weblogic] :weblogic
Please enter your password [welcome1] :
Please enter your server URL [t3://localhost:7001] :t3://hostname:7001
Connecting to t3://hostname:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'OIMDOMAIN'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Location changed to domainRuntime tree. This is a read-only tree with DomainMBea
n as the root.
For more help, use help(domainRuntime)
Problem invoking WLST - Traceback (innermost last):
File "C:\Oracle\Middleware\Oracle_IDM1\server\bin\weblogicExportMetadata.py";,
line 22, in ?
File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py";, line 134, i
n exportMetadata
File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py";, line 568, i
n executeAppRuntimeMBeanOperation
File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py";, line 538, i
n getMDSAppRuntimeMBean
UserWarning: MDS-91002: MDS Application runtime MBean for "OIMMetadata" is not available. "exportMetadata" operation failure.
i have exported these files multiple times, it never gave an errror, but this time i see this error, please help.
Thanks in advance

Glad that worked.
Working with MDS, another way is to use the EM console for exporting/importing data from/to MDS. This I find lot easier rather than working with the OOTB script.
Steps are:
http://ADMINSTRATION_SERVER/em
Navigate to Identity and Access, oim. Right-click and navigate to System MBean Browser.
Under Application Defined MBeans, navigate to oracle.mds.lcm, Server:oim_server1, Application:oim, MDSAppRuntime.
To export the configuration files:
•     Click the Operations tab, and then click exportMetaData.
•     In the toLocation field, enter /tmp or the name of another directory.
•     Select createSubDir as false.
•     In the docs field, enter the complete file location as the Element.
•     Also select false for excludeAllCust, excludeBaseDocs, and excludeExtendedMetadata. Then, click Invoke.
This exports the file specified in the docs field to the directory specified in the toLocation field.
To import the configuration files:
•     Click importMetaData
•     In the fromLocation field, enter /tmp or the name of the directory in which you have the configuration files.
•     Select createSubDir as false.
•     In the docs field, enter the complete file location as the Element. For example, /db/oim-config.xml.
•     Also select false for excludeAllCust, excludeBaseDocs, and excludeExtendedMetadata. Then, click Invoke.
This imports the file specified in the docs field to MDS in the toLocation field.
HTH

Exporting Metadata (caption information) from JPEGS to a comma separated value (CSV) file

Here is my dilemma. I am an archivist at an arts organization and we are in the process of digitizing many of our materials to post them on the web and make them available to internet users. One of the principle components of our collection is a large trove of photographs. We have been in the process of digitizing these images and embedding metadata (in the Caption/Description, Author/Photographer and Copyright fields) via PhotoShops File Info command.
Now I am at a crossroads. We need to extract this metadata and transfer it into a comma separated value form, like an Excel spreadsheet or a FileMakerPro database. I have been told that it is not possible to do this through PhotoShop, that I must run a script through Acrobat or Bridge. I have no clue how to do this. I have been directed to a couple of links.
First I was directed to this (now dead) link: http://www.barredrocksoftware.com/products.html
The BSExportMetadata script allegedly exports the metadata from files selected in Adobe's Bridge into a comma separated value (CSV) file suitable for import into Excel, Access and most database programs. It installs as a Bridge menu item making it simple to use. The the Export Metadata script provides you with an easy to use wizard allowing you to select associated information about a set of images that you can then export. This script requires Creative Suite 2 (CS2). This script sounds like it does exactly what I want to do, but unfortunately, it no longer exists.
Then I found this:
Arnold Dubin, "Script to Export and Import Keywords and Metadata" #13, 8 Aug 2005 7:23 am
I tried this procedure, but nothing seemed to happen. I also tried to copy the script into the JAVASCRIPT action option in Acrobat, but I received a message that the script had an error. It also seems to me that this script does not set up a dumping point, that is, a file into which this information will be exported to.
I am a novice, not a code writer or a programmer/developer. I need a step-by-step explanation of how to implement this filtering of information. We have about 2000 jpeg and tiff files, so I would rather not go through each file and copy and paste this information elsewhere. I need to find out how to create a batch process that will do this procedure for me. Can anyone help?

Hello -
Is anyone aware of a tool that will do the above that is available for mac? Everything I've found so far seems to be PC only.
Any help is appreciated, thanks!

JS metadata CS3 & CS2

I have a script in CS3 that writes to the documents meta data using:
myDocument.metadataPreferences.setProperty("http://ns.adobe.com/pdfx/1.3/", "myTitle", myTitle);
This works fine in CS3 but does not work in CS2.
if I try:
app.activeDocument.metadataPreferences.setProperty("http://ns.adobe.com/pdfx/1.3/", "myTitle", "myTitle");
In the console of ExtendScritp Toolkit I get:
Result: undefined
I need to make a CS2 version of this script so if anyone has any suggestions it would be greatly appreciated.

Looking to CS2 & CS3 rererences, the way to define Metadatapreferences is the same.
MetadataPreference.setProperty (namespace:string, path:string, value:string)
so it's quite weird.
Here is a example written by Olav,
Maybe you can watch for info in it :
//MetadataExample.jsx
//An InDesign CS2 JavaScript
//Adds metadata to an example document.
var myDocument = app.documents.add();
with (myDocument.metadataPreferences){
author = "Olav Martin Kvern";
copyrightInfoURL = "http://www.adobe.com";
copyrightNotice = "This document is copyrighted.";
copyrightStatus = CopyrightStatus.yes;
description = "Example of xmp metadata scripting in InDesign CS";
documentTitle = "XMP Example";
jobName = "XMP_Example_2003";
keywords = ["animal", "mineral", "vegetable"];
//The metadata preferences object also includes the read-only
//creator, format, creationDate, modificationDate, and serverURL
//properties that are automatically entered and maintained by InDesign.
//Create a custom XMP container, "email"
var myNewContainer = createContainerItem("http://ns.adobe.com/xap/1.0/", "email");
setProperty("http://ns.adobe.com/xap/1.0/", "email/*[1]", "[email protected]");
Loic

Possible to remove selective Metadata?

Hi everyone
I am quite new to Javascript, but have managed to create a script that can modify a metadata tag and also add metadata tags (e.g. create a custom namespace with various tags).
I have however not found a reliable way to remove metadata. Sometimes one can delete a metadata tag (and the tag's value) by writing an empty string into it. Other times it leaves the tag name and just deletes the tag value.
Does anyone know if there is a simple way to delete a whole namespace (e.g. all the camera-raw settings) along with all the tags?
Any suggestions welcome!
Regards, Nigel

Nigel,
I can't tell you how to clear the whole namespace, but I might be able to help figure it out if I could see the code you are working with.
I am sure that other javascript noobs (like myself) would like to see what you came up with. It would be great if you could share your successful metadata scripts with us. You can do so using the Exchange link below.
http://share.studio.adobe.com/axBrowseProduct.asp?p=9
Alex

XMP metadata in active indd document

Is there any possibility to add XMP metadata in the active InDesign document using scripting?
Thanks
SS

Hi Sankar,
You can use the Scripting guide example below here.
var myDocument = app.activeDocument;
with (myDocument.metadataPreferences){
author = "Adobe";
copyrightInfoURL = "http://www.adobe.com";
copyrightNotice = "This document is copyrighted.";
copyrightStatus = CopyrightStatus.yes;
description = "Example of xmp metadata scripting in InDesign CS";
documentTitle = "XMP Example";
jobName = "XMP_Example_2003";
keywords = ["animal", "mineral", "vegetable"];
//The metadata preferences object also includes the read-only
//creator, format, creationDate, modificationDate, and serverURL
//properties that are automatically entered and maintained by InDesign.
//Create a custom XMP container, "email"
var myNewContainer = createContainerItem("http://ns.adobe.com/xap/1.0/", "email");
setProperty("http://ns.adobe.com/xap/1.0/", "email/*[1]", "[email protected]");
thx
csm_phil

Metadata into database

Hi,
I’m very happy to use Adobe Bridge and I think that is a great tool, and I will thank you for that. I have thousands of images in my computer and for a great number of that I already have a lot of information in the metadata… I know how to demand information, I know how to search inside, but I need to know if I can import all this information in a different software …. Something like excel or access….
For example: I need to put in a database all images that are made for a client, and I need to see all the information for each image in the same table, also I need to print all this information…please teach me how to do that
Thank you

You can extract data from your files into a CSV file that will open in Excel or import to a database.
Using Bridge there are a couple of scripts.
The Barred Rock script that can be found in this thread.
http://www.ps-scripts.com/bb/viewtopic.php?f=19&t=2365&sid=d3879143b95adbfff4998c35f85c336 b
If only a few fields are required then the "Extract Metadata" script in the Bridge section might work for you.
http://www.ps-bridge-scripts.talktalk.net
Exiftool should also be considered for the task.
http://www.sno.phy.queensu.ca/~phil/exiftool/
Good luck.

Non-scripter attempting a metatagging script

my script is doing everything i want except it is converting all spaces and periods to semicolons in the final metatag and i cannot figure out why.
It will be VERY obvious that the attached script is nothing but a bunch of snippets clipped together to perform most of what i want...
I want to run this script at the end as i am completing a project to insert the needed metatags.
i want the project name
i want the copyright info
i want keywords to include all images used in the document
i want to be able to add keywords.
to run this script you will need a character style called    KeywordsCStyle
//-----document title and copyright---------
var myDocument = app.activeDocument;
with (myDocument.metadataPreferences){
    //author = "Adobe";
    copyrightInfoURL = "UPMC.com"
    copyrightNotice = "© 2014 UPMC";
    copyrightStatus = CopyrightStatus.yes;
    //description = "Example of xmp metadata scripting in InDesign CS";
    documentTitle = myDocument.name.split(".indd")[0];
    //jobName = "XMP_Example_2003";
    //var myNewContainer = createContainerItem("http://ns.adobe.com/xap/1.0/", "email");
    //setProperty("http://ns.adobe.com/xap/1.0/", "email/*[1]", "[email protected]");
with (myDocument.metadataPreferences){
        //author = "scott rudy";
        documentTitle = myDocument.name.split(".indd")[0];
//var curDocTitle = app.activeDocument.metadataPreferences.documentTitle;
//var curAuthor = app.activeDocument.metadataPreferences.author;
var curKeywords = app.activeDocument.metadataPreferences.keywords;
Array.prototype.unique = function (){
    var r = new Array();
    o:for(var i = 0, n = this.length; i < n; i++){
        for(var x = 0, y = r.length; x < y; x++){
            if(r[x]==this[i]) continue o;}
        r[r.length] = this[i];}
    return r;
function addXMP(/*find GREP*/findString, /*para style*/paraStyle, /*chr style*/chrStyle, /*insert to*/XMPdest){
// reset search fields
app.findGrepPreferences = NothingEnum.nothing;
app.changeGrepPreferences = NothingEnum.nothing;
// setting search parameters
if(findString)app.findGrepPreferences.findWhat = findString;
if(paraStyle)app.findGrepPreferences.appliedParagraphStyle = paraStyle;
if(chrStyle)app.findGrepPreferences.appliedCharacterStyle = chrStyle;
switch (XMPdest){
    // insert keywords
    case "Keywords":
      var myKeywords = app.activeDocument.findGrep();
      var myKeys = Array();
      // loop through keywords and get contents
      for(var i = 0; i < myKeywords.length; i++)
        myKeys.push(myKeywords[i].contents);
      //myKeys.sort();
      // delete duplicates
      //myKeys = myKeys.unique();
      // insert Keywords to document XMP
      app.activeDocument.metadataPreferences.keywords = myKeys;
      break;
    // Heading search/insert
    case "Heading":
      var myHeading = app.activeDocument.findGrep();
      app.activeDocument.metadataPreferences.documentTitle = myHeading[0].contents;
      break;
    // Author search/insert
   // case "Author":
    // var myAuthor = app.activeDocument.findGrep();
    // app.activeDocument.metadataPreferences.author = myAuthor[0].contents;
   //   break;
// copy all image names //----------------------------------------------//
f = app.activeDocument.textFrames.add({geometricBounds:[0,0,"20mm","20mm"]});
f.contents = app.activeDocument.links.everyItem().name.join("\r");
f.parentStory.texts[0].select();
//-----------change character style-------------------//
var cName = "KeywordsCStyle";
var mCstyle = app.activeDocument.characterStyles.item(cName);
if (mCstyle.isValid)
       app.selection[0].applyCharacterStyle(mCstyle);
app.copy();
// add Keywords
addXMP("\\w{1,}","","KeywordsCStyle","Keywords");
// add Heading
//addXMP("","HeadingPStyle","","Heading");
//add Author
addXMP("","AuthorPStyle","","Author");
//----delete image names textbox--------
f.remove();

I decided to give up on the character style to add keywords so i have to thank JUmp_over for all the help with my complete script...
here it is after i cleaned it up if anybody else has a need to add keywords to their indesign file (and ultimately to the resulting PDFs
//-----document title and copyright---------
var myDocument = app.activeDocument;
with (myDocument.metadataPreferences){
    copyrightInfoURL = "UPMC.com"
    copyrightNotice = "© 2014 UPMC";
    copyrightStatus = CopyrightStatus.yes;
    documentTitle = myDocument.name.split(".indd")[0];
//---------------------add document name-------------------------------
with (myDocument.metadataPreferences){
        documentTitle = myDocument.name.split(".indd")[0];
//-----------------------images to keywords--------------------------//
app.activeDocument.metadataPreferences.keywords = app.activeDocument.links.everyItem().name;
//-------------open file info dialog box---------------------
app.menuActions.itemByID(89092).invoke()

Setting metadata in Bridge

Can someone give some advice on setting metadata values within Bridge using javascript? The examples all seem to deal with Text types like the following:
md = tn.metadata;
md.namespace = "http://ns.adobe.com/photoshop/1.0/";
md.Author = "Jane Smith";
But when trying to set other types, like the "caption" (which gets mapped to "http://purl.org/dc/elements/1.1/description"), the script will throw an exception.
md.namespace = "http://purl.org/dc/elements/1.1/";
md.description = "New Caption"
-- Uncaught exception description --
I'm thinking this is probably because dc:description is defined as a "Lang Alt" type in the xmp specification which in turn is defined as:
"Language alternatives are a form of rdf:Alt array, referred to as the Lang Alt type. In this
example, each array item is a simple text value; the value has a property qualifier, specified as
the property xml:lang, giving the language of that value. "
But no matter how I try accessing this object (there is no "reflect" available on metadata objects), I can't seem to change the string value.
Any ideas would be much appreciated.
On another topic, would it be possible for someone to post the Export Metadata Script here in this forum for those of us who don't have access to the partners site? Here's is my working go at an export metadata script for Bridge that simply prints to the debugger. It's basically a quick hack of some of the routines in AdobeLibrary3.jsx which it also needs in order to run.
Thanks,
Bruce
#target bridge
if( BridgeTalk.appName == "bridge" ) {
DebugMeta = {};
DebugMeta.execute = function() {
// print out the metadata for the selected thumbnails
var sels = app.document.selections;
for (var i = 0; i < sels.length; i++) {
var t = sels[i];
var m = t.synchronousMetadata;
// loop through all possible elements (properties)
var elements = MdNs.elements.keyList;
for (var j = 0; j < elements.length; j++) {
var el = MdNs.elements.get(elements[j]);
if (el.scriptAccessible) {
try {
// print the value (and the mapping if it's redirected)
var val = el.getValue(m);
if ( isValidReference( val )
&& ( val.length > 0 )
&& ( trim( val ) != null ) ) {
$.write(el.handle + " = " + val);
if (el.redirected) {
$.writeln(" (" + el.redirectElement.ns.ns + el.redirectElement.property + ")");
} else {
$.writeln();
} catch (e) {
// setup menu
var myMenu = createMenu( "command", "DebugMeta",
"-at the end of Tools-", "tools/DebugMeta", DebugMeta.execute);
var contextMenu = createMenu ( "command", "DebugMeta",
"-at the end of Thumbnail-", "thumbnail/DebugMeta", DebugMeta.execute);

Bruce,
I think most people here agree with your 2c, but there just wasn't time to do everything.
But one of the great things about Bridge Scripting is, if you don't like it, change it, or create something that will do what you need. If you don't like the way collections work, create your own browse scheme, and do it your way.
The MdNs object has a definition for an object, MdManager. The MdManager constructor takes a thumbnail object. It's "grab" method creates 2 enumerations. MdManager.enumeration contains a KeyedArrayList (object defined in lib3 just above MdNs) of all the metadata elements that actually have values. MdManager.noValue is a KeyedArrayList of metadata elements that do not have values. Now, the standard MdManager only provides checks against the standard XMP schemas. But if you want to extend that, just add a MdNs.MetadataNamespace and the MdNs.MdElement 's necessary to define the non-standard data you want to enumerate.
So while you can't use the metadata object to traverse the metadata structure, there are always other ways.
The concept of modifying the scripting features of Bridge didn't stop there. In Lib1, we extended the File object prototype in Bridge:
File.isFileType() - give it a comma delimited list of extensions, returns true if file matches any of the extensions
File.isPhotoshop() is the file one of "PSD,PDD,8BPS,JPEG,JPG,GIF,"
File.isPageMaker()
File.isInDesign()
File.isPDF()
File.isIllustrator()
File.isOpenableIllustrator()
File.isOpenablePhotoshop()
File.isScript()
File.getExtension( noDecode ) - gets you the extension of the file - noDecode is a boolean - if true it will not perform a decodeURI on the result. Default is false
File.getNameWithoutExtension( noDecode ) - gets you the name of the file without the extension. noDecode is a boolean - if true it will not perform a decodeURI on the result. Default is false
File.getFileWithExtension( ext ) - creates a new File object with the original file name and the provided extension. You provide only the extension ( "jpg" ), the function adds the dot (".jpg").
We also extended the Thumbnail object prototype:
Thumbnail.isFileType( ext ) - same as File.isFileType but for Thumbnails.
Then there's handy functions like:
ensureUniqueFile( file ) - pass it a file object. If the file object exists, it will return a new File object with a "(integer)" added to the filename. So if My Documents/foo.jpg exists, and you called:
ensureUniqueFile( new File( "~/My Documents/foo.jpg ) );
the result would be a file object: My Documents/foo(1).jpg
These next two are defined in lib3:
ensureUniqueFolder( folder ) - does the same thing for a folder
And one of my personal favorites:
verifyFolder( folder, silent ) - if you give it a Folder, it will verify that the folder actually exists, creating the entire path to the folder if necessary. "silent" is a boolean. If true - it will just make the folder (and path to the folder). If false (the default) it will flip up a "Folder does not exist - Do you want to create it" alert to the user, to give them the choice. IF the user opts not to create the folder, it returns undefined.
If My Documents is empty (no files/folders), and you want to write a file into My Documents/1/2/3/My Folder/foo.txt
var f = new File( "~/My Documents/1/2/3/My Folder/foo.txt" );
var folder = verifyFolder( f.parent, true );
f.open( "w" );
f.write( "Four score and seven years ago..." );
f.close();
The result of that ditty will be the successful writing of the file, and the creation of the entire path to the file. It will only create the path elements that do not exist.
Bob
Adobe Workflow Scripting

Extract 'File Properties' Metadata

I am looking for a way to extract all the information in the File Properties to a .csv. I have downloaded the Export Metadata script and it, works except I cannot include the File Properties in the Schema field. I hope there is a way to modify this script to include the File Properties.
Eric

Thanks
Good Luck.
My
Si
tes

User Modifiable Metadata Files - Oracle Identitty Manager

Hi everyone,
I'm a newbie in OIM 11.1.1.5.0 and I want to configure auto-approval for self-registration as it's explained in the User's guide for oim. I just don't understand where I can get the SelfCreateUserDataset.xml default template. I mean in which directory can I find it ?
I thought it was in the Oracle_HOME/server/metadata directory but the only sub-directories I have in this one are /db and /ldapReconJobs.
Thanks,
Thibault

Hi Rajiv,
Thanks for your quick answer ! I've already used the MDS Export Utility but it doesn't change anything ...
This is my weblogic.properties file :
wls_servername=oim_server1
application_name=oim
metadata_from_loc=@metadata_from_loc
metadata_to_loc=C:\Users\Administrateur\Desktop\metadata (metadata is the directory where I want to have this default template)
metadata_files=/metadata/iam-features-requestactions/model-data/SelfCreateUserDataset.xml
And when I launch weblogicExportMetadata.bat this is what I have in the console :
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Starting export metadata script ....
Please enter your username :weblogic
Please enter your password :
+Please enter your server URL [t3://localhost:7001] :t3://localhost:7001+
Connecting to t3://localhost:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'base_domain'.
Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or Admin port should be used instead.
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)
Disconnected from weblogic server: AdminServer
End of export metadata script ...
Exiting WebLogic Scripting Tool.
And I don't have any file in my metadata directory ...

Metadata Scripting

Similar Messages

Maybe you are looking for