Export metadata in Bridge

Is there a way to export the metadata for each image in Bridge?Currently the export option only includes the file name and extension.

Yes the metadata can be extracted, see...
http://forums.adobe.com/thread/966789?tstart=0

Similar Messages

Exporting Metadata from bridge to excel or other like program.

Is there a way to export just the metadata, using Bridge, associated with an image file into excel, access, or some other like program?
I would like to perform some kind of batch processing, so as to make the process quick. But I would be open to any other work around scenario.
I am working with Windows XP Professional and Adobe CS2.
Any help would be appreciated!

I've followed the instructions and I am having problems getting data to the folder I set up on my desktop.
I have tried selecting several images and then just one image to export the slected metadata to said folder. By right clicking the images and chosing the script you sent me and then followed your instructions for when your CSV Data Collector Window pops up.
For the Please Slect Folder option i browsed to the folder where I want the info to go to.
~/Desktop/Kens Files/KensTest
For the Please Enter CSV Filename, I copied the title of the image name "2005-agropyron002.jpg"
Then I chose the type of data that I want to import such as:
FileName
DocWidth
DocHigth...
I then go to that folder and there is no info. there.
Please, if you can, give me more detailed instruction.
Thanks,
Bill

Problems exporting metadata (using bridge).

Hello.
I'm trying to export metadata from OWB to Discoverer. I've a multidimensional model and now I want to explore it using Discoverer.
When I export metadata, OWB creates a file like:
BEGIN End User Layer Export
EUL_Version 3.1.92.0.7
EUL_Unique_Id 20030315095138
EUL_Characterset_WE8MSWIN1252
Define Object
Type BUSINESS AREA
Name AREA CASO 1
mName AREA CASO 1
mDescription Área de negocios del caso de estudio del almacén de comestibles.
mId
EndDefine Object
Define Object
This file can't read by Discoverer because not is a XML file. How can I export the .eex using XMI especification?
Thanks.

Juan Antonio,
What version of Warehouse Builder are you using?
It seems you have selected the Discoverer 3 bridge which may not generate an XML file (I am not sure about the Discoverer 3 format).
Anyway, you have to define a business area in OWB (or collection if you use OWB904) that contains the object definitions you want to export when you run the bridge.
Mar.

Exporting Metadata In Bridge CS4

Bridge CS3 used to have a decent metadata export script, CS4 seems not to have this feature. How do I export the metadata from multiple image files in CS4 as a file type readable by EXCEL?

   An excellent little script Paul and I thank you for it.
   May I make several suggestions. This comes from a user and not a programmer so I am looking at it from the possibility of future usage. I am not trying to be critical, as I do love this little gem, only seeing how I would use it.
Have it so that the directory structure does not export. A user will likely be saving the CSV file in the same directory so showing the directory is moot. Or make it optional.
Have it so that the last used set of selected fields (row headings) become the default. It saves the user from having to select the same ones time after time.
Have the selected fields show up as the row headings in the file.
   I have needed something like this. I have a large collection of digital archives (10,000+ images) which is metadata centric and which I am using for a web site. Since Adobe does not have a way to export my carefully created and crafted metadata enmasse I can easily see where this script can aid in my design.
   In the past I have been forced to copy my metadata information from Bridge into my design. This was tedious after the 800th or so crafted HTML file. Using this script I can now export it to a spreadsheet for usage.
   Thank you!

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!

Can I Export Metadata Using CS2?

Hi Everbody,
I'd like to generate a text file for my client with filenames, captions, and credits. Can I do this from CS2 somehow? I can't see how to do it in Bridge or Photoshop at this point. Thanks in advance for your time, folks.
Phil

Phil,
Go to www.creativescripting.net
Look for the barred rock scripts. There's a script in there that exports metadata to a csv file.
Make sure you download all the docs too!
Bob

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

Aperture Metadata and Bridge Metadata

