XMP File Info SDK for CS4

Hi,
on our SDK page, the link to the CS4 SDK accidentally got lost,
but you can still download it here.
Here is short guideline which SDK to use:
If you or your customer are using only CS5, use the the CS5 SDK
When your custom panel shall be used with both CS4 and CS5, please use the CS4 SDK
For users of CS3 or earlier, you can create custom panels using a textual syntax, please use this SDK
When you have existing "EVE panels", you can convert them to MXML,
please read the forum discussion "Convert CS3 XMP Panels to work with CS
-- Stefan

Acrobat X custom panels are still compatible to Acrobat 8/9.
You can neither use the File Info SDK CS4 nor CS5.
To create a custom panel, please use this package on DevNET.
-- Stefan

Similar Messages

Custom File Info Panel CS2- CS4

I have a Custom File Info Panel that has been created in Adobe Photoshop CS2 and works in CS3. I am having trouble figuring out how to get it to work in CS4. Is there a way to port the Custom File Info Panel into CS4 without entirely recreating it?
I am seeing references to FileInfo SDK and creating a new Flex UI but I can't seem to find a definitive method on this pre-CS4 File Info Panel to the new UI - and I am in unfamiliar territory.
Any assistance or points in the proper direction would be most helpful.
UPDATE: Answering at least some of my own questions, I have followed the procedure here:
http://blogs.adobe.com/gunar/2008/11/customizing_metadata_ui_in_cs4.html
I am still having some trouble with a couple of the unique properties but I expect that they will be typos... I hope...
Any good reference information is still welcome.

Thank you for suggesting the PS Scripting forum but I think the next stop might be the XMP SDK Forum as there are a few similar questions there such as http://forums.adobe.com/thread/540397. But before I go impolitely cross-posting...
I've had some success and it appears that my custom file info metadata edited and saved in CS2 is now visible in CS4 and the reverse is also true - metadata edited and saved in CS4 is visible in CS2. This was built using the Generic Panel from the SDK according to the instructions shown at the link in my original post.
The only problem is that the external application that relies on the custom metadata doesn't see the CS4 version of the metadata. I suspect that this is just some general namespace issue. Perhaps if an XMP expert would be willing to comment on the conversion of the Custom Info Panel based on the following single portion of the metadata to see if I am doing it correctly - I would very much appreciate it.
In the CS2 Custom Info Panel XML I have this field:
<panel title="$$$/CustomPanels/XYZ/PanelName=XYZCorp Graphics MetaData" version="1" type="custom_panel">
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/XYZ/fullName=Full Name/Title of Graphic', font: font_big_right, vertical: align_center);
cat_container_edit_text(xmp_ns_prefix: 'xyzcorp', xmp_namespace: 'xyzcorp', xmp_path: 'FullName', container_type: seq_struct, horizontal: align_fill);
mru_popup(xmp_ns_prefix: 'twcable', xmp_path: 'FullName', no_check: true, vertical: align_top, container_type: seq_struct, mru_append: true);

</panel>
In my CS4 properties.xml the corresponding field:
<xmp_definitions xmlns:ui="http://ns.adobe.com/xmp/fileinfo/ui/">
<xmp_schema prefix="custom" namespace="xyzcorp" label="$$$/Custom/Schema/Label=XYZCorp Graphics MetaData" description="$$$/Custom/Schema/Description=CS4 Version of XYZCorp MetaData Custom Panel.">

<xmp_property name="FullName" category="external" label="$$$/Custom/Property/FullName_Label=Full Name/Title of Graphic:" type="seq" element_type="text"/>

