Editing XMP mismatches SFV

Hello. After reading a lot about it, I am very interested in using XMP metadata to organize my digital assets, especially my digital photos. However, I have been testing adding metadata to my photos (JPEG), and I have encountered a problem. This is what I do:
I create an sfv file (to check for changes in file) of my original photo.
I open Adobe Bridge and view my files.
I add a keyword to my original photo.
I remove the keyword from the photo.
I run sfv file check and get "FAILED" mismatch.
So, my question is this: If I add and then remove a keyword, shouldn't the file remain the same (unaltered)? Or, is XMP metadata editing "irreversible"? XMP metadata editing sounds like a great tool to use, but I want to be sure of what is happening to my files (that I'm not hurting them). Please help clarify this for me.

The XMP metadata format allows many different syntaxes for representing the exact same set of metadata, and software like the XMP toolkit is only required to be faithful to the data model, not to the exact surface syntax chosen. The difference shown by SFV, which presumably knows nothing about XMP's data model, is probably just due to the XMP software using a different syntax on output from the one it originally encountered in the file.
If you need to revert a change cleanly, it's probably best to keep a checkpoint copy of your entire media file. If you need to compare two files for having the same XMP data model, you'll need a specialized tool. I don't personally know of any, but maybe some other reader does.

Similar Messages

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)

Editing xmp files in Windows

Windows XP SP2 Pro
Just read on another forum that it is possible to edit xmp data in a text editor in Windows. If possible, could someone kindly stear me in the right direction for doing this or post a link.
I took a few dozen shots the other day and for some reason or other when imported into LR 99% of them showed up with the correct lens being used in the Metadata browser whilst the remaining 1% were indicated as 'Unknown Lens'. I would like to edit this data if possible so if the above is possible as suggested would appreciate some direction in the way to proceed. Thanks.

Bogdan
The situtation is this - last weekend I was asked to do a shoot of a friends daughter at her Church Communion. The shoot was a good result and I couldn't be more pleased with what I captured - the family are also :-)
For the shoot I used a Canon 30D with an EF 17-40 f/4L USM and shot off countless images. There was no camera or lens change throughout the shoot and all images were shot in RAW.
Upon Import to LR (only import, no editing done up to this point), the Metadata browser in the left hand panel of the Library indicated that 99% of these images were shot with the camera/lens combination above whilst the remaining 1%, whilst showing the correct camera, were indicated as 'Unknown Lens'. This may or may not be a corruption of the impregnated EXIF data within the RAW file itself but in this regard is not important.
My gaol was to change the 'Unknown Lens' entry in the Metadata entry to reflect the lens actually used. To this end I first Exported an xmp file, opened the file, found where unknown lens was indicated and substituted it for the lens used. I first checked another xmp with the correct info shown to ensure that I typed the correct data in precisely in the format as shown in the referenced file. I then saved the modified xmp file, went back to LR and 'Removed' the RAW image from the Library. Following this I Re-Imported the image and imported the xmp file just in case it hadn't been brought in at the same time as the RAW file.
Unfortunately, when highlighting this RAW image in the Library the Metadata browser panel still indicated the lens used as being 'Unknown'. I checked back in the xmp file and that still reflected my changes e.g. no mention of unknown lens and the correct lens being shown. I can only assume from this that upon Import of the .CR2 file into LR, LR is giving priority to the EXIF data buried deep within the .CR2 file itself and only takes data from the xmp file that is not contained within the EXIF file. I am no expert in these matters and therefore cannot come up with any other reason as to why when the xmp file has been corrected this is not reflected in the Metadata browser window in LR.
This is certainly not the end of the world but it is something that would obviously be desirous if this problem keeps on repeating itself. If LR is to show 'statistics' of Cameras and Lenses used etc then for it to have worth it must reflect accurate data. Not that I am suggesting for one moment that this is a failure within LR itself you understand.
Edit: Forget all references made to Camera model e.g. 30D/20D which may be confusing the issue. It was just that when I failed in my attempts to change the 'Unknown' lens entry to the correct data that I then attempted to see if it was possible to change any other data e.g. Camera model. This too was unsuccessful, but as stated can be dismissed as it is not the important issue here as is the case for the lens used and was only done for experimentation purposes.

Edit XMP-tags for MP3

Hello
Not sure if this is the right forum but I give it a try... I have used XMP for keyword-tagging a big collection of recordings (MP3) in Adobe Bridge. Unfortunatley the CreateDate-tag is wrong and I would like to modify the tags. For image or video there are several softwares availible to edit XMP-tags (like Exiftool and MetadataTouch) but for MP3 I haven't found anything. Is there any external software (Windows) availible for editing XMP-datetags in audio files?
Best reagrds
Fredrik