I am a photographer and my workflow is to import all my images into Aperture library and add metadata.
When exporting an image is it possible to integrate Apertures metadata with Bridge metadata? This is important feature as most people do not import images with Aperture. The issue is that many of the field names are different or non existent between the two programs. For example Location field in Bridge is Sub location in Aperture.
Can you add fields such contact info such as URL, email that are included within Bridge ITPC Metadata?
Is there a way to customize the metadata fields to work with CS3?

Unfortunatelly, not really.
I am currently using Nikon Transfer (latest version) to download the pictures from the camera. This software allows me to enter quite a number of IPTC data (including contact information, url, mail, phone, etc.), but maybe not all which are available in CS3.
Then I do import the pictures from the folder into Aperture where I only add contact information in the respective IPTC field. From the tests, I did I do know, that with this step I am using the "old IPTC standard" with Aperture and the new IPTC standard with Nikon Transfer. Clearly the newer is better and meets the needs you described.
In Aperture, I do only see the IPTC data fields, which are common between the two standards (copyright, keywords and description).
When I go to CS3 Bridge, I can see the IPTC data from both, but only of you turn on the "IPTC old" in the Photoshop Bridge settings.
This is how far I have come. I have tested the export with the original and the aperture work copy. As a test reader/viewer of the pics I used Photoshop Elements 5.0 ... but except the copyright information, key words and description, I could not find "my" IPTC data. So there was no contact info. This may be a problem of the old version, so I also checked on a windows PC the file properties (picture viewer), which has more or less the same information.
So the only work around maybe to add contact information into the copyright field - which is not ideal.
Regards
Diethard

Is there a way to export metadata specific metadata

Regardless of the metadata view I choose, Aperture exports only 21 columns of metadata, and not in the order that they appear in Ap. Actually it exports metadata that don't even appear in the view I'm using.
Is there a way export metadata specific metadata, so it can be used in Numbers, or Excel?

Do you have any suggestions for how to pass distribute .mov files with my contact info and description info?
Just two ideas:
if you like commandline tools, you could try "exiftool" to write "Artist", "copyright", and "user comment" to your movies. Download from here: http://www.sno.phy.queensu.ca/~phil/exiftool/ The documentation says, that MOV files are supported; I did not try it with MOV, however.
Or use the "spotlight comment field (see above). But that would only be visible on a mac.
To write to the Spotlight Comment field open "Get Info" for the exported movie.
Can other programs like Bridge or lightroom read that metadata?
Sorry, I don't know since I do not work with those programs.

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 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

Viewing Microsoft Office Metadata in Bridge

Is is possible to view metadata in Bridge for non-Adobe files? We have project folders that often contain non-Adobe documents as well as Adobe documents. The file info from these non-Adobe documents is not visible nor searchable in Bridge. Am I missing something or is this just the way it is?

There is a library for working with excel files:
http://code.google.com/p/as3xls/
But I'm not aware of anything for Word.
Converting everything to PDF on the server may be a more realistic approach.

Exporting Metadate for multiple images

Hi, I can't find a way of easily exporting the metadata for a number of images into a csv file. The "Export Metadata" function in Aperture 1.5 only exports the file name and the keywords, with a number of blank columns, and there are no column headings for useful information like shutter speed and aperture!
I've looked at tools like "exiftool" but they are quite difficult to run and seem to only do one image at a time. I also tried using Automator to extract metadata, but couldn't make it work
It would be very useful if I could (a) enter comments in a metadata field and (b) extract technical metadata to a csv file for a number of images
any suggestions welcomed!
Richard

You should be able to do it using AppleScript. It is not straightforward, unfortunately, but the information seems to be there.
http://homepage.mac.com/jlarson7/metadata/index.html

Replace Metadata in Bridge CS4 appears to truncate 5.9GB .PSB File; Does CS6 do this too?

