Custom XMP document metadata panel

Hi
Is it possible to create our own form for metadata entry using our own XMP schema? We have specific business processes for different types of document management and a specific schema/entry form for each would be helpful.
Ideally a common template and fields with similar input panels for both Adobe XMP and MS OpenXML formats would be the idea.
Is it possible and are there any online reference materials you could direct me to?
e.g. One tab for Description, one for advanced and one or more for our processes:
Thanks and take care,
Shayne

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

Similar Messages

How to install custom XMP Get Info Panels in Adobe Bridge CC

Adobe changed their way they store the custom XMP Get Info Panels in Adobe Bridge CC. Check out this blog to see how you can install the XMP Get Info Panels that you used in Adobe Bridge CS6 in Adobe Bridge CC:
http://www.databasepublish.com/blog/installing-custom-metadata-panels-and-get-info-panels- adobe-bridge-cc

Check your Bridge preferences. It seems that you have the "Don't process images larger than…" option set to a lower amount than some of your files.
So, don't blame it on Bridge, but on the user who neglects that setting.

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

Central (web based?) location for custom XMP panels

We maintain 3 custom XMP panels for a global network of photographers & DAM's. We'd like to be able to update our custom XMP panels (say add new drop down choices,) and have those immediately reflected globally. If Bridge checked a central resource (say a website) for what should be the most up to date version of an XMP panel, we would have an easier time managing the process.

Yes, the ability to subscribe to centrally-published custom XMP file info panels from CS apps would be extremely helpful, and since the CS4 panels are just XML files, a simple mechanism such as a subscription to an RSS feed would probably do the trick.

Custom XMP panels don't show in Bridge CS4's Metadata palette

I've got a CS4 custom XMP panel working (using the "Generic" panel in the SDK) but I can't get it to display in the metadata palette of Bridge CS4 (the thing normally bottom right in the default Bridge "essentials" view).
In the old CS3 format, you could do this by adding an "fbname" attribute to fields of the custom panel. How do we now do this in the new SDK?
The Bridge metadata palette is mentioned on page 25 of the SDK programmer's guide, but the example given is merely of Dublin Core keywords (i.e. dc:subject) so shows in the Bridge metadata palette by default already.

Following on from this question, is it possible to build up a Metadata panel group of fields drawn from different namespaces? (by group I mean something like the IPTC Core label and arrow which expands into the IPTC fields).
One would have a heading such as "My data", which when expanded shows x fields from one namespace #1 and y fields from namespace #2. I've tried to do this by leaving the namespace blank and hardcoding it and the prefix into the properties' name argument - eg http://ns.adobe.com/photoshop/1.0/photoshop:Urgency
Hope this isn't a hijack!
John

Using SDK to create custom XMP panel in Bridge CS4

Using the SDK materials how exactly does one go about creating their own custom XMP panel for Bridge CS4?
I feel like I'm getting close- I was able to copy the BasicControlSamplePanel folder from SDK to my local C drive @
C:\Documents and Settings\tony\Application Data\Adobe\XMP\Custom File Info Panels\2.0\panels
I figure once that file is in the right place I can simply modify it to get custom fields
Now when I did this I noticed in Bridge when rightclicked on an image and clicked file info- the BasicControlSamplePanel tab was visible but upon clicking on BasicControlSamplePanel tab there was nothing in this dialogue box. Tried restarting computer- and still nothing- seems like it is the correct folder what do I need to do to get the properties to show up
Help please
Thanks
Tony

Hi Tony,
please refer to the section "Creating custom XMP properties using XML" in the XMP FILEINFO SDK PROGRAMMER’S GUIDE for information how to create custom panels for the metadata panels in applications like Bridge or Premiere.
Regards
Jörg
Adobe XMP

Creating custom Metadata panels in Bridge CS3

I want to create a custom panel that allows me to enter 14+ pieces of information about an image that are not contained within the existing metadata panels.
I can create a custonm panel in photoshop that is seen under 'File info' but I cannot see this information against a file in the metadata in Bridge.
In the Bridge metadata panels you have individual panels such as GPS, IPTC Core, History, etc. Can I create my own custom panel to add to this list?
If so how is it done? Where are the custom panel files stored?
Many thanks

