Photoshop xmp metadata editing

Adobe xmp metadata in photoshop, is there a way to edit script info so files will show the transactions done on a photograph?
(eg. such as number of times saved, copied, printed, log in time)

Hi,
I do not fully understand which kind of script files you want to show or edit.
You can see all XMP metadata in the "raw packet" view.
To show or edit XMP metadata properties that does not show up on the panels that are delivered with Photoshop,
you have to create a "custom panel" to leverage these properties.
-- Stefan

Similar Messages

Metadata edited in Bridge is not reflected in the Info Dialogue Box, but shows up in Photoshop.

Metadata edited in Bridge is not reflected in the Info Dialogue Box, but shows up in Photoshop.

Dear Ramón,
You are right that not all metadata is shown in the Finder info but in my case the once added in IPTC core do show as expected for most file types (but not CR2 raw). As you now I convert my CR2 to DNG for a long time now I had to look up the original Raw file and create the data for description, location, keywords again. The data you can add and alter yourself in the IPTC Core field. I added a series of screenshots showing different info and to my surprise (another reason to keep to DNG…) the Raw file had very less info and the xmp shows it all in a rather long and obscure way. Yet PSD, DNG and File info in PS show the same.
Could not recreate the Bridge metadata workspace from the OP because mine (Bridge CC) does not have the description field as an option anymore for some obscure reason. Also checked this in my CS6 version with same result, making the metadata workspace unusable but that was it already for a long time.
Still leaves us with the problem the OP showed, having all info in most files, as in Finder info, but not in Bridge. So could the OP respond to the purge cache for selection option in post 4?
Here are (a bit to many, sorry) my screenshots showing different file info (in Dutch but you will manage with that) and metadata in Bridge:
Finder info for PSD and DNG:
Finder info for CR2 and XMP:
File info Bridge / PSD:
And a Bridge Metadata view:

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.

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)

How to transfer metadata (tags etc) from Adobe Photoshop Album Starter Edition 3.2 to A P Elements 8

I have just bought the Adobe Elements 8. I was told that this product was the upgrade product from the trial version of Adobe Photoshop Album Starter Edition 3.2. Can't find a clear solution in this forum of how to transfer the metadata to the Adobe Elements 8 and continue the indexing with the latest product. Hopefully somebody can help.
Bjorn

If you still have your 3.2 psa catalog in your "My Catalogs" folder, try
downloading PSE5 from here:
http://www.johnrellis.com/photoshop_elements_5.0_trial_version.exe.
PSE5 should be able to find your catalog and you can convert it into PSE5.
If that doesn't work, it may be because you weren't able to run "reconnect
all missing files" in PSA3.2 before attempting the conversion. If all your
photos were still connected, this should work. Then you can open PSE8 and
convert PSE5 into PSE8. Do a "reconnect all missing files" in PSE5 before
you do the conversion. Even though all my files were connected when I
converted PSA2 into PSE5, PSE5 had about 30 unconnected photos.
Good luck!
http://www.johnrellis.com/photoshop_elements_5.0_trial_version.exe

Extract XMP metadata from specific Photoshop Layer in After Effects

How do it extract XMP metadata from specific Photoshop Layer in After Effects?
I am just getting my hands dirty with metadata.
I know it is possible to attack metadata to a layer/layerset in Photoshop, but how to I get it out in After Effects.
Here is the process.
I create BunchaLayers.psd.
Using the PerLayerMetaData.jsx file attached.
I use the setCommMetadata("something") function to attacked metadata to a selected layer.
I know that is is there because I check it using the exportLayerMetadata().
I save and imprt BunchaLayers.psd into AE as a comp.
Here I am lost.
I select my layer in the project window and check the XMP metadata window.
I can't find my comment.
Is the XMP data actually attached to the layer I imported in AE?
I want to be able to select the layer and see that the data is attached. Is this possible?
If it is will it work on layersets (comps in AE)?
I would appreciate any layer specific XMP insight.
Thanks for looking.
- Josh

John Nack on Adobe : Per-layer metadata comes to Photoshop
This was the article that made me think this might be possible.
There is also the preference to Create Markers From Metadata
["Metadata"]
"CreateLayerMarkersFromFootageXMP" = 01
Which made me wonder if there is a way to create the metadata in the first place that made it something AE would read and automatically change to layer markers.
Any ideas?

