Custom Metadata Schema Support Needed

So, it's 2011, and we still don't have metadata support like Bridge. VRA Core 3 and 4 are being supported by major applications across the web. Large institutions and individuals alike are needing to quickly batch edit large amounts of raw scans and export/embed with compatible image metadata. They have already embraced Bridge as a defacto with its custom file info panels but Lightroom still doesn't support that even though it advertises its strong metadata credentials. The fact of the matter is the world just doesn't use only IPTC anymore.
So I'm wondering if Adobe's already standard XMP "Custom File Info Panels" functionality will be implemented in Lightroom v4. If this is confirmed, large institutions can plan on buying Lightroom as a better (future proof) pre-upload (and personal collection) organizer for large sets of images vs Bridge as Bridge relies directly on a file system and the file system can become a very disorganized place. Also, Lightroom is less costly and more functional for Art Historians.
This has been a constant feature request since v1 in 2007. It has been 4 years. Is there a plan to add this in v4 or some functionality like it?
All the best,
Walker Blackwell
University of Vermont
Art History

You may want to address this over at the Feedback/Feature Request Site which is being used more and more for discussion related to this kind of request.

Similar Messages

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.

How to export / share Metadata Schemas?

The title says it all:
When I create a great custom metadata schema in Premiere Pro that contains all the relevant categories for my project it is all useless to me unless I can share those schemas with my collegues on their computers! Is there any way how I can make my metadata schemas available to them? If yes, will the values I enter into the schema be attached to the media I apply my schema on, so they are available for my collegues as well? Otherwise, there is no point in sharing. It strikes me that there are so many collaboration impeding obstacles with Adobe products like that! Not every project has a commonly used server to work with after all.
Anyway, if there is a work around, I would be happy to learn it.
Thx

Thx for your quick answer! Im using CS6 btw.
Do you suggest that I should copy the folders in:
on Windows: C:\Users\<USERNAME>\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\custom
on Mac: Users/<USERNAME>/Library/Application Support/Adobe/XMP/Custom File Info Panels/4.0/custom
and paste them onto my collegues system?

Need to export custom metadata fields to a national data base, can I ???

In Aperture3 are custom tags embedded in exported Versions or Masters. I have a task to embed matadata on 2000 items and need to pass on the information to someone who doesn’t have Aperture

I am not sure whether you really can embed custom metadata in the jpeg file itself. However you can quite easily export all metadata associated with a file in Aperture using AppleScript. The script below shows you how it works in principle with the different data categories in aperture: IPTC, custom fields etc. To adapt the script to your needs, replace eg "Photo Category" with the name of your own custom field. By copy/paste you can add more fields...
tell application "Aperture"
set tSelection to the selection
-- this is the header, not really necessary
set tValues to "Version Name" & tab
set tValues to tValues & "File Name" & tab
set tValues to tValues & "Keywords" & tab
set tValues to tValues & "Category" & tab
set tValues to tValues & return
--here starts the real stuff
repeat with i from 1 to number of items in tSelection
set tImg to item i of tSelection
--add Version name
try
set t to name of tImg
on error
set t to ""
end try
set tValues to tValues & t & tab
try
--add FileName
set t to the value of other tag "FileName" of tImg
on error
set t to ""
end try
set tValues to tValues & t & tab
try
--add IPTC tag
set t to the value of IPTC tag "Keywords" of tImg
on error
set t to ""
end try
set tValues to tValues & t & tab
try
--add a custom field
set t to the value of custom tag "Photo Category" of tImg
on error
set t to ""
end try
set tValues to tValues & t & tab
--next line/image
set tValues to tValues & return
end repeat
set f to choose file name with prompt "Choose file name..."
set my_log to tValues
set mylogfile to open for access f with write permission
set eof of mylogfile to 0
write my_log to mylogfile starting at eof
close access mylogfile
end tell

Need to pass custom metadata with Managed Attachment in EBS

Hi All,
I have enabled Managed attachment in EBS.
I also want to pass few custom metadata along with managed attachment.
I have followed the section "6.5 Configuring Managed Attachments Settings"
from the Application Adapter's guide at http://docs.oracle.com/cd/E23943_01/doc.1111/e17953/c06_confg_attchmts.htm#BABIEIDF
but still i dont see the custom metadata in the Managed attachment checkin screen.
thanks,
swapnil

