Customizing metadata properties in DAM

Hi all,
I have been looking into leveraging the DAM to allow for content providers to attach specific global meta data to particular assets. Perhaps I am thinking incorrectly on a strategic level, so any alternate approaches are appreciated as well.
The problem is, we have a set of affiliates which are listed out in the dam, containing a prescribed set of images/assets/links. These providers can be viewed via pages in CQ5, but also within a set of mobile apps for droid and iPhone.
The iPhone and droid crews are currently accessing a set of JSON files to get the required metadata, which is placed within the DAM. I think is a very nasty solution, as this data will not be filled in by developers, but rather an affiliate on ramp team. (Essentially a team of Sales staff).
What I am looking into now, is to store the additional metadata on an affiliate folder as JCR metadata, which I have successfully done, but only by generically customizing the properties for folders/images. Ie, for folders, right click -> properties.
You can add additional items to the basic properties tab by adding the relevant component nodes to /libs/foundation/components/primary/sling/OrderedFolder/tab_basic/items, even add entirely new tabs by creating a new node at the /libs/foundation/components/primary/sling/OrderedFolder level (i.e. myTab) and then specifying it in the dialog /libs/foundation/components/primary/sling/OrderedFolder/dialog/items/tabs/items
The problem is that the tab/extra question fields will be universally displayed, and are not folder dependant, so they appear in every folder context.
What I would love to do, is to have it so that if you access http://localhost:4502/damadmin#/content/dam/affiliate/affiliateA you get your newly customized options/panels etc, but if you were to view properties on http://localhost:4502/damadmin#/content/dam/affiliate you would not get any additional questions being asked.
Any help would be greatly appreciated.

Recently there was a similar discussion internally & suggestion came from group was
1. Create & confiure an acl.
OR
2. using Listener on the particular field you want to hide and then hide the field based on the path. To do this, create a listeners node of type nt:unstructured under the field (e.g. /apps/dam/content/asseteditors/image/jpeg/formitems/person/listeners) and set the beforeloadcontent property to [1]. This will hide this field for assets under /content/dam/geometrixx. You could adjust this to meet other requirements.
Verify 2 & let us know how it goes.
[1] function(f, r, p) { if (p.indexOf("/content/dam/geometrixx/") == 0) { f.hide(); } return true; }

Similar Messages

Custom metadata properties give no results after upgrade from 2010

Hi,
Although I see my custom managed properties in my Search Schema in Central Admin, I am unable to find results using them e.g. 'VendorName:Marcel'. I have tried changing the column value in a document and performed a full crawl, but still no results. General
searches such as 'Marcel' work fine and even something like 'author:marcel' (which is a built in managed property) works too. What am I missing? How can I determine the issue? Nothing stands out in the ULS logs.
Background:
I recently upgraded my managed metadata service and search service from 2010 to 2013.
I then upgraded the content db holding my root site collection, and had to re-create my search service proxy to get searches to work. I then upgraded the content db which holds my content hub site collection. This includes site columns, many of which
are also Managed Properties.
Crawls are running with 8 errors - none of which are for the document I changed. Warnings are mainly about 'png' files.
In 2010 I had scopes, which I no longer see in Central Admin. Although I have converted the content database without error, I have not converted the Site Collection to 2013 yet.
macrel

I had to set each metadata property 'queryable' property and then run a full crawl after which the results were returned. I am surprised that this did not come over from the upgrade of the search service.
macrel

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

Introducing Custom Metadata property through a package

Hi,
I want to introduce a new custom metadata property for my assets which could be displayed in the DAM metadata UI of an asset as below. I can see some steps mentioned to do this in http://dev.day.com/docs/en/cq/current/dam/how_to_edit_metadata.html. However I want to do this through a package that I am developing. Hence whenever my package is installed in CQ some custome metadata properties must be automatically regisitered for all assets.
To summarize I have following queries:
How to create/register custome metadata proerties for assets in a package using CQ APIs ?
Once a custome metadata prperty is registered how to update its value using Asset API ?
Appreciate any help here!

