About geting Info panel

hey, guy, i'v got a very strange problem with my snow leopard.
today i try to change my settings of the file association with right click get info taste.
but it turns out that nothing is displayed????
no file name, no file typ, no file size , no nothing
i've never confronted such a problem with my earlier Mac version...
hope some one knows how...

some one can help?

Similar Messages

My users folder has 140GB used on it, but I cannot find where it is getting that calculation. I went through all of my folders and opened them all in an info panel, and they all come out to about 30GBs. Where is the rest of the data? -Using Mountain Lion

My users folder has 140GB used on it, but I cannot find where it is getting that calculation. I went through all of my folders and opened them all in an info panel, and they all come out to about 30GBs. Where is the rest of the data? -Using Mountain Lion

First, empty the Trash if you haven't already done so.
Use a tool such as OmniDiskSweeper (ODS) to explore your volume and find out what's taking up the space. You can delete files with it, but don't do that unless you're sure that you know what you're deleting and that all data is safely backed up. That means you have multiple backups, not just one.
Proceed further only if the problem hasn't been solved.
ODS can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.
Back up all data now.
Install ODS in the Applications folder as usual.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Triple-click the line of text below to select it, then drag or copy — do not type — into the Terminal window:
sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper
Press return. You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up.
I don't recommend that you make a habit of doing this. Don't delete anything while running ODS as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means.
When you're done with ODS, quit it and also quit Terminal.

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

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.

Custom info panel from CS5 not showing in CS6

Do I need to move the custom panel entry from
"\AppData\Roaming\Adobe\XMP\Custom File Info Panels\3.0\custom" to a new location?
Also on a related front, at NAB I was asking about adding dropdown boxes to entries so we could standardize on a few set entries to make searching easier. I couldn't get an answer there - any ideas on the forums?

You can design custom metadata panels - I have one for Client's name, project name, element type, Approved, etc. Whenever we generate files for a client we try to get the data filled in. It makes searching for clips from previous projects much quicker. The custom panel isn't showing in Bridge - i usually appears at the bottom of the metadata list after "File Properties" IPTC Core" etc.
The dropdown box question - Some of the data we want to be picked from a list to make searching more acurate. For instance - "Element Type" would either be "Interview", "Background", "Logo", etc. We just wnat everyone labeling things with the same terms. (See "Property Release Status" under the IPTC Extension)

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

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

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

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

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

Copy-Paste from info Panel

Info Panel is useful when you wanna count words, spaces, etc.
But today i wanted to send my client a small note about "we calibrated the frame for a thousand signs and 160 words, there's a few more"
It would have been very practical to get an easy copy paste of the values in the panel, and their labels.
Of course, i proposed an official Feature Request there.

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

Copying From Info Panel

Hi,
I created a Powerpoint for a class project at school. I downloaded about 100 random images from the web and saw that the source/url was in the cmd/I info panel. I wasn't sure which ones I'd use so I waited till I was done to copy the source/web site url from the info panel.
I'm just finishing and now find out I can't copy and past from this info panel! To copy by hand will take me way too long!
Is there a way to quickly get this info out of the file?
Thanks,
W

The mdls attribute name you are looking for is kMDItemWhereFroms. I wrote an AppleScript a while back to put up a dialog of the download URL, with the option to copy it to the clipboard:
<pre style="
font-family: Monaco, 'Courier New', Courier, monospace;
font-size: 10px;
font-weight: normal;
margin: 0px;
padding: 5px;
border: 1px solid #000000;
width: 720px; height: 340px;
color: #000000;
background-color: #FFD891;
overflow: auto;"
title="this text can be pasted into the Script Editor">
property getSpecific : true -- show the specific download URL?
set aFile to quoted form of POSIX path of (choose file)
set theURL to (do shell script "mdls -name kMDItemWhereFroms -raw " & aFile)
if theURL is "(null)" then -- no attribute
set theURL to "(URL info not found)"
set theMessage to ""
else
if getSpecific then -- get the first item (the download URL)
set theMessage to "download "
set theURL to paragraph 2 of theURL
set here to offset of "\"" in theURL
set theURL to text (here + 1) thru -3 of theURL
else -- get the last item (the page/site URL)
set theMessage to "page/site "
set theURL to paragraph -2 of theURL
set here to offset of "\"" in theURL
set theURL to text (here + 1) thru -2 of theURL
end if
end if
if theURL is "(URL info not found)" then
set theButtons to {"OK"}
else
set theButtons to {"Copy to clipboard", "OK"}
end if
display alert "kMDItemWhereFroms info" message "The " & theMessage & "URL for " & aFile & " is: " & return & return & theURL buttons theButtons
if button returned of the result is not "OK" then set the clipboard to theURL
</pre>

Info panel not displaying eps info

I cannot get the ppi information to display in the info panel. Is this some new spangly feature of InDesign, or a bug?

