Asset Archive
Digest
When a publishable Asset (Page, File, or Folder) passes its expiration date as specified in its metadata, it will be archived. The archival process involves two steps:
- The asset will be unpublished (removed from the remote server),
- The asset will be moved in the CMS to the Expiration Folder (as defined in the asset’s metadata)
If no expiration folder is specified, the asset will still be un-published; however, it will not be moved in the CMS.
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.