Check http://www.wemblog.com/2013/01/how-to-associate-cug-with-dam-asset-in.html is that helps.
Yogesh

Problem in adding custom metada properties

Hi All,
I want to add some custom properties while creating a document in KM repository. I am getting problem while adding the custom group in the property structure "all_groups"...
This is waht i have done so far,
1) I created the custom metadata properties..
2) Created one property struture group XXX and added all the metadata properties in the gruop items field...
3) Added this structure group in all_groups. While saving the changes, its saying "<b>These changes would introduce problematic settings: Group item "XXX" is neither a property ID nor a group name defined in the configuration. Check whether it is the ID of an unmodelled property or the ID is misspelled. Click on OK or Apply to confirm these changes. </b>"
After saving it, following massege is displayed,
"<b>The following configuration objects have some invalid or problematic properties: "all_groups</b>"..
Also the newly created structure is not getting displayed in the document properties.
Please help me.
Regards,
Sandip<i></i>
Message was edited by: Sandip Agarwal

Hi Robert,
Thanks for your reply. I guess I have taken care of the spelling (have done it 4-5 times )....So may be something else is wrong.
I have sent you a screen shot of the problem to your mail id
Thanks again for you help.
Regards,
Sandip
Message was edited by: Sandip Agarwal

Updating KM Metadata properties using KM API

Hi All,
We are tring to update the custom Metadata properties using KM API from the Abstract Portal Component.
We have written the below code for updating the metadata.
We have checkbox called "Region" which has multiple option values like "Asia,America,Europe". I was able to update this property with single value. But when i try to update with multiple value it is not working. I tried with comma seperated but it didn't work.
Can somebody through light on this. How to update multiple values?
Code snippet
IUserManagementService service=(IUserManagementService)PortalRuntime.getRuntimeResources().getService(IUserManagementService.KEY);
          com.sapportals.portal.security.usermanagement.IUser user =null;
               user= service.getDefaultFactory().getEP5User(request.getUser());
IResourceContext context = new ResourceContext(user);
RID path = RID.getRID("/documents/src/ex1.doc");
                    IResource res = ResourceFactory.getInstance().getResource(path,context);
                    IPropertyName propName = new PropertyName("http://ars.com/xmlns/cm","Region");
                    IMutablePropertyMap map = new MutablePropertyMap();
                    IProperty property = new Property(propName,"Asia");//How to pass multiple Values?
                    map.put(property);
                    res.setProperty(property);
Helpful answer would be appreciated and Rewarded....
Regards,
Birla.

Hi Birla,
try this:
IResource res = ResourceFactory.getInstance().getResource(path,context);
IPropertyName propName = new PropertyName("http://ars.com/xmlns/cm","Region");
java.util.List values = new List();
values.add("Asia");
values.add("America");
values.add("Muenster, Germany");
IProperty property = new Property(propName, PropertyType.STRING, values);
res.setProperty(property);
Best regards,
Michael

Custom Metadata Panel and Palette

Hi,
We have created a custom metadata panel file and placed that file to the particular folder mentioned in user guide, and we can able to see/edit/save the custom metadata properties in FileInfo menu.
But we need a new Palette in Adobe Bridge CS3 GUI to see this custom metadata and edit the details onto that palette (as same as in FileInfo menu). Is there any possiblities to do that?
Regards,
Karthik

Not sure I understand what you are asking, but I think it's that you want to add a section in the Metadata panel that is shown via Window > Metadata Panel. On that assumption, does this help?
John

Restrict custom metadata for DAM assets

Can we restrict custom metadata to appear only for a few DAM assets? For eg, I have assets under two folders, myProject1 and myProject2 in DAM. Suppose I want the custom metadata fields to show up only for the assets under myProject1, can that be done? If yes, how?
This is with respet to the details in http://wem.help.adobe.com/enterprise/en_US/10-0/wem/dam/how_to_edit_metadata.html

