Add a metadata requirement - Fluid Topics - 4.0

Fluid Topics Configuration and Administration Guide

Category
Reference Guides
Audience
public
Version
4.0

By adding one or more metadata requirements, administrators can apply a pretty URL template only to content with certain metadata.

It is possible to add more than one metadata requirement to a pretty URL template. However, Fluid Topics will only apply the template if all the metadata requirements are met.

Add a metadata requirement to a document template

The steps to add a metadata requirement to a document template are as follows:

  1. In the Pretty URL administration interface, select the Add metadata requirement button for the template in question.
  2. In the Add metadata requirement drawer, select a metadata key from the first menu and a metadata value from the second menu.
  3. Select the Save button.

Add a metadata requirement to a topic template

The steps to add a metadata requirement to a topic template are as follows:

  1. In the Pretty URL administration interface, select the Add metadata requirement button for the template in question.
  2. By default, the toggle in the Add metadata requirement drawer is set to use the book's metadata. If preferred, select the toggle to use the topic's metadata instead.
  3. Select a metadata key from the first menu and a metadata value from the second menu.
  4. Select the Save button.

Metadata hierarchy

The Fluid Topics pretty URL generator takes into account the first metadata value indicated for each metadata key. For hierarchical metadata, the generator takes into account the last value of the first branch of the hierarchy. It is currently not possible to enter multiple values for the same metadata.

Use case

A Fluid Topics administrator is configuring pretty URL templates for a portal where the documentation has three possible values for the Category metadata: Blueprint, Handbook, and Technical Notes. The administrator would like to apply the following configuration:

  • All documents where Category=Blueprint should use the template /{ft:title}/Blueprint.
  • All documents where Category=Handbook should use the template /{ft:title}/Handbook.
  • All others documents (including those where Category=Technical Notes) should use the template /{ft:title}.

The administrator configures pretty URL templates as follows:

Most specific to least specific templates