I am running Photoshop CS4 on a MacBook Pro with Mac OS X 10.6.8, and ran into a problem with Bridge. I would like to know if this problem occurs with Photoshop CS6. Here's the sequence of events:
1. I have a 5.9GB .psb file created with PS; it loads into PS cleanly - no errors.
2. In Bridge, I create a metadata template, and apply it to my .psb file using "Replace Metadata".
3. The "Replace Metadata" operation completes quite quickly, no error messages
4. Immediately after the "replace Metadata" operation Bridge reports that my 5.9GB file is now a 1.6GB file - 4.3GB smaller!!
5. Bridge displays the updated metadata, no visible indication anything is wrong.
6. Now the file will not open in Photoshop - the read starts, but errors out with "unexpected end of file".
7. I restore the 5.9GB file and can open it in Photoshop without problems.
Update:
This problem is not specific to the "Replace Metadata" function in the Bridge menu. I get a similar result by updating the metadata for this file in the Metadata Panel; the resulting file is truncated, but appears to be a different size this time, and it will not open in Photoshop - same error message as before.
This is a 34-image 36856px X 7464px panorama

Thanks for your suggestion, appreciate your effort to help. The link you provided seems to focus on transfer rates and performance; it does take a while to write or read this file, but I expect that. I'm not using RAID of any flavour. I do not expect file corruption, which is what I believe is happening (and PS is reporting).
I have a number of large panoramas; this is the largest. I believe the largest of the others is a bit over 3GB; I have no difficulty updating the metadata in the other panoramas through the metadata panel or with "Replace Metadata". All of these files live on the same drive (therefore connected to the same firewire port). They are backed up to a USB drive with Time Machine, and I've recovered the 5.9GB file from the Time Machine drive a number of times. I can always read the recovered file with PS, and the size after recovery is always exactly the same. When I realized that the size of my 5.9GB file changed during/because of the metadata update, I reverted to an earlier stage in the post-processing, got a 3.8GB .PSB and put a copy on DVD; the DVD copy is good, and I can easily and quickly reconstruct the 5.9GB file by applying the same actions used the first time (the 5.9GB file has three layers that are not in the 3.8GB .PSB). I have not tried to change metadata in the 3.8GB PSB, and can't try that for the next few weeks as I'll be travelling. The only thing I'm certain of is that updating the metadata in the 5.9GB .PSB reduces the size to 1.6GB (put text in Headline field through Metadata panel) or 1.4GB ("Replace Metadata" in Bridge Tools menu), depending on how the update is done.
So, the 5.9GB file has survived several complete transfers (PS=>Disk, Disk=>Time Machine, multiple Time Machine=>Disk, PS=>Disk to 3.8GB after deleting layers, and Disk(3.8GB)=>DVD) with no signs of corruption.
It's very hard to accept the idea that there's some kind of hardware problem that afflicts just one file. The 5.9GB file is output from PS CS4, and I can read it back into PS with no problem.
I'll watch this forum for a few days to see if there are more answers until I have to travel. If not, I'll figure it out another way and report a bug in CS6 if that appears to be appropriate.

Editing XMP metadata in Bridge for checked-out files?

Our custom connector does not implement the WRITE_XMP_METADATA Capability because we do not want to change the XMP of a file in our DAM system without checking in a new file version.
However, when a file is checked out through Adobe Drive, we would expect to be able to edit its XMP metadata in Bridge just like we can for local files.
It looks like this is still not possible with Adobe Drive 3, i.e. if your connector does not implement the WRITE_XMP_METADATA Capability you cannot edit XMP for checked out files either.
It seems weird that you can edit XMP metadata for checked out files with regular CS applications but not with Bridge. Is this something that is expected to be fixed in a future version?
Thanks

In our design, editing XMP data in Bridge and in regular CS applications is different, the former one will be routed to SetXMPHandler in you connector, in the latter case, CS applications take the normal file writting ways to embed XMP data in the file content.
The purpose of this design is to offer similar user experience for normal users when they edit XMP data for AD assets and local file assets, they don't need to check-out files first.
To address your issue, I think you can add some codes in SetXMPHandler to auto check-out files before real XMP operation, and check-in them before exiting the handler
We will consider to make some enhancements for this part, that's, to allow editng XMP data for the checked-out files in Br, in the next release, thanks for this advice.

Export metadata in Bridge

Similar Messages

Maybe you are looking for