<ui:separator/>
</xmp_schema>
</xmp_definitions>
It seems that the following CS2 => CS4 translations should be true:
"xmp_namespace" => xmp_schema namespace property (in this case "xyzcorp")
"xmp_path" => xmp_property name property (for this one property, "FullName")
is there another translation that I am missing? I am betting it has something to do with the CS2 "xmp_ns_prefix" but I am not entirely sure how to map this. Also perhaps something in manifest.xml (though it didn't seem like it)?
Many thank you's to anyone that can offer words of wisdom.
j

Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata

The cmd-keys / shortcuts doesn't work in the xmp file info panel btw. in the xmp / iptc fields (e.g. cmd+c, cmd+v, ...) of Adobe Bridge CS6 (Mac OS 10.6.8 and 10.7.3). You are not able to cut and paste info from one box to another like previous versions.
This bug only appears in the xmp file info window (opened via alt+i) in Bridge CS6 - if you edit information or metadata in the file info panel in Photoshop CS6 copy and paste from one field to another works.
The shortcuts also work under Windows (tested under Vista).
I noticed this minor bug already one in the Photoshop CS6 Beta more than one months ago. I hoped that this was corrected in the official test version, but unfortunately it is not. Although it is a minor bug, it is IMHO a basic function and would be very helpful in my daily work - it is too bad, that such a small thing is making working with the application a little bit annoying.

Thanks! If there is a workaround or simple solution, I would be very glad if you could inform me.
Christian
(signature removed by the Admin)
Am 14.05.2012 um 13:49 schrieb FrankBiederich:
Re: Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata
created by FrankBiederich in XMP SDK - View the full discussion
Thanks for your report; we'll look into it.
Frank
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: Re: Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata
To unsubscribe from this thread, please visit the message page at Re: Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in XMP SDK by email or at Adobe Forums
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.
Message was edited by: Arpit Kapoor

Is xmp files only availble for RAW files?

When we develop a RAW image with Camera Raw, we always get an xmp file with all the settings,
But after I developed a JPG image, I saw the Camera Raw Settings icon appeared above the right upper corner of the image thumbnail in Bridge,
however, I couldn't find the xmp file.
Is xmp files only availble for RAW files? JPGs or TIFs don't have xmp files for their Camera Raw settings??

Read-only didn't work for me, on a single jpg file, although it did lead to some interesting behavior. Set the read-only attribute on a jpg file in Windows XP and then tried the following:
1. Opened in Bridge, then into ACR 5.4. Performed some edits, then tried "Done", received permissions error and would not save edits.
2. Did the same except now invoked "Open", went into CS4 with edits intact and allowed saving out as different file. However, the ACR edits were not saved within the jpg, as expected, nor was a xmp created.
3. Removed the read-only attribute, repeated (2). Even though did not save file in CS4 the "Open" action did embed the edits into the jpg.
So read-only doesn't really allow creation of a xmp file, other than perhaps temporarily for transfer to Photoshop. It does lead to somewhat inconsistent behavior, in that I would have expected the "Open" to fail also since it could not bury the edits in the jpg.
Richard Southworth

Custom XMP File Info Panel; Popup fields only showing 64 values max?

I've created a custom file info panel for use with Creative Suite (Primarily for Bridge, but works just as well for any "File Info..." aware app.
I just recently noticed that there seems to be a limit to the amount of values in a Popup (aka drop down) field? I have a few that are intended to have up to 132 values, but they stop at 64!
Here's a snippet of my .xml code. I'm thinking there could (hopefully) be a simply solution, but I don't know what that is, yet.
I've removed names to protect the innocent:
#/ ---- Header starts with this:
<xmp_definitions xmlns:ui="http://ns.adobe.com/xmp/fileinfo/ui/">
<xmp_schema prefix="xwnv" namespace="http://ns.xinet.com/ns/xinetschema#" label="Offline_Tagging"
description="$$$/Custom/Schema/Description=This panel for use by ___ team only.">
#/ ---- Field code example is the following:
<xmp_property name="Art_Director" category="external" label="$$$/Custom/Property/Art_Director = Art Director:" type="openchoice" element_type="text">
<xmp_choice raw_value="" label="$$$/Custom/Property/=(select)"/>
<xmp_choice raw_value="Firstname.Lastname" label="$$$/Custom/Property/Firstname.Lastname=Firstname.Lastname"/>
#/ -----repeat values x130
</xmp_property>
It would be great to solve.
Thanks in advance.

You might try the Bridge Scripting forum at http://forums.adobe.com/community/bridge/bridge_scripting

Print XMP File Info?

Hello -
Anyone know if there's a way (a relatively easy way) to include certain fields from XMP File Info in a printout? Specificaly, I'm trying to do this from Illustrator CS.
Thanks,
John

well i see this one has everyone stumped. whatsup, nobody knows the answer? I have the same question and would like to know, even if the answer is "no, it is impossible, can't be done, no way, no how".
If that is indeed the answer, please support it.

Custom xmp file info panels

Add support for custom file info panels just like PS does now with custom
xmp panels.

[email protected] wrote:
> Add support for custom file info panels just like PS does now with custom
> xmp panels.
Are you talking about customizing the Metadata panel on the right hand
side of the library. If so, Lightroom already supports custom
panels...it just doesn't have the interface for facilitating the
customization. There is a nice website that lets you build a custom
metadata panel. Then you just download the resulting file and place it
where it tells you to on your hard drive.
http://regex.info/blog/2007-02-20/386

No XMP files are written for JPGs even when explicitely requested

Morning all,
I have learned not to trust the LR database too much. Thanks to Dan Tull I had my corrupted file repaired, but with 10,000+ tagged and processed RAWs, I do not feel too safe with the database alone. So I have decided to have XMP files written for all photographs. With 1.0 it worked only for my RAW files, not for my JPGs (have no other types).
So I was happy to find a flag "Write XMPs also for JPGs" in the catalog settings of 1.1. However, whether I check it or uncheck it, no XMP is written for JPGs. Neither when I let LR automatically write XMPs nor when I do it manually from the menu...
Anyone having an idea how to make this setting work?
Thanks,
Dirk

The advantage of sidecar files is that they are nondestructive to the original image. So exporting the images is no point.
And that the data written to the JPG contains all the settings is simply not the case. Try it out as follows: get hold of any one JPG in the finder. Import it to Lightroom. Do some strange manipulations on it, crop and go b/w. Then choose "Save metadata to file" from the Metadata menu in Library module. Now go to finder. The JPG is updated indeed. Copy it and import the copy into LR. The new version is the same as the original, no settings applied. And how could it? JPG is a defined format and it does not have room for most of the information that can be put to XMPs. So whatever you might expect from that export will disappoint you should you ever need it ;-)
Anyway, the issue remains: I would not expect LR to write more (e.g. virtual copies) than it does for RAWs, but I would expect it to write an XMP which is what the option offers: "Write develop settings to XMP for JPG...". How can I make it work?