Not sure how many other people noticed, but iTunes 8 removed the ID3 tag "set version" feature from the "Advanced" menu. Part of the whole simplification push, I guess.
My DJ software (Traktor) doesn't like certain ID3 versions, so I sometimes need to batch change tags to ID3 v2.3. I.e. I don't need to edit the song metadata -- iTunes is great for that. I just need to batch change the tag version to ID3 v2.3.
I guess this is a bit arcane- any suggestions?

Extracting and editing XMP

Anyone have any tips for extracting and editing XMP? I've noticed that when I edit the metadata for pdf files, it doesn't embed the Dublin Core metadata (unless I'm doing something wrong, I guess). I've also noticed that if I change simple pdf properties like the title before I try to convert to a PDF-A1b, I'll get an error that says the titles are conflicting in the XMP. So I try to convert to PDF-A before I edit the metadata, then save as a PDF-A again.
Thanks for any suggestions.

Thanks Matthew,
That was the answer. There were a couple of funny little things, but I guess that's iMovie HD 5.
The first time I tried to reimport the Quick Time clip it was rejected but I gave it a shorter name and it was accepted. The first name was the same as, or close to, that of the extracted audio. Also, when I first extracted the audio of the short clip and checked Show Info, it gave the duration as being the same as the clip, about 6 minutes, but in iTunes it was 50 minutes or so.
I saw somewhere advice on selecting the extracted audio only and sending it to Quick Time Expert Settings but I guess the long version would still be the problem.
Thanks again.

Editing XMP data related to image files.

Dear members:
While working on organizing my photo library I have encountered a problem.
How can the XMP data file related to image files be edited in a way that the file info panel can see these changes ?
I made a mistake while saving the current filename as part of my file renaming scheme and need to have the XMP data edited so that it reflects the right (original) filename. I tried using the Mac's TextEdit application but it doesn't seem to have worked properly. Although the file was edited and then re-saved when I use the file info command to look at the data the old filename still appears under the raw data tab instead of the new, revised one.
What is the best way to edit this information ?
Any help will be appreciated as this is a semi-urgent matter.
Thank you in advance,
Joseph

So I was missing something. Thank you Hal.
I had not realised that XMP goes inside of actual image files with those file types. Obviously my new backup routine spotted that, as I was on backuping only modified/new files.
I would much prefer that also with above mentioned file types XMP-data would be stored in sidecar files instead of modifying the original file. To support this there are two arguments that I think are valid:
1) modification of the file is always risky (and spesifically, with image originals I prefer to avoid that),
2) modification leads to the fact that "smarter" backup strategies relying on "full backup" supported with differential or incremental backups lead to unnecessary long backuptimes and media consumption.
That said, I prefer to have XMP-data also outside of the catalog so that other tools can also utilise it (further, in addition to the catalog with sidecars I have sort of failover approach, and some of you may now say "belt and syspenders" after mentioning backups...).
Is there a way to have all file types to utilise sidecars rather that modifying original file?

Edit Capture Time XMP vs. EXIF

