CreatorContactInfo struct in Generic File Info Panels

Hi all,
I developed a custom panel with custom metadata in Adobe Bridge CS4, using the Generic File Info Panels.
In this panel, I have to include custom metadata and the IPTC Contact metadata.
No problem with custom metadata, I have a problem with IPTC Contact:
If I insert value in the IPTC Panel provided by Adobe, I see that metadata is written in this way:
<Iptc4xmpCore:CreatorContactInfo
    Iptc4xmpCore:CiAdrExtadr="value"
    Iptc4xmpCore:CiAdrCity="value"
    Iptc4xmpCore:CiAdrRegion="value"
    Iptc4xmpCore:CiAdrPcode="value"
    Iptc4xmpCore:CiAdrCtry="value"
    Iptc4xmpCore:CiTelWork="value"
    Iptc4xmpCore:CiEmailWork="value"
    Iptc4xmpCore:CiUrlWork="value"/>
If I insert values in my custom metadata I haven't CreatorContactInfo structure:
<rdf:Description rdf:about=""xmlns:Iptc4xmpCore="http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/"
Iptc4xmpCore:CiAdrExtadr="value" Iptc4xmpCore:CiAdrCity="value" Iptc4xmpCore:CiAdrRegion="value"
Iptc4xmpCore:CiAdrPcode="value" Iptc4xmpCore:CiAdrCtry="value" Iptc4xmpCore:CiTelWork="value"
Iptc4xmpCore:CiEmailWork="value" Iptc4xmpCore:CiUrlWork="value"
xap:MetadataDate="2010-04-20T09:07:47+02:00">
<tiff:BitsPerSample> <rdf:Seq> <rdf:li>8</rdf:li> <rdf:li>8</rdf:li> <rdf:li>8</rdf:li> </rdf:Seq>
</tiff:BitsPerSample> </rdf:Description>
Is there a way to reproduce the orginal (and standard) structure??
There is my custom properties.xml (only the IPTC rows):
<xmp_schema prefix="Iptc4xmpCore" namespace="http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/" label="$$$/Custom/IPTC Contact=IPTC Contact" >
     <xmp_property name="CreatorContactInfo:CiAdrExtadr" category="external" label="$$$/Custom/Property/Address=Address:" type="text"/>
     <xmp_property name="CreatorContactInfo:CiAdrCity" category="external" label="$$$/Custom/Property/City=City:" type="text"/>
     <xmp_property name="CiAdrRegion" category="external" label="$$$/Custom/Property/State/Province=State/Province:" type="text"/>
     <xmp_property name="CiAdrPcode" category="external" label="$$$/Custom/Property/Postal Code=Postal Code:" type="text"/>
     <xmp_property name="CiAdrCtry" category="external" label="$$$/Custom/Property/Country=Country:" type="text"/>
     <xmp_property name="CiTelWork" category="external" label="$$$/Custom/Property/Phone=Phone:" type="text"/>
     <xmp_property name="CiEmailWork" category="external" label="$$$/Custom/Property/Email=Email:" type="text"/>
     <xmp_property name="CiUrlWork" category="external" label="$$$/Custom/Property/Website=Website:" type="text"/>
     <ui:separator/>
          </xmp_schema>

Edited reply:
Try:
name="CreatorContactInfo/Iptc4xmpCore:CiAdrExtadr"
name="CreatorContactInfo/Iptc4xmpCore:CiAdrCity"
name="CreatorContactInfo/Iptc4xmpCore:CiAdrRegion"
name="CreatorContactInfo/Iptc4xmpCore:CiAdrPcode"
name="CreatorContactInfo/Iptc4xmpCore:CiAdrCtry"
name="CreatorContactInfo/Iptc4xmpCore:CiTelWork"
name="CreatorContactInfo/Iptc4xmpCore:CiEmailWork"
name="CreatorContactInfo/Iptc4xmpCore:CiUrlWork"
Carl

Similar Messages

XMP data not showing up in the custom file info panels when upgraded to CC

