Custom Metadata

Hi guys,
I have noticed custom class metadata is now preserved in Flash Builder 4 and I was wondering which tech update introduced that - Flash Player 10 or the Flex 4 SDK?
Thanks.
PS: Flash Builder 4 is fantastic. Great work Adoblings.

Sorry to bother you again, a question has just popped into my head related to custom metadata:
Is it possible to modify the Flex SDK (a personal modification) in order to handle custom metadata tags? In other words, if I wanted to use the following metadata tags to embed files would it be possible for me to modify the SDK to get this working?
    // embeds the file as a BitmapData class
    [CustomTag( file="/assets/image.png" )]
    // embeds the file as a Sound class
    [CustomTag( file="/assets/sound.mp3" )]
    // embeds the file as a Sound class, uses LAME for the MP3 encoding
    [CustomTag( file="/assets/sound.wav", encodingOptions="..." )]
If this is possible where should I start researching?
FYI: This would be for projects that did not use MXML or Flex components etc.

Similar Messages

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

Editing and sharing custom metadata/keywords through Adobe Drive in Adobe Bridge

I am part of a four-person video production unit operating within a local governmental entity. We are currently using four licenses of Adobe Master Collection CS5, and are about to get access to dedicated SAN storage.
We would like each user to have the ability to assign specific keywords to any given video clip (or remove keywords from clips) within Adobe Bridge, and have the three other users see the same results. I've noticed that Bridge alone will allow for keywords to be added or removed, but this list is specific to each user. Importing one list into other users' profiles is a start, but would no longer work, once keywords are added or taken away.
The overview page for Adobe Drive 3 says that it, "allows users to edit and view custom metadata/properties through Adobe Drive in Adobe Bridge," but I haven't found any explanation in either the website, forums, or user's guides that delves any farther into this area. If we incorporate Adobe Drive/Bridge into our workflow, will we be able to share/sync keywords between users? Is there some other (affordable) solution that would let us do this?
Thanks for any insight you might be able to offer.
Chuck

Hi,
Thanks for sharing your case.
The keywords you mentioned is XMP metadata, if all your digital assets are managed by ADEP CQ DAM service, you can use AD3 with built-in ADEP connector to communicate with the DAM server, then, I think it can meet your requirement, it means, the keywords can be set by one user through metadata panel in Bridge, and can be viewed by other users.
for custom properites, it's different from XMP metadata, it refers to the properties of one asset which is managed by a Content Management service. users have to use another UI to edit/view them in Br after AD3 is installed.
here are some requirements to use it.
1) CMIS 1.0 compiliant server should be used to manage all your digital assets
2) use the built-in CMIS with AD3 to connect to the server.
if other kind of servers are used, you should develope a custom connector through AD SDK to enable custom properties feature as well as some other handler required by AD SDK
thanks

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

Rich Text Editor Option for Custom Metadata

Hi,
We have created custom profiles for our clients. In one such profile which was created for news updates, client wants to have rich text editor in case of certain custom metadata fields such as description similar to comments.
As far i as i understand this can be achieved by creating region defintion which gives the option to create a web asset which can edited using site studio api. But is it possible to bring in rich text editor features for custom metadata fields in profiles ?
Regards,
Boopathy P