Scope:
- LR 1.4.1 and 2 Beta
- Any file that is edited using Metadata:Edit Capture Time
(Note: detail info below may be helpful to those seeking to understand date/time problems/issues with LR and other tools)
Background:
LR allows editing/offsetting of image capture time via the Metadata:Edit Capture Time menu option.
Changing the time in LR alters the following EXIF date/time metadata fields as displayed in LR:
- Date Time Original
- Date Time Digitized
- Date Time
Writing the LR metadata to the image file via the Metadata:Save Metadata to File command writes the values into the images relevant EXIF and XMP date/time metadata fields.
Challenge:
LR writes the correctly edited times into the XMP date/time metadata fields but writes incorrect times into the EXIF date/time metadata fields.
LR uses XMP date/time metadata fields for its displayed time data, not EXIF date/time metadata fields. As a consequence, the user does not know the EXIF time fields have been incorrectly changed unless they check them in a tool that displays or uses the EXIF date/time metadata fields.
Solution:
Use a batch file based on exiftools to copy the LR edited XMP date/times into the EXIF date/time metadata fields.
Resources:
- Batch file LR XMP/EXIF date/time bug fixer here - LR-xmpdatetime2exif.bat: http://www.hackneys.com/photos/lr/LR-datetimexmp2exif.bat
- Batch file arguments file (required) here LR-xmpdatetime2exif.args: http://www.hackneys.com/photos/lr/LR-datetimexmp2exif.args
A few useful tools to better understand this challenge:
- Batch file to display relevant date/time metadata fields here - list-exif-tags-sample-datetime.bat: http://www.hackneys.com/photos/lr/list-exif-tags-sample-datetime.bat
- Batch file to display set of EXIF metadata here - list-exif-tags-sample.bat: http://www.hackneys.com/photos/lr/list-exif-tags-sample.bat
- Batch file to display set of XMP metadata here - list-xmp-tags-sample.bat: http://www.hackneys.com/photos/lr/list-xmp-tags-sample.bat
- Batch file to display complete set of metadata here- list-metadata-tags-sample.bat: http://www.hackneys.com/photos/lr/list-metadata-tags-sample.bat
- Sample photo file here sample.jpg: http://www.hackneys.com/photos/lr/sample.jpg
Preparation:
All batch files require an installed copy of exiftools by Phil Harvey (free) available here: http://www.sno.phy.queensu.ca/~phil/exiftool/
1. Download exiftools windows command line version and rename the file exiftools.exe.
2. Place the exiftools.exe file in your windows directory or on your system path.
Utilization
1. In Lightroom, select the folder containing the photos you need to fix.
2. In Lightroom, select all the photos you need to fix.
3. In Lightroom, select Metadata:Save Metadata to File (this step ensures you dont lose any Lightroom specific metadata that has not been embedded in the file).
4. Using Windows Explorer or another utility, backup your jpg files
5. Using Windows Explorer copy the LR-xmpdatetime2exif.bat and LR-xmpdatetime2exif.args files to the folder with the jpg files you need to fix.
6. Using Windows Explorer double click on LR-xmpdatetime2exif.bat
7. Wait for the batch file to process.
8. In Lightroom, ensure the photos you just fixed are still selected, if not, re-select them.
9. In Lightroom, select Metadata:Read Metadata from File (this step ensures that Lightroom has all the revised EXIF date/time metadata loaded).
Detail:
This challenge is a subset and another manifestation that LR 1.4 uses the XMP date/time metadata fields, not the EXIF date/time metadata fields that other programs use and rely on. There have been numerous posts regarding other manifestations of this problem.
Most of the confusion relates to several primary factors:
1. Cameras embed EXIF metadata into photo files. Adobe products, and some others, support XMP metadata, which is not part of the EXIF standard. If a tool was developed p

Detail:
This challenge is a subset and another manifestation that LR 1.4 uses the XMP time data fields, not the EXIF fields that other programs use and rely on. There have been numerous posts regarding other manifestations of this problem.
Most of the confusion relates to several primary factors:
1. Cameras embed EXIF metadata into photo files. Adobe products, and some others, support XMP metadata, which is not part of the EXIF standard. If a tool was developed prior to XMP, such as Exifer or PSP 9, then that tool has no way to view or edit XMP metadata. If a tool only displays, edits and maintains XMP, such as LR, then the two data sets can become de-coupled for common data points, such as date/time. If a tool relies on the EXIF version of a common data point, such as RoboGEO, but the date/time was edited by a tool that only maintains XMP data, such as LR, then the EXIF dependent tool will be working with out of synch data.
2. LR, PSE, Bridge, etc. use, either exclusively or primarily, XMP metadata, even though they may label/display it as EXIF. LR, for instance, only displays the XMP date/time values, even though they are labeled EXIF.
3. The EXIF specification assigns time field names different than those commonly used in various tools when labeling/displaying EXIF time data fields. You will find the very same EXIF date/time field labeled a wide variety of ways in even a handful of tools.
4. The XMP specification has a namespace area labeled EXIF. Adding to the confusion even more, the XMP-EXIF namespace has date/time field names that duplicate those of EXIF date/time fields.
As you can see, if you add these four factors together, it is no surprise there is widespread confusion related to photo file date/time in general and LRs handling of it in particular.

CS4 problem when importing older CS3 Project, mismatched edits

I am trying to import a CS3 project into CS4 and for some reason some of the edits don't match up. It's only in some parts, most of it is fine. I really want to be able to use the new Media Encoder so I can make a DVD from the CS3 project (I was unable to do this in CS3 + older Media Encoder because it would always crash on my long length project).
I also tried bypassing Premiere CS4 by using the Media Encoder CS4 standalone project import option and selected the CS3 project and then the sequences....I scrubbed through the player and the same edits are mismatched/incorrect.
If I go back to the project in the older CS3, all edits are fine...but of course I can't export a MPEG for DVD because CS3's exports crash.
What is the deal?
If it matters, I am using 720p P2 footage.

