A selected list of terms used in the Cascade CMS for University of Houston web pages.
within the Cascade CMS an asset represents "any entity within the system that can be used to generate content."
Commonly used assets include: Folder, Page, File, Block, Dynamic/Symbolic External Link. Folder, Page, and File assets will be Published to a server as static entities, and so the system names for these assets need to follow UH filenaming conventions.
a dynamically tracked association between two assets within a site, created by using a Chooser from one of the CMS editing dialogs.
Internal Links will be translated into hyperlinks using actual web addresses in the page's source code once the CMS creates the actual PHP webpage - which only happens during a publishing step, when a web page file is actually created and written to a server location. Prior to publishing, CMS page type assets are basically comprised of a collection of instructions to the CMS on how to build that final web page file and on what will be included in its contents.
a hyper link created by using a specific URL string to define the link, and which the CMS does not update dynamically (e.g. web address such as http://www.uh.edu/ and which is typed into or pasted into an external link text field, as with the Insert/Edit Link dialog; or, may also be any text-string web address used elsewhere, such as a path in an included script or a manually written anchor tag in the HTML Editor, etc.).
(n) asset name (aka system name) of the single default page for menu-enabled "Folder with [Page-type]" assets.
(v) function within the CMS whereby enabled assets share system metadata with the CMS; aka 'indexing'.
This metadata sharing supports:
- automated navigational element builds (e.g. Left Nav Menu);
- Article Listing type page content (e.g. News Listing);
- Related Links Sets' link text for internally linked assets.
See also metadata / metadata set[s] discussion.
metadata / metadata set[s]
a standard set of information about each asset which is stored in the CMS database for each asset, whether it is actively used or not; see also 'index / indexing'
The basic metadata for every asset can include a(n):
- Display Name*
- Start Date
- End Date
- Expiration Folder
- Review Date.
Metadata sets may also include additional custom data which has been defined by CMS admin users for specific uses.
An asset's existing metadata assignments can be reviewed by selecting the asset and then clicking the Details button. The Details >> Info panel can be expanded to show all metadata categories.
For page and folder assets, editors have control over the textual content of, and/or the settings for, the metadata which is used in:
- dynamic site navigation: Folder Titles of pages included in left nav menus;
- internal linking: Display Names can provide link's text, for internally-linked assets;
- the building of the final published webpage[s]:
- Page Titles feed text to the Browser window title tab/bar;
- Page Display Names are used for standard webpages' main headlines;
- Search engine optimization (Summary, Teaser, Keywords, and Description metadata for pages inform search results; and can provide on-page text for dynamic features such as news articles and listings);
- asset management:
Start Date; End Date; Expiration Folder; Review Date.
- asset tree: User 'Appearance of Asset Links' Setting determines whether items in the asset tree will be shown using their Title metadata, or their system-names (aka asset name).
* The most critical categories of metadata include the Title, Display Name, and Description. Thus, Editing fields for these items may appear at the top of the Edit >> Content panel for greater prominence, even though the rest of the categories in the Metadata Set appear on the Edit >> Metadata panel itself.
synchronize, synchronizing your site
Any publishing from the CMS which includes all the areas of a site which are affected by any change/edit within the CMS (including multiple changes or edits) is considered to be "synchronizing" your CMS site with the version of the site which has been written to a server location - whether those materials are published only to Staging, or whether they may also be published to a Live site.
The CMS allows users to take advantage of dynamic features, such as: automatic updating of an entire area's left nav menus based on an editor changing the title metadata for just one folder within that area. However, any dynamically propagated changes would still need to be published for those changes to be seen by anyone without access to the CMS site. It is especially important to be aware of the scope of any dynamic updates propagated within the CMS, so the appropriate material can be synchronized with the material on the server.
equivalent to an Asset Name, and distinct from an asset's Title or Display Name metadata. The system name for any publishable asset determines that material's filename upon being written to the server, thus it is important that system names follow UH server file naming conventions. System names in general should be all lower-case with no spaces and with individual words separated by dashes.
Because system names are dynamically tracked within the CMS, a system name can only be changed by using a Rename dialog; while editing, see your More button options with the asset selected.
Warning: do not change a page asset's system name from "index" to something else without a specific reason for doing so, as CMS navigation-building-defaults expect pages to retain the system name of "index."
The system name for a folder asset will be used as the proximal segment of its child page's web address
(e.g. for this page: http://www.uh.edu/infotech/services/web-services/cms/cms-how-tos/cms-glossary/index.php);
and that folder's direct line of ancestor folders, back to the site's home folder, will also typically be represented, respectively, as segments in the address. For sites on the UH website, the UH home location would typically begin the address.