Supply context

Boris Pocatko

2 minutes

0% complete

Even the best system needs supporting metadata to decide which content is fit for publishing in the given context. This metadata is much more difficult to identify as there are no boundaries to which it’s constrained. In this lesson, you'll learn how to choose your context-related metadata.

There is a vast number of possible metadata to be entered, collected, and personalized if available. It’s easy to include too many metadata categories with no added value. You need to focus on relevant categories only to minimize content entering overhead. You can start with the two most common context-supplying metadata categories: location and time.Example metadata category: Exact Location [Longitude, Latitude], Proximity to a POI [Café, Shop, Vending machine, Gym, etc.], Time of day [Morning, Noon, Evening] Make sure you make a case for every metadata category you plan to include in your content type definition. It’s also possible that other, less common metadata may be more fitting for your scenario. You need to determine in what context your content becomes relevant. Then, evaluate if it’s possible to have that level of context awareness within your content channels and associate supporting metadata with your content.

Not all examples above are feasible, but they illustrate how much context can be added to your content to be displayed in the relevant situation. The key part is for you to determine what metadata is important for your particular case.

How to choose

You can follow the suggestions below on how to choose your context-related metadata.

Prioritize one or two context factors that you want your content to adapt to. What kind of personalization would your customers most value?

Decide which content variations your content designers and developers need to create consistently. For example, you might need a “long description” and “short description” text for every product or every podcast. You might need a set of device-specific terms, like “click,” “tap,” and “say select,” in every set of instructions. Start with the high-value variations; get those working before adding more.

As discussed when answering the “When” question in the previous lesson, adaptive content has to know when it should change. Your metadata should support rules that will tell your system when to display what content.

Sign in with your Kontent.ai credentials or sign up for free to unlock the full lesson, track your progress, and access exclusive expert insights and tips!