Documentation Center

Declaring metadata using TriDK XML Setup

You can use the TriDK XML Setup tool to declare metadata.

TriDK metadata organization

The underlying relational database structure of Content Manager requires that customer specific metadata is added in a specific manner and order.

Content Manager uses CardTypes to define a number of objects types for its core business logic. TriDK XML Setup does not allow you to create, update or delete CardTypes however, it is possible to add or remove Fields to or from CardTypes. For example, you can add the field, Manual Type, to the logical level of a topic.

  • Before a Field can be added to a CardType, it has to be created.
  • Some Fields contain a set of predefined values called List of Values (LOV).
    • Before a Field that contains an LOV can have values assigned to it, the LOV object has to be created.
    • Once the LOV object exists, individual values can be assigned or removed from it.
    • The LOV object can be assigned to a particular Field.

Naming convention

While declaring customer specific metadata in Content Manager, you often need to provide a unique identifier for the object that you declare, this is the element name. The element name is the unique identifier that is used when coding Content ManagerActive Server Pages (ASPs) and in Web Services API calls.

The following naming convention should be respected:
TypeNaming Convention
List of Values (LOV)"D" + [element name LOV]
Values inside an LOV"V" + [element name LOV] + [element name value]
Content Manager-specific field"FISH" + [element name field]
Customer-specific field"F" + [element name field]