Hi Bob,
It seems that almost every day there is a new secret to explore on this forum... :-)
According to the description in the link you had only a small typo (XML instead of XMP)
here is a copy of the file locations text from the PDF:
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
regards

CS5 - Live Caption with Custom XMP Metadata?

(I USE CS5 on WINDOWS 7)
I currently have a custom panel (witch custom namespace) up and running, and have many of my photos correctly tagged.
For this example, I opened a new Indesign document, placed a previously tagged JPEG
Then I right-click the image from the Links panel and select "XMP File Info..."
I see the custom XMP namespace tab, along with all of the data I previously entered (so I know the image is correctly tagged)
BUT, when I go to Caption Setup, I only see legacy IPTC options from the metadata dropdown
Am I missing something here?

I'd be interested to know the same thing. I have metadata stored in a custom XMP namespace, populated through a custom File Info panel. But I don't see if it's possible to edit the 'Metadata' list in the Live Captions Setup to access these or if it's limited to the default set that I can see when I access the feature?

Exporting/Sharing Custom XMP metadata schema not possible?

I've written a Python script which automatically encodes Quicktime files which I've mastered out of Premiere Pro CC with embedded custom XMP metadata (created using "New Schema" in the Metadata Display panel). I'm using the embedded custom metadata to drive the Python script (e.g. "Spot Title", "Client Name", fields etc etc), which encodes the source QT file to several different formats, based on the delivery specifications of various local TV broadcasters which the encoded files will go to.
Everything about the XMP metadata entry/writing/parsing is fantastic. My only hitch is in the exporting/sharing of the custom metadata schema which I created for this purpose. I would like to roll the schema out to the other editors in our facility, so that they can also enter the XMP metadata on their own systems when they export out master timelines from Premiere.
But unless I'm missing something, I can't figure out a way to "share" or export my custom schema for use on another system. Is this not possible in Premiere Pro CC?