Well I'm interested in this thread because I'm having a similar problem importing CS2 projects - audio filters are screwy, especially EQ.
I can't finish this project in CS2 for several reasons.
I can't seem to convert every project CS2 project -- some work, some do not. Missing preview files, probably. I know that CS4 conversions hanging are a separate documented issue.
So I'm trying to import projects instead. Everything looks all right but everything does not SOUND all right.

Will edited Raw files retain the xmp edited information when converting to DNG format?

I have a bunch of old nikon and canon Raw files that was edited in Photoshop Camera Raw. The Raw files have corresponding xmp files. I want to convert these edited Raw files into DNG format. Using the Photoshop Camera Raw converter or using the free Adobe DNG Converter tool - will the edited information from the Raw files be automatically converted over to DNG? What would be the best method to convert an edited RAW file into a DNG file, and retain all the editing (xmp files)? Thanks for help!!!

Using either the dng converter or camera raw though PS and Bridge will convert your RAW files to dng and keep the edited info from your xmp files, which will be add into the dng format. If you have a lot of files to convert, it might be faster to use the dng converter. Next choice would be to select them all in Bridge, right click and select "Open in Camera Raw."

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

Editing avchd xmp

When I import an AVCHD clip directly from the AVCHD folder on my camera into Premiere CS4, I can edit the file's XMP using the Metadata panel. Premiere creates an XMP sidecar. Fine.
However when I copy the same file to some random folder on my Mac and import it from there, the Metadata panel reports that the file is "Not editable". Huh!?
What's going on? Why is Premiere refusing to create/ edit xmp sidecars in some situations and not others?
Bridge is completely broken in that it refuses to edit xmp sidecars under all circumstances.
This is pretty frustating. Any way to work around these problems in Bridge/ Premiere or any other CS4 application?
eamonn

I'm at a loss to understand what the reason might be. It makes no sense to me.
I hear ya. The MXF container format was specifically designed so that a single file could hold video, multiple streams of audio, timecode and various metadata like exposure, zoom level, date recorded, etc. Why Panasonic chose to use a proprietary implementation of the MXF format for the P2 cameras is beyond me.
Tapeless media cameras, using a proper implementation of the MXF container format, could very easily create single clips for every stop/start of the camera. No "folder" structure required. But some idiot technocrat muffed it up on the design table, and now we're stuck with it.

Progamming export / import of XMP

Hi folks,
I'm still very new to this (just bought a book on Lua ) but I want to create something that export the XMP files (so that I can edit them on the road) and import them back to Lightroom. I've been reading the API reference and SDK manual lately, had a feeling that this is not possible but since I've seen some workarounds to achieve certain goals in this forum, thought still worth asking.
So, assuming that this is not possible, here are a few of my ideas:
Create some keyboard macros to automate the XMP export / import porcess. It'd nice and sweet if it's some simple application I'm dealing with, but with a complex app like Lr there are too many unpredictables and since it's all valuable data maybe this is not a good idea.
Create a plug-in that does not thing but generate XMP files using the post-processing part, and then import edited XMP manually. In this case though, I wonder if it's even possible to create a plug-in that will not export photos but only performs post processing.
Would anyone please shed some lights?
Thanks.
Nick.

Hi Rob,
To be honest I just Googled your name and found your web site that contains plug-ins that do similar things of what I wanted to do, this is nice to know because I just wanted to know if there's a way to go around this -- I didn't want to waste my time putting codes that wouldn't eventually give me what I wanted, thus the intention to ask the question in the first place. ;-)
I have some development background dealing with XML version control and conflict management so merging online VS offline content is okay for me, -- since all I want to do at moment is editing keywords and titles (or any other description fields) maybe I'll just create some CRC from online files, and write any changed values in the offline file back to the online file.
How I plan to edit the XMP file was to create a XSLT stylesheet that converts XMP files into a spreadsheet so I can edit on the road. If it's too much work I might just create a PHP script that sits on my home PC host the XMP web edit interface so I can edit them from any device with a web browser -- with this method I might not even have to deal with XMP versioning since I'll probably have the PHP to read XMP and write changes in realtime.
The mortifying part is -- as you pointed out already -- using a keyboard macro isn't really elegant, but guess this is the only way to automate this kind of stuff...
Thanks.
Nick.

Read specific XMP field

