I'm Bluffing

 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 asset

Setting the scene  Ever since the acquisition of StyleLabs by Sitecore, I've been interested in the platform and its capabilities. ContentHub, as the product under the Sitecore umbrella is now referred to, comes with quite a set of platform capabilties alltogether. It serve primarily as a DAM platform, but has strong ties and capabilities into PIM, CMP and so on. As well as some capabilities towards print, obviously on collaboration but also on DRM (Digital Rights Management). Over the course of the numerous CH (ContentHub) trainings that I've partaken in so far, the concept and functionality of the DRM module came up a few times. This first post will just show the details of DRM in ContentHub What is the DRM in ContentHub? Found on the main navigation, DRM opens up into the DRM contacts screen as shown below: Note that the above are obviously dummy contracts in a DEMO. When new contracts need to be created or existing need to be edited: Inside such a DRM Contract, the informat

 Stepping up your Sitecore game   The whole Sitecore ecosystem is changing. Sitecore is looking into more and more acquisitions following its large capital injection of last year. And it is not only changing on a level of acquisitions and platform capabilities. The platform is moving forward at cruising speed, with a solid release cadence moving the platform onward. Over the last years we have seen the technology change, noticed remarkable architectural shifts back and forth. All these changes obviously make an impact on several levels; how should you host this application, what about integrations, what about containers, what about platform functionalities. And even though the above questions feel pretty redundant, a lot of customers are still on older versions of Sitecore, and Sitecore 10 is still a distant dream. Which is why this article aims to provide a mix of where the platform is, where it is headed, and what would be a good approach and timing to get back on track. Evol