There's no feature for exporting and importing custom schemas, but it's entirely doable. Here are the path to the custom schemas
MAC: Macintosh HD ▸ Users ▸ <username> ▸ Library ▸ Application Support ▸ Adobe ▸ XMP ▸ Custom File Info Panels ▸ 4.0 ▸ custom
WIN: C:\Users\AppData\Roaming\Adobe\XMP\custom file info panels\4.0\panels [I can't vouch for this path as I'm on Mac at the moment and it's been ages since I poked around for custom schemas, but this should at least be the right neighborhood.]
You might also be interested in sharing your custom metadata display profiles. They in Documents ▸ Adobe ▸ Premiere Pro ▸ 8.0 ▸ Profile-mapes ▸ Metadata Preferences.

Bugs: open new doc, custom XMP panel crash

When opening a new document after starting Photoshop, it appears with half a checkboard pattern:
Drawing on it looks like below:
I also had an issue where I closed the doc (without saving) after drawing, then opened a new doc. The previous drawing then appeared partially twice (large, and a small version in top left corner) in the new doc, this only happened once though.
I added a custom XMP panel that works fine with CS5 to $user-dir\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels
On selecting the custom panel, in the File Info window, the panel window / CS6 crashes. (The grey window in the sshot below is an imprint of the irfanview settings I used to take these screenshots, this imprinting behaviour (not sure if it has a proper name) is reasonably common with crashed programs).
I am using the 64 bit version on Windows 7 business 64. 8GB RAM, Sys info from PS CS6 below:
Adobe Photoshop Version: 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:15, Stepping:6 with MMX, SSE Integer, SSE FP, SSE2, SSE3
Physical processor count: 2
Processor speed: 2666 MHz
Built-in memory: 8191 MB
Free memory: 4745 MB
Memory available to Photoshop: 7256 MB
Memory used by Photoshop: 60 %
Image tile size: 128K
Image cache levels: 4
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: NVIDIA Corporation
Video Card Renderer: GeForce GT 240/PCIe/SSE2
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 960, right: 1280
Video Card Number: 1
Video Card: NVIDIA GeForce GT 240
OpenCL Unavailable
Driver Version: 8.17.12.9610
Driver Date: 20120229000000.000000-000
Video Card Driver: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Video Mode: 1280 x 960 x 4294967296 colors
Video Card Caption: NVIDIA GeForce GT 240
Video Card Memory: 512 MB
Video Rect Texture Size: 8192
Serial number: Tryout Version
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Temporary file path: C:\Users\Rusty\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
Startup, 136.7G, 48.9G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Additional Plug-ins folder: not set
Installed components:
   A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112
   ACE.dll   ACE 2012/01/18-15:07:40   66.492997   66.492997
   adbeape.dll   Adobe APE 2012/01/25-10:04:55   66.1025012   66.1025012
   AdobeLinguistic.dll   Adobe Linguisitc Library   6.0.0
   AdobeOwl.dll   Adobe Owl 2012/02/09-16:00:02   4.0.93   66.496052
   AdobePDFL.dll   PDFL 2011/12/12-16:12:37   66.419471   66.419471
   AdobePIP.dll   Adobe Product Improvement Program   6.0.0.1642
   AdobeXMP.dll   Adobe XMP Core 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPFiles.dll   Adobe XMP Files 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPScript.dll   Adobe XMP Script 2012/02/06-14:56:27   66.145661   66.145661
   adobe_caps.dll   Adobe CAPS   5,0,10,0
   AGM.dll   AGM 2012/01/18-15:07:40   66.492997   66.492997
   ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56
   aif_core.dll   AIF   3.0   62.490293
   aif_ocl.dll   AIF   3.0   62.490293
   aif_ogl.dll   AIF   3.0   62.490293
   amtlib.dll   AMTLib (64 Bit)   6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00)   1.000000
   ARE.dll   ARE 2012/01/18-15:07:40   66.492997   66.492997
   AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
   AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
   Bib.dll   BIB 2012/01/18-15:07:40   66.492997   66.492997
   BIBUtils.dll   BIBUtils 2012/01/18-15:07:40   66.492997   66.492997
   boost_date_time.dll   DVA Product   6.0.0
   boost_signals.dll   DVA Product   6.0.0
   boost_system.dll   DVA Product   6.0.0
   boost_threads.dll   DVA Product   6.0.0
   cg.dll   NVIDIA Cg Runtime   3.0.00007
   cgGL.dll   NVIDIA Cg Runtime   3.0.00007
   CIT.dll   Adobe CIT   2.0.5.19287   2.0.5.19287
   CoolType.dll   CoolType 2012/01/18-15:07:40   66.492997   66.492997
   data_flow.dll   AIF   3.0   62.490293
   dvaaudiodevice.dll   DVA Product   6.0.0
   dvacore.dll   DVA Product   6.0.0
   dvamarshal.dll   DVA Product   6.0.0
   dvamediatypes.dll   DVA Product   6.0.0
   dvaplayer.dll   DVA Product   6.0.0
   dvatransport.dll   DVA Product   6.0.0
   dvaunittesting.dll   DVA Product   6.0.0
   dynamiclink.dll   DVA Product   6.0.0
   ExtendScript.dll   ExtendScript 2011/12/14-15:08:46   66.490082   66.490082
   FileInfo.dll   Adobe XMP FileInfo 2012/01/17-15:11:19   66.145433   66.145433
   filter_graph.dll   AIF   3.0   62.490293
   hydra_filters.dll   AIF   3.0   62.490293
   icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   image_compiler.dll   AIF   3.0   62.490293
   image_flow.dll   AIF   3.0   62.490293
   image_runtime.dll   AIF   3.0   62.490293
   JP2KLib.dll   JP2KLib 2011/12/12-16:12:37   66.236923   66.236923
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   10.0
   LogSession.dll   LogSession   2.1.2.1640
   mediacoreif.dll   DVA Product   6.0.0
   MPS.dll   MPS 2012/02/03-10:33:13   66.495174   66.495174
   msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CS6   CS6
   Plugin.dll   Adobe Photoshop CS6   CS6
   PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)   3.0.0.383
   PSArt.dll   Adobe Photoshop CS6   CS6
   PSViews.dll   Adobe Photoshop CS6   CS6
   SCCore.dll   ScCore 2011/12/14-15:08:46   66.490082   66.490082
   ScriptUIFlex.dll   ScriptUIFlex 2011/12/14-15:08:46   66.490082   66.490082
   tbb.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   TfFontMgr.dll   FontMgr   9.3.0.113
   TfKernel.dll   Kernel   9.3.0.113
   TFKGEOM.dll   Kernel Geom   9.3.0.113
   TFUGEOM.dll   Adobe, UGeom©   9.3.0.113
   updaternotifications.dll   Adobe Updater Notifications Library   6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   6.0.0.24
   WRServices.dll   WRServices Friday January 27 2012 13:22:12   Build 0.17112   0.17112
   wu3d.dll   U3D Writer   9.3.0.113
