Sometimes when you have a lot of content inside your document repository, they can be quite a bit and the user is going to have a hard time find what they are looking for. When this is the case, it makes sense to tag your content. So we're just going to show how you can not tag your content, but tag your product. So in an earlier video tutorial, we showed you how to tag your asset. So for example, to tag your asset, you can go to any given course, you can go to the content, and then you can say manage tags, and there's also this tag here. So this is covered in a different tutorial that we showed earlier. So you can tag this here. But in this particular case, your problem is not the learner finding the content within a course, it's the learner finding the course itself. When that is the case, you should go to the course level and click on metadata, and then you can tag the course the same way. So you can say level, let's say this is one, two. So you can tag it exactly the same mechanics that you use to tag the asset. You can also go to the very top level at the course and look at all the tags holistically. Imagine you do this enough times and you tag everything, your content will look like this. I'm going to switch to a different tab. This is when everything has been properly tagged. So now the learner can basically say, okay, I want only level one and two. And then the content listed is going to be filtered down to what they are looking for. And then they can say, okay, give me only 2018 and 2017. So these filters allow the learner who might want to buy your content to quickly find the content that they're looking for. So it's just easier to sell your stuff to your audience if you have a lot of things to sell.

tagging content

document repository

users

find

tutorial