Clarification of what is claimed, and why we are perpetuating this conversation.
John, that's jut nit picking at what I said.
Sorry, I tried to make it clear, it's a nit but I think it is a very important one. Please feel free to disagree. But when we're talking about whether a file format that's important to people is doing to be supported, or is going to go away, it's very important to be clear about the public statements that have been made. Similarly, I do get bothered when EPS is described as "archaic" or "obsolete." It fills needs that are not filled by PDF or AI files, and while it is certainly older than PDF, it is of peer age to TIFF and JPEG. It is certainly less frequently used, and in many applications there are better choices (like PDF). But not in all.
The issue of "double standards."
John, nor do you really say why you think EPS is preferred. Double standards here.
I'm sorry, but please reread my post. I do not say that "EPS is preferred." I talk about several things it can and cannot do, and explain why, for instance, it and PDF show some of the same deficiencies in InDesign's Info panel. I tell you some reasons that I like it. But I do not in fact believe that it is a "better" format most of the time, and make no such claim. It is unfair to ask me to substantiate claims I did not make. I tried to be quite careful on this one.
Yes, generally PDFs are better. But.
You have produced quite a link storm there, but I'm afraid they don't do a terribly clear job of explaining why these other formats are better than EPS, and for exactly which applications. If your point is to say that in general, one should not prefer EPS over PDF, then that's fine. I think it is a true statement.
What bothers me about the statements in this thread (and this forum in general frequently echoed on this forum) is that it is wrong to use EPS; that EPS is obsolete; that Adobe InDesign will drop support for EPS; that EPS is archaic. That's simply not the case. It might be the wrong format for bigdrunk (it probably is; but we don't really know what he is doing). It is not the wrong format for everyone.
Addressing the external links/references
But we should be clear on what we're talking about. Your initial link, to Real World Illustrator's What's in a file? does a great job of describing the output formats from Illustrator. It doesn't really make a recommendation, other than to note that PDF supports some features that EPS does not. Transparency being the key point, and we've mentioned that only four times before your post. I'm not sure if that's the "plain as day" or not.
Adobe's David Evans' psvspdf post similarly discusses both formats, and suggests that EPS is a replacement for PDF -- which it is. But that only gets you so far. It doesn't address the fact that PDF files can have downsides compared to EPS files (many articulated above in the thread), but really just says that PDF can do most of the things that EPS can do. That's certainly true. After all, you can put EPS files inside PDF files! But that doesn't tell you that you're better off writing to a PDF file in any particular case. To pick a few examples from above, some apps can only read EPS files and can't read PDF files. And others can generate EPS files much more easily than they can generate PDF files.
I am rather apalled that you would cite eHow. They are rather notorious for giving bad advice that is not vetted by experts. In this case, though, the eHow post merely answers the question, "If an EPS file won't work, what are the alternatives?" It seems to do so correctly, but its not relevant to this discussion.
Craig Kirkwood's Pixel Therapy link is more general advice, for "How should I save my Illustrator work?" And again, none of us here who are speaking up for EPS are saying that it is the preferred file for Illustrator work (though I did point out that Illustrator can produce smaller EPSs than PDFs, which is bizarre).
PDF-in-AI or AI-in-PDF?
(although I disagree about saving as PDF from Illustrator with editing capabilities, best to save as ai with PDF)
Why do you think so? In general, they should be equivalent -- in both cases a PDF file is available to PDF-reading applications, and in both cases (and in Illustrator EPS, by the way), Illustrator private data is preserved for full Illustrator editing capability. I would say that distributing .PDF files is a better choice, because if a non-expert person receives a .ai attachment in their email, they are more likely to be confused about how to view, print or render it than they would be if they receive a .pdf file. That may not sound like the most compelling reason, but I can't think of one that is more compelling.
No flat recommendation of EPS over PDF.
I quite literally CANNOT find one source that recommends EPS over AI or PDF???
I wonder why that is?
To be honest, I think it is because there are very few experts on these file formats. You need to really understand the low-level file format to be qualified to offer an opinion on the merits of the file format by itself. And the merits of the file format aren't really the point most of the time -- what matters is the applications that you use, and how they handle it. Does a given application produce better PDF files or better EPS files. Does another application read EPS files better than it reads PDF files? Are there apps that read or write one but not the other? Is there a savings in file structure, in maintenance, in cost, in aggravation.
Most of the people who write about these things are aware of the ramifications and the practical effects of the choices, but not the low-level details.
Most of the time the low-level details do not matter. But they do indeed matter to some of us, and it is those of us who have spoken up in this thread.
In favor of EPS, but in a limited way.
Why EPS is sometimes better.
Can you explain why you think EPS is better than ai or PDF? Can you point me to any online sources, or books?
As we have enumerated in this thread (and the other recent one, I guess), EPS has the following potential advantages over PDF; they may not be important to you, but they are sometimes important to some of us in some cases:
1. It can be easily authored by humans and tools without requiring complex tools to convert into intermediate formats (e.g. Acrobat Distiller; pstopdf or GNU Ghostscript; expensive libraries to produce PDF output);
2. If appropriately written, it can produce human-readable ASCII output that can be understood by someone familiar with EPS. For programatically generated output, seeing that the code says "Draw a circle at coordinates (1 inch, 1 inch)" can be extremely valuable. In such an EPS file, that might be "1 inch 1 inch drawcircle."
3. Bitmap binary data can be more efficiently JPEG encoded in EPS than in PDF. (I was not aware of this, and do not know it to be the case. But Uwe mentions it.)
4. Gernot's point regarding direct CMYK specifications. I'm honestly not sure what it is, so I won't try to explain it.
5. Some apps output cleaner EPS files than they do PDF files. Apparently Illustrator is one such app. Which is bizarre.
6. Some applications/clients/specifications require EPS, such as the CUMULUS database.
As for AI, well, as we've already said above AI and PDF are essentially equivalent, as both can contain PDF images and Illustrator private data. But EPS is certainly better than Illustrator private data because it is an open, well-documented standard. Anyone with enough time on their hands can interpret an EPS file acording to a public, published spec that's been around for years. There are free and commericial software PostScript renderers, and there are an abundance of PostScript printers. None of those things are true for AI.
The rest.
What's left? I think that's really about it. You've spent quite a bit of time arguing against a position I do not think anyone was adopting.

About geting Info panel

Similar Messages

Maybe you are looking for