XMP Metadata Question

I need guidance in creating a custom file info panel in Flash Builder 4 for Illustrator CS4. I'm trying to link a AI CS4 text variable to a XMPTextArea component and im having no luck. Any input would be appreciated.
Thanks,
-Frank

I
suspect that a tool/application was used to alter the metadata, but, my
belief was that InstanceID will always change whenever metadata is
modified.
May be that this tool/application doesn't change the InstanceID.

Similar Messages

How can I get Adobe Bridge to show XMP metadata using Adobe Drive 4 CMIS Connector?

I have successfully connected to an Alfresco Enterprise Edition 4.1.0 repository, using the Adobe Drive 4, created a test folder and uploaded a jpeg file containing XMP metadata into it.
When I view the image's metadata (using Adobe Bridge), I observe that only part the standard file properties are displayed.
When I view a local copy of the image using the same, I see all fields of the standard file properties plus available metadata.
My question: what should I do in Adobe Bridge to be able to see all available XMP metadata?
Kind Regards and Appreciation
Don Greenwood
Pixelboxx GmbH
Dortmund

How did you get through to customer service? They've changed the website and I can't even find phone numbers or a chat button any more.
Here's my story that I posted on discussion yesterday, but no one has replied:
I am screaming and pulling my hair out right now! The last six months with Adobe has been a nightmare.
Once again I am completely locked out of Creative Cloud and cannot use the apps even though my automatic monthly deduction for payment was just made a couple of days ago. Creative Cloud continues to reset itself to the trial version which runs out in 30 days and after that I am locked out once again.
Now it looks like it is harder to access support than before. Where are chat and the phone numbers now? This was a nightmare with countless hours spent on chat and the phone over the last six months, and now I don't even know how to access support in order to spend even more time that does not solve the problem. What am I to do?
I cannot use the product I have paid for!
Please help!

Problem with Bridge CS4 reading/editing XMP metadata added in Bridge CS6

Please excuse me if this is a dumb/obvious question. I did try searching the forums for similar problems and didn't find anything that seemed to speak to my issue.
I'm having a problem where Bridge CS4 won't read/edit xmp metadata (specifically, keywords and descriptions in the IPTC panel) that I have entered using CS6. it will read some files, not others. The files are all .mp4s. Of these files, I can read/edit IPTC panel metadata for some of them in Bridge CS4; I can add metadata for all of them in CS6. I see no particular pattern in these files to explain what is and isn't read/editable in CS4.
My question is whether this is a compatibility issue between different versions of CS (in this instance, CS4 and CS6). i know it's a tired refrain to blame software when it could easily be user error, in which case I'd be frankly delighted to know what i'm doing wrong. Please bear with me as I give a few more details.
I'm using macs. I've tried this on multiple systems - for instance, on a mac pro 3 which for some reason has both CS4 and CS6 installed, i can add and edit keywords using CS6, but not when using CS4. Again, in CS4, some .mp4 files read/edit, others do not.
Bridge CS4 blames the files and tells me that the selected file cannot store xmp metadata, and that the properties cannot be modified. To be specific, in the metadata panel it says "this property cannot be modified"; in the keyword panel, it says, "This file (zzz.mp4) cannot store xmp metadata. No changes will occur." This seems odd, because I'm able to add xmp metadata for the same files in CS6 on the same computer, and other computers. I know this problem would disappear if all our computers were using CS6 (or CC), but unfortunately that's not a possibility at the moment. Some of them only have CS4.
Computer details (not an exhaustive list, but two instances): mac pro 3.1 running snow leopard, 16GB memory; macbook pro 4.1 running snow leopard, 4GB memory; adobe bridge cs6 (5.0.0.399) and cs4 (3.0.0.464).
Things I have tried:
Permissions - the files are set to read/write for everyone. Given that I can add/edit metadata in CS6, it doesn't seem to be a permission issue.
Purging the cache - other users seem to have had problems adding metadata in Bridge CS4 where purging the cache for affected files solved the problem. Didn't work in this instance.
Upgrading all affected computers to CS6/CC is beyond my control. I need to figure out why CS4 won't let me read/add/edit xmp metadata, if only for the sake of understanding the broader implications for interoperability.
Any helpful suggestions would be much appreciated.
Thanks,
Kevin