Hey Sham,
I have customized the granite interface to have the additional metadata field.
I have even overlayed /apps/dam/gui/content/assets/metadataeditor/items/content/col2/image/items to add an additional metadata node , to be present in the granite interface, but i see that it works fine for "projectA", ie. both png and jpeg files have the sample metadata in the granite interface, but the .png files of projects, other than "projectA" eg geometrixx have the sample metadata field, while the jpg files dont, after using the function: function(f, r, p) { if (p.indexOf("/content/dam/project/providers") != 0) { f.hide(); } return true;.
Kindly suggest where i have gone wrong.
Regards,
NZ

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

Add dropdown column in Metadata properties in Search SharePoint2010

Hi all,
i have some drop-down columns in library and i need to add these column in metadata properties in search. and dose dropdown column support in search refinement panel and in advance search page xml ? also i
need to add library dropdown column in search center for filter the data on search page. is there any out of the box way to do this.
BestRegards|SharePoint Techies

Hi ,
According to your description, my understanding is that you want to create custom SharePoint 2010 Search Refiners for some drop-down columns in library.
For achieving your demand, you can refer to the blog:
http://blogs.msdn.com/b/spnext/archive/2010/08/09/customising-sharepoint-2010-search-refiners.aspx
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
contact [email protected]
Eric Tao
TechNet Community Support

Access custom metadata from another plugin

I was wondering if it would be possible to access the custom metadata from one plugin from another plugin.
I know you use the _PLUGIN object when you read or write the metadata with a plugin.Is there any way to pass the varible to another plugin, maybe stored in a xml or text file in the modules folder? I also see where you can use the "unique identifying string" or plugin.id. Is this id differant for every installation of Lightroom?

Allen, I'm pretty sure the answer is no - you can't access another plug-in's custom fields.
I'm sure I have read this limitation somewhere - even if I can't now see it stated explicitly in the documentation. If anything, the docs imply getPropertyForPlugin can do so by specifying the LrToolkitIdentifier value (which you may be able to pass as a preference). So this doesn't work:
getData = photo:getPropertyForPlugin("uk.co.beardsworth.missing", jbMissing )
It is an important point though that one plug-in should be able to access another's custom fields. Obviously one can think of many ordinary circumstances where it would be handy, but I'm more worried about the longer term DAM viability of custom metadata. Let's say I decided to release a plug-in based around custom fields and users entered metadata which had some value to them - whether that's just input time or business data (eg client or agency account number). Now move on to LR3 and the plug-in no longer works - I've disappeared, driven mad by SDK changes, or you're unwilling to pay my extortionate plug-in upgrade fee.
Now what happens to that valuable metadata? The data is still in the database but you can't read it because the original plug-in's unavailable, and Adobe's built-in "All" Plugin Metadata panel only shows data from enabled plug-ins. It's not in the XMP either. You're stuffed - unless you're resourceful enough to reverse engineer chunks of the plug-in. Assuming that I encrypted my plug-in's code, that means you're going to have to dig around the SQL to figure out my plug-in's ID and its field names. Only then can you create a plug-in to rescue your custom data. And you've got to hope to hell that my plug-in didn't encrypt or obscure the values you entered.
For me what this shows is
1) You're taking a big risk if you store valuable custom metadata - if you can't sort it out yourself, should you do it?
2) You should ensure any plug-in with custom metadata stores its field definitions in unencrypted files
3) The All Plug-in Metadata panel needs to show all plug-in metadata
4) The SDK should allow you to get custom metadata from other plug-ins
4) Custom fields should be mapped to XMP
Short answer - No.
John

Custom Metadata url

I have some custom metadata as type url and the button works perfectly in the metadata panel to open the page.
I was wondering is there a way to show text for the url in the field instead of the url itself. Like you do in a html like with the text between the starting and ending tags.
What I am getting at is I would like to display a action in the metadata and when you click the button in the field it goes to the webpage to proform the action.ex: http://mypage.com/admin.php is in the field but I want to display Admin and still go to that address when it is clicked in the metadata field.
If it won't work not, please make it a feature request.