Some comments on Adobe 'Custom Panels for XMP File Info' document

In developing a couple of Photoshop/Bridge custom metadata panels for cataloguing my photo collection, I noticed one or two things that look like possible errors in the above document. These comments relate to the version of the document dated April 2005.
P10, description of 'cat_container_edit_text' widget type: surely this should also list custom variable 'container_type', which is needed to specify whether the metadata array is a bag, seq or whatever.
P25, details of 'cat_container_edit_text': same comment applies.
P8 et seq: the requirements for use of the 'name' variable appear contradictory. The summary descriptions of various widgets such as 'edit_text' contain the statement that 'You must provide name, xmp_namespace and xmp_path values for this widget to supply a dynamic
value', but the description of 'name' on P16 says that it 'Applies only to fixed-text widgets. Do not use this variable to change the value or text of the widget at run time.'
Regards
Adrian

Joe, here is the Adobe link that I could not find yesterday when I put up the link to the (suspect) archive site:
http://partners.adobe.com/public/developer/xmp/sdk/topic_cust_file_info_panels.html
I have not looked into these panels for years and I am not sure what has changed in CS4.
Yes, the free software mentioned previously was limited in the amount of fields, however correct me if I am wrong - the output was just XMP text data and one could simply open it in a text editor and copy/paste/edit extra fields and resave, as the limitation was with the GUI frontend and not with XMP.
Obviously the computer reading the file needs the custom info panel installed to see the panel in it's full glory, otherwise the metadata is "hidden" away in one of the other metadata listings (I can't remember where). I also had problems picking up the custom metadata when searching via catalogue applications that could read other common metadata such as IPTC.
It was a bit of a mixed bag if I recall, showing promise however it was not really ready for the average user to use.
Anyway, it sounds as if my very limited knowlege on this area is being exhausted...
While on the topic, some other links that may help:
http://www.idealliance.org/industry_resources/branding_media_and_color/digital_image_submi ssion_criteria/metadata_fields
http://www.idealliance.org/industry_resources/branding_media_and_color/digital_image_submi ssion_criteria/resource_center/xmp_custom_panel
http://www.disc-info.org/resources/xmp.zip (perhaps you look at the source code for ideas)
http://www.iptc.org/IPTC4XMP/
http://www.controlledvocabulary.com/forum.html
http://www.controlledvocabulary.com/imagedatabases/mtworkaround.html
http://metadatamanifesto.blogspot.com/
iView Media Pro software also had a custom panel for Photoshop that may also give you ideas.
Regards,
Stephen Marsh

Why Can't I export cs5 file to .idml for cs4?

The link below is the final version of a project I'm working on along with an obscure font you need to install to view the file properly
http://www.mediafire.com/?m9oumck6g13sovz
I can't convert it to an .idml to open with cs4 for some reason. I had read something about certain fonts causing export problems in the past so i made an alternate version with only Tahoma font (I know there are alot of pink boxes, I would convert them in cs4), link below
http://www.mediafire.com/?psp5h8nvlwnqfsq
still no luck. If anybody could either to idml (preferably the first link, that's the final version), and send me a link, or even just tell me what i'm doing wrong, I would greatly appreciate it, thank you so much! The error I get for the first file is out of memory, for the second I can get a Visual C++ runtime error

I'll give it a shot, if only because you're working in, what's this, Gujarati? and I have a soft spot in my heart for anyone who typesets complex scripts in InDesign.
... five thousand pages of Gujarati translation? Dang. No wonder you used autoflow.
... nope, it crashes out for me as well. I'll try again tomorrow, but I think this is going to be a case where the only thing to do is going to be to chop the file into smaller pieces, export the pieces, and rebuild the complete file from the IDML fragments in CS4.

XMP File Info Panels in Lightroom?

I read in:
http://www.adobe.com/products/xmp/related.html
Adobe applications that support XMP:
Eventually all Adobe applications will use XMP.
What about Lightroom?
/Thomas.

You may want to address this over at the Feedback/Feature Request Site which is being used more and more for discussion related to this kind of request.

Bridge CS4 File Info dialog broken

Hi all,
I hope somebody may help:
My Bridge used to work fine, until I experienced the following error:
"Fatal Error in running FileInfo:
Please run the XMP Panels 2.0 STI first and restart your App.
The STI will install necessary swf files to: C:\Program Files\Common Files\Adobe\XMP\Custom File Info Panels\2.0\ "
I´m using a VISTA Home Premium 32-bit system.
As I had no idea what is meant by "STI" I simply copied all files from the folder above (...XMP\Custom File Info Panels\2.0\) from a friends machine (same operating system, same Photoshop version) to mine.
Unfortunately this did not solve the problem.
If I now select "File Info" in Bridge CS4, the error is gone. But now an empty window opens. Or better to say, it´s not a window but a blank dialog box with nothing on it but white color. I can close this box by pressing ESC.
Best regards, Sebastian

I've been having the same problem now for a few weeks and its killing me. Not sure what I can do, but in Photoshop and Bridge, the only programmes I use on a daily basis, it takes me forever to enter file information.
My specs are:
eMachines ET-XXXX
Windows 7 Home Premium
4GB RAM
500GB HDD

Help creating custom XMP file for Photoshop CS5

I was wondering if there is anyone out there that would be willing to help me create a custom XMP file for Photoshop CS5. What I need is very simple, I really just don't know how to go about creating it myself.
Feel free to email me at [email protected]

Hi Robert,
please have a look at the "Generic Panel" example of the File Info SDK.
Using that you only need to create a simple XML-file to create a simple custom panel.
-- Stefan Makswit

How to make my old file info panel from photoshop work in xmp

Help. Not a photoshop guy but rather a genealogist. Many years ago downloaded a custom file info panel for photoshop which I used to enter meta text about the family photos I scanned. Currently using adobe creative cloud but cant figure out how to use panel or see most of my metatext last few version. Below is information about the panel. All I really want to do is install my panel and get back to genealogy. I apologize but not sure I need to understand the basics of photoshop..
john weis
[email protected]
This is the authors description of the panel:
Genealogy Photo (Private Collection) Custom File Info Panel 1.0 for Photoshop. 11 FEB 2007
Developed by Ron Reiger [email protected]
Please contact me to suggest improvements.
1. BASIS FOR THIS CUSTOM FILE INFO PANEL
2. DESCRIPTION OF EACH PROPERTY NAME
3. WHERE EACH PROPERTY NAME MAPS & OTHER NOTES
4. WHERE TO INSTALL THE CUSTOM FILE INFO PANEL
1. BASIS FOR THIS CUSTOM FILE INFO PANEL
The Custom File Info Panel is used to capture metadata about a genealogy/family history photo that is privately held (that is, the photo is not in the possession of a library). The metadata property names on the File Info Panel are based on my interpretation of the recommended primary citation for a photograph (private possession) (annotated, with provenance) as described on page 95 of Elizabeth Shown Mill's "Evidence! Citation & Analysis for the Family Historian" and on my interpretation of recommended primary citation for an Electronic File (Image from Private Files - Annotated), Mills, "Citation!", page 81. I added a few more property names for location and date the photo was taken and keywords (to ID people by number rather than by name), the name of the person who provided the description, a surety for their description, and an informal description. Each field is discussed below.
2. DESCRIPTION OF EACH PROPERTY NAME
Date Scanned: This is the date the photo was scanned. Date is populated by Photoshop and is not editable.
Provider: The owner of the photo as of the date it was scanned. A researcher in a future generations will know who had the photo at a particular point in time.
Provenance: Describe as best you can how the photo got from the person in the photo to the Provider.
Description Provided By: List the person who identified the people and location in the image.
Description Surety: (This is an open text field. You can use any surety rating system you want.) Describe or rate the quality of the Description of the image's people and location. Note any uncertainties regarding any particular people in the photo.
Complete Subject Description: List the full name of each individual in the image, in order. You may want to list the location and date of the image even though there are separate property names for that data.
Informal Subject Description: An optional non-genealogical description of the image, perhaps for using the photo outside of genealogy. Example Informal Subject Description: "Grandpa as a young man."
Media Description: Describe the paper photo you scanned. Dimensions, border, frame, damage, etc. Your ancestors will have an easier time finding the paper photo later if you describe it well!
Annotations: Copy any annotations on the front or back of the photo and frame. Transcribe any photographer embossing/imprint; this is a clue for dating/locating photos.
Special Editing/Alterations: Describe any restoration you performed on the digital image. Did you correct for the lateral reverse of a tintype or daguerreotype?
City/County: List the City/County where the image was taken.
State: List the State where the image was taken.
Country: List the County where the image was taken.
Photo Date: List the date the image was taken.
Keywords: This is the standard keyword entry. Commas or semicolons can be used to separate keywords. I type the TMG ID number of each person in the photo here so I can search for all photos of the person without typing their name.
3. WHERE EACH PROPERTY NAME MAPS & OTHER NOTES
I have not created a working namespace URI or rdf ala http://purl.org/dc/elements/1.1/ for this panel. I have not created localization dictionary files for this panel. Data entered into the panel will appear in Adobe Bridge. As you can see below I re-used lots of pre-existing property names and dumped all my new property names into the photoshop namespace. I don't know if this approach has drawbacks.
Date Scanned:                xmp_path: 'CreateDate'   Pre-existing property name
Provider:    xmp_namespace: photoshop, xmp_path: 'Credit'    Pre-existing property name
Provenance:    xmp_namespace: photoshop, xmp_path: 'Provenance'
Description Provided By: xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy' Pre-existing property name
Description Surety:   xmp_namespace: photoshop, xmp_path: 'DescriptionSurety'
Complete Subject Description:   xmp_namespace: photoshop, xmp_path: 'Description'   Pre-existing property name
Informal Subject Description: xmp_namespace: photoshop, xmp_path: 'Caption'   Pre-existing property name
Media Description:   xmp_namespace: photoshop, xmp_path: 'MediaDescription'
Annotations:     xmp_namespace: photoshop, xmp_path: 'Annotations'
Special Editing/Alterations: xmp_namespace: photoshop, xmp_path: 'SpecialEditing'
City/County:    xmp_namespace: photoshop, xmp_path: 'City'    Pre-existing property name
State:     xmp_namespace: photoshop, xmp_path: 'State'    Pre-existing property name
Country:     xmp_namespace: photoshop, xmp_path: 'Country'   Pre-existing property name
Photo Date:    xmp_namespace: photoshop, xmp_path: 'DateCreated'   Pre-existing property name
Keywords:               xmp_path: 'Keywords'   Pre-existing property name
4. WHERE TO INSTALL THE CUSTOM FILE INFO PANEL
I have tested this panel with Photoshop CS2 and Adobe Bridge CS2 only. It may not work on earlier versions. FWIW a malformed Custom File Info Panel will fail to load in File Info; it won't crash Photoshop.
The following was taken from "XMP Custom Panels," Adobe, Oct 2003.
Each time an Adobe application opens the File Info dialog, it scans all the files in these directories and appends them to the file list. If more than one of the description files has
the same panel name, the one found in the last file to be loaded is added, and others are ignored.
Changes to the contents of the directories do not require you to reload an application; changes are automatically reflected in the dialog the next time it is opened.
The panel description and localization dictionary files must reside in the following locations for use with Adobe Creative Suite applications:
Mac OS X
{Root Volume}/Library/Application Support/Adobe/XMP/Custom File Info Panels
{Home Directory}/Library/Application/Adobe/XMP/Custom File Info Panels
Windows
\Program Files\Common Files\Adobe\XMP\Custom File Info Panels
\Documents and Settings\<user>\Application Data\Adobe\XMP\Custom File Info Panels
The panel description and localization dictionary files must reside in the following locations for use with Adobe Acrobat 7.0 or 6.0:
Mac OS X
{Root Volume}/Library/Application Support/Adobe/Custom File Info Panels
{Home Directory}/Library/Preferences/Adobe/Custom File Info Panels
Windows
\Program Files\Common Files\Adobe\\Custom File Info Panels
\Documents and Settings\<user>\Application Data\Adobe\Custom File Info Panels
I actually do not understand how to write a panel but here is the actual panel:
<?xml version="1.0">
<!DOCTYPE panel SYSTEM "http://ns.adobe.com/custompanels/1.0">
<panel title="$$$/CustomPanels/Acro/PanelName=Gen Photo (Private Collection)" version="1" type="custom_panel">
group(placement: place_column, spacing: gLargeSpace, horizontal: align_fill, vertical: align_top)
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/AWS/FileInfoLib/Panels/Description/DateCreated=Date Scanned:', font: font_small_bold_right, vertical: align_top);
date_static_text(fbname: '$$$/AWS/FileInfoLib/Panels/Description/DateCreated=Date Scanned', name: '$$$/AWS/FileInfoLib/Panels/DateCreated=Created', xmp_path: 'CreateDate', horizontal: align_fill, vertical: align_top, truncate: true, locked: true);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/Genealogy/Provider=Provider:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Provider=Provider', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'Credit', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Credit', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/Genealogy/Provenance=Provenance:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Provenance=Provenance', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Provenance', container_type: alt_struct, v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Provenance', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/DescriptionProvidedBy=Description Provided By:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/DescriptionProvidedBy=Description Provided By', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/DescriptionSurety=Description Surety:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/DescriptionSurety=Description Surety', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'DescriptionSurety', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'DescriptionSurety', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/Genealogy/Description=Complete Subject Description:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Description=Complete Subject Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Description', container_type: alt_struct, v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Description', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/Caption=Informal Subject Description:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Caption=Informal Subject Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Caption', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Caption', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/MediaDescription=Media Description:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/MediaDescription=Media Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'MediaDescription', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'MediaDescription', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/Annotations=Annotations:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Annotations=Annotations', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Annotations', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Annotations', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/SpecialEditing=Special Editing/Alterations:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/SpecialEditing=Special Editing/Alterations', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'SpecialEditing', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'SpecialEditing', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/City=City/County:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/City=City/County', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'City', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'City', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/State=State:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/State=State', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'State', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'State', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/Country=Country:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Country=Country', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'Country', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Country', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/PhotoDate=Photo Date:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/PhotoDate=Photo Date', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'DateCreated', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'DateCreated', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/AWS/FileInfoLib/Panels/Description/Keywords=Keywords:',font: font_small_bold_right, vertical: align_top);
cat_container_edit_text(fbname: '$$$/AWS/FileInfoLib/Panels/Description/Keywords=Keywords',horizontal: align_fill, height: gTextViewHeight, xmp_path: 'Keywords', container_type: bag_struct, v_scroller: true);
mru_popup(xmp_path: 'Keywords', container_type: alt_struct, no_check: true, vertical: align_top);
</panel>

You are not going to be able to run your old system from the backup on this old computer as the hardware is incompatible.
You need to get a new computer or a refurbished one.

XMP Custom File Info panels vs. Custom Metadata

Sorry if this question is a little confused, but I don't exactly know what I am talking about yet.
I use Rob Cole's custom metadata plug-in, which is great as far as it goes. As I understand it, it is a way to create custom data fields in the Lightroom database, give them labels, and manipulate and sort images according to those values. It is very useful for what it is. However, where it shows its seams is when you want to edit an image outside of Lightroom and then import the image back into Lightroom (for instance exporting the image, or editing it in Photoshop). In that case there is no way to get the data in the original into the derived copy except by doing it by hand, which can be very labor intensive if you, say, export a few hundred or a few thousand images. And, of course, you can only see the custom metadata in Lightroom, since it doesn't live in the file.
If I understand it correctly, "Custom File Info panels" for xmp data should just solve this problem. You would define your data, and it would be understood by "standard Adobe applications". A brief search of the web does not indicate that Lightroom is one of these "standard Adobe applications", so I assume that while I can use these panels in Bridge and in Photoshop, the data would not be available to me in Lightroom?
Any insight?
Thanks
Alan
robcole

alanterra wrote:
there is no way to get the data in the original into the derived copy except by doing it by hand
Better ways:
1-1 or 1-many:
(on the file menu: plugin extras) which brings up:
If you want to do "many to many-others-like-them", you have to use a different plugin, like Relative Antics..
alanterra wrote:
If I understand it correctly, "Custom File Info panels" for xmp data should just solve this problem.
Many of us are hoping Adobe enhances Lr to provide better support for custom metadata - as you've noticed, Lightroom is not one of those "Standard Adobe Applications" referred to in the above link.
Rob

XMP File Info SDK for CS4

Similar Messages

Maybe you are looking for