The content profiling system in WebGUI (also known as the metadata system) allows you to identify content. Metadata is information about the content, and is defined in terms of property-value pairs.

Examples of metadata:

• contenttype: sport
• adult content: no
• source: newspaper

In the example source: newspaper, this metadata has a property named source with a value of newspaper.

Metadata properties are defined globally, while Metadata values are set for each asset under the tab "Metadata" in the asset properties.

Setting up Content Profiling

1. Before you can use metadata in WebGUI, you have to enable metadata in the WebGUI Settings (Content tab)
2. create the metadata fields you would like to use under teh "Content Profiling" area in the Admin Console.

Usage of metadata:

• Passive Profiling
  When passive profiling is switched on, every wobject viewed by a user will be logged. The WebGUI scheduler summarizes the profiling information on a regular basis. This is basically content ranking based upon the user's Areas of Interest (AOI).
  By default the summarizer runs once a day. However you can change that by setting: passiveProfileInterval = <number of seconds> in the WebGUI config file.

• Areas of Interest Ranking
  Metadata in combination with passive profiling produces AOI (Areas of Interest) information. You can retrieve the value of a metadata property with the ^AOIRank(); and ^AOIHits(); macros.

• Show content based upon criteria
  The Wobject Proxy allows you to select content based upon criteria like:

  contenttype = sport AND source != newspaper

  You can use the AOI macro's described above in the criteria, so you can present content based upon the user's Areas of Interest. Example:
  type = ^AOIRank(contenttype);

• Display
  Metadata fields are exposed to the asset templates as their property name. So you can actually display the metadata to the rendered page using a template variable like <tmpl_var propertyname>

• Meta tags/SEO
  Since the meta data is exposed as template variables, you can use them in the Head Block of Style templates to create meta tags from meta data, including the tags from the Dublin Core standard.