Restrict custom metadata for DAM assets | Community
Skip to main content
S
sameryadav
Level 4
January 19, 2016
Solved

Restrict custom metadata for DAM assets

  • January 19, 2016
  • 9 replies
  • 5164 views

Hi

1. Can we show/hide the few metadata fields and few disable (graout) programmatically? Does anyone have any example or article url?

Thanks

~S

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Amit_Kumar

Option 1: 

  • overlay /libs/dam/components/asseteditor/form/metadata component in your project and
  • set HTML form field to hidden or if you want to hide this in editor.
  • Similarly you can change the other behaviour by overlaying or overriding components available in /libs/dam/components/asseteditor based on your requirements.

Option 2: 

Option 3:

9 replies

Amit_Kumar
Amit_Kumar
Level 10
January 19, 2016

Can you share more details about: where do you want to show/hide the metadata? 

S
sameryadavAuthor
Level 4
January 19, 2016

Hi Amit,

Basically our original requirement is to show/hide few metadata fields of DAM assets based on the users. There are no way to do this OTB in AEM that's why we are trying/looking to implement it pro-grammatically if it is possible.

We are able to disable it by setting the property "disabled=true" in classic UI view. But looking to hide the properties.

Thanks

~S

smacdonald2008
smacdonald2008
Level 10
January 19, 2016

The only way I can think of is to treat these assets as nodes and properties and use the AEM JCR to modify properties. So you will need to build a custom AEM service that uses the JCR API to do this. 

Amit_Kumar
Amit_KumarAccepted solution
Level 10
January 19, 2016

Option 1: 

  • overlay /libs/dam/components/asseteditor/form/metadata component in your project and
  • set HTML form field to hidden or if you want to hide this in editor.
  • Similarly you can change the other behaviour by overlaying or overriding components available in /libs/dam/components/asseteditor based on your requirements.

Option 2: 

Option 3:

S
sameryadavAuthor
Level 4
January 20, 2016

This help us.Thank you so much.

One thing, In Option 2, My understanding is that if for same assets few user want to see few metadata fields (like title, description, approved status etc) and few others users only want to see only the title and description not the approved status fields. Then in this case we need to maintain that assets in two separate folders in to the DAM, right?

Thanks

~S

francisco_ribei
francisco_ribei
Level 6
January 20, 2016

You can control tabs using groups:

www.xicojunior.com/blog/2015/12/19/enabling/disabling-tabs-on-aem-6.1-assets-metadata-schemas-using-groups/

Maybe you can try this with fields.

I hope this helps.

Amit_Kumar
Amit_Kumar
Level 10
January 20, 2016

yes,you are right.
I think if you set correct permissions then i am sure you need not to hide them Rest it depends on your business requirements. Moreover one though if you have a limited number of user group i.e author, approver then you can override the HTML code for this asset editor and write a servlet to get the user roles and based on the user roles you can render the html code for this again that will take some extra efforts and yeah If you got your solution then mark this as answered please.

Thanks,
Amit

edubey
edubey
Level 10
January 20, 2016

This could be done with the help of listeners as well. Write a widget listener so that based on user group you have hidden = true/ hidden = false.

S
sameryadavAuthor
Level 4
January 20, 2016

Hi All,

Thank you so much for valuable solution. These all help us.

Thanks

~S

Terms & ConditionsAccessibility statement

Loading footer...