Hi Swapnil ,
You will need to apply the following patch :
Patch 13943045
Read me file has all the steps required in addition to the patch to get Custom Parameters sent with EBS request , please check it and complete the steps .
Once done , check to see if OAF is able to send the parameters .
If not , then check the request / response files from EBS to get more details .
Thanks,
Srinath

Custom Metadata for Microsoft Word

Since Microsoft Word has a limited property/metadata fields and there is no budget to purchase a document management system, I am thinking of storing custom metadata fields in a XML file or a database.
Can Ultra Search be configured to search the Word documents by full-text and metadata fields? If so, how?

You should start by downloading the Acrobat SDK and building the sample plugins. This is C/C++, there is no support for .NET.
Next you will need to read the relevant section of ISO 32000-1:2008 (the PDF standard) or a book such as “Developing with PDF” (from O’Reilly). This is required to understand how the PDF file format and objects work.
Finally, you can then start looking at the SDK documentation around the Cos and PD layers to apply to what you need to do.

Retrieve a list of different values of custom metadata field of an UCM connection

Hi
I am planning to create a custom search document functionality for my UCM and Portal integration. Basically, I am planing to create CMIS queries dynamically. In order to create the CMIS query, I need the possible values of custom metadata for the user to select from and through a backing bean construct the cmis query based on this selection.
I have created a custom metadata field (lets say, 'KindOf'). So I want to show the user a list of all possible 'KindOf' values, so user selects the values he wants and I use those values to build the cmis query and show the results.
What is the easiest, best practices, how would you do it, way of achieving this?
I have little experience with UCM.
Regards

Hi,
As rightly pointed out by jiri machotka, you want that option list .
if you create a option list metadata, you have to publish schema to get the values. You can do it by two ways:
1) Wait for the event which publish the schema automatically.
2)Select "Publish schema" in the options menu of the Configuration Manager.
Some good implementation info about searching can be found at - Students at Oracle: UCM: Creating search and check-in profiles with custom metadata
and http://www.slideshare.net/heikim/effective-strategies-for-searching-oracle-ucm
Otherwise if you want faceted search or something near to enterprise searching capabilities, then go for enterprise search engines.
I have recently worked on Enterprise Search Engines on various CMS products for better,intuitive and relevant search results.
Hope, above information can help you out.
Regards,
Hoque

Custom Metadata Panels from CS3 to CS4.

I have install CS4 on my Vista Ultimate PC. It runs like a dream. However there is now a new format for the custom metadata panels. I have two panels that I created in CS3 that I need to convert to the new format. Is there an easy way to do this?
The CS3 files are txt files that all I had to do was copy to the proper directory and they appeared. Thanks.
Fred