Required plug-ins:
   3D Studio 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Accented Edges 13.0
   Adaptive Wide Angle 13.0
   ADM 3.11x01
   Angled Strokes 13.0
   Average 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Bas Relief 13.0
   BMP 13.0
   Camera Raw 7.0
   Chalk & Charcoal 13.0
   Charcoal 13.0
   Chrome 13.0
   Cineon 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Collada 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Color Halftone 13.0
   Colored Pencil 13.0
   CompuServe GIF 13.0
   Conté Crayon 13.0
   Craquelure 13.0
   Crop and Straighten Photos 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Crop and Straighten Photos Filter 13.0
   Crosshatch 13.0
   Crystallize 13.0
   Cutout 13.0
   Dark Strokes 13.0
   De-Interlace 13.0
   Dicom 13.0
   Difference Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Diffuse Glow 13.0
   Displace 13.0
   Dry Brush 13.0
   Eazel Acquire 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Embed Watermark 4.0
   Entropy 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Extrude 13.0
   FastCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Fibers 13.0
   Film Grain 13.0
   Filter Gallery 13.0
   Flash 3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Fresco 13.0
   Glass 13.0
   Glowing Edges 13.0
   Google Earth 4 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Grain 13.0
   Graphic Pen 13.0
   Halftone Pattern 13.0
   HDRMergeUI 13.0
   IFF Format 13.0
   Ink Outlines 13.0
   JPEG 2000 13.0
   Kurtosis 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Lens Blur 13.0
   Lens Correction 13.0
   Lens Flare 13.0
   Liquify 13.0
   Matlab Operation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Maximum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Mean 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Measurement Core 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Median 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Mezzotint 13.0
   Minimum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   MMXCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Mosaic Tiles 13.0
   Multiprocessor Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Neon Glow 13.0
   Note Paper 13.0
   NTSC Colors 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Ocean Ripple 13.0
   Oil Paint 13.0
   OpenEXR 13.0
   Paint Daubs 13.0
   Palette Knife 13.0
   Patchwork 13.0
   Paths to Illustrator 13.0
   PCX 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Photocopy 13.0
   Photoshop 3D Engine 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Picture Package Filter 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Pinch 13.0
   Pixar 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Plaster 13.0
   Plastic Wrap 13.0
   PNG 13.0
   Pointillize 13.0
   Polar Coordinates 13.0
   Portable Bit Map 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Poster Edges 13.0
   Radial Blur 13.0
   Radiance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Range 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Read Watermark 4.0
   Reticulation 13.0
   Ripple 13.0
   Rough Pastels 13.0
   Save for Web 13.0
   ScriptingSupport 13.0
   Shear 13.0
   Skewness 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Smart Blur 13.0
   Smudge Stick 13.0
   Solarize 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Spatter 13.0
   Spherize 13.0
   Sponge 13.0
   Sprayed Strokes 13.0
   Stained Glass 13.0
   Stamp 13.0
   Standard Deviation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Sumi-e 13.0
   Summation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Targa 13.0
   Texturizer 13.0
   Tiles 13.0
   Torn Edges 13.0
   Twirl 13.0
   U3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Underpainting 13.0
   Vanishing Point 13.0
   Variance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Variations 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Water Paper 13.0
   Watercolor 13.0
   Wave 13.0
   Wavefront|OBJ 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   WIA Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Wind 13.0
   Wireless Bitmap 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   ZigZag 13.0