Import XMP Metadata Kills My Image Edits

I imported a batch of JPGs from a recent trip and happily used LR to rank them, add labels and adjust them in the Develop module. Later, when LR was not running, I used another program to modify some of the embedded meta data in these JPGs (in particular the dates).
On my next visit to LR I used the Import XMP Metadata From File command, hoping to get LR to recognize the modified dates. This turned out to be a big mistake. All my previous ranking, labeling and developing was lost. Oh dear.
I guess I was under the impression that the Import XMP Metadata From File command would synchronize the metadata in the files with the metadata in the database. It appears to have simply replaced the database values with what was in the file. So is this a bug or did I just misunderstand the feature?

Last history state? See
Loading metadata resets Develop settings.
>I can go back to Develop and "back up" because the history is all there, but this would have to be done file by file,
Don
Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.8 & Win XP, Pentax *ist D
http://donricklin.blogspot.com/

XMP metadata lost in PNG files

Hello,
My XMP metadata is lost from a PNG file if the file is modified and saved. Here is what I am doing
1. Put some metadata in a PNG file using m_xmpFile.OpenFile( FileName, kXMP_PNGFile , kXMPFiles_OpenForUpdate)
2. Edit this file in Photoshop (changed the brightness and contrast of the file)
3. Saved the the modified files.
All my XMP metadata is now lost fromt the file.
is my implementation wrong? Is there some other way to stamp metadata in PNG files?
Thanks,
Hitesh

Info: Mac, Yosemite, Bridge CC
I have an extensive collection of PNG files that HAD been keyworded in Bridge (XMP). I noticed several days ago that the XMP of all those files is now missing.
When attempting to assign keywords back in, I also get the message: "The file ####.png canot store XMP metadata. No changes will occur." Weird. Like you said, it's looking like a bug.
And here's the kicker... if I duplicate the PNG file (Edit > Duplicate), the "copy" DOES contain the original XMP that went missing.
I really don't want to have to manually duplicate all my PNG files just to regain the metadata. Any brainy solution? I'm attaching an example of the original PNG (missing XMP) and the duplicated PNG (magically restored XMP).

Synchronizing IPTC/IIM and XMP metadata in JPEG images

Excerpt of "IPTC Core Implementation Guidelines", section 2.2.1 available on http://www.iptc.org/IPTC4XMP/:
The basic functionality of this synchronising mechanism [between IPTC/IIM metadata in IRB and XMP metadata] is:
- To move metadata from the IRB to a new XMP packet in case an image file is opened with such an IRB but without an XMP packet. If the file is saved both the IRB and the XMP packet will be stored to the header section of this file.
- To move metadata from the XMP packet to a new IRB in case an image file is opened with an XMP packet but without an IRB. If the file is saved both the IRB and the XMP packet will be stored to the header section of this file.
- To update the metadata values of the IRB respectively the XMP packet from the newer source to the older destination. Which set is newer or older is detected by a hash value over each block of metadata. (More detailed information is available from Adobes XMP web pages at www.adobe.com/xmp and in the software development kits.)
I have checked for Adobe XMP web site and searched in "XMP Specification, January 2004" and I have not found explanations about this "hash value over each block of metadata" mechanism.
Moreover, it seems that it does not work regarding to the following simple experiment:
- 1. add metadata to a JPEG image using Photoshop CS (which adds both IPTC/IIM data in IRB and data in XMP)
- 2. edit these metadata using an "IPTC/IIM-only and non-XMP-aware" editor like IrfanView, XNView or any other one
- 3. go back to Photoshop CS which displays the "old" XMP metadata ignoring changes done previously using the IPTC-only editor.
Of course this experiment works using an "XMP-aware" editor like iView Media Pro or PixVue in step 2.
So it seems very easy to get images with IPTC/IIM and XMP metadata not synchronized when the image workflow uses different programs to edit metadata.
Am I missing or misunderstanding something ?
I have found a radical method stripping XMP metadata (in a step 2 bis...) using David Crowell's JStrip, see
http://davidcrowell.com/jStrip.aspx
Do you know any other best method to keep IPTC/IIM and XPM data synchronized when an image workflow uses different metadata editors and some of them are not XMP-aware ?
Patrick Peccatte
www.softexperience.com