Hi Richard,
the property syntax since NW04 SPS9 or higher and EP6 SP2 Patch 5 or higher is the following:
&SelectedCustomProps=<namespace>:<propid>(value=<value>/operator=<OP>),...
as example: &SelectedCustomProps=default:description(value=banana/operator=EQ),default:description(value=apple/operator=EQ)
Properties queries with multiple properties are linked with a logical AND. Occurence of the same property multiple times are linked with a logical OR.
Regards,
Thilo

Display custom metadata/ add new columns in document explorer of spaces

We have client requirement to show custom metadata in the document explorer home sceen, like Document name, Size, Author, etc..
Can we display metadata from advanced properties of a file like a column or can we add new columns to display to document explorer.
How can we achieve this goal, can we customize taskflow to achieve this goal.
Thank you,

For what it's worth, I posted pretty much the same question a couple of days ago:
How to show document title instead of file name in Document Manager
If you check the source of the task flow you'll notice that the document explorer contains an af:treeTable that iterates over a collection of items.
I have not yet identified the class it is iterating over, but I doubt you will be able to add custom metadata to this table. Perhaps the document title (which I am looking for) which is a common field, but not others.
Might be an enchancement request for Oracle Support.

Multiselect metadata propert in xml form

Hi,
I have created an xml form to create news items for our company. I would like to add a custom metadata property that i have created that is multiselect.
Eg I have created a multi valued property named sls_region with allowed values All, America, Europe. I have assigned this property in custom parameter section of Editxsl file of xml form.
I have created a filter with sls_region property with all allowed values for property available in dropdown.
While uploading news whatever value is selected in dropdown of filter gets assigned to custom property of the form.
To make it more clear
sls_region has value All, America, Europe
If in filter dropdown America is selected ..custom property has value set as America
If in filter dropdown Europe is selected ..Custom property has value set as Europe
If in filter dropdown All is selected ..Custom property has value set as All
This is working fine .Code which I am using for this is
<xsl:param name="ext_mars:sls_region" />(Defined in custom parameters section)
<input size="30" type="hidden">
<xsl:attribute name="name">wcmprop.mars:sls_region</xsl:attribute>
<xsl:if test="$ext_mars:sls_region=' '">
               <xsl:attribute name="value" /> </xsl:attribute>
          </xsl:if>
             <xsl:if test="$ext_mars:sls_region!=' '">
               <xsl:attribute name="value">
<xsl:value-of select="$ext_mars:sls_region"/></xsl:attribute>
          </xsl:if>
</input>
But I need to change functionality like when user select All in dropdown of filter, all available values for that custom property get sets in form.
If in filter dropdown All is selected ..Custom property should have value set as All, America, Europe
Please guide me how to modify above code to achieve this.
Regards,
Madhvika

Thanks for responding
sls_region is a multi value property with values ALL , America, Europe.
My current code which is working fine is like whatever I select in my filter (a sender iview, custom developed component with multi value properties sls_region appearing as dropdown) get passed to receiver iview (basic search iview with a modified epcf receiver as collection renderer).
Receiver iview is used for both uploading news and searching news. To upload news I am using xml form. I have modified edit xsl of form .by adding code as mentioned above in my thread in detail
So if in filter if I select America as region ..Uploaded news will have sls_region property set to America.
If All is selected uploaded news has sls_region set to All.
Code mentioned in my thread is working fine but now I need to modify it like .
If I Select All in filter...Uploaded news should be set with all allowed values of sls_region property i.e. All, America, Europe.
To make it more clear if you look at my code above I want to add logic like
if (test="$ext_mars:sls_region=' '")
<xsl:attribute name="value" /> </xsl:attribute>
Else {
If (test="$ext_mars:sls_region = All)
Value of select = All and America and Europe means news get uploaded with            available values of sls_region
Else
<xsl:value-of select="$ext_mars:sls_region"/></xsl:attribute> only with what is selected in filter either America or Europe.
I want to set all allowed values of property sls_region in case when All is selected in filter.
Hope this will help you to have a clear understanding of my problem.

Customizing metadata properties in DAM

Similar Messages

Maybe you are looking for