File Info XAP XMP XML

I'm not having any luck trying to figure out how to store some XML data into an AI file using the SDK. I was wondering if anyone had any suggestions on how to accomplish what I am trying to do:<br /><br />My plugin is notified when the file is being saved.<br /><br />At this point, I extract some information, and want it to be stored with the file when it's saved, so it can be extracted later.<br /><br />If you open the AI file in a text editor, you will see that there is a readable XML packet (<x:xmpmeta>) near the top of the file.<br /><br />Using AIXMLDocumentSuite and AIXMLNodeSuite I'm able to save some nodes to the file, however, that information does -not- get stored in the human readable <x:xmpmeta> text packet at the top of the file. This is not good enough for my purposes.<br /><br />I tried using:<br /><br />AIDocumentSuite::GetDocumentXAP<br />Which seems to return exactly the information I'm referring to in the file.. Make modifications, then:<br />AIDocumentSuite::SetDocumentXAP<br /><br />My changes are not saved into the file. I suspect that maybe I write the data with Set, and then immediately afterward, as Illustrator finishes the saving process, it's overwritten.<br /><br />I need to insert my data into the AI structure somehow, so that it is written when the file is saved...<br /><br />This information is available through illustrator if you choose the menu options "File -> File Info" then click on "Advanced" in the list on the left.<br /><br />Does anyone know how I can properly manipulate this "File Info" data? and store custom information? There are no XML related examples in the Illustrator SDK, and very little documentation on how it is supposed to be used.<br /><br />Thanks in advance.

Ok, I've made some progress on this issue, that being I finally forced my way to getting my data saved into the file.<br /><br />I talked about this a bit in another thread, but I'll reiterate here, hoping that someone else searching for solutions to this problem can know where to start.<br /><br />I did exactly as I suggested above:<br /><br />AIDocumentSuite::GetDocumentXAP<br /><br />Make modifications, then:<br /><br />AIDocumentSuite::SetDocumentXAP <br /><br />It was not easy to avoid the phenomenon I described above however.<br /><br />The modifications you make must comply with some undocumented rules; because if you pass some text in that does not pass the rule, all of your changes are discarded; replaced by whatever was there originally.<br /><br />There is no error reported. There should be an error when calling SetDocumentXAP if you pass in 'invalid' data, or at the very least, the valid data structure (schema) should be defined in the documentation (it's not).<br /><br />What I did was put all of my additions inside a <rdf:Description> tag and put it right after the other ones already in there.<br /><br />Sample:<br /><br />     <rdf:Description rdf:about=""<br />            xmlns:my_tagname="http://www.mycompany.com/1.0/"><br />         <my_tagname:my_metadata rdf:parseType="Resource"><br />            <my_tagname:my_parameter>value</my_tagname:my_parameter><br />            <my_tagname:my_data_1><br />               <rdf:Bag><br />                 <rdf:lirdf:parseType="Resource">                     <br /><my_tagname:my_parameter_2>Value</my_tagname:my_parameter_2><br />                     <my_tagname:my_parameter_3>Value</my_tagname:my_parameter_3><br />                     <my_tagname:my_parameter_4><br />                        <rdf:Seq>                        <br />                        <rdf:li>some data</rdf:li><br />                        <rdf:li>some data</rdf:li><br />                        </rdf:Seq><br />                     </my_tagname:my_parameter_4><br />                  </rdf:li><br />               </rdf:Bag><br />            </my_tagname:my_data_1><br />         </my_tagname:my_metadata><br />      </rdf:Description><br /><br />I hope this helps someone else. (Excuse the bad formatting in this forum post)

Similar Messages

  • How do I save File Info in an MP3 file using audition 3.0

    Dear Anyone,
    I am worling on a project that is time sensitive. I have been helped on the markers/mp3 scenario.
    Thanks to ryanclark and jay moore.
    So that is done. But I have yet another issue with the MP3 file. Here it is:
    I filled in all the File Info, saved the MP3 file in audition 3.0. Then I burned the CD. When I opened
    the file up from the CD in Windows Media, there was no file information at all in there.
    So, I went back to the drawing board and filled out the File Info and XMP file, still the same thing.
    I can't seem to get any help on the help area of the Audition so here I am.
    Does anyone have the answer to this? I sure would appreciate it.
    thanks.

    See the other thread - the answer, such as it is, is in there now.

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

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

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

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

  • Photoshop changes file info xmp metadata - unknown to public domain?

    Curious if anyone has feedback or solution for the following:
    My PSD file's metadata enters photoshop with "unknown" as the copyright status, and then after I save it in a new format or with a new name
    , I notice that in Bridge the copyright status shows up incorrectly as "public domain." This is incorrent and should not change on
    its own. I've been using Photoshop with Bridge for many years, and have never seen this...

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

  • 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

  • XMP Custom File Info panels vs. Custom Metadata

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

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

  • XMP File Info SDK for CS4

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

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

  • A multi-file version of File Info/Export (to xmp)

    I have 8500 video files that I have tagged with multiple keywords.  These are all AVI so the file cannot store metadata.
    I want to preserve a backup of the metadata in xmp sidecars for safety (backup, future proofing, sharing).
    File Info/Export seems to do the trick but only works on single files (if you multi-select, export is disabled).
    Has anyone written a script to exactly mimic this Export feature but for multiple files??  I have both CS5.5 and CS6.
    I have seen some that export custom schema but I want something that is standardized.  I like how the export function writes both hierarchical and flat keyword trees for example.
    Thanks!
    Mark.

    XMP sidecar files are not very useful as they contain all the metadata, most of which is not worth keeping.
    A much better method is to extract the relevant metadata to a CSV file.
    These CSV files can be used to put metadata back into files.
    As an example...
    To extract basic metadata information...
    http://www.scriptsrus.talktalk.net/Extract%20Metadata.htm
    To put metadata back into files...
    http://www.scriptsrus.talktalk.net/DIYmetadata.htm

  • Can't see my custom xmp panel in file info in PS CC 2014.

    Has the "Custom File Info Panels" location moved with CC 2014?  For previous CC versions, location was (mac):
    HD/users/username/Library/Application Support/Adobe/XMP/Custom File Info Panels/
    Anyone know?  Thanks!

    Hi,
    The extensibility mechanism for the FileInfo dialog has changed for Photoshop CC 2014.
    Please have a look at this thread we had posted last week: Update for XMP FileInfo SDK available
    Kind regards
    Jörg

  • 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

  • Print  XMP File Info?

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

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

Maybe you are looking for