Excerpt of "IPTC Core Implementation Guidelines", section 2.2.1 available on http://www.iptc.org/IPTC4XMP/:
The basic functionality of this synchronising mechanism [between IPTC/IIM metadata in IRB and XMP metadata] is:
- To move metadata from the IRB to a new XMP packet in case an image file is opened with such an IRB but without an XMP packet. If the file is saved both the IRB and the XMP packet will be stored to the header section of this file.
- To move metadata from the XMP packet to a new IRB in case an image file is opened with an XMP packet but without an IRB. If the file is saved both the IRB and the XMP packet will be stored to the header section of this file.
- To update the metadata values of the IRB respectively the XMP packet from the newer source to the older destination. Which set is newer or older is detected by a hash value over each block of metadata. (More detailed information is available from Adobes XMP web pages at www.adobe.com/xmp and in the software development kits.)
I have checked for Adobe XMP web site and searched in "XMP Specification, January 2004" and I have not found explanations about this "hash value over each block of metadata" mechanism.
Moreover, it seems that it does not work regarding to the following simple experiment:
- 1. add metadata to a JPEG image using Photoshop CS (which adds both IPTC/IIM data in IRB and data in XMP)
- 2. edit these metadata using an "IPTC/IIM-only and non-XMP-aware" editor like IrfanView, XNView or any other one
- 3. go back to Photoshop CS which displays the "old" XMP metadata ignoring changes done previously using the IPTC-only editor.
Of course this experiment works using an "XMP-aware" editor like iView Media Pro or PixVue in step 2.
So it seems very easy to get images with IPTC/IIM and XMP metadata not synchronized when the image workflow uses different programs to edit metadata.
Am I missing or misunderstanding something ?
I have found a radical method stripping XMP metadata (in a step 2 bis...) using David Crowell's JStrip, see
http://davidcrowell.com/jStrip.aspx
Do you know any other best method to keep IPTC/IIM and XPM data synchronized when an image workflow uses different metadata editors and some of them are not XMP-aware ?
Patrick Peccatte
www.softexperience.com

Adobe xmp metadata searchable on osx 10.5 server?

i'm not sure if this is the right category for this. we have 5 mac pro's that are connected to a NAS via Xserver running Mac OS X 10.5.x server. we've started using the xmp funtionality in adobe photoshop. on the 5 local clients, searching via spotlight, we can find files using the info typed in the xmp metadata portion of photoshop. however, when we store that same file on our NAS, searching the nas via the finder search box doesn't recognize the xmp metadata (i'm told we can't use spotlight because it only works on the local machine...even if that's not true, i tried it and it doesn't find the files). all of the local macs are on the same os version (the latest one) and spotlight indexing is enabled on the Xserve. is there a way for the xmp metadata to be searchable when searching the NAS from the local clients?
thanks

Just to let you all know... I came across this now, and will try it out tonight and confirm if it works or not
<key>interface</key>
<string>en0</string>
Using the "interface" keyword instead of "aliasIP"
Hope this works out =D

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!

[CS3 JS] Possible to Inspect Custom XMP Metadata With JavaScript?

I am using custom XMP metadata in InCopy and InDesign docs in CS3 to hold custom metadata that can vary wildly. I know the full set of possible items but not what values will be in a particular document.
Short of writing the XMP to a file and then processing that from my script, is there a way to inspect the custom properties from JavaScript. I didn't see a way to do it from the data model.
Thanks,
Eliot

