Image Map feature getting stored in DAM asset metadata

[#1]

When I add map to image component, imagemap property is stored in content component node and DAM asset metadata. So when I drag-drop this same image in different page/comp, same imagemap is getting added.

Is there a way to store only under content/component node ?

My requirement is to have image map reference only in the page where I edit. Not to change the asset in DAM, so that it affects all the places where it is used. 

[Nithyasri_K]

Hi @Nithyasri_K,

If the map details are available in DAM asset metadata, then the map would have been applied from being in Assets console via "Edit action on an asset". (Since it applied at image level, it will be available in all the pages/components referencing it).

You can try the following

For the specific image of concern:

• Navigate to assets console -> look for the respective image -> select and choose "Edit" -> Launch Map -> You would see the mapped areas -> select and delete -> Try to use same image at different pages/image component -> Observe the behavior.

New image:

• Upload new image -> without any edits, add the same image in a component -> apply map at component level -> imageMap property will be available only at respective image component node under the page (Not at asset metadata)

If you observe different behavior, share the same with AEM version and Core image component version details.

[Nithyasri_K]

Thanks Viji, this works as you have mentioned above with inline editing.

But I am using an image component inside carousel, inline editing does not work here. Also imagemap property is getting stored in the carousel node and not in image.

Any suggestions for this case