KB Version:

Page Navigation

Related Links

Learning Levels

Most Read

Announcements RSS Feed of Announcements

Asset Archive

Digest

When an asset with metadata (page, file, folder, block or Symlink) passes its expiration date as specified in its metadata, it will be archived. The archival process involves three steps:

  1. The asset will be moved in the CMS to the Expiration Folder (as defined in the asset's metadata).
  2. The asset will no longer be indexed by index blocks.
  3. Publishing of publishable assets (page, file or folder) that occurs after the designated expiration date will no longer include the asset.  It is important to note that the asset will not be unpublished from the remote server.

If no Expiration Folder is specified, the asset will not be moved when the expiration date is passed but it will stop being indexed by all index blocks and will no longer be included in the publishing after the expiration date (see #2 and #3 above) .

Concept

Asset Archive Details/Location

The location for storing outdated content is entirely at the manager/administrator’s discretion. Specific folders can be set up to house recently expired content and keep it accessible, and content can be moved to a deeper directory after a designated holding period.

Technical

Setting Up Asset Archiving

To set up archiving so that your old content appears to expire (even though it's not unpublished), set up a publish set that will publish the pages that link to that asset on a schedule.  For example:

        - A news article's expiration date is reached.

        - The news article is linked from the "news index" page and the "top stories" page.

        - The links to articles from those two pages are coming from index blocks.

        - The article that has expired is no longer indexable, so when the "news index" and "top stories"          pages are published, it will not provide a link to that article anymore, making it inaccessible.

Using the "Expiration Date" (setting to an asset to not index and publish) and setting the expiration folder results in creating an automated archive that will not allow you to publish or index the content.  This archive would exist and be viewable in Cascade Server but would not be accessible from the live site.

Related Links