I'd suggest looking into the profile rule's "Use custom include" option.
You need to build the new control on your own, but you'll be able to plug it in via the "Use custom include" profile rule option. It's on the "Edit Rule Field" page.
You can also override the template, but I believe that's a lil' too hardcoded for best practices. This way, you can create a ckeditor textarea and apply it to any metadata you wish (of course, it's up to you to make sure the datatypes match).
Let us know if this helps!
-ryan

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.

Adobe CQ5.5 Digital Asset - Delete default metadata and how to create custom metadata

Hi
I am trying to create custom metadata for all format of assets (PDF, DOC, TXT, etc.,). I have created the dam folder under apps node as below:-
Step 1: /apps/dam/content/asseteditors/formitems
Step 2: Included the four property as textfield and selection according to our requirement under formitems
Step 3: I changed the cq:allowedTemplates from /content/dam/jcr:content
Step 4: I tried to upload the asset, I could get the custom metadata for Txt, Doc, PPT, XLSX
Step 5: But for JPG, PNG and PDF I am getting the default metadata which is huge list.
How to control this one? I want my custom metadata only displayed for creation assets. Find the attached.
CRX - Custom Template Configured
CRX - Custom Metadata populated for ZIP format
CRX - Custom Metadata not populated for PDF format

Hi,
If you read the description under section http://dev.day.com/docs/en/cq/current/dam/how_to_edit_metadata.html#Creating New Metadata Property for Assets you will find yout the format for images and its different format stores at different location. So to deal with image metadata plz try below
1. Create a "image" node under "/apps/dam/content/asseteditors" as sling folder and configure it similar to "/apps/dam/content/asseteditors"
2. under this folder again copy paste the "/libs/dam/content/asseteditors/formitems" and customize it accordingly
Above will help you to manage with all types of images. Now if you want to have separate group of property for different image types then similar to above you have to create format node inside image folder for example jpg file type create a node with name "jpeg" under "image" node & configure similarly as you did for image.
I hope it will help you to proceed. Please let me know for more information.
Thanks,
Pawan

How To Set Custom Metadata Programmatically?

I could have sworn there was a way, but I sure can't figure it out right now - anybody know if or how?
PS - I thought at first catalog:setPropertyForPlugin would do it, but it seems to just set some invisible property, not the viewable, filterable, custom metadata kind.
Thanks,
Rob

To build on John's reply, double-check that the metadata definition declares the field browsable and searchable, e.g.
    metadataFieldsForPhotos = {
        {id = 'type',
         title = "Type",
         dataType = 'string',
         browsable = true,
         searchable = true},

How to rename Custom Metadata Field?

I have some pics with custom metadata field "gadget brand", i with to rename the field name to "brand", how can i do that? I tried to rename in the custom metadata manager, but it doesn't apply the change.

Don't believe you it will allow you to rename it.
You're going to have to create a new field with the name you want and copy the data over. Unfortunately Aperture doesn't have any built in means of copying metadata from one field to another. Applescript however could do it fairly easily.

How to export custom metadata fields

How do I export custom metadata fields (or even the DATE) to a text or spreadsheet? Why does Aperture have dozens of metadata choices, but only allows a few to be exported?

You can try Automator which must be installed already in your computer. Create a new workflow, on the left pane select Aperture to see a list of actions, select "get selected items" and "extract metadata", and drag both to the right most pane. there you'll choose the Tag names to extract from the images already selected inside aperture and choose an output method, tabbed text should work fine for a spreadsheet. Hope it works.

How to hide custom metadata field in custom profies ??

hi,
how to hide custom metadata dropdown list in a custom profile based on choosing the security group.
ex: if i choose xxx security group, custom metadata dropdown should not appeared, for remaining security groups it should be visible.
so, Based on criteria, custom metadata should be hidden in custom profiles..
how to achieve it ?? where and how to configure ??
Detail guidance should be required
Thanks in advance

You cannot do this through profiles alone if I understand you correctly.
If I load a check in page, choose a security group and at this moment want a custom metadata field to disappear then you are beyond what profiles offers.
Rules evaluation can only be based on information that is know at the time the page is requested. That means in order for this to work you would need to make security group an non editable field and have a set of profiles for each security group.
The alternative is to customize the UI with soem DHTML or AJAX
Tim

How to use ADD_METADEF to add a custom metadata field

Hi All,
I am trying to add a custom metadata field to check in profile, and this I want to do using RIDC library through my java program. I have tried the following code, but some how I could not see its getting added to Information Fields and also to Standard check in profile.
Can you let me know what am I missing?
            myIdcClient = myIdcClientManager.createClient("idc://XXXX:4444"); // just commented out
            IdcContext myIdcContext = new IdcContext("weblogic", "weblogic1");
            ServiceResponse myServiceResponse = null;
              DataBinder myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "UPDATE_OPTION_LIST");
                myRequestDataBinder.putLocal("dKey", "xLocationList123");
              myRequestDataBinder.putLocal("OptionListString", "Madrid\nTokyo\nLondon\nWashington");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
                myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "ADD_METADEF");
                myRequestDataBinder.putLocal("dName", "xLocations123123");
                myRequestDataBinder.putLocal("dIsRequired", "0");
                myRequestDataBinder.putLocal("dOptionListKey", "xLocationList123");
                myRequestDataBinder.putLocal("dOptionListType", "choice");
                myRequestDataBinder.putLocal("dIsOptionList", "1");
                myRequestDataBinder.putLocal("dIsSearchable", "1");
                myRequestDataBinder.putLocal("dIsEnabled", "1");
                myRequestDataBinder.putLocal("dType", "Text");
                myRequestDataBinder.putLocal("FieldName", "xLocations123123");
                myRequestDataBinder.putLocal("dCaption", "Locations");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
                myRequestDataBinder = myIdcClient.createBinder();
                //IdcService=UPDATE_META_TABLE
                myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "UPDATE_META_TABLE");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
                myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "START_SEARCH_INDEX");
                myRequestDataBinder.putLocal("IsRebuild", "1");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
                myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "PUBLISH_SCHEMA");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
