Limitation of Metadata forms for custom MIME types | Community
Skip to main content
Level 2
August 11, 2020
Solved

Limitation of Metadata forms for custom MIME types

  • August 11, 2020
  • 2 replies
  • 1523 views

Hello All

 

We want to create custom metadata forms for custom mimetypes. But as per current implementation, that has to be present inside "default" folder and which forces to add default tab via inheritance. Is there a way to create these forms without inheritance OR to create them outside of default folder for custom MIME type.

 

Note that "Apply folder" will not work as we want the form based on MIME type of the asset and not based on the parent folder due to content organization of the business.

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 gkkhatal

Hi @vijayalakshmi_s 

 

Thanks for the response. Below are the information you requested. While looking into it further, I feel the feature provided assumes that the any custom MIME types will need the inheritance and it "forces" these additional tabs and properties through inheritance. This is bit odd and it would have been nice to have a option to break the inheritance rather than having custom implementation 😞

 

Any ideas how we can achieve this through custom implementation.

 

1. I am using AEM 6.5 SP4

2. I see the tabs - Basic, Advanced, IPTC, IPTC Extension, Camera Data, Product Data 

 

Edit: Comment from @vijayalakshmi_s below solves the problem.

 

Thanks

2 replies

Vijayalakshmi_S
Level 10
August 11, 2020

Hi @gkkhatal,

If it doesn't has to follow inheritance from "default", we can create custom metadata schema in the equal hierarchy as "default" and then apply to desired folders. But the actual requirement of associating it to mimeType might not be directly possible as is. 

On a high level, looks like it calls for custom implementation. 

Could you please provide inputs on the below

  • AEM instance version
  • Tabs which you see as inherited from parent while trying to create custom metadata schema
gkkhatalAuthorAccepted solution
Level 2
August 11, 2020

Hi @vijayalakshmi_s 

 

Thanks for the response. Below are the information you requested. While looking into it further, I feel the feature provided assumes that the any custom MIME types will need the inheritance and it "forces" these additional tabs and properties through inheritance. This is bit odd and it would have been nice to have a option to break the inheritance rather than having custom implementation 😞

 

Any ideas how we can achieve this through custom implementation.

 

1. I am using AEM 6.5 SP4

2. I see the tabs - Basic, Advanced, IPTC, IPTC Extension, Camera Data, Product Data 

 

Edit: Comment from @vijayalakshmi_s below solves the problem.

 

Thanks

gkkhatalAuthor
Level 2
August 13, 2020

Hi @vijayalakshmi_s 

 

Thanks, this worked fine for us. Thanks for the solution and the clarity. Appreciate it!

 

Thanks

Ganesh