Here is another script to catch MetaData, some more than the basic:
// metaDataOfLinks.jsx
//DESCRIPTION: Catches MetaData of linked images and creates a report at the DeskTop.
// Martin Fischer 10/2008
var myLinkXmpArray = ["author", "copyrightInfoURL", "copyrightNotice", "copyrightStatus   ", "creationDate", "creator", "description", "documentTitle", "format", "jobName", "keywords", "modificationDate", "serverURL"];
var myIPTCArray = ["CiAdrCity", "CiAdrCtry", "CiAdrExtadr", "CiAdrPcode", "CiAdrRegion", "CiEmailWork", "CiTelWork", "City", "CiUrlWork", "CopyrightNotice", "Country", "CountryCode", "Creator", "CreatorContactInfo", "CreatorJobtitle", "DateCreated", "Description", "DescriptionWriter", "Headline", "Instructions", "IntellectualGenre", "JobID", "Keywords", "Location", "Provider", "Province-State", "RightsUsageTerms", "Scene", "Source", "SubjectCode", "Title"];
var myPSArray = ["photoshop:AuthorsPosition", "photoshop:CaptionWriter", "photoshop:Category", "photoshop:City", "photoshop:Country", "photoshop:Credit", "photoshop:DateCreated", "photoshop:Headline", "photoshop:Instructions", "photoshop:Source", "photoshop:State", "photoshop:SupplementalCategories", "photoshop:TransmissionReference", "photoshop:Urgency"];//var myPSArray = ["photoshop:AuthorsPosition", "CaptionWriter", "Category", "City", "Country", "Credit", "DateCreated", "Headline", "Instructions", "Source", "State", "SupplementalCategories", "TransmissionReference", "Urgency"];
var myTiffArray = ["tiff:ImageWidth", "tiff:ImageLength", "tiff:BitsPerSample", "tiff:Compression", "tiff:PhotometricInterpretation", "tiff:Orientation", "tiff:SamplesPerPixel", "tiff:PlanarConfiguration", "tiff:YCbCrSubSampling", "tiff:YCbCrPositioning", "tiff:XResolution", "tiff:YResolution", "tiff:ResolutionUnit", "tiff:TransferFunction", "tiff:WhitePoint", "tiff:PrimaryChromaticities", "tiff:YCbCrCoefficients", "tiff:ReferenceBlackWhite", "tiff:DateTime", "tiff:ImageDescription", "tiff:MakeProperName", "tiff:Model", "tiff:Software", "tiff:Artist", "tiff:Copyright"];
var myExifArray = ["exif:ExifVersion", "exif:FlashpixVersion", "exif:ColorSpace", "exif:ComponentsConfiguration", "exif:CompressedBitsPerPixel", "exif:PixelXDimension", "exif:PixelYDimension", "exif:UserComment", "exif:RelatedSoundFile", "exif:DateTimeOriginal", "exif:DateTimeDigitized", "exif:ExposureTime", "exif:FNumber", "exif:ExposureProgram", "exif:SpectralSensitivity", "exif:ISOSpeedRatings", "exif:OECF", "exif:ShutterSpeedValue", "exif:ApertureValue", "exif:BrightnessValue", "exif:ExposureBiasValue", "exif:MaxApertureValue", "exif:SubjectDistance", "exif:MeteringMode", "exif:LightSource", "exif:Flash", "exif:FocalLength", "exif:SubjectArea", "exif:FlashEnergy", "exif:SpatialFrequencyResponse", "exif:FocalPlaneXResolution", "exif:FocalPlaneYResolution", "exif:FocalPlaneResolutionUnit", "exif:SubjectLocation", "exif:ExposureIndex", "exif:SensingMethod", "exif:FileSource", "exif:SceneType", "exif:CFAPattern", "exif:CustomRendered", "exif:ExposureMode", "exif:WhiteBalance", "exif:DigitalZoomRatio", "exif:FocalLengthIn35mmFilm", "exif:SceneCaptureType", "exif:GainControl", "exif:Contrast", "exif:Saturation", "exif:Sharpness", "exif:DeviceSettingDescription", "exif:SubjectDistanceRange", "exif:ImageUniqueID", "exif:GPSVersionID", "exif:GPSLatitude", "exif:GPSLongitude", "exif:GPSAltitudeRef", "exif:GPSAltitude", "exif:GPSTimeStamp", "exif:DateTimeOriginal,", "exif:DateTimeDigitized.", "exif:GPSTimeStamp", "exif:GPSSatellites", "exif:GPSStatus", "exif:GPSMeasureMode", "exif:GPSDOP", "exif:GPSSpeedRef", "exif:GPSSpeed", "exif:GPSTrackRef", "exif:GPSTrack", "exif:GPSImgDirectionRef", "exif:GPSImgDirection", "exif:GPSMapDatum", "exif:GPSDestLatitude", "exif:GPSDestLongitude", "exif:GPSDestBearingRef", "exif:GPSDestBearing", "exif:GPSDestDistanceRef", "exif:GPSDestDistance", "exif:GPSProcessingMethod", "exif:GPSAreaInformation"];
var myCameraRawArray = ["crs:AutoBrightness", "crs:AutoContrast", "crs:AutoExposure", "crs:AutoShadows", "crs:BlueHue", "crs:BlueSaturation", "crs:Brightness", "crs:CameraProfile", "crs:ChromaticAberrationB", "crs:ChromaticAberrationR", "crs:ColorNoiseReduction", "crs:Contrast", "crs:CropTop", "crs:CropLeft", "crs:CropBottom", "crs:CropRight", "crs:CropAngle", "crs:CropWidth", "crs:CropHeight", "crs:CropUnits", "crs:Exposure", "crs:GreenHue", "crs:GreenSaturation", "crs:HasCrop", "crs:HasSettings", "crs:LuminanceSmoothing", "crs:RawFileName", "crs:RedHue", "crs:RedSaturation", "crs:Saturation", "crs:Shadows", "crs:ShadowTint", "crs:Sharpness", "crs:Temperature", "crs:Tint", "crs:ToneCurve", "crs:ToneCurveName", "crs:Version", "crs:VignetteAmount", "crs:VignetteMidpoint", "crs:WhiteBalance"];
var myInfo = new Array;
var myDoc = app.activeDocument;
var myLinks = app.documents[0].links;
for ( i = 0; i < myLinks.length; i++)
   getMetaData ( myLinks[i] );
