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.

Similar Messages

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

File Info panels in Lightroom.

Hello, everybody.
My workflow involves the use of Photoshop, Bridge and more recently I decided to make Lightroom part of it also. As described in Martin Evening's "The Adobe Photoshop Lightroom 2 Book" I am trying to use Bridge as a front end for Lightroom and think that both applications really complement each other well.
Now, to my questions:
1. I am trying to find the File Info panels in Lightroom that can also be accessed in Photoshop and Bridge. I must have missed the obvious but I haven't been able to find it. Could you point me in the right direction ?
2. Where is the keyword catalog for Lightroom located ? What is the proper syntax for this file ? Is there an application I can use that will allow me to create my own keyword catalog that can then be imported into Lightroom ? Last but not least, can Lightroom have more than one catalog installed ? What about Bridge ? Can it also have more than one keyword catalog installed ?
Thanks,
Joe

Those panels are specific to Bridge, Photoshop and other Adobe suite apps. Sadly, they don't exist in LR. Instead, use the Metadata panel.
LR's keywords are stored inside the LR catalogue - there is no "keyword catalog for Lightroom" concept. You can import a list of keywords using the Metadata > Import Keywords command. This list will be a txt file which you can prepare in any text editor or in Excel. To see the format, add a few keywords in Lightroom, and create a txt file using the Metadata > Export Keywords command. Then just edit this file, or copy its format - eg indenting child keywords.
Fr now, if you are asking questions like these, I would recommend sticking to one tool, a single Lightroom catalogue, for entering your metadata. Until you find your feet, using more than one tool will only make work for yourself and will result in inconsistencies. Also, treat yourself to a copy of Peter Krogh's DAM Book (his forum is good for metadata workflow issues).
John

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

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

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

Error when building File Info Panel

I'm trying to rebuild my custom XMP File Info panel so that it will work in CS5, but am getting the following error:
Description     Resource     Path     Location     Type
1046: Type was not found or was not a compile-time constant: XMPComboBox.     DKimageXMP.as     /dkphoto/as     line 223     Flex Problem
The line causing the problem is:
private function updateComboBox(comboBox:XMPComboBox, xmpPath:String): void
     //blah blah blah
Near the top of my actionscript file I have
import com.adobe.xmp.*;
So I don't understand why XMPComboBox is not a valid type?
Dave

Hi Stefan
Thanks for your help, that fixed the problem.
I'm now having trouble with a TextInputMRU - when I give it a dataProvider the panel builds okay, but appears empty when viewing it in Photoshop.
My panel code looks like this:
<?xml version="1.0" encoding="utf-8"?>
<fi:XMPForm
          xmlns:mx="http://www.adobe.com/2006/mxml"
          xmlns:fi="com.adobe.xmp.components.*" width="100%" height="100%"
          label="dkphoto" >
     <mx:Script>
          [Bindable]
          private var CountryList:Array = new Array("Afghanistan",
               "Åland Islands",
               "Albania",
               "Zimbabwe");
     </mx:Script>
     <fi:XMPNamespaces>
          <fi:XMPNamespace prefix="Iptc4xmpExt" value="http://iptc.org/std/Iptc4xmpExt/2008-02-29/" />
     </fi:XMPNamespaces>
     <fi:XMPFormItem label="$$$/xmp/Iptc4xmpExt/CountryName=Country Name" labelTooltip="$$$/xmp/Iptc4xmpExt/CountryName_tooltip=The name of a country of a location. This element is at the second level of a top-down geographical hierarchy." >
          <fi:XMPTextInputMRU id="LocationCreatedCountryName1" xmpPath="Iptc4xmpExt:LocationCreated[1]/Iptc4xmpExt:CountryName" width="300" dataProvider="{CountryList}" />
     </fi:XMPFormItem>
</fi:XMPForm>
Any idea what the problem would be there?
Thanks
Dave

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

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 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);

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.

Is there a date entry widget for XMP custom file info panels?

Looking through the Custom File Info Panels documentation, the samples, and the default info panels presented in Photoshop, I can't find any reference to a date entry widget - the closest I've seen is the date_static_text widget.
Is there any way to present an editable, validating date entry field to our end-users through the File Info panel?
(the info we're wanting to store is a release date so it's user-specified, and not derivable from the file in any way)

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

File Info Panel to hit web service to fill out XMP data

Hi there,
Is there any way to use the File Info panel inside Indesign (for example) to hit a web service based info entered in a few fields which will return data to fill out the rest of the xmp data?
Or would you have to write some sort of plugin to do this?
I know Metagrove already does this, but it's a standalone plugin. We were wondering if anything can integrate directly into the File Info panel.
Thanks,
mark

Do you have a proxy defined in your jdev? This might prevent reading from the address you specified.
If you can access the url in a browser, you can store the WSDL on your local pc and use the local file to create the webServiceDataControl.
Timo

XMP Custom File Info Panels

I've downloaded the new XMP Custom File Info Panels software. I installed the sample xmp panel descripter files in the proper location. Is it possible to view the customized metadata on a computer that doesn't have the descripter files? I hope the descriptor files get imbedded in the image with the customized xmp metadata.
-Mark Thiessen

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 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

XMP File Info Panels in Lightroom?

Similar Messages

Maybe you are looking for