adobe bridge cs6 (5.0.0.399) and cs4 (3.0.0.464).
Without having experience with mp4 files and metadata my observation is that you certainly have not updated Bridge CS6 ( should be 5.0.2.4) and I believe also not the latest version of CS4, can't imaging this also stayed at .0.0 so first try to update both.
And if CS4 can read the data of some files it should be capable of reading them all. Be sure to have the files completely cached first, can take a while.
Other things to try in CS4 is refresh preferences (hold down option key while restarting Bridge and choose reset prefs).
And also check for hidden cache files using menu view/show hidden files. Sometimes those cache files can be troublesome between versions.
If purge cache did not work and reset prefs also failed consider to also delete Bridge plist file and Bridge cache file manual (from user library)

Incrementally appending custom XMP metadata into PDF files

I have a problem writing custom XMP metadata into a PDF document (I'm using the XMP Toolkit SDK).
The problem is that I don't know whether is possible to expand the XMP packet in order to append metadata incrementally into the document, and, if it is possible, I don't know how to do it. The program I wrote succesfully appends an item to an array four times, but it fails when trying to append the fifth one. The reason obviously is that the packet gets full and there is not room for more metadata. The error message, if I force the PutXMP call, is:
ERROR: Can't fit into specified packet size
So, what can I do? How to enlarge the packet or make it expandable? Or, otherwise, have I to inject a new XMP packet with the up-to-date information in it? How?
And a last question: Have I to scan for packets when dealing with PDF files? No smart handlers are available for this kind of files?
Thanks in advance.
Xabier Artola.
Univ. of the Basque Country.

Were you able to find a solution to this problem? I am having the same issue.
Jason

Examples of web photo galleries that display xmp metadata

Hello, I am wondering if anyone knows of an online image gallery that displays xmp metadata for the images displayed?
Thanks,
Bob

Something you may want to consider is DBGallery (http://grrsystems.com/DBGallery). This product stores iptc/xmp data in a MySql database as well as in the image file (using Adobe's XMP Toolkit). Websites can access this data using any number of ways: PHP (google 'accessing mysql with php'), MS Access, and many others. Unfortunately right now there isn't an extremely easy means to access it directly from html like in the sample above: "< div class="content">DESCRIPTION: %FILEINFO% "; although finding someone to put together a little PHP to get close to this easy wouldn't be difficult (elance.com, etc).
DBGallery itself allows that data to be extracted and placed in emails and pdf's (see a sample at http://grrsystems.com/DBGallery/DBGallery_Sample.pdf). It also generates websites with Title and Description, but the websites are fairly basic I'm afraid (see
http://www.grrphotography.com/Collections/WorldPlaces/index.htm)
Dropping any images with iptc/xmp data into DBGallery gets their data into the database because the metadata is automatically read and added to the database.
If there are questions about this option reply here or email me at [email protected]
Best Regards,
Glenn Rogers
Designer of DBGallery: Photo DATAbase System
http://grrsystems.com/DBGallery

Best practice in writing xmp metadata?

I know to switch off the 'automatically write to xmp metadata' feature. But, after doing this, what is the best way to ensure the xmp metadata does actually stay up to date?
My understanding is that by switching the automatic writing back on, LR goes through the whole catalogue, comparing the data in its database with the data in the xmp files, and every time it finds something different, it copies from the database to the xmp. However, there would seem to be two problems with this. i) it's extremely slow, because it's such a big job, and (b) presumably any changes made elsewhere, eg in ACR, will be overwritten.
The alternative seems to be to right click on the folder while in library mode and select "save metadata". However, for some unknown reason, this is unbelievably slow. What prompted me to write this message is that nearly an hour ago, I did this with a folder of 78 files, and it's still churning away. In that time, I've had time to log on to this forum, read a few messages, do a search to see if there is anything helpful, and then write and edit this. I don't dare try this with the folders I have with three hundred photos in!
The LR catalogue is in a partition with hardly anything else in it, on a different physical drive from LR itself. It gets defragged more frequently than the defrag utility thinks it needs to be. During metadata writing and many other operations, the CPU maxes out at 100% yet only about 75% of my 1GB memory is used.
Is there anything I can do?
I'm on an old-ish PC and am not in a position to upgrade (please - any messages just saying I need a newer computer are not going to be any help :-) ). Any other help would be appreciated.

Thanks, Mel. You just posted as I was writing the previous message!
I think you nailed it. The 78 pictures, I did by right-clicking on the folder name in the right-hand fly-out panel in library and selecting 'save metadata' (hope the choice of words here is clear!). I've just tried the ctrl-a, ctrl-s technique you describe, and it whizzed through a folder of 127 photos in no time.
So, you're right - there appears to be a bug.
One more problem - there was an error in saving to the tifs in the folder. A separate problem which I'll look at tomorrow.
Back to the other part of my original question. What is the most efficient way to keep the xmp data up-to-date? Considering that there's massive scope for human error in having to remember to save manually all the time, this can't, surely, be the best way to do it. What do people generally do, and has anyone evolved a 'best practice'?

XMP metadata generation

is XMP metadata generation only for images, do it support video?
What are the techniques and standards follows for metadata genaration. Is xmp metadata generation is also for videos also. What all are XMP read and write tools.

Hi Sethunath,
>is XMP metadata generation only for images, do it support video?
XMP Metadata is a standard way to describe metadata about any resource in general. “XMP metadata generation” I assume here that by generation you mean = creating or processing or handling of Metadata. Yes, XMP Toolkit SDK , which is a tool to manipulate Metadata, does support different image and video formats. For more information on which file formats it supports please refer to XMP Spec part 3<http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/xmp/pdfs/cc-201306/XM PSpecificationPart3.pdf> .
>What are the techniques and standards follows for metadata genaration. Is xmp metadata generation is also for videos also. What all are XMP read and write tools.
You may want to have a look at XMP developer home to get all the information you need.
http://www.adobe.com/devnet/xmp.html
The page lists different tools to view , handle or manage XMP metadata , and the specifications on which they are based.
Please do let us know in case of questions regarding the technology or the SDKs.
Thanks
Inder

Incrementally appending custom XMP metadata

I have a problem writing custom XMP metadata into a PDF document (I'm using the XMP Toolkit SDK).
The problem is that I don't know whether is possible to expand the XMP packet in order to append metadata incrementally into the document, and, if it is possible, I don't know how to do it. The program I wrote succesfully appends an item to an array four times, but it fails when trying to append the fifth one. The reason obviously is that the packet gets full and there is not room for more metadata. The error message, if I force the PutXMP call, is:
ERROR: Can't fit into specified packet size
So, what can I do? How to enlarge the packet or make it expandable? Or, otherwise, have I to inject a new XMP packet with the up-to-date information in it? How?
And a last question: Have I to scan for packets when dealing with PDF files? No smart handlers are available for this kind of files?
Thanks in advance.
Xabier Artola.
Univ. of the Basque Country.

One of the known limitations of the XMPToolkit is that it is NOT smart about PDF documents - it treats them as "generic binary" and thus can not add beyond the pre-allocated whitespace already in the PDF.
If you are doing any serious operations of XMP with PDF - I recommend that you look at licensing the Adobe PDFLibrary which is a full functioning PDF library and incorporates the XMPToolkit inside it (among many other things).

Modify LabelGraphics.js to extract other XMP metadata from images

This script works flawlessly. However, I would like to be able to extract other XMP metadata than just
//XMP description
        case 2:
            try{
                myLabel = myLink.linkXmp.description;
            catch(myError){
                myLabel = "No description available.";
            break;
        //XMP author
        case 3:
            try{
                myLabel = myLink.linkXmp.author
            catch(myError){
                myLabel = "No author available.";
I have developed a custom info panel (based on the generic one) with following "properties.xml":
<xmp_definitions xmlns:ui="http://ns.adobe.com/xmp/fileinfo/ui/">
    <xmp_schema prefix="custom0" namespace="http://my.custom0.namespace/" label="$$$/Custom0/Schema/Label=Ref_SAP" description="$$$/Custom0/Schema/Description=This example panel contains most of the options available for the 'Generic Panel'.">
        
        <xmp_property name="Ref_SAP" category="external" label="$$$/Custom0/Property/TextInputLabel=Referentie nummer SAP:" type="integer"/>
        <ui:separator/>
    </xmp_schema>
    <xmp_schema prefix="custom1" namespace="http://my.custom1.namespace/" label="$$$/Custom1/Schema/Label=FRANS" description="$$$/Custom1/Schema/Description=This example panel contains most of the options available for the 'Generic Panel'.">
        
        <xmp_property name="Titel_FR" category="external" label="$$$/Custom1/Property/TextInputLabel=Titel FR:" type="text"/>
        <xmp_property name="Tekst_FR" category="external" label="$$$/Custom1/Property/TextInputML_Label=Tekst FR:" type="text" ui:multiLine="true" ui:height="100"/>
        <ui:separator/>
    </xmp_schema>
    <xmp_schema prefix="custom2" namespace="http://my.custom2.namespace/" label="$$$/Custom2/Schema/Label=VLAAMS" description="$$$/Custom2/Schema/Description=This example panel contains most of the options available for the 'Generic Panel'.">
        <xmp_property name="Titel_VL" category="external" label="$$$/Custom2/Property/TextInputLabel=Titel VL:" type="text"/>
        <xmp_property name="Tekst_VL" category="external" label="$$$/Custom2/Property/TextInputML_Label=Tekst VL:" type="text" ui:multiLine="true" ui:height="100"/>
        <ui:separator/>
    </xmp_schema>
    <xmp_schema prefix="custom3" namespace="http://my.custom3.namespace/" label="$$$/Custom3/Schema/Label=NEDERLANDS" description="$$$/Custom3/Schema/Description=This example panel contains most of the options available for the 'Generic Panel'.">
        <xmp_property name="Titel_NL" category="external" label="$$$/Custom3/Property/TextInputLabel=Titel NL:" type="text"/>
        <xmp_property name="Tekst_NL" category="external" label="$$$/Custom3/Property/TextInputML_Label=Tekst NL:" type="text" ui:multiLine="true" ui:height="100"/>
        <ui:separator/>
    </xmp_schema>
</xmp_definitions>
Now I would like to adapt the LabelGraphics.js to retrieve the information stored in the fields "Titel_FR", "Tekst_FR", "Titel_VL", "Tekst_VL", "Titel_NL", Text_NL". These fields contain fixed text that goes with the image and should be retrieved in several "goes".
Question 1: is this possible at all ?
Question 2: how to proceed ?

Have you already found Marijan Tompa's "Extract Metadata with Adobe XMP"?
David

CS6 METADATA QUESTIONS

CS6 METADATA QUESTIONS
Working with record album saved in a wave format, on a computer running windows 7
I break the album into individual songs using markers which I name the title of each song, I check the include metadata box when I export each marker to individual file. In the ID3 metadata I enter the artist , album name, recording date, and genre. In the xmp under riff I enter the album name under product. Before I save each marker to a separate file.
The information that shows up in windows explorer is the file name, album name, and contributing artists. Unless you enter a space after the information entered in the metadata columns, such as album name, windows cuts off the last letter. Is this a windows problem or a CS6 problem?
Is there somewhere in the metadata that you can enter the track no. so it will show up in windows explorer track no. column?
3.Is there anyway to have the marker names entered into the id3 title column and the xmp/rff name columns.?
After the markers have been saved as individual files , windows explorer has the file name, album name ,and artist. I then open each individual song file and copy the file name into the ID3 title column and the xmp/rff name column, add the track no. in the id3 track no column ,and hit file save . At this point windows explorer no longer shows any information but the file name. In order to get the title, album name, and artist to show up in windows I have to hit file “save as” and then save it again as the same file name. Why? Am I doing something wrong?
After I get the information in the metadata of the individual songs saved in a wave format. I then save a copy in the mp3 format . Even though the id3 information is in the meta data of the songs saved in a wave format when I save a copy in the mp3 format the information is no longer available, Why? Is there a way to convert a wave file with id3 information to an mp3 without having to re enter it all again?
Is there another low loss format that would handle the metadata better and allow it to show up when converted to mp3?
Is there a more detailed help article on metadata standards?

I've been doing some workflow rehearsals with Pl and Pr (Still more to try out) and I have shifted my thinking a bit on how to use these two programs together in the most useful way.
I have started thinking of Prelude as the "Turbocharged" version of Premiere's Project window, bins, browser and metadata panel. If you start to think of Pl as a break-out companion, and use the two in conjunction, I think it can make for a very powerful combo.
I know that it has been suggested to only flow in one direction - use Pl first and then switch over to Pr, but since Pl's capabilities for marking, adding and searching for metadata is stronger, i have been going back and forth a lot.
In your example above, you can mark your comment (marker) sections in Pl and send over the clips you are interested in. If you find you need more clips or a different "Answer1", pop back to Pl and do a search, find the clip, and send over to Pr. It's like going back to the well for more media only when you need it. The search is much better over at Pl (in my opinion)
There are still a lot of new features I would add to Pl to make it more robust, but for now it is working well as my Clip org and Search in place of the meager abilities in Pr.

Modifying XMP metadata does not modify the document

Another from couple questions which accumulated over time.
If I modify layer in document by adding or updating XMP metadata, the document itself is not modified (does not enable save), so far if document is closed without doing some other action which marks document as modified, data are lost.
Question: how to either force document to see changes in XMP meta or how to mark document as modified?
Code snippet:
activeDocument.activeLayer.xmpMetadata.rawData = meta.serialize();
Thanks,
--Petr

When you ask app-specific questions, you should really specify the app you are referring to.
I'm guessing you are talking about Photoshop. This seems to be a scripting related question, and you'll probably get better answers on the Photoshop forum: http://forums.adobe.com/community/photoshop/photoshop_scripting
Harbs

Alfresco XMP Metadata Extractor

Hi all,
First of all I want to apologize if I do stupid questions, as I am new to Adobe world....
I'm an Alfresco Consultant and want to extract the uploaded Adobe file's XMP metadata. As Alfresco is a Java product I need to do it in Java, so I was wondering if there's any Maven repository I can point to to use Adobe libraries (is there any Java library for XMP metadata extraction?)
Thanks in advance.

It looks like the XMP toolkit supports Java.
Overview of the XMP Toolkit: (Link to tool kit located inside of document.
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/xmp/pdfs/XMP-Toolkit- SDK-Overview.pdf
I'm sure you've already been through that just thought I'd direct you there JIC.
Take care and good luck finding your solution,
Kurtis

XMP metadata from Flashbuilder why not visible in Adobe Bridge?

Hi there,
I'm currently wondering around XMP metadata and swf files.
A: Flash CS5: works
When I use the XMP panel in Flash CS5 and export a swf, open Adobe Bridge CS5 and select the file, the XMP data are correctly displayed.
B: Flash Builder(Flex 4.1): don't work
When I use Flashbuilder and add my metadata to the compilation, then compile, open Adobe Bridge CS5 and select the file, nothing is included in metadata.
Procedure based on the following (same problem if metadata are directly set through compiler arguments):
http://livedocs.adobe.com/flex/3/html/help.html?content=compilers_14.html
../src/config/ProductMetaData.xml
<flex-config>
<metadata>
    <title>My title</title>
    <description>My description</description>
    <publisher>The publisher</publisher>
    <creator>The creator</creator>
    <language>EN</language>
</metadata>
</flex-config>
compiler argument
-load-config+=config/ProductMetaData.xml
As far as understood, on the background the following is added to the swf at compile time:
<rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
    <rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1'>
        <dc:format>application/x-shockwave-flash</dc:format>
        <dc:title>My title</dc:title>
        <dc:description>
            <rdf:Alt>
                <rdf:li xml:lang='x-default'>My description</rdf:li>
            </rdf:Alt>
        </dc:description>
        <dc:publisher>The publisher</dc:publisher>
        <dc:creator>The creator</dc:creator>
        <dc:language>EN</dc:language>
    </rdf:Description>
</rdf:RDF>
I've checked that the medata is correctly added to the swf file using this small software polarswf:
http://download.cnet.com/Polar-SWF-MetaData/3000-6676_4-10738623.html
I do not know if it is safe to use it in a produciton context at least in trial mode it allows to check the metadata included in your swf.
I wonder if this metadata coonot be read by Adobe Bridge because they are at a "lower level" than those put by flash CS5 XMP panel?
Thank you in advance for your help.
This is not a blocking situation, but I'm curious to understand what happend.
Cedric Madelaine (aka maddec)

I was following this post for a LONG time, since I noticed the same problem.
This week I was getting in it into myself again and I noticed you use load-config. I used these compiler options :
contributor name
Sets metadata in the resulting SWF file. For more information, see Adding metadata to SWF files.
creator name
Sets metadata in the resulting SWF file. For more information, see Adding metadata to SWF files.
date text
Sets metadata in the resulting SWF file. For more information, see Adding metadata to SWF files.
But that resulted in this XML string where the dc namespace was missing a / on the end of the URI
That caused the metadata which was added in flashbuilder was only visible in bridge in the rawXML panel, and not the specific fields
changing the URI in http://purl.org/dc/elements/1.1/ did the trick ( did this in bridge by exporting the rawXML, changed the / , and imported it )
<rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
    <rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1'>
        <dc:format>application/x-shockwave-flash</dc:format>
    </rdf:Description>
</rdf:RDF>
Sadly there was no way I could add this / myself everytime.
BUT then I discoverd this option :
raw-metadata XML_string
Defines the metadata for the resulting SWF file. The value of this option overrides any metadata.* compiler options (such as contributor,creator, date, and description).
This is an advanced option.
And you could give the exact RAW XML as you described
<rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
    <rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1/'>
        <dc:format>application/x-shockwave-flash</dc:format>
        <dc:title>My title</dc:title>
        <dc:description>
            <rdf:Alt>
                <rdf:li xml:lang='x-default'>My description</rdf:li>
            </rdf:Alt>
        </dc:description>
        <dc:publisher>The publisher</dc:publisher>
        <dc:creator>The creator</dc:creator>
        <dc:language>EN</dc:language>
    </rdf:Description>
</rdf:RDF>
to the compiler. This could also be done in Flash with JSFL.
In the end I wrote an ANT script which injects the exact XMLstring of metadata to Flash and Flex projects by using the raw-metadata parameter in FLEX and JSFL for flash.
Hope this helps

How to get XMP MetaData as an XML String in a process?

Hi there,
I have a process where I would like to export a documents XMP MetaData, manipulate the XMP MetaData and then import the MetaData again to the document.
I thougt first I will use the service Name "XMPUtilityService" with the Service Operation "Export XMP" to export the XMP MetaData as a document.
Hoewer I am not sure how to manipulate the output document from the Export XMP service.
When I print out the document.toString() in a execute Script Service I get the following:
<document state="active" senderVersion="0" persistent="false" senderPersistent="false" passivated="false" senderPassivated="false" deserialized="false" senderHostId="null" callbackId="0" senderCallbackId="0" callbackRef="null" isLocalizable="true" isTransactionBound="false" defaultDisposalTimeout="600" disposalTimeout="600" maxInlineSize="65536" defaultMaxInlineSize="65536" inlineSize="3440" contentType="null" length="-1"><cacheId/><localBackendId/><globalBackendId/><senderLocalBackendId/><senderGl obalBackendId/><inline><?xpacket begin="ï»¿" id="W5M0MpCehiHzreSzNTczkc9d"?>
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="A...</inline><senderPullServantJndiName/><attributes/></document>
Actually I expected something like this:
<?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?>
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.0-jc006 DEBUG-1.0, 2009 Jun 23 11:07:21-PDT">
   <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
      <rdf:Description rdf:about=""
            xmlns:pdf="http://ns.adobe.com/pdf/1.3/">
         <pdf:Producer>Adobe LiveCycle PDF Generator ES2</pdf:Producer>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:xmp="http://ns.adobe.com/xap/1.0/">
         <xmp:ModifyDate>2010-04-20T20:43:59+02:00</xmp:ModifyDate>
         <xmp:MetadataDate>2010-04-20T20:43:59+02:00</xmp:MetadataDate>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/">
         <xmpMM:DocumentID>uuid:0cf2c6c6-2fba-2b39-5fb6-33ad8ccf58aa</xmpMM:DocumentID>
         <xmpMM:InstanceID>uuid:187bc5a2-acb0-2fa9-711d-33ad8ccf58aa</xmpMM:InstanceID>
      </rdf:Description>
   </rdf:RDF>
</x:xmpmeta>
<?xpacket end="w"?>
What do I need to do to get the XMPMeta data as an XML String from a document within a process?
Thanks in advance!
Paul

Hi,
thanks for the answer.
I know that I can retrieve the XMPUtilityMetadata object, but this object provides only access to a few information suche as creator, subject, producer, etc.
However I would like to retrieve the whole XML String of the XMP Metadata.
How is this possible?
Thanks.
Paul

Viewing XMP Metadata in Adobe Bridge via Adobe Drive Connector

Hi there,
I've been trying to view remote file XMP metadata in Adobe bridge via our adobe drive connector. I've added the READ_XMP_METADATA capablitiy, and I've seen the DataType.XMP has been requested. but I'm not sure how to display the metadata on the Adobe bridge metadata panel. since the metadata is embeded in the file, when i browse the file in local drive, the metadata shows fine, but when it's on our remote server, some how bridge doesn't extract the info and display it. I can see the metadata when I browse the remote file in windows explorer adobe drive. and we do download the file to local to a temp copy, browse the temp copy in bridge also showing the metadata, The only thing not working is browsing the remote file in bridge via adobe drive connector.
Please advise what should be done, in the programmer's guide, it says for each item, request that the server return the XMP data for that asset. How should I do that? If the XMP is embeded in the file, why would I need to request for it, would it be automatically extracted from the file?
Thanks,
Katherine

Hi there,
I've been trying to view remote file XMP metadata in Adobe bridge via our adobe drive connector. I've added the READ_XMP_METADATA capablitiy, and I've seen the DataType.XMP has been requested. but I'm not sure how to display the metadata on the Adobe bridge metadata panel. since the metadata is embeded in the file, when i browse the file in local drive, the metadata shows fine, but when it's on our remote server, some how bridge doesn't extract the info and display it. I can see the metadata when I browse the remote file in windows explorer adobe drive. and we do download the file to local to a temp copy, browse the temp copy in bridge also showing the metadata, The only thing not working is browsing the remote file in bridge via adobe drive connector.
Please advise what should be done, in the programmer's guide, it says for each item, request that the server return the XMP data for that asset. How should I do that? If the XMP is embeded in the file, why would I need to request for it, would it be automatically extracted from the file?
Thanks,
Katherine

XMP Metadata Question

Similar Messages

Maybe you are looking for