For several versions of Photoshop, I have been able to use a modified custom file info panel to input, update, and track psd files. With each version of photoshop there are always some changes in the way the object data is handled. The lastest challenge is:
1. XMP data not showing up in the custom file info panels when upgraded CC from CS6.
2. Raw data is not visible in CC in the File info panel.
3. This occurs in new documents where we create the xmp wrapper while the file template is built.
4. When metadata is manually entered into the file, the data is not added to the XMP wrapper when it is recreated on the save.
5. When a file that was created in CS6 is opened that contains the Metadata in the file info template. It is visible. the Raw data is also visible. Once the XMP wrapper is recreated - write and then close. The data is no longer available. the Raw data will not pull up in the file info panel.
Any feedback or a direction will be appreciated.

I have a script that the user runs to input xmp data into a Customized version of the generic file info panel. it is data that is gathered from the user when the psd file is created. once the file is open in photoshop. the information is visible in the File info panel , the raw data, and as a schema addition in the advanced tab.
in CC the nodes and the children of the XMP packet have changed positions. so that the XML -this.XMP.child(0).appendChild(this.createNode())
is no longer the node that can be appended.
Where XML.child(0).elements().length(); would enable the xmlns to be added in CS6
<rdf:Description xmlns:phsa="' + this.namespace + '" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:x="adobe:ns:meta/" rdf:about="" />'
it is visible in CC as namespace in a different arrangement. XML.child(0).child(0).namespaceDeclarations().toString()) and the children are XML.child(0).child(0).elements().length().toString()); There are now 7 child nodes where before there were 1.
with all shifted, the initialize of the values and the delete XMP packet wrapper and create new or the amend to the XMP packet wrapper is undefined.

CS5 Custom File Info Panels showing up in Bridge

If I create a custom XMP panel using the GENERIC model, how do I make it appear in Bridge, also?

I have a script that the user runs to input xmp data into a Customized version of the generic file info panel. it is data that is gathered from the user when the psd file is created. once the file is open in photoshop. the information is visible in the File info panel , the raw data, and as a schema addition in the advanced tab.
in CC the nodes and the children of the XMP packet have changed positions. so that the XML -this.XMP.child(0).appendChild(this.createNode())
is no longer the node that can be appended.
Where XML.child(0).elements().length(); would enable the xmlns to be added in CS6
<rdf:Description xmlns:phsa="' + this.namespace + '" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:x="adobe:ns:meta/" rdf:about="" />'
it is visible in CC as namespace in a different arrangement. XML.child(0).child(0).namespaceDeclarations().toString()) and the children are XML.child(0).child(0).elements().length().toString()); There are now 7 child nodes where before there were 1.
with all shifted, the initialize of the values and the delete XMP packet wrapper and create new or the amend to the XMP packet wrapper is undefined.

Custom File Info-panel stays empty

Hi all!
I want to create my first custom File Info panel and I have trouble with it.
I use either a sample from the XMP-FileInfo-SDK-5.1 (e.g. "BasicControlSamplePanel") or even the "Generic" tool for simple XMP based panels.
I use Photoshop CS4 (on Mac OS X 10.6.4) and so I copy the panels to "~/Library/Application Support/Adobe/XMP/Custom File Info Panels/2.0/".
Now I look with Photoshop and I see the tab for the new panel but the content is empty...
Of course I did no modifications on the samples for my first try.
Any clues what's wrong here? I guess it may be a simple error because even the sample does not work...
TIA,
H.Sup
PS. I did also a test on Win XPwith the same result.

To answer my own question:
The documentation really sucks.
I found this reply from Adobe <http://forums.adobe.com/message/2540890#2540890>
usually we recommend to install custom panels into the "user" location at:
WINDOWS XP: C:\Documents and Settings\username\Application Data\Adobe\XMP\Custom File Info Panels\2.0\panels\
WINDOWS VISTA: C\Users\username\AppData\Roaming\Adobe\XMP\Custom File Info Panels\2.0\panels\
MAC OS: /user/username/Application Data/Adobe/XMP/Custom File Info Panels/2.0/panels/
The reason why your panels did not work properly was a missing Flash trust file for that user location. Without such a trust file the embedded flash player refuses to "play" your custom panel.
Please see section "Trust files for custom panels" in the XMPFileInfo SDK Programmer's Guide on page 50 for all details on how to create such trust files.
After many wasted hours I have now the simple panels running.
Cheers,
H.Sup

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

Custom File Info Panel: Bridge Locks Up (trials, tribulations, woes)

