In this video I am going to walk you through the administration of the Sitecore Digital Asset Management (DAM). Hoping that future videos will capture the setting up of DAM and the technical aspects.
Note: The following is the transcription of the video produced by an automated transcription system.
Hey, guys, this is Akshay Sura today will be covering the Content Hub Digital Asset Management Administration, most of the things we do in here in terms of administration will cover content hub in general. So, when we’re extending schema or adding taxonomy values, so we’re pretty much touching the Common Core functionality of content hub. And it will be similar between CMP, PCM, because in all of these products, which are all content hub products, you will be touching schemas and taxonomies and in order to customize these entities content types exactly to what your business needs. So, let’s go ahead and take a look at how to do that. In content hub once you click on an asset and as usual with our videos on the left, it’s a demo instance of content hub, and on the right it’s a plain instance. So, we don’t really have anything set up in terms of metadata or taxonomy. So, when you click on an asset, you can see that you have different values available for the metadata of the assets or the overview section. There’s a couple other sections, depending on image analysis. If you’re running cognitive services, they can have if it’s a product asset, you’ll have product data associated with it, the system information and system properties. So, these are all come out of the box. So, there are certain properties which get hydrated at a system level. So, any file-based metadata properties. So, once you get uploaded, the system updates them. Metadata can, as I mentioned, can come from file attributes. When you upload it, it can be set by the system, you know, such as, you know, who uploaded it, when was it uploaded?
Certain parts of the metadata can be set by cognitive services to get tags based on the image analysis and then these properties, which can be set by the user themselves. So, there’s quite a bit of different ways in which you can hydrate these properties for the metadata. Some can be automated as part of the image analysis in order to extract. So, you could have integrations which will use the image and then hydrate some metadata. So different ways of doing it. There are two types of metadata, its control vocabulary, which is structured metadata predefined with predefined set of options. It’s like an option list or taxonomy in case of option list. Your if you have less than 10 options, that’s pretty much when you end up using option lists. If you need hierarchical metadata, then you would choose the taxonomy. And these are typically things like asset type. So, if you if I were to go in here, as you can see asset type is a taxonomy, you can brand as it is multilevel. As you can see, some are multileveled, some aren’t so controlled vocabulary. We’ll will look into how to set up the option lists as well as taxonomy. The second type of metadata, as I mentioned, our properties or anything like text such as these, and you could store numbers, date time and a couple of other field types so you can add them to any of these sections in order to get user input.
Let’s add option lists and taxonomy. So, I’m going to manage going to options. Let’s create a new one. Call it target audience for target audience. Let’s add developers and let’s add one more marketers. So now we have a target audience. If you have an existing list you want to update, you can absolutely do so. It’s pretty much it’s pretty easy. They have hierarchical here as well and you can move things around if you choose to. Next, let’s get back into taxonomy. All right. Let’s go into taxonomy. What I’m going to do is I’m going to find as a type add a new asset type. And, you know, once you don’t really have to specify the identifier, it automatically creates it. Labels pretty much are used, you know, when you’re doing excel import and things of that sort. It’s that. So, we added a product as a type, which is great. Now, OK, let’s create a new taxonomy. Let’s call it testing. And then in here, let’s create.
You know one. Then create another one. Create that if you want to create a sub item, you can either created here and then use the move function to move it. But if you would like, you could just create, you know, click on the specific level two. This is mainly just for us to do some testing. So, as you can see, I have no hierarchical you and you can go on multiple levels if you choose to and you can have as many values as you want. So now we’ve created a brand new option list. We’ve created a brand new taxonomy. We have updated an existing taxonomy. And you can use the same process to update an existing option list as well. Next, we’ll look into how we can add this onto the asset. So, I’m going to go into schema, look for asset. Now, as you can see, there’s several sections inside of Assets. When you notice there’s an overview section, there is image analysis, product data. So, you could pretty much put create new sections if you choose to and put your attributes in different areas. What I’m going to do is I’m going to add an asset type, which is an existing metadata right there.
And to add that into the overview section. So, we added an existing metadata. I’m going to add our option list. Which is target audience is probably. Darwinians and. It is, you know, and then I am also going to add our new taxonomy, which is testing. And then make sure you publish and then once you publish, you go back to your asset will open to the same one for consistency sake. And when I edit, as you can see now, we have an asset type notice. We have the product which we added so I can select an asset type. Sometimes you can control whether you can select one or more. In this case, looks like we can select multiple, which is great, but you might just want one for that matter. Target audience we added three lets other developers if we need to testing. As you can see, we have multileveled to level one and do so again. Looks like it lets to select multiple but there are options to control that. So, you can customize this according to your business needs, according to your requirements. So, this is a good way to add multiple attributes to the metadata to control different aspects of an asset.
Next, we’ll look into adding a property. So, going to manage schema, let’s look for the asset and let’s add a new member. And you have several options to choose from. I’ll stick with string for now. Let me. That’s the name. The label is typically for the people using. The system, you could specify help text, you could turn on quite a few of these attributes, depending on your need, if you need it to be multilingual, type ahead, you can add conditions. You can make it required if you choose to. I’m going to set this as a multiline save that. Once you save it, you publish. Once you publish, get back into the assets, will open the same asset. And then once I get in here, we have a market purpose. So it’s pretty easy to extend metadata, you can use metadata for several things, it’s not just you might have a business purpose for it, but it also helps you search for these assets out of the box. The metadata you get might be great in terms of identifying the asset. But for your business users to be able to search, find these assets in hundreds and thousands, it helps for you to tag it with different things like market segments whose it key to do any business purpose and descriptions or tags of any sort which will help them search for it.
Next, we’ll look at conditional statements on either sections or on fields. So, if we go in, manage and get into schema. So, what I want to do is on the asset. I’m going to say that for market purposes only show the market purpose if the asset type is a product. So, we save that, publish it. Now, let me get back to the asset. As you can see, this guy now doesn’t show the market purpose at all. If I go ahead and hit product, the moment I add that, I get the market purpose. So, this kind of helps you have this conditional logic depending on if the product is about as it is of product, you could probably show a product section. If the asset is a type advertisement, for instance, you could show a different section so you can keep the UI pretty clean, simple enough for your end users to use it without too much hassle and cluttering the whole UI. Next, we’ll look at the cognitive services for media processing, which generates metadata for us. So, for instance, the colors, the tags and description of an image, it helps us hydrate more information about an asset automatically as part of media processing.
So, in here, the asset type really determines if we process the cognitive services. So, if are going to type. And then we look at a specific asset type, the trigger vision is what determines it, so if I enable product. That’s the one then trigger vision is what will put that into that process flow. And also, there’s a cost associated with this. Next, we need to figure out what exactly will be extracted as part of the media processing. So, if you’re going to meet a pricing vision, choose the image type each of these steps, you could do certain parts of the process. You could add more steps or modify existing one. The panel on the right helps you define what exactly will happen in this case. We chose tags, description and color. I’m going to leave it as is because we have not modified anything at this moment. Now, if we go into an existing asset and the type as part of, you know, OK, save, and then what this does is add to jobs in the jobs section. Once the job is completed and you refresh this page, you’ll be able to see the image analysis. So, at this moment, as you notice, we don’t see any tags. We don’t see any values inside of the image analysis at this moment in time. So, we will wait for the job to finish. And then once we refresh, we should be able to see it. As you notice, we got the cognitive services running, we got the tags for this, we got the image analysis, which is it’s white for whatever reason. And still you have to take it with a grain of salt with some of these cognitive services.
As they learn more, they are able to generate better results for you. But in terms of tags, that cartoon drawing sketch illustration back to graphics, so might not be the best example, but this is an example of cognitive services. In terms of auditing, you notice this icon, which shows the history of what’s been happening at the field level, you can also point to the reporting logs, which kind of give you an overview of all the things which have happened in the system. And you can go into each one and kind of figure out what exactly happened in terms of all the events which took place in the system. You can also look at the raw audit logs as well. These have very my new information as to this is the job that triggered the changes we had made to the asset. So, you could pretty much piece together all the events which happened in the system using these audit lines. And again, content hub is an ocean. There’s a million things you could do in here from theming. You could do translations, a bunch of security UI configurations for pages, search customizations, adding facets and providing different options. I mean, as your need grows and you try to find new functionalities, you can definitely customize this and make it your own. And as I mentioned, most of these activities we, you know, just concentrated on asset. But there’s different kinds of entities. So, on content, all of these customizations can be applied to any of those.
That’s it for today. If you have any questions, be sure to reach out to us. Hopefully we’ll have another video coming soon with the integration.</i>
If you have any questions, please get in touch with me. @akshaysura13 on twitter or on Slack.