writeData ( 'Metadaten zu ' + myDoc.name + '\r-----------\r\r' + myInfo.join ( '\r\r'), File ('~/Desktop/Metadaten_' + myDoc.name.replace(/.indd$/, '') + '.txt'));
// ===============================================================
//                                  Funktionen
// ===============================================================
function getMetaData ( aLink )
   var myLinkXmp = aLink.linkXmp.properties.toSource().replace( /^$\{/,'' ).replace (/$\}$/,'').replace( /parent.+$/,'').replace(/:/g, ':\t').split( ', ');
   var myString = aLink.name;
   myString += loopLinkXmp ( aLink, myLinkXmpArray );
   myString += loopArray ( aLink, "http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/", "Iptc4xmpCore:CreatorContactInfo/Iptc4xmpCore:", myIPTCArray);
   myString += loopArray ( aLink, "http://ns.adobe.com/photoshop/1.0/", "", myPSArray );
   myString += loopArray ( aLink, "http://ns.adobe.com/tiff/1.0/", "", myTiffArray );
   myString += loopArray ( aLink, "http://ns.adobe.com/exif/1.0/", "", myExifArray );
   myString += loopArray ( aLink, "http://ns.adobe.com/camera-raw-settings/1.0/", "", myCameraRawArray );
   myInfo.push( myString.replace( /, $/,'') );