o/ all!
So I've spent the better part of this morning trying (for what I think is the fifth time this year) to get a custom file info panel installed properly. I've managed to successfully install a generic panel with most of the properties that I'd like in the panel proper, however, I'm having no end of trouble publishing and installing the panels and having them display properly in Bridge CC (64-bit).
I've followed the instructions provided in the Programmer's Guide to the letter (yes, including the trust files), and I'm still having issues.
-- System Information --
OS: Windows 7 64-bit
Flash Builder 4.7 (64-bit)
Adobe Bridge CC (64-bit)
Right now, all I'm trying to do is:
Create the flash builder project for an XMP File Info Panel
Publish the file info panel
Confirm the file info panel was installed correctly in Adobe Bridge CC.
The process:
1. I create the new project in Flash Builder (I've attempted using the 4.6.0 and 3.6A flex SDKs).
Now, at this point, I'm simply attempting to confirm that everything is hunky-dory with the installation process before I start converting my generic panel into a flash/flex panel; so I'm not modifying any of the files that the wizard created.
2. Right-click the root project folder in the leftmost pane in Flash Builder, select XMP>Publish.
3. Locate the published panel's output directory that Flash Builder published to
4. Copy/paste the published panel's root directory to the following directories:
C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels\
C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\custom\
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\4.0\panels\
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\4.0\custom\
I put the panel definition in all of these folders as per various 'fixes' to what I think my issue is that I've discovered while google-troubleshooting.
5. Create a trust file in FlashPlayerTrust folder with the name testPanel36A.cfg (contents listed below):
C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels\testPanel36a\bin\testPanel36a.swf
C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\custom\testPanel36a\bin\testPanel36a.swf
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\4.0\panels\testPanel36a\bin\testPanel36a.swf
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\4.0\custom\testPanel36a\bin\testPanel36a.swf
As far as I know, I can put multiple paths in these .cfg files, but I'm not-at-all confident that this is, in fact, the case.
After all this, I fire up bridge, right click an image file, and select FileInfo. The dialog displays fine, and the panel tab appears on the right. Clicking on the panel reveals nothing but a gray area with no content, and Bridge locks up entirely. I can't cancel out of the dialog, and end up having to end the process from Task Manager.
My gut tells me that I'm doing something wrong with the trust files, as this seems like the issue that most closely resembles what I'm encountering. Secondarily, It may be the flex SDKs -- I only have the 4.6.0 and the 3.6A SDKs, and the link in the Flash Builder dialog takes me to the sourceforge page for Adobe, and from there, I cannot locate any additional older SDKs to try this with (I've seen posts around saying that people got their panels to work with 3.0, or 3.5).
Anyone have ANY insight on this? Seriously at my wits end -- I've tried everything but nothing seems to work . Many thanks,
.e

Hi The_Mumm,
     You need to correct content fo the .cfg file (hope your .cfg file is at correct directory i.e. C:\Documents and Settings\<user name>\AppData\Roaming\Macromedia\Flash Player\#Security\FlashPlayerTrust). Yes, I agree that you have followed the documentation and put the path upto .swf file.
    Could you please modify the content of the trust file, with the below content (you path have been modified)
C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels\testPanel36a\bin\
C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\custom\testPanel36a\bin\
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\4.0\panels\testPanel36a\bin\
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\4.0\custom\testPanel36a\bin\
Hope everything will work now. If it doesn't work, please put only one path in trust file e.g. "C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels" and put the publish panel in this folder.
One more precaution, don't copy, if required move the custom panel from one place to other.
Please let me know if you still faces any issue. Enjoy you new year.
For your reference, I am following the following steps and everything is working fine
1. Open the Fb7,
2. file->new->project
3. in the new project wizards, select "xmp->custom panel wizard"
4. xmp->publish custom panel
5. Open the .cfg file and added the path (C:\Users\<user name>\appdata\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels) where my panel has got published.
6. Ran Bridge CC, panel is there and working fine.
One more variations I did is, moved custom panel from C:\Users\<user name>\appdata\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels to C:\Program Files\Adobe\Adobe Bridge CC (64 Bit)\Custom File Info Panels\4.0\panels (the location of the custom file info panel inside bridge).
      For you doubts I tried with flex SDK 3.3A and 3.6a both worked fine. As in forum you have written that you don't have any other sdk. If you like please go on the following links for older SDKs "http://sourceforge.net/adobe/flexsdk/wiki/Download%20Flex%203/"
-Sunil

Two Custom File Info Panel Issues

When I add a second custom file info panel that has a different name (panel, .xml, and folder), the panel name that appears is the same as the first. What is causing this?

Hi,
here is how it works:
If you open the properties.xml you will find a zString key for every label:
i.e. label="$$$/Custom/Schema/Label=Custom Properties" (which is the panel name).
Depending on the language of the application it will load the values from the zstring files. If there are no files it will use the value of the properties.xml.
So if you want to change any label it is not enough to change the value in the properties.xml or the folder name. Is you leave the key as it is it will load the value based on the key. So you have to change the key and value in both the properties.xml and the Generic_en_US.dat and all other language files you would like to support.
example:
properties.xml:
label="$$$/Custom/Schema/Label2=Custom Properties 2"
*.dat:
"$$$/Custom/Panel/Label2=Generic Panel 2"
Or you remove the Keys completly from the properties.xml, but then multilanguage is not supported.
Hope this helps,
Samy
P.S. You can test different languages by changing for example Bridge to a different language (in the settings) and restart it. If you then open FileInfo it will load the correct *.dat files based on the language. You can add more *.dat files for more languages for you panel if you like.

CS5 Generic File Info Memory Problem

We have been using a very large custom generic panel in CS4 File Info. The MRU file has grown to 2.5 mb, the properties are 1.5 mb -- but they have been working great in CS4. In CS5 they frequently do not work . The panel will either be empty when you open it, although there are xmp values in file, or after entering data, the panel will spin for a while, show empty again, often after trying to process the MRU's.
Are panels in CS5 products OK to be used for this large of a metadata set of attributes and values?
Using latest Macs, 4GB of ram, happens in all CS5 apps.
Thanks for your help.
Todd

Todd,
I understand your requirement. Controlled vocabularies can be a
critical component of a metadata strategy.
I know people that use a semicolon delimited file to pre-load the CS3
File Info MRU of a bag or seq field via a single copy and paste. Its
limit appears to be fifteen entries. Like you they are simulating a
controlled vocabulary for a list.
Pound Hill's MetaGrove Plug-in provides controlled vocabularies for
lists (bag and seq). These are displayed as a table of one column,
popup at the top, open or closed choice.
The largest single (internal) MetaGrove vocabulary I have implemented
has 4004 entries in one language, 1 mb in size. PHS's format is more
verbose than Adobe's MRU or File Info panel formats. It takes 20
seconds to initialize.
MetaGrove vocabularies can optionally be external text files, with tab
delimited value/label pairs, local or on the network. These are single
language, by definition. This is intended for an enterprise where the
external vocabulary file is typically updated monthly or quarterly.
The plug-in will automatically cache the update within a week
(default). The vocabulary can be maintained using a spreadsheet or
output from an application like yours.
Regarding your test with repeated red, green blue, for 100,000 entries:
In File Info v0 and v1 (CS through CS3), "All names and keyphrases
(values) in the list must be unique." This constraint is not mentioned
in the v2/3 File Info document. Does repeated red, green blue work
with 9 entries or so?
Most CS3 applications have odd behaviors with more than 99 entries in
a File Info popup. This appears to be fixed in Acrobat 10. I haven't
attempted more than 200 entries in a CS3 panel popup.
I suspect that building a in-memory copy of a vocabulary from a panel
file, or from the MRU file, is a serial process and does not scale
linearly. Each incremental entry takes longer to add to the in-memory
representation because the entire in-memory copy must be scanned each
time. The design goals of tens to entries probably did not warrant
using database techniques for the internal representation. The
performance in CS4 is your benchmark.
CS4 and 5 File Info appears to be doing some central caching.
Sometimes, I need to remove the panel entirely, Exit all File Info
applications, run an application and its File Info, Exit and then add
the panel in again to get changes to take. You probably need to get
everyone-out-of-the-pool before you touch the MRU file.
The CS3 copy and paste technique mentioned above might be an
alternative to let FIle Info manage the MRU. However, in your case, it
will test the implementation limits of the menu field payload capacity.
Carl crambert at poundhill dot com

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.

Custom File Info panels from PS into LR

I have a large number of Custom File Info panels created for use within Photoshop that are imperative to our workflow of different departments. These Metadata strings are later read by Extensis Portfolio as our DAM tool of choice.
I don't see to be able to find where to change this other than making minor tweaks to existing Metadata presets. Any clues hmmm? Ta

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

Custom File Info Panel Multi select options

Hi,
I have created a custom file info panel and working on simple properties.
it does not have options for provisioning a multi select list box. Say for example, I want to select multiple values from the dropdown values.
How should i do it? Any help is much appreciated.
Thanks,
Sriram

Hi,
Following is my sample property file. I want to make the property "Line Year" to be multiselect.
<xmp_definitions>
</xmp_schema prefix='x' namespace='x....'
                  <xmp_property name='LineYear' category='external' label='Line Year' type='closedchoice' element_type='text'>
                                <xmp_choice raw_value="2007" label="2007"/>
                                <xmp_choice raw_value="2008" label="2008"/>
                                <xmp_choice raw_value="2009" label="2009"/>
                </xmp_property>
    </xmp_schema>
</xmp_definitions>

Custom File Info Panels Doc Available !!

Documentation for creating your own custom file info panels is available at:
http://www.adobe.com/products/xmp/custompanel.html
I'm interested in hearing your feedback!
The custom File Info panel for XMP metadata allows you to define, create, and manage custom metadata properties using standard Adobe applications. You can do this by creating a Custom Panel Description file, and placing it in a common location referenced by Adobe applications that support this feature. You can also supply localization dictionary files to localize the contents of your Custom Panel Description files. The resulting custom dialog panel is seen by users when they select the File Info menu option.
The File Info panel allows you to support paths to metadata properties which are not defined in default or other standard XMP schemas, but are needed for your application, company, or industry. By using XMP for that metadata, you take advantage of the potential of XMP for interchange and participation in asset management systems, while providing the ability to use standard Adobe applications to manage it.

Mark,
The PDF/A extension schema provides a big step to the self-sufficient functionality that you are asking about. It permits the XMP schema description information of custom XMP schemas to be embedded into the XMP as payload so that the file can be opened in years to come and the target metadata acurately interperted. Currently, PDF tools are active candidate to make use of this facility. However, there is nothing preventing future use with other file formats, and other tools (via plug-ins?).
It does not include vocabulary, static text, and panel presentation layout information.
http://www.pdfa.org/doku.php
It defines a "known" subset of standard XMP properties from the 2001 XMP Spec. Everything else is "custom".
You could craft a custom File Info "template" with the PDF/A extension for your custom XMP fields. Then import the template into each file.
The PDF/A extension schema itself is implemented with multi-dimensional XMP arrays. MetaGrove Plug-in dialog screen shots can be viewed on http://www.poundhillsoftware.net/Acrobat.htm
Regards,
Carl Rambert

Custom file info panel to xmp

I have a custom file info panel I use on an old version of photoshop, have 20gigs of pictures with data. with cs5 and 6 haven't figure how to convert except manually which would be VERY painful. Is there a conversion for file info panels to xmp? can I run creative cloud and still install an older version of photoshop?

I've found answer:
group(placement: place_row, spacing: gSpace, horizontal: align_fill, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Widgets/static_text=Naglowek:',font: font_small_bold_right, vertical: align_top);
edit_text(horizontal: align_fill, height: 54, xmp_namespace: photoshop, xmp_path: 'Headline', container_type: alt_struct, v_scroller: true);

MetaData in file not shown in Illustrator cs6 file info panel

I have a command line application that puts meta-data into files. It was created using the 5.1.2 xmp toolkit. The metadata is in the file. I can see it if I just use TextEdit to look at the file. I can also see the custom metadata in the Illustrator CS5 File Info Panel AND the Photoshop CS6 File Info Panel. The information doesn't show up in the Illustrator CS6 file info panel. Any clue why?

The files I am testing with are .jpg's. They ultimately need to be opened with Illustrator which is why I posted. I only tested with Photoshop to see what would happen and was pretty surprised to see the data there. Like I said, it works in CS5 Illustrator, CS6 Photoshop, but the data just doesn't show up in the CS6 Illustrator (in the advanced nor the raw tab), and when I view the .jpg with textedit the data is difinitely there. Pretty weird.

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

CreatorContactInfo struct in Generic File Info Panels

Similar Messages

Maybe you are looking for