Optional and third party plug-ins: NONE
Plug-ins that failed to load: NONE
Flash:
   Mini Bridge
   Kuler
Installed TWAIN devices: NONE

According to Nvidia's website, I already have the latest drivers installed (I updated them just a few days ago). I turned off hardware acceleration as you suggested, and that fixed the problem.
You can download the XMP panel that causes the crash from: http://www.iliveinabin.com/image-xmpPanel%20v2.zip That contains the source for the panel and also the compiled panel I'm using, which is in the target folder.

[CS3 JS] Possible to Inspect Custom XMP Metadata With JavaScript?

I am using custom XMP metadata in InCopy and InDesign docs in CS3 to hold custom metadata that can vary wildly. I know the full set of possible items but not what values will be in a particular document.
Short of writing the XMP to a file and then processing that from my script, is there a way to inspect the custom properties from JavaScript. I didn't see a way to do it from the data model.
Thanks,
Eliot

Here is another script to catch MetaData, some more than the basic:
// metaDataOfLinks.jsx
//DESCRIPTION: Catches MetaData of linked images and creates a report at the DeskTop.
// Martin Fischer 10/2008
var myLinkXmpArray = ["author", "copyrightInfoURL", "copyrightNotice", "copyrightStatus   ", "creationDate", "creator", "description", "documentTitle", "format", "jobName", "keywords", "modificationDate", "serverURL"];
var myIPTCArray = ["CiAdrCity", "CiAdrCtry", "CiAdrExtadr", "CiAdrPcode", "CiAdrRegion", "CiEmailWork", "CiTelWork", "City", "CiUrlWork", "CopyrightNotice", "Country", "CountryCode", "Creator", "CreatorContactInfo", "CreatorJobtitle", "DateCreated", "Description", "DescriptionWriter", "Headline", "Instructions", "IntellectualGenre", "JobID", "Keywords", "Location", "Provider", "Province-State", "RightsUsageTerms", "Scene", "Source", "SubjectCode", "Title"];
var myPSArray = ["photoshop:AuthorsPosition", "photoshop:CaptionWriter", "photoshop:Category", "photoshop:City", "photoshop:Country", "photoshop:Credit", "photoshop:DateCreated", "photoshop:Headline", "photoshop:Instructions", "photoshop:Source", "photoshop:State", "photoshop:SupplementalCategories", "photoshop:TransmissionReference", "photoshop:Urgency"];//var myPSArray = ["photoshop:AuthorsPosition", "CaptionWriter", "Category", "City", "Country", "Credit", "DateCreated", "Headline", "Instructions", "Source", "State", "SupplementalCategories", "TransmissionReference", "Urgency"];
var myTiffArray = ["tiff:ImageWidth", "tiff:ImageLength", "tiff:BitsPerSample", "tiff:Compression", "tiff:PhotometricInterpretation", "tiff:Orientation", "tiff:SamplesPerPixel", "tiff:PlanarConfiguration", "tiff:YCbCrSubSampling", "tiff:YCbCrPositioning", "tiff:XResolution", "tiff:YResolution", "tiff:ResolutionUnit", "tiff:TransferFunction", "tiff:WhitePoint", "tiff:PrimaryChromaticities", "tiff:YCbCrCoefficients", "tiff:ReferenceBlackWhite", "tiff:DateTime", "tiff:ImageDescription", "tiff:MakeProperName", "tiff:Model", "tiff:Software", "tiff:Artist", "tiff:Copyright"];
var myExifArray = ["exif:ExifVersion", "exif:FlashpixVersion", "exif:ColorSpace", "exif:ComponentsConfiguration", "exif:CompressedBitsPerPixel", "exif:PixelXDimension", "exif:PixelYDimension", "exif:UserComment", "exif:RelatedSoundFile", "exif:DateTimeOriginal", "exif:DateTimeDigitized", "exif:ExposureTime", "exif:FNumber", "exif:ExposureProgram", "exif:SpectralSensitivity", "exif:ISOSpeedRatings", "exif:OECF", "exif:ShutterSpeedValue", "exif:ApertureValue", "exif:BrightnessValue", "exif:ExposureBiasValue", "exif:MaxApertureValue", "exif:SubjectDistance", "exif:MeteringMode", "exif:LightSource", "exif:Flash", "exif:FocalLength", "exif:SubjectArea", "exif:FlashEnergy", "exif:SpatialFrequencyResponse", "exif:FocalPlaneXResolution", "exif:FocalPlaneYResolution", "exif:FocalPlaneResolutionUnit", "exif:SubjectLocation", "exif:ExposureIndex", "exif:SensingMethod", "exif:FileSource", "exif:SceneType", "exif:CFAPattern", "exif:CustomRendered", "exif:ExposureMode", "exif:WhiteBalance", "exif:DigitalZoomRatio", "exif:FocalLengthIn35mmFilm", "exif:SceneCaptureType", "exif:GainControl", "exif:Contrast", "exif:Saturation", "exif:Sharpness", "exif:DeviceSettingDescription", "exif:SubjectDistanceRange", "exif:ImageUniqueID", "exif:GPSVersionID", "exif:GPSLatitude", "exif:GPSLongitude", "exif:GPSAltitudeRef", "exif:GPSAltitude", "exif:GPSTimeStamp", "exif:DateTimeOriginal,", "exif:DateTimeDigitized.", "exif:GPSTimeStamp", "exif:GPSSatellites", "exif:GPSStatus", "exif:GPSMeasureMode", "exif:GPSDOP", "exif:GPSSpeedRef", "exif:GPSSpeed", "exif:GPSTrackRef", "exif:GPSTrack", "exif:GPSImgDirectionRef", "exif:GPSImgDirection", "exif:GPSMapDatum", "exif:GPSDestLatitude", "exif:GPSDestLongitude", "exif:GPSDestBearingRef", "exif:GPSDestBearing", "exif:GPSDestDistanceRef", "exif:GPSDestDistance", "exif:GPSProcessingMethod", "exif:GPSAreaInformation"];
var myCameraRawArray = ["crs:AutoBrightness", "crs:AutoContrast", "crs:AutoExposure", "crs:AutoShadows", "crs:BlueHue", "crs:BlueSaturation", "crs:Brightness", "crs:CameraProfile", "crs:ChromaticAberrationB", "crs:ChromaticAberrationR", "crs:ColorNoiseReduction", "crs:Contrast", "crs:CropTop", "crs:CropLeft", "crs:CropBottom", "crs:CropRight", "crs:CropAngle", "crs:CropWidth", "crs:CropHeight", "crs:CropUnits", "crs:Exposure", "crs:GreenHue", "crs:GreenSaturation", "crs:HasCrop", "crs:HasSettings", "crs:LuminanceSmoothing", "crs:RawFileName", "crs:RedHue", "crs:RedSaturation", "crs:Saturation", "crs:Shadows", "crs:ShadowTint", "crs:Sharpness", "crs:Temperature", "crs:Tint", "crs:ToneCurve", "crs:ToneCurveName", "crs:Version", "crs:VignetteAmount", "crs:VignetteMidpoint", "crs:WhiteBalance"];
var myInfo = new Array;
var myDoc = app.activeDocument;
var myLinks = app.documents[0].links;
for ( i = 0; i < myLinks.length; i++)
   getMetaData ( myLinks[i] );