Thanks Gunar,
I already had my custom XMP panel for my server product for InDesign. I tried to create a CS4 compatible panel on MacPro (Mac OS X 10.5.5 3GB RAM) using every possible method from the XMP FileInfo SDK pdf - it didn't work. The panel did show up in the dialog, but not the fields. Not only this, all fields also disappeared from some other panels. After I removed my custom panel, everything went back to normal.
I tried:
-Generic panel method - the fields didn't show up
-The Flex SDK method: when I run
ant built.xml
I got the "Target "build.xml" does not exist in the project "TestPanel"." error (I checked many times - all the files were where they're supposed to be, and I run it from the correct directory).
-I downloaded Flex Builder, followed all the steps - the fields didn't show up, and fields in other panels disappeared.
The idea of building the panel interface interactively is great - I hope it will ever work.
Any ideas of why it didn't work for me?
While we're on this, I think that the new tabbed interface for the File Info dialog is a huge step back. You already had a great interface, with the list of panel names on the left side - which is easy to use and is standard through many Adobe dialogs.
The multi-tab approach for many items proved to be inefficient long time ago. Right now you created a dialog that works like a dilaog in QuarkXPress 4 - what's the point?
To support the new tabbed interface, you had to introduce TWO new "arrow" controls, none of which is user-friendly, and which make a simple task of choosing a panel extremely confusing.
The new feature of changing panel position by dragging is great, but it could be also achieved through the side list approach.
Bottom line: could you please restore the side list approach. I think it will help advance the XMP technology further and encourage people to actually use it , instead of doing exactly the opposite.
Best,
Leo Revzin
Zevrix Solutions
zevrix.com

Will somebody please post an Aperture-written xmp file *with* custom metadata in it - thanks.

It is my understanding that Adobe's migration tool will NOT support transferal of custom metadata from Aperture to Lightroom.
I have recently enhanced my Custom Metadata plugin to read custom metadata from Expression Media xmp, and it seems like a no-brainer to have a "preset" which can read/import/transfer custom metadata from Aperture xmp too - I just need a sample to work with - thanks.
If you don't want to post here, please send directly to me.
robcole.com - Contact Me
Rob

To attempt a wrap-up for this thread:
Aperture does NOT provide a means to save custom metadata in XMP - the initial premise of this thread was incorrect: a thank you to John Beardsworth for setting me straight. Specific question asked has been answered.
The purpose for the thread however was to learn how to get information out of Aperture so it can be gotten into Lightroom (final destination: custom metadata fields).
Here is one way to get custom metadata in Aperture to custom metadata in Lightroom, recommended if you have enough free IPTC fields to house the custom data temporarily:
* Create an applescript file with the following contents, modified to support your custom metadata fields; note: it must also be modified to specify the IPTC fields to be used:
tell application “Aperture”
    set imageSel to the selection
    repeat with i from 1 to count of imageSel
        tell library 1
            tell item i of imageSel
                set customFieldValue to value of custom tag "myCustomFieldName"
                set value of IPTC tag "myFreeIptcFieldName" to customFieldValue
            end tell
        end tell
    end repeat
end tell
Note: you must adapt script depending on your custom fields, and which IPTC fields you have free.
* Select photos in Aperture.
* Execute the script.
* Once photos are in Lightroom, with IPTC fields populated.., then in Lr's plugin manager, with 'Custom Metadata' plugin selected, click 'Transfer Metadata' button, then "follow the yellow-brick road" (you will be prompted with instructions..). Metadata will be transferred from IPTC fields to custom metadata in Lightroom.
If you do NOT have sufficient IPTC fields to use, or would rather not use IPTC fields for this, then you'd have to modify the script to populate a row in a CSV file for each photo, then use the 'Import from CSV' function in Custom Metadata plugin. I can help if it comes to this..
PS - There may be other ways as well, but maybe this is enough..
Rob

Can PPro view custom xmp schema?

As the title, can PPro view custom xmp schema in its metadata view?

Bridge's metadata panel only supports plain-text fields for custom metadata. See the following article on how to submit and feature request to Adobe via the feature request form:
http://kb2.adobe.com/cps/800/e8008c68.html
I assume you already know that you can open the File Info dialog itself directly within Bridge for a selection of one or more files, yes? The same custom File Info panel that appears in Photoshop's File Info panel will appear in Bridge. To open File Info in Bridge, use the File or thumbnail-contextual menus or the keyboard shortcut Cmd+Opt+Shift+I.
If you really require a highly customized metadata UI right inside the Bridge window (File Info is a modal dialog box), and you are willing to invest some coding effort, then I suggest using Flex Builder to create a custom Flash Panel for Bridge. You will have to take on some non-trivial work to sync up what's displayed/edited in your custom panel with the current selection of Thumbnails, etc., but such a solution should be technically possible. The Bridge Scripting SDK includes example for how to add a Flash panel, how to get your Flash ActionScript and Bridge JavaScript to talk to each other via the Flash External Interface, and how to use the XMPScript API to modify metadata for files. Again, I think the effort required is non-rivial, but Bridge does provide a platform upon which you can build a highly customized solution.
-David

In A3, How Do I Apply One Of My (many) Custom Metadata Views To The Viewer?

In A3, it appears that both the Viewer and Browser are limited to just 2 views: Basic and Expanded.
In A2, I had many custom metadata views that I could easily change via the Metadata-pane (now gone) in Prefs. depending on the type of workflow, customer needs, etc.
Now, if I'm limited to just 2, I'll have to go in and manually change the composition of A3's 2 views for each workflow. If this is the case, I see it as a big step backwards. This is the type of limitation that iPhoto often has, and flexibility is what I expect from a Pro-App.
I spent a great deal of time developing custom metadata views for various workflows so that I could align the various displays in Aperture to each workflow. What do I do now?

Just stumbled over this thread:
Yes, its the truth. There is no way to quickly change the display of Metadata in Browser or List View.
You can tell from the form of the Settings - Window (Command - J) that there is no way anymore. You have one Standard View, and one Extended.
Strange. I did not use it a lot, I always display pictures to customers with no metadata, except when we do a selection on site (and then its standard with only rating).
wok4

Custom metadata fields used in file name?

Hi,
Is it possible to add to the list of meta data fields that are used as tokens for file names?
I've been using Rob Cole's excellent custom meta data in the library module and now I want to use these fields to name the file during export...
While at it, is it possible to add the same custom meta data fields to the info view overlay in develop mode?
Cheers,
Bonny

1. Its possible an export filter (post-process action) could be defined that supports the custom metadata for export filenaming (Lightroom itself does not have any other hooks I'm aware of) - dunno if anyone's done that, yet.
2. I think not (see PM).
Rob

Get value based on column names for custom metadata field of Webcenter Content

In UCM, I created a custom metadata field of type Text. I then enabled optlist in that field. I populate values to the optList, I am using a View. The View has three columns. Let us call them ID, Key, Value. OptList displays the Keys in its list. I then create a Content (Content ID: MyContent) in Webcenter Content and choose values from OptList for my new metadata field (MyField).
From Webcenter Portal, I am populating a selectOneChoice with values of MyField in the Content ID: MyContent. Remember from previous step, the values populated in selectOneChoice is the list of values selected from optList field MyField. This optList is in-turn populated from View. After the user selects a value in selectOneChoice, in Javascript, I need to alert a message in this format "value chosen - corresponding value from View of optList that populates MyField"
I think an example will be useful:
Here is a View that I created in Configuration Manager applet in Admin Applets of Webcenter Content:
ID | State | Capital
1 | North Carolina | Raleigh
2 | California | Sacramento
3 | Illinois | Chicago
Then, I create a Custom Field (Name: MyField). MyField is an optList the values are populated from View created above. The internal value and display value are both State. Then I Check-In a new content with Content Id: MyContent. For MyContent, I select these values from OptList for MyField: {North Carolina, Illinois}.
In my Webcenter Portal application, I create a Content Presenter Taskflow. I configure it as a single item content presenter. I assign MyContent as Content Id. Then, in templateView, I get all values of MyField in MyContent and display them as selectOneChoice. I created a javascript function that would get the value that user selected in selectOneChoice. In the View created in Webcenter Content's Configuration Manager (above), there is a value corresponding to each value displayed. So, for the selected value, I need to get the corresponding Capital and display it in my alert message.
From Javascript, how can I get the value of Capital, given I have the value of State.

Hi.
The idea to achieve your requirement is next:
Create a helper manage bean that will be call as Map access: #{stateUtil['Calofironia']} (it will return Raleigh). This value will be get calling GET_SCHEMA_VIEW_VALUES IDC service using RIDC in your manage bean.
Pass the result of #{stateUtil['statename']} to your JavaScript function using <af:clientAttribute.../>
I hope this information help you.
Regards,

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

Select Button beside custom metadata field on Check In Form

Hi
In Oracle Content Server 10gR3, is there a way to add a "Select" button to User Alias Applet for a new Meta data field on New Check In Form? I tried creating a component but I don't see a select button being shown up. The button does shows up if it's a standard metadata fields but not for the custom one. Here is the component code. Any idea what I am doing wrong and how to fix it.
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>
CustomMetaData htmlIncludeOrString
</title>
</head>
<body>
<@dynamichtml std_meta_fields@>
<textarea name="xClbraAliasList" rows=3 cols=40 wrap=virtual></textarea>
<input type="button" value="Select..."
onClick="popupSelectAlias(document.Checkin);">
<script language="JavaScript">
     var aliasForm;
     function popupSelectAlias(frm)
          var selUser = document.selectAliasApplet;
          aliasForm = frm;
          selUser.createFrame();
     function setAliasString(val)
          if (val.length == 0)
               return;
          var str = aliasForm.xClbraAliasList.value;
          str.trim;
          if (str.length > 0)
               str += ",";
          str += val;
          aliasForm.xClbraAliasList.value=str;
     </script>
     <applet name="selectUserApplet"
    code=com.intranetsol.utilities.SelectUserApplet.class
      codebase="/idc/common/"
     archive=suapplet.zip
    id=selectUser
    width=0
    height=0
     MAYSCRIPT>
          <param name=CGI-URL value="/idc/idcplg">
          <param name=JsDisplaySeparator value=",">
          <param name=IsPaged value="1">
          <param name=IsUserList value="1">
          <param name=JsFunction value="setUserString">
</applet>
<applet name="selectAliasApplet"
    code=com.intranetsol.utilities.SelectUserApplet.class
      codebase="/idc/common/"
     archive=suapplet.zip
    id=selectAlias
    width=0
    height=0
     MAYSCRIPT>
          <param name=CGI-URL value="/idc/idcplg">
          <param name=JsDisplaySeparator value=",">
          <param name=IsPaged value="1">
          <param name=IsAliasList value="1">
          <param name=JsFunction value="setAliasString">
</applet>
<@end@>
</body></html>
Then I tried using the same code as above but instead used the built-in dDocType to show a "Select" button. This works but the button obviously shows besides dDocType but when I try for custom metadata as shown above it doesn't. Here is the sample code for dDocType:<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>
CustomMetaData3 htmlIncludeOrString
</title>
</head>
<body>
<@dynamichtml std_doc_page_definitions@>
<$include super.std_doc_page_definitions$>
<$include custom_modify_comments_definitions$>
<@end@>
<@dynamichtml custom_modify_comments_definitions@>
<$if isCheckin$>
<$xComments:isHidden = 1$>
<$xComments = "some preset and hidden comments"$>
<$elseif isUpdate$>
<$xComments:isInfoOnly = 1$>
<$endif$>
<@end@>
<@dynamichtml compute_std_field_includes@>
<$include super.compute_std_field_includes$>
<$if fieldName like "dDocType"$>
<$if isCheckin or isUpdate$>
<$fieldEntryInclude = "custom_doc_type_popup_field_entry"$>
<$endif$>
<$endif$>
<@end@>
<@dynamichtml custom_doc_type_popup_field_entry@>
<input type="text" name="dDocType" value="<$fieldValue$>">
<input type="button" value="Select..."
onClick="popupSelectAlias(document.Checkin);">
<script language="JavaScript">
     var aliasForm;
     function popupSelectAlias(frm)
          var selUser = document.selectAliasApplet;
          aliasForm = frm;
          selUser.createFrame();
     function setAliasString(val)
          if (val.length == 0)
               return;
          var str = aliasForm.xClbraAliasList.value;
          str.trim;
          if (str.length > 0)
               str += ",";
          str += val;
          aliasForm.xClbraAliasList.value=str;
     </script>
<applet name="selectAliasApplet"
code=com.intranetsol.utilities.SelectUserApplet.class
     codebase="/idc/common/"
     archive=suapplet.zip
id=selectAlias
width=0
height=0
     MAYSCRIPT>
          <param name=CGI-URL value="/idc/idcplg">
          <param name=JsDisplaySeparator value=",">
          <param name=IsPaged value="1">
          <param name=IsAliasList value="1">
          <param name=JsFunction value="setAliasString">
</applet>
<@end@>
</body>
</html>
Can someone please let me know what is in my above code that I am missing that is preventing the button not being shown in-front of the custom metadata field.
Any help would be greatly appreciated.
Thanks
Edited by: guest0012 on Aug 29, 2009 4:24 PM

Interesting!
You'll need a component. You already mentioned you had a custom metadata field. You will also need to add a counter to the counters table for your component. During a check in you will need to fetch the next value from the counters table, increment the counter and store the new number back in the table. The year portion of the id is easy, get the current year and grab the last two characters. Then, put this all togther to get the data for your metadata field.
The big question now is where in the check in process will you do all this? You will need something called filters probably. Maybe addFiles, maybe validateStandard, there are several that this could work with.
Check out the how-to-components:
http://www.oracle.com/technology/products/content-management/ucm/samples/index.html
-Jason
http://www.corecontentonly.com

Custom Metadata Schema Support Needed

Similar Messages

Maybe you are looking for