function loopArray( aLink, s1, s2, anArray )
   var temp = '\r\t--- ' + s1 + ' ---\r\t';
   for ( var a = 0; a < anArray.length; a++)
      try {
         var theEvalString = 'aLink.linkXmp.getProperty(\"' + s1 + '\", \"' + s2 + anArray[a] + '\")';
         var myCode = eval( theEvalString );
         if ( myCode != '' )
            temp += '[' + anArray[a] + ']\t' + myCode + '\r\t';
      } catch (e){ //temp +=e + '\r'
   return temp;
function loopLinkXmp( aLink, anArray )
   var temp = '\r\t--- LinkMetadata ---\r\t';
   for ( var a = 0; a < anArray.length; a++)
      try {
         var theEvalString = 'aLink.linkXmp.' + anArray[a] ;
         var myCode = eval( theEvalString );
         if ( myCode != '' )
            temp += '[' + anArray[a] + ']\t' + myCode + '\r\t';
      } catch (e){ //temp +=e + '\r'
   return temp;
function writeData ( aData, theFile )
   theFile.open ( 'w', 'Text', 'R*ch' );
   theFile.encoding = 'UTF-8';
   theFile.write ( aData );
   theFile.close ();
Ressources:
Adobe XMP Developer Center: http://www.adobe.com/devnet/xmp/
XMP Specification: http://www.adobe.com/devnet/xmp/pdfs/xmp_specification.pdf
Martin Fischer

Adding/Reading XMP Metadata in a psd file

Hi,
I'm having some troubles to understand how to add and read XMP metadata on a psd file. I followed the Panel developer guide tutorial, and try to look on the internet for some answers, but I'm still stuck ...
Here is the simple example I'm trying to make (using part of the code from the panel developer guide) :
     The function loads the XMP Script Library.
     @returns True if the XMP Script Library was loaded successfully.
     @type Boolean
function loadXMPLibrary(){
     if ( !ExternalObject.AdobeXMPScript ){
          try{
               ExternalObject.AdobeXMPScript = new ExternalObject('lib:AdobeXMPScript');
          }catch (e){
               alert("Can't load XMP Script Library");
               return false;
     return true;
     The function unloads the XMP Script Library.
function unloadXMPLibrary(){
     if( ExternalObject.AdobeXMPScript ) {
          try{
               ExternalObject.AdobeXMPScript.unload();
               ExternalObject.AdobeXMPScript = undefined;
          }catch (e){
               alert("Can't unload XMP Script Library");
    Try to put a new property into the metadata
if( app.activeDocument || !loadXMPLibrary()){
    var xmp = new XMPMeta(activeDocument.xmpMetadata.rawData);
    xmp.setProperty( XMPConst.NS_EXIF, "myProperty", "test" );
    activeDocument.xmpMetadata.rawData = xmp.serialize();
    unloadXMPLibrary();
    Window.alert(activeDocument.xmpMetadata.rawData);
I don't really know where I'm wrong, could you help me please ?
Thanks,
Julien

Rather mess with EXIF and Dublin Core namespaces, wouldn't it be better to create your own?
IE:
#target photoshop
addtoMeta();
function addtoMeta(){
if(!documents.length) return;
if (ExternalObject.AdobeXMPScript == undefined) ExternalObject.AdobeXMPScript = new ExternalObject("lib:AdobeXMPScript");
var xmp = new XMPMeta( activeDocument.xmpMetadata.rawData);
var myNamespace = "http://my.fantastic.newspace/";
var myPrefix = "nsfns:";
XMPMeta.registerNamespace(myNamespace, myPrefix);
xmp.setProperty(myNamespace, "myProperty", "A Test String");
app.activeDocument.xmpMetadata.rawData = xmp.serialize();

Lightroom Metadata editing and workflow is tedious nightmare!

I'm new to Lightroom in just the past month, but have used it enough to see that a serious interface problem makes Lightroom version 1x virtually unusable in a deadline-oriented publishing workflow. Lightroom's Metadata editing and workflow is just a terrible nightmare, and far too tedious and slow. It appears to be an afterthought implemented by good-hearted souls who've never had to edit this sort of information under serious deadline pressures. I know Lightroom is marketed as an image database and not a file browser, but we're all looking to simplify our workflow here and with just a few subtle enhancements, Lightroom could be an excellent file browser and file import manager too.
As it is now, the Lightroom v1x handling of File Naming and Renaming, Metadata Editing and Keyword Editing is poorly implemented and in need of an immediate overhaul to help professional photographers expedite this crucial and time-consuming first step in the archiving workflow. While Lightroom is very good at many other tasks, I give it a big fat "F" of a failing grade for these tasks.
First, the Lightroom Library Module needs an even more simple, linear interface that steps users through a precise procedures (and helps them remember them). Arguably, to accomplish this, the Import function may need to become a separate Module that can be selected and used separately before entering the Library. As File Naming and Renaming, Metadata Editing and Keyword Editing currently are implemented, I, for one, am always forgetting to fill out one of these critical sections and can't even seem to remember that some may need to be done before importing while others appear to be conceived to be done after importing. My point is, all these related steps really need to be done together, but the Interface spreads out the functions too much, and it is nearly impossible to build a logical and linear Import workflow, especially when you are first learning Lightroom.
I'd like to see a workflow that walks me through applying and editing (in order), File Naming, Basic and IPTC Metadata, Captioning and Keywords, so that I don't always forget some obscure step in the process (which I keep doing). Here are some specific suggestions, some of which may prove to be valid, some of which may be problems due to my lack of experience with thye software.
1. As currently implemented, Metadata editing requires too much thought, and does not have enough intelligent automation. Eliminate as much typing as possible (See Photo Mechanic!)
2. Lightroom needs better Metadata Presets. A "Quick Edit" view to simplify interface for editing minimal metadata info (File Name, Basic Info, Keywords, Headline, Limited Copyright Info).
3. Separating Keyword Tags, Metadata Browser, Keywording Presets and Metadata Presets confuses the workflow. They should all appear together under one selectable module that organizes a suggested, linear workflowfor these tasks, but allows it to be customized. This is the sort of tasks that need to be learned by rote memory, and having all these panes floating around on both sides of the photo make it impossible to quickly step through these tasks.
- Name (or Rename) files, Edit/Apply Basic and IPTC Metadata, Edit/Apply Keywords, Import or...
- Import, Name (or Rename) files, Edit/Apply Basic and IPTC Metadata, Edit/Apply Keywords, Import
4. Rename should offer the option of renaming the master file names on the disk, not just file names in the database (which I think is what Lightroom does, but again, this is very confusing for new users)! So, it is my belief that this feature needs a checkbox option to rename one, the other or both. But you need to be able to quickly find this dialog box every time you do an import, and it should not be hidden away out of view under the Library menu. Ideally and logically (for workflow), File Renaming should be handled when starting the Import into Lightroom.
This is critically important because many user

Lightroom metadata editing Part 2 (see Part 1 at top of thread)...
...This is critically important because many users just do not want to trust their images solely to any database and we want the ability to go look for master files with identical names should something go wrong with the software or we decide to edit the file in Photoshop outside of Lightroom or even switch to another library software program.
My own habit is to rename every file with the date followed by a unique, three-digit file number, as in 20070717_001, 20070717_002...up to 999 etc. (I have never shot more than 999 files in a single day, but this could be a four-digit number). To file these on disk, a folder with a similar naming scheme is created for each day's shoot, although a keyword slug is added to the end instead of file numbers.
5. Metadata Presets (Basic Info, IPTC metadata, EXIF metadata), Keywords need to be able to toggled on or off (promote/demote-expand/contract). Turning Off/On one section at a time via the Metadata Presets popup menu is too tedious...and you can't display IPTC and Large Caption together or leave Large Caption turned on. It also is difficult to remember where the Large Caption default (Preferences) setting is...
6. Please get the EXIF data out of the way entirely when editing captions and visa-versa...And the EXIF data should not separate Basic Info and IPTC Info fields. Please relocate the EXIF to the bottom of the Metadata pane...
7. IPTC Content, IPTC Copyright, IPTC Creator, IPTC Image expand/collapse sections need more automation:
- The Presets fields need Preset lists of entry choices for cities, states, countries, etc.!
- ISO Country Code automatically should be filled in when a country is entered.
- Date created automatically should be filled in from camera EXIF data
- Metadata Presets "Save As" should fill in old name, and allow you to rename it; (When it appears, the new name field should not be empty. This would aid in consistent, alphabetical naming
- Metadata Presets naming should support job names, with actual Presets saved under each job name...
8. IPTC Status EXIF, Contact, etc.
- Caption field MUST display more than one line...(6-8 lines)!
- Caption field MUST support Shift/Return!
- Headline (IPTC Content) should be displayed with (and above) caption. Please present information logically!
- Yellow popups should describe what each field name is for...some are real brain teasers...

How do you import (or convert) XMP metadata into iPhoto '08?

Having recently made OS X my primary operating system, I switched from using Picasa/Windows Photo Gallery on Vista to catalogue my photos to iPhoto '08. However, the 7,000+ pictures I have all have XMP metadata tags. None of them show up in iPhoto '08 after import. Needless to say, I am not looking forward to having to retag 7,000+ pictures in iPhoto.
I know people in various forums, here and elsewhere, have said that iPhoto '08 does not do XMP at all. Is this true? Is there a workaround or plugin? I find it weird that XMP has been an open standard since May, and 6 months later, there isn't a plugin or solution, especially from Apple. Unless I am just daft and missing something obvious, which is entirely possible.
At any rate, I would really appreciate any help in me not having to retag over 7,000 pictures...thanks in advance!

mrbofus:
Do you still have the PC and the photos on it? If so you might look into the demo version of iView MediaPro and see it if can read those Picasa files and embed the metadata into the files like it can when reading an iPhoto library on the Mac platform. If it can, you'll be able to write the metadata to the files and bring them over again to the Mac and import into a new library. This is only speculation as I'm not conversant in Windows at all.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Photoshop xmp metadata editing

Similar Messages

Maybe you are looking for