DRM in ContentHub pt2 - Intersections of contracts

 Setting the scene

My previous post was a pretty vanilla post on the use and features of the DRM functionality inside Sitecore's Content Hub. This post can be found here: https://kverheire.blogspot.com/2021/11/digital-rights-management-in-contenthub.html

But, as with everything, the real intricacies really only show themselves once you start to research them or get actual business requirements and are able to test them out against the product. 

The premise for this post is what I noticed when multiple contracts / profiles seem to overlap.
So, as an example, lets say there is a specific element present in a picture. This could be a celebrity or a detail of an asset/article (let's assume a car). 

In that case, it may very well be that two policies would apply:
1) The digital rights contract with the photographer who signed into contract for that photo-session
2) The rights attributed to the car or celebrity (or both) shown in the picture.

What should happen?

DRM on multiple assets and profiles

As stated in the previous post; an asset can be assigned to multiple DRM profiles at the same time.
And this in turn should allow for complex rules to be constructed.

Let's say we have our first digital contract that was created to account for all the photos delivered by a specific agency named 'X':


This digital contract holds a single profile (for now) that details that all these images are allowed to be used Worldwide and this over an infiite timespan (Dec 31 9999 apparently... :p). Also, as an actual restriction, the assets contained under this contract can only be used for Traditional media as well as the Website (child of Digital). So... not for Social in this case...

The sample structure of DRM.Media here is:

- All
    - Digital
        - Social
            - Facebook
            - Twitter
        - Website
    - Traditional
        - Magazine
        - TV

Next to this contract, there is a second contract that concerns itself with the Personality rights. Let's say we have a famous royal or actor in one of the pictures, then this asset is subject to this contract as well. The contract is defined as follows:



In other words, all images attributed to this profile (and displaying the bespoke personality) are allowed to be used in Europe for use on the Website BUT, this time restricted in time up to Dec 31 of 2022.
So... no social media, but no traditional media either and not worldwide, but Europe only.

Now, the interesting case would be to see if the platform supports the following setup:



You can see the blue digital asset stuck in the intersection of these two rights.
From left to right we have an asset created by Agency X, but with no other peculiars. Next, we have an asset by Agency X that features a specific personality (contained under the second DRM profile). And lastly, the third asset hold the same personality but was not created by Agency X.

My expected behavior inside Content Hub,for the blue asset depicted above, would be the following for me at this moment; based on the following cases:

If my company would want to download an asset for use in

1) a European campaign for the Website to be used this year -> OK
2) a Chinese  magazine for 2023 -> NOK
3) a European Website for 2050 -> NOK
4) a European Social campaign for 2023 -> NOK

However, as it turns out, this is not (in the test I used version 4.0.0), I got the following results:

1) a European campaign for the Website to be used this year -> OK
2) a Chinese  magazine for 2023 -> OK
3) a European Website for 2050 -> OK
4) a European Social campaign for 2023 -> NOK

This implies that the ContentHub DRM approach is now checking if there are any roles that match the requirements of the DRM request, rather than check if all of them are met...


So, in conclusion...

No intersections are taken into account by default. 
I'm going to listen in with ContentHub if this is by design, how to modify this behavior and configure it according to the specific business requirements the customer demands.


Comments

Post a Comment

Popular posts from this blog

Stupid exception: Device is not ready – System.IOException .net

Sitecore 8.2 in-depth preview + 8.3 update info and Sitecore Ecommerce information

Date Ranges in C#