Thanks in advance.

Try calling the following code:
import static intradoc.shared.MetaFieldUtils.hasDocMetaDef;
import static intradoc.shared.MetaFieldUtils.updateMetaDataFromProps;
import intradoc.common.ServiceException;
import intradoc.data.DataBinder;
import intradoc.data.DataException;
import intradoc.data.Workspace;
    protected static void addMetadataFields(final Workspace workspace, final DataBinder binder) {
        traceVerbose("Start addMetadataFields");
        // Parameters for metadata field
        final String[] parameters = new String[] { "dsdComponentName", "dComponentName", "dsdVersion", "dType", "dIsRequired", "dIsEnabled", "dIsSearchable", "dIsOptionList", "dOptionListKey", "dOptionListType", "dDefaultValue", "dOrder", "dIsPlaceholderField", "dsdCheckFlag",
                "dsdDisableOnUninstall" };
        // Common values for primary and alternate field values
        final String[] values = new String[] { "ComponentName", ComponentName, "build_1_20131206", "BigText", "0", "1", "1", "0", "", "", "", "2500", "0", "", "" };
        // Primary file checksum field parameters and values
        final Properties field = new Properties();
        for (int i = 0; i < parameters.length; i++) {
            field.put(parameters[i], values[i]);
        // Setup primary file specific parameters
        field.put("dName", "Metadata field name");
        field.put("dCaption", "Metadata field caption");
        try {
            // Name of metadata field
            final String fieldName = field.getProperty("dName");
            trace("dName: " + fieldName);
            if (fieldName != null && fieldName.length() > 0 && !hasDocMetaDef(fieldName)) {
                try {
                    updateMetaDataFromProps(workspace, null, field, fieldName, true);
                    trace("Successfully added metadata field " + fieldName);
                } catch (final ServiceException e) {
                    warn("Metadata field " + fieldName + " was not installed.", e);
                } catch (final DataException e) {
                    warn("Metadata field " + fieldName + " was not installed.", e);
            } else {
                trace("Metadata field already exists; will not modify");
        } finally {
            traceVerbose("End addMetadataFields");
Jonathan
http://jonathanhult.com

Custom Metadata and the Filter Bar

A couple of month ago this was posted by another member/LR user:
I'm running Lightroom 2.3 on a WinXP system. I'm trying to use the library filter mechanism to display a subset of images based upon the values of some custom metadata fields.
All of the values for a given field are correctly displayed in the filter's drop-down list, but if I select one that contains embedded blanks, I'll get an empty set ("No photos in selected folder"). Take a look at the attached "embedded_blanks" screen shot. I should see one image, but instead don't see any. (BTW, an embedded underscore ['_'] will cause the same behavior, so there are probably other characters as well.)
There are also problems if I select the "No Value" option (which should show be the items for which the metadata hasn't been set). The attached "no_value" screen shot shows an example of this. Instead of showing 1 image, Lightroom is showing 4 -- all of the ones that do have a value!
Has anyone seen this before? I don't know where to check to see if this is a known problem.
One of the answers from a community expert confirmed it was a known problem, but not widely known. I have thus far installed v2.5 and this is still not working as it should - pretty much the same problem as above. I have created (and filled) certain thematic custom metadata fields specifically so I would be able to use them for the filter bar/Smart Collections and of course am a bit disappointed. The good news is that my limited testing shows that v3b has indeed corrected this issue YEAH!
In the meantime, does anyone know if this was corrected in v2.6? It appears from the release notes that this as for camera updates only so I was not planning on installing unless somehow this problem was addressed.
Thanks!
Jeff

I don't think so. But it does appear to be fixed in the LR3Beta as you say.
John

Custom Metadata

Similar Messages

Maybe you are looking for