Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED
Custom Metadata Schema not getting applied to image with .eps format
Hi,
We have a custom metadata schema used in our project where customized tabs and fields are getting applied to the image formats - png, tiff, and jpg. Whereas it is not getting applied for Images with eps format.
Does anybody know how we can apply metadata schema for eps format as well similar to other image formats.?
Please Refer picture for the same.
TIA!
1 Accepted Solution
Correct answer by
Hi @mrudul, I was able to reproduce the issue on my local instance. I think you need to add new Schema form for MIME type. It is because only some schemas are available OOTB, here is the documentation.
Background of observed issue:
If you will look under /system/console/mimetypes you will see that *.eps extension is correlated with application/postscript MIME type.
Knowing that, if you will refer to the documentation - application/postscript is already associated with application/pdf schema form. This is why your custom eps schema is not applied.
Solution
You will need to follow below guide additinaly to what you have already configured.
Create new Schema form for application/postscript MIME type and connect it with *.eps extension. This will allow to recognize your custom metadata schema correctly. Assuming your schema for *.eps files is located under image schemas, you have to add below eps node under /etc/dam/metadataeditor/mimetypemappings. This can be done directly from crx/de or from code e.g. you can include it in your crx package. See below screen, with all the details:
@mrudul I do not see any issue in adding a new tab in custom metadata schema and adding a new field.
I am not sure if missing anything here.
Refer below link
Correct answer by
Hi @mrudul, I was able to reproduce the issue on my local instance. I think you need to add new Schema form for MIME type. It is because only some schemas are available OOTB, here is the documentation.
Background of observed issue:
If you will look under /system/console/mimetypes you will see that *.eps extension is correlated with application/postscript MIME type.
Knowing that, if you will refer to the documentation - application/postscript is already associated with application/pdf schema form. This is why your custom eps schema is not applied.
Solution
You will need to follow below guide additinaly to what you have already configured.
Create new Schema form for application/postscript MIME type and connect it with *.eps extension. This will allow to recognize your custom metadata schema correctly. Assuming your schema for *.eps files is located under image schemas, you have to add below eps node under /etc/dam/metadataeditor/mimetypemappings. This can be done directly from crx/de or from code e.g. you can include it in your crx package. See below screen, with all the details:
