XML export action/plugin?

hey folks. i am attempting to work LR into my workflow 100%. this involves my custom data-driven website, which uses XML for as a sort of meta-datbase, stored in memory -- it contains image info, captions, keywords, etc, and allows for speedy searches on the site. i currently have 5,000 images (non LR) and it works very well.



to obtain total LR workflow, when exporting a shoot to web-ready .JPGs, i also need a way to export the images' info into an .XML file in the JPGs directory. then my automated process can pick this folder up, move the jpgs into place, and integrate the shoot's XML into the master website XML file.



im a programmer. can anyone recommend a good place to start for a task like this? im guessing it would likely be a LR plugin? which would then use the LR API or access the SQLite db directly or something...?



thanks!

matt
XML export action/plugin?
You got your answer on another forum. Until Adobe releases the SDK your out

of luck and you could still be out of luck if they don't allow for

import/export plug-in creation with that SDK. That has not been mentioned.

The only thing mentioned in regards to the SDK is that Adobe is still

working on it. I should be out sometime this year. Depending on what Adobe

has planned for the 1.1 update to LR that could push the SDK release back

even futher.



Robert
XML export action/plugin?
You could write something that extracts the XMP information from the exported JPEGs and processes it as needed. All the metadata you want is there; it's just not in a separate file.



You don't mention what language you're working with, but a quick search found this for .NET. Seems pretty simple to get at the XMP in the JPEG.



http://www.shahine.com/omar/ReadingXMPMetadataFromAJPEGUsingC.aspx

wow. i cant imagine that would deny 3rd party developers the ability to write import/export plugins...especially export -- this is an area of weakness in LR and is really is well-suited for customization.



but good to know, thanks. i hope they dont drop the ball w/ a SDK; often its the extensibility of a thing that makes it truly awesome.



matt

''would deny 3rd party developers the ability to write import/export plugins...especially export ''



Don't worry, they won't.



Once the Lightroom engineers get a bit of breathing room making an SDK will be a priority because the whole reason Lightroom is developed as a modular application is to make extensibility easier and more prowerful. But there is the issue of time %26amp; resources as well as flushing out the core engines in Lightroom so that they can commit to maintaining the SDK when developed...

DW - that link is awesome, thanks. i had written an EXIF parser in C#, but i quickly discovered that parsing exif sucks...hit or miss, different per camera, etc.. was discouraged so i didnt bother w/ IPTC, and im glad i didnt -- w/ XMP there is a published map, and since its XML its very easy to work with.



this will provide me w/ a great solution.



tho, i may still write an XML exporter sometime if feasible -- XML is just so damn useful; and if it can come directly form the horses mouth (LR) it removes more margin of error.



thanks!

matt

DW - this worked quite well, done. rock! thanks again.

Glad I could help.

Hi Matt Del Vecchio I have the same problem and am very keen to have a look at the solution you came up with. Could you please share here and/or send me a not on my blog. http://madteckhead.com. Thanks a million.