writeData ( 'Metadaten zu ' + myDoc.name + '\r-----------\r\r' + myInfo.join ( '\r\r'), File ('~/Desktop/Metadaten_' + myDoc.name.replace(/.indd$/, '') + '.txt'));
// ===============================================================
//                                  Funktionen
// ===============================================================
function getMetaData ( aLink )
   var myLinkXmp = aLink.linkXmp.properties.toSource().replace( /^$\{/,'' ).replace (/$\}$/,'').replace( /parent.+$/,'').replace(/:/g, ':\t').split( ', ');
   var myString = aLink.name;
   myString += loopLinkXmp ( aLink, myLinkXmpArray );
   myString += loopArray ( aLink, "http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/", "Iptc4xmpCore:CreatorContactInfo/Iptc4xmpCore:", myIPTCArray);
   myString += loopArray ( aLink, "http://ns.adobe.com/photoshop/1.0/", "", myPSArray );
   myString += loopArray ( aLink, "http://ns.adobe.com/tiff/1.0/", "", myTiffArray );
   myString += loopArray ( aLink, "http://ns.adobe.com/exif/1.0/", "", myExifArray );
   myString += loopArray ( aLink, "http://ns.adobe.com/camera-raw-settings/1.0/", "", myCameraRawArray );
   myInfo.push( myString.replace( /, $/,'') );
function loopArray( aLink, s1, s2, anArray )
   var temp = '\r\t--- ' + s1 + ' ---\r\t';
   for ( var a = 0; a < anArray.length; a++)
      try {
         var theEvalString = 'aLink.linkXmp.getProperty(\"' + s1 + '\", \"' + s2 + anArray[a] + '\")';
         var myCode = eval( theEvalString );
         if ( myCode != '' )
            temp += '[' + anArray[a] + ']\t' + myCode + '\r\t';
      } catch (e){ //temp +=e + '\r'
   return temp;
function loopLinkXmp( aLink, anArray )
   var temp = '\r\t--- LinkMetadata ---\r\t';
   for ( var a = 0; a < anArray.length; a++)
      try {
         var theEvalString = 'aLink.linkXmp.' + anArray[a] ;
         var myCode = eval( theEvalString );
         if ( myCode != '' )
            temp += '[' + anArray[a] + ']\t' + myCode + '\r\t';
      } catch (e){ //temp +=e + '\r'
   return temp;
function writeData ( aData, theFile )
   theFile.open ( 'w', 'Text', 'R*ch' );
   theFile.encoding = 'UTF-8';
   theFile.write ( aData );
   theFile.close ();
Ressources:
Adobe XMP Developer Center: http://www.adobe.com/devnet/xmp/
XMP Specification: http://www.adobe.com/devnet/xmp/pdfs/xmp_specification.pdf
Martin Fischer

Incrementally appending custom XMP metadata into PDF files

I have a problem writing custom XMP metadata into a PDF document (I'm using the XMP Toolkit SDK).
The problem is that I don't know whether is possible to expand the XMP packet in order to append metadata incrementally into the document, and, if it is possible, I don't know how to do it. The program I wrote succesfully appends an item to an array four times, but it fails when trying to append the fifth one. The reason obviously is that the packet gets full and there is not room for more metadata. The error message, if I force the PutXMP call, is:
ERROR: Can't fit into specified packet size
So, what can I do? How to enlarge the packet or make it expandable? Or, otherwise, have I to inject a new XMP packet with the up-to-date information in it? How?
And a last question: Have I to scan for packets when dealing with PDF files? No smart handlers are available for this kind of files?
Thanks in advance.
Xabier Artola.
Univ. of the Basque Country.

Were you able to find a solution to this problem? I am having the same issue.
Jason

Add support for custom xmp panels

Please add support for custom xmp panels.
Thanks

I would strongly support that too!!!
Here is why: We have been working at an XMP implementation of the Darwin Core to support standardized metadata on biodiversity information. Have a look here. I would love to have an Panel in Lightroom to support the metadata that I am embedding with IDImager:
http://wiki.idimager.com/index.php?title=DarwinCoreXMP#.27.27.27Darwin_Core_XMP.27.27.27
Cheers,
Frank

Managed metadata columns in document information panel with multiple content types

Hi everyone,
The problem I have is that for custom content types not all managed metadata columns are displayed in Document Information Panel (DIP) for the document in the Office client application.
However, everything works fine with 1 specific content type. Even though the others using exactly the same site columns. The content types are deployed using visual studio to the content type hub, and after this the content types are correctly published to
the site collections, there are no publish issues here.
When I create a document based on the second content type in the same library, all fields are showed in the document information panel, except the managed metadata columns.
Detailed explanation:
Library: procedures
Content types:
- simple procedure (with 4 managed metadata fields and some other text fields)
- procedure with approval (with the same 4 managed metadata fields and some other text fields)
Scenario 1: I add the 'simple procedure' content type to the procedures library as only content type. Everything works fine, and all fields show correctly in the document information panel in Word.
Scenario 2: I add the 'procedure with approval' content type to the procedures library as only content type. Everything works fine, and all fields show correctly in the document information panel in Word.
Scenario 3: I add the 'simple procedure' and 'procedure with approval' content types to the document library procedures (added simple procedure first). When I create a new document based on the 'simple procedure'
content type, everything works fine and he shows all metadata fields. When I add a new document based on the 'procedure with approval' content type, the document information panel shows correctly, except all managed metadata fields. These are not visible at
all. Though they worked perfectly in scenario 1 and 2.
Is this a known issue or is there a workaround for this?
Thanks in advance!
Kind regards, Davy

Yes!
This problem is solved right now.
My issue was that I'm using custom content types deployed by Visual Studio in the content type hub. To create a managed metadata site column in visual studio, you need to have first of all your managed metadata field, but also a hidden field accompagnied
to make the actual mapping like the example below:
<Field ID="{B654D984-187A-471B-8738-F08F3356CFDA}"
Type="TaxonomyFieldType"
DisplayName="Countries"
ShowField="Term1033"
EnforceUniqueValues="FALSE"
Group="Demo"
StaticName="Countries"
Name="Countries">
<Customization>
<ArrayOfProperty>
<Property>
<Name>TextField</Name>;
<Value xmlns:q6="http://www.w3.org/2001/XMLSchema" p4:type="q6:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">{67308AC2-9556-456B-BF9E-43E8F23EBEE6}</Value>
</Property>
</ArrayOfProperty>
</Customization>
</Field>
<Field Type="Note"
DisplayName="Countries_0"
StaticName="CountriesTaxHTField0"
Name="CountriesTaxHTField0"
ID="{67308AC2-9556-456B-BF9E-43E8F23EBEE6}"
ShowInViewForms="FALSE"
Required="FALSE"
Hidden="TRUE"
CanToggleHidden="TRUE"
Group="Demo"
RowOrdinal="0"
/>
</Elements>
VERY important here is that when you create your content type using visual studio, you not only have to add the managed metadata site column in your xml (which let the content type work already perfectly) but also add the hidden field to your content type
xml !! This way, SharePoint knows that when you have multiple content types with the same site columns in the same library, the second content type also need to get the hidden field from this site columns like in the example below!
<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
;
<ContentType ID="0x010100571ebc0f478a49d5a775039347ee1535"
Name="Document Location"
Group="Demo"
Description="A content type containing Managed Metadata Column."
Inherits="TRUE"
Version="0">
<FieldRefs>
<FieldRef ID="{B654D984-187A-471B-8738-F08F3356CFDA}" Name="Countries"/>
<FieldRef ID="{67308AC2-9556-456B-BF9E-43E8F23EBEE6}" Name="CountriesTaxHTField0"/>
<FieldRef ID="{f3b0adf9-c1a2-4b02-920d-943fba4b3611}" Name="TaxCatchAll"/>
<FieldRef ID="{8f6b6dd8-9357-4019-8172-966fcd502ed2}" Name="TaxCatchAllLabel"/>
</FieldRefs>
</ContentType>
</Elements>
I'm very happy I found this solution, because in the whole project i'm implementing, this was used a lot!
Special thanks to the blog of @cann0nf0dder (http://cann0nf0dder.wordpress.com/2013/04/01/creating-a-site-column-with-managed-metadata) which let me think about this!
This ticket is answered now! :-)
Kind regards,
Davy

Custom XMP document metadata panel

Similar Messages

Maybe you are looking for