As a Librarian relating a translated version of an asset to the English version (which already has other related translations) I want to trigger the auto creation of the relationships to the other versions.

Greg Milosovic 12 months ago in Digital Asset Management updated 11 months ago 4

We are constrained to the current model in DAM which is hub and spoke. E.g., The English version of an asset serves as the hub. Each translation is manually related to that EN version. The bi-directional sync helps relate the EN version to the newly added translation. EN --> ES and ES --> EN.

The problem is that a librarian has to then go into the other translated versions and manually build those relationships with the newly added translation in order to break away from the appearance of hub and spoke.


ES --> IT

ES --> KO

ES --> JA

ES --> DE

DE --> JA

DE --> KO

DE --> IT


Red Hat supports 9 languages so the problem is compounded if we want to show all the related translations no matter which language a user is on.

Also, there's another issue around related assets that are not translations. E.g., we may have 10+ web banners, display ads, and other creative that were designed specifically to promote an asset like a whitepaper or E-book. Our librarians now need to build the relationship between each of those creative pieces as well as the whitepaper. So they have to build:

Ad #1 --> Ad #2

Ad #1 --> Ad #3

Ad #1 --> Ad #4

Ad #4 --> Ad #2

Ad #4 --> Ad #3


Then they have to build:

Ad #1 --> Whitepaper

Ad #2 --> Whitepaper

Ad #3 --> Whitepaper


I'm looking for a way to automate this relationship building by leveraging a common denominator within the metadata. Then I would hope a biz rule could run on a regular cadence to evaluate that metadata field, package up all the assests with an exact matching value, and build the relationships if they don't already exist.

Content Types / Metadata Rules / Actions

These type of logical challenges are easier to solve with custom code than if we have to build a framework to support this in product code, because you can be so more specific about it. This challenge is solvable today with a scheduled rule and custom code.

Thanks, Petra. I reached back out to services and they will work with us to implement a solution via custom code.