Expand my Community achievements bar.

SOLVED

filter large pictures from being published to the publish instance when the assets are activated

Avatar

Level 1

We would like to start using high-resolution source files for the product images. The source files are generally large .tiff files ranging from 25-50Mb in size.

We currently have 5500 product images and expect to add 5000 more.

We need to explore how we can filter these source files and the "original" rendition that is generated when the asset is uploaded to the DAM and activated for publishing (replication) to the publish instances.

We want to implement a solution that filters the large source files from being published to the publish instances when the assets are Activated.

We are on CQ 5.6

I have talked with Adobe support and it seems that it is currently not supported OOB. Have anyone implemented this before? Please help! Any suggestion is highly appreciated. Thank you!

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi,

It's not overly complicated to prevent publishing of all original renditions. On the author server, configure the replication agent(s) with a specific agent user id (See http://dev.day.com/docs/en/cq/current/deploying/replication.html#Replication%20Agents%20-%20Configur...). Then create an access control rule which prevents this user from reading any node named "original".

Where things get more complicated is where you want to replicate some original renditions, but not all. If this decision is based on path (say, don't replicate originals under /content/dam/products), then that can be done with a more refined ACL. If it is not path driven, you would need a custom ContentBuilder.

Regards,

Justin

View solution in original post

1 Reply

Avatar

Correct answer by
Employee

Hi,

It's not overly complicated to prevent publishing of all original renditions. On the author server, configure the replication agent(s) with a specific agent user id (See http://dev.day.com/docs/en/cq/current/deploying/replication.html#Replication%20Agents%20-%20Configur...). Then create an access control rule which prevents this user from reading any node named "original".

Where things get more complicated is where you want to replicate some original renditions, but not all. If this decision is based on path (say, don't replicate originals under /content/dam/products), then that can be done with a more refined ACL. If it is not path driven, you would need a custom ContentBuilder.

Regards,

Justin