KB Version:

Page Navigation

Related Links

Learning Levels

Most Read

Metadata

Digest

Metadata is data within the CMS that describes an Asset. Common fields such as title, summary, or keywords provide quick information about the content contained inside of a particular Asset. Because the system manages all assets as XML, the Metadata that a user enters for Assets can be used for display purposes on site pages. When used in conjunction with Index Blocks, an XSLT format can be applied to the Metadata to create common HTML content listings such as a listing of recent press releases including the title and a quick summary of the press release content. Cascade Server uses two types of Metadata – wired and dynamic.

Concept

Wired Metadata Fields

"Wired" Metadata fields are the default fields that are included with Cascade. They include:

  • Display Name - the short name of the Assets, distinct from the system name that is displayed on the left hand navigation

  • Title - the title of the Asset
     
  • Summary - the synopsis of the Asset
     
  • Teaser - a short enticing phrase about the Asset
     
  • Keywords - words or phrases about the Asset
     
  • Description - the description of the Asset
     
  • Author - the person or organization responsible for the Asset
     
  • Review Date - an optional Date/Time chooser; this field specifies the date and time the content to be reviewed in a workflow.
     
  • Start Date - an optional Date/Time chooser; this field specifies the date and time the content should "go live". Publishable assets will not be eligible for publishing (even if the "Include when publishing" option is enabled for the asset) until after the Start Date.
     
  • End Date - an optional Date/Time chooser; this field specifies the date and time the content should no longer be public.

    At the End Date, the asset is moved to the Expiration Folder, if specified, and "Include when publishing" and "Include when indexing" options are turned off for publishable assets. Lastly, if system email is configured, an expiration notice will be sent to the user that last modified the asset. If that user no longer exists, the expiration notice will be sent to the user that created the asset. If neither user can be found, no expiration notice is sent.
     
  • Expiration Folder - an optional Folder chooser; this field specifies which Folder in Cascade the content should be moved to upon reaching the End Date.

Display Name, Title, Summary, Teaser, Keywords, Description, and Author are all free-form text fields.

Dynamic Metadata Fields

Dynamic metadata fields are custom fields that can be created by an administrator and can include:

  • custom text fields
  • custom drop down boxes with an optional preset default value
  • custom radio button options with an optional preset default value
  • custom check box options with an optional preset default value
  • custom multi-select options with optional preset default values

Dynamic Metadata fields are especially effective in allowing users to filter specific assets via Formats based on the Metadata values that describe them. For example, a user could tag a particular Asset with Metadata that places that Asset into a certain category that could then be referenced in a Format.

FAQs

  • Does Cascade Server include Metadata for content?
  • How do I access the metadata of the page I'm currently on?

Technical

Adding Metadata

Metadata offers additional information about an Asset (e.g. a page) that helps to classify or describe the Asset.

Metadata may be viewed on any Asset by selecting the Asset and clicking the Properties tab.

To edit Metadata for any Asset:

  1. Select the desired Asset and click Edit on the action bar.

  2. Select the Metadata tab.

  3. Adjust the Metadata as desired

  4. Either click Submit to save and close the Asset, or select another tab to continue editing.

m

m2

Although an Administrator has the ability to change which Metadata is shown and add customized Metadata fields, here are the default Metadata fields for each Asset:

  • Display Name - The short name of the Assets (typically four or less words).

  • Title - The title of the Asset.

  • Summary - The synopsis of the Asset.

  • Teaser - A short enticing phrase about the Asset.

  • Keywords - Words or phrases about the Asset.

  • Description - The description of the Asset.

  • Author - The person or organization responsible for the Asset.

  • Review Date - The date and time for the content to be reviewed with a respective workflow.

  • Start Date - The date and time the content should be made public.

  • Expiration Date - The date and time the content should no longer be made public.

  • Expiration Folder - The folder that the content should be moved to upon reaching the expiration date.

*Note- Depending on the settings selected by the Administrator, certain Metadata fields may appear in-line with the WYSIWYG editor.

Metadata and Metadata Sets (Administrators and Managers)

metadata set A Metadata Set is a system Component that provides the interface for customizing the kinds of Metadata fields that can be visible and/or associated with an Asset. Since Metadata fields can be broken into two categories, wired and dynamic, Metadata Sets allow Administrators to choose which wired fields can be made visible to end users and which ones will be turned off. Likewise, the interface allows for dynamic fields to be created that help to further describe an Asset beyond the scope of what regular wired fields allow.

Metadata sets also allow for Administrators to customize the wired and dynamic Metadata fields so that they appear "inline" in the editing interface for an asset instead of appearing in the Metadata pane, making the fields more accessible to end users. Additionally, fields can be set to 'required' so that end users must enter acceptable values for Metadata before saving the Asset.

For more information on Metadata Sets and their construction, please see our Metadata Set page.

An Extensive Look at the Review Date Field

The review date is the date and time for the page to be submitted into a workflow associated with the field.

When the review date approaches, if the Asset is not workflow enabled, then nothing will happen. However, if the Asset is workflow enabled, then the CMS will go through all of the workflows associated with the Asset's parent folder and use the first "Edit Workflow" found. If no workflow is found in the parent folder and the parent folder has "Inherit Workflows" option enabled, then all ancestor folders will be searched until an "Edit Workflow" is found. This is an unordered option. There is currently no ordered option.

  • If a workflow is found, then a new one should be created under the user who last modified the Asset. If that user does not exist, then the workflow should be created under the user who created the Asset. If that user does not exist, then nothing will happen.
  • If no workflow is found, then nothing will happen.

    It is important to note, while folders are enabled to have workflows, they cannot be entered into one. A review date can be assigned, however, upon attempting to create a workflow, an error will display.

Related Links

Related Videos