My clients rename the PDF files that I send them for review. So when they send one back as "Approved" I need to figure out which InDesign document created the PDF. I have created a JavaScript that saves the InDesign document name into a custom XMP field every time the document is saved.
Now, to make this as easy as possible, I want to create a menu item in Acrobat that allows the user to select it and have Acrobat display a dialog box showing the value of the custom XMP field. I have read the documentation, but it isn't very clear.
I know that I can call 'this.metadata' to return ALL of the metadata, but all I want is "xmp:InDesignDocumentName" which is in the name space "http://ns.adobe.com/xap/1.0/"
Anyone have experience digging into the XMP record?
James

I can't find details in the documentation on how to access extended metadata properties via the "info" property.
i.e. from the following RAW XMP data, I am trying to retrieve the xmp:InDesignFileName value, which is in the "http://ns.adobe.com/xap/1.0/" name space.
Any Ideas?
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.6-c014 79.156797, 2014/08/20-09:53:02
">
<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/"
xmlns:xmp="http://ns.adobe.com/xap/1.0/"
xmlns:xmpTPg="http://ns.adobe.com/xap/1.0/t/pg/"
xmlns:xmpGImg="http://ns.adobe.com/xap/1.0/g/img/"
xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/"
xmlns:stEvt="http://ns.adobe.com/xap/1.0/sType/ResourceEvent#"
xmlns:stRef="http://ns.adobe.com/xap/1.0/sType/ResourceRef#"
xmlns:stMfs="http://ns.adobe.com/xap/1.0/sType/ManifestItem#"
xmlns:idPriv="http://ns.adobe.com/xmp/InDesign/private"
xmlns:LCC="http://ns.lightcatcherphoto.com/"
xmlns:wn_private="http://ns.xinet.com/webnative/private/1.0/"
xmlns:xmpG="http://ns.adobe.com/xap/1.0/g/"
xmlns:stFnt="http://ns.adobe.com/xap/1.0/sType/Font#"
xmlns:wn_text="http://ns.xinet.com/webnative/text-extraction/1.0/"
xmlns:wn_image_info="http://ns.xinet.com/webnative/imageinfo/1.0/"
xmlns:wn_thumbnails="http://ns.xinet.com/webnative/thumbnails/1.0/"
xmlns:wn_previews="http://ns.xinet.com/webnative/previews/1.0/">
<dc:format>application/x-indesign</dc:format>
<dc:subject>
<rdf:Bag>
<rdf:li>Keywords</rdf:li>
</rdf:Bag>
</dc:subject>
<xmp:CreateDate>2015-03-11T17:06:09-05:00</xmp:CreateDate>
<xmp:MetadataDate>2015-03-31T08:55:35-05:00</xmp:MetadataDate>
<xmp:ModifyDate>2015-03-31T08:55:35-05:00</xmp:ModifyDate>
<xmp:LCCRevisionTime>Mon Mar 30 2015 16:28:03 GMT-0500</xmp:LCCRevisionTime>
<xmp:LCCDocumentStatus>In Progress</xmp:LCCDocumentStatus>
<xmp:LCCUserName>jhaney</xmp:LCCUserName>
<xmp:LCCRevisionNotes>More edits</xmp:LCCRevisionNotes>
<xmp:InDesignFileName>Untitled-8.indd</xmp:InDesignFileName>

Indesign JS -- XMP access without Bridge?

Is there a way to r/w XMP metadata in an InDesign script without having Bridge open?
I have read through a lot of the documentation, but the only way I am seeing to change metadata is by opening Bridge and loading the XMP library from there.
Can someone point me to any documentation about this other than the current Javascript Tools Guide?
Is there an InDesign class or library that can read and write XMP?
Is there a way to load the XMP library without actually having Bridge run?
Do I have to have that library to edit XMP data?
Can I move/copy the library somewhere else, load it, and have it still work the same way?
If anyone has any ideas, that would be great. I am pretty new to the scripting world and I am still learning.

Hi lanejd,
You can use InDesign's own XMP objects/properties/methods. (History note: we developed our own XMP tools early on, before the ExtendScript XMP library was available.) Do you want to change the metadata for an InDesign file, or look at the metadata for an imported element in an InDesign document?
If the former, you use the metadataPreferences object on the document itself (several examples in the Documents chapter of the Scripting Guide demonstrate the use of this object); if the latter, you use the metadataPreferences object on the itemLink element of the imported graphic.
By design, InDesign can't change the XMP of an imported graphic, so you'd still have to do that outside InDesign.
Thanks,
Ole

Editing XMP mismatches SFV

Similar Messages

Maybe you are looking for