Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Custom Metadata Schema not getting applied to image with .eps format

Avatar

Level 3

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.

mrudul_0-1648828532591.png

 


TIA!

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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.

eps-mimetype.jpg

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:

eps-form-config.jpg

⚠️Please be aware that order matters - so your eps node have to be located before pdf node. It's because pdf node is also connected with application/postscript MIME type - so first match will be selected.

View solution in original post

1 Reply

Avatar

Community Advisor

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

nitinjl_0-1648842503016.png

Refer below link 

https://experienceleague.adobe.com/docs/experience-manager-64/assets/administer/metadata-schemas.htm...

Avatar

Correct answer by
Community Advisor

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.

eps-mimetype.jpg

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:

eps-form-config.jpg

⚠️Please be aware that order matters - so your eps node have to be located before pdf node. It's because pdf node is also connected with application/postscript MIME type - so first match will be selected.