Level 2

Solved

Avoid redundacy in the DAM

Forum|Forum|4 years ago
October 29, 2021
4 replies
3567 views

It is required to implement a DAM using AEM Assets. The taxonomy leverages on the product ID and the structure is the following one
.../Product ID/Images/image.jpg

It might happen that for different products we have the same picture. This causes a replication of assets as in the example below

.../Product ID1/Images/image.jpg
.../Product ID2/Images/image.jpg

How can I avoid the redundancy maintaining the taxonomy designed? Is it possible to refer to logical links?

Thanks in advance.

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 joerghoh

Hi,

Does this really match the expectations of the users? Wouldn't they be surprised, that if they remove a product asset for product A, that this asset is also used for different products? Especially if they are not aware that they influence other products as well?

To assess the impact this requirement, I would recommend you to list all different cases:

* an asset is added to a product, and the asset is not yet available in the system

* an asset is added to a product, and the asset is already available in the system

* an asset is removed from a product, and the asset is also used for other assets

* (and potentially more)

and define how the system should behave; also consider the various users in this case:

* the user who performs the activity

* a user who has worked with that asset before on the system and added it to an asset.

* ...

Then match this to the ootb capabilities of the AEM and understand where you need to add a customization so the system behaves as you want.

From my point of view this requirement is highly risky, and not only from an implementation side, but also from a management point of view. Not to mention the problematic to train all users dealing with it.

Siva_Sogalapalli

Community Advisor

Yes, you can try below:

Create tags based on your requirement at http://<hostname>:<port>/aem/tags

You can create Tags similar to product Ids, then attach tags for the image.

Example, if you have Products like Product ID1, Product ID2, Product ID3 ,

1. Create tags for each product

2. Go to the image and attach the specific product tags

Then if you're using component to render product details, configure the product tag at component level and query for the image based on tag and use it.

This way you can avoid keeping same image under multiple folders in DAM.

Thanks

serenapitottiAuthor

Level 2

Hi @siva_sogalapalli and thanks for your reply but with this approach I should change the taxonomy right?

Thanks again.

Siva_Sogalapalli

Community Advisor

@serenapitotti , if you have existing tags related to the products, you can use them otherwise you need to create new tags and attach respective tags for the images.

Your component should render images based on products tags.

joerghoh

Adobe Employee

Is this a common case, that you have the same asset for multiple asset? Do you have enough metadata on the image or the product that it is even possible to detect this situation automatically? How should this be handled? What should happen if the image is removed from a product? What if moved or renamed?

serenapitottiAuthor

Level 2

Yes, it is a common case and unfortunately I don't have enough metadata to detect this situation automatically (I don't have any rule).
If the image is removed from a product, I expect to do the same with all the products with the same pic.
Cc: @joerghoh

VeenaVikraman

Community Advisor

@serenapitotti I have exact same questions as @joerghoh mentioned.

If you have same image under P1 , P2, P3 ; will they be related in anyway ? Means , if the image is removed from P1 , should it be removed from all other products ?
If you want to avoid duplication of images with exact same metadata, then better way to organize them would be using tags as @siva_sogalapalli mentioned. But that decision should be made after properly considering all the requirements.

serenapitottiAuthor

Level 2

If I have the same image under P1, P2, P3, I'd like them to be related. Therefore, if the image is removed from P1, I expect it to be removed also from P2 and P3.
I agree about using tags but this will bring me to a such hybrid situation for which for some products I get the Product ID from the folder (.../Product ID/Images/image.jpg) while for the others with these images in common, I get the Product ID from a tag.
Consequently, how should I manage the assets retrieve using the QueryBuilder? I think that a generic approach should be preferable.

Cc: @veenavikraman

joerghoh

Accepted solution

Adobe Employee

Hi,

Does this really match the expectations of the users? Wouldn't they be surprised, that if they remove a product asset for product A, that this asset is also used for different products? Especially if they are not aware that they influence other products as well?

To assess the impact this requirement, I would recommend you to list all different cases:

* an asset is added to a product, and the asset is not yet available in the system

* an asset is added to a product, and the asset is already available in the system

* an asset is removed from a product, and the asset is also used for other assets

* (and potentially more)

and define how the system should behave; also consider the various users in this case:

* the user who performs the activity

* a user who has worked with that asset before on the system and added it to an asset.

* ...

Then match this to the ootb capabilities of the AEM and understand where you need to add a customization so the system behaves as you want.

From my point of view this requirement is highly risky, and not only from an implementation side, but also from a management point of view. Not to mention the problematic to train all users dealing with it.

arunpatidar

Community Advisor

Hi,

If you have common images among products, you should be using the common folder and tag those images with product.

But still if you want to create duplicate copies then use Live copy of image to create duplicate image so that the duplicate images always in a sync with original one.

Arun Patidar

joerghoh

Adobe Employee

Hi @arunpatidar

I am not sure if the MSM is the correct solution here. First, that only works if not only the asset (the binary itself) are identical, but also if all the other properties are identical, and from my point of view that's questionable.

Also I assume that this requires then automation, because you cannot request that from authors, because you would require from that they know that they are about to upload the same asset as it's already available somewhere in the system.

And you have to write that automation on your own.

arunpatidar

Community Advisor

Hi @joerghoh

Yes, you are right, I totally forgot about the asset metadata which may vary due to different product.

If the binary and metadata is identical then this could be used to allow automatic sync if master changes.

Yes the Author has to know in advance if there is a same asset is already availble or not.

Arun Patidar

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded