Open topic with navigation
Working with Metadata
Metadata is information about a contenttypes of content include HTML, XML Smart Forms, forms, polls, surveys, DMS documents, Office documents, multimedia, blogs, Web calandars, discussion boards, assets, and content imported from Sharepoint. item, such as its title and language. Ektron provides extensive and flexible support for metadata, which is used in both standard and innovative ways.
<title>identifies the content in the screen title, favorites list, and browser history. Creating and Deploying a Title Tag Definition
- When anyone creates a new Metadata definition, it is assigned the next available ID number. The ID numbers determine the order in which metadata definitions are arranged on the Folder properties screen’s Metadata tab. By planning ahead, you can enter metadata definitions in logical groupings, which make it more intuitive for the person assigning the metadata to pick the correct ones.
- You can use metadata as a search criterion for your website content, but the metadata definition name cannot include a space. Eliminate spaces from metadata definition names.
You define metadata in the Workarea at Settings > Configuration > Metadata Definitions, but you assign metadata in the Content area.
Only Administrator group members and those defined in the Manage Members for Role: Metadata-Admin screen can view, add, or edit metadata definitions. See also: Using the Roles Screens
Use the Add Metadata Definition screen to define metadata (such as keywords and title). You can define as many instances of metadata as you wish. If your site supports multiple languages, you create metadata definitions for each supported language.
IMPORTANT: After creating a definition, you assign it to folders, whose content uses it. See also: Assigning Metadata to a Folder
To add a metadata definition:
IMPORTANT: You can apply additional languages only when creating a metadata definition. You cannot apply them when editing.
The following definition was copied from
The META element is an extensible container for use in identifying specialized document meta-information. Meta-information has 2 main functions:
The following definition was copied from
The title should identify the contents of the document in a global context. A browser may display the title of a document in a history list or as a label for the window displaying the document.
content="document management web content management content management cms"
Searchable metadata allows content to be found by a search phrase that you add to the content’s metadata. The content is typically found by either a website search or a Workarea search.
For example, each DMSDocument Management System; Ektron's way of managing assets (Microsoft Office files and other types of files) document has a unique part number. To let site visitors and Ektron users locate the document by its part number, you need to:
NOTE: Regardless of whether this is checked, content to which this metadata value is applied can be found using the Workarea’s Search Content Folder screen > Advanced Search tab > metadata field.
Also, if you have set up an Ektron search (using the Solr or SharePoint provider), Publicly Viewable and Searchable metadata is searchable if you use property queries.
NOTE: Child folders inherit from their parent folders by default. So you only need to apply metadata to the top-level folder, not all folders beneath it. See also: Inheriting Metadata by Folder
You can set up a Web page so that whenever a source content item appears, related information appears next to it by associating the following types of content with a content item.
For example, your website sells motorcycle helmets. On a page that shows a particular helmet, the left column lists a collection of motorcycle drivers who wear that helmet. Another example might show the profile of a user when a certain content item appears.
Related content lets you connect a content item with several types of related content (see list above), and is associated with a content item, not a Web form. For example, you can display a library image of the company logo on a page whenever content in a certain folder appears. For content in a different folder, a different logo could appear.
NOTE: This capability is similar to the MetadataList Server control except that MetadataList shows a link to every content item with a selected term in the keywords or title. Also, a MetadataList is associated with a Web form (.aspx page), not a content item.
To create and deploy a related content definition:
IMPORTANT: If you are using Collection Selector type, only users with permission to work with collections can select a collection. Also, if you are using Image, Hyperlink or File Selector type, only users with permission at least read-only Library permissions can select a library item. See also: Managing Folder and Content Permissions.
If you create a metadata definition, assign it to a folder, then users apply metadata information to content, the information takes on the characteristics of the metadata definition. For example, if the metadata is title and its type is HTML tag, this is how it appears in the Web page’s source code.
If you later change its type from HTML tag to Meta, the following occur:
<meta name="title" content="CMS developer">.
NOTE: For information about metadata, see The Meta Element.
When you change the style of searchable property type metadata, Ektron attempts to maintain data stored in content that uses the definition. For example, if data style was number but you change it to text, the number stored in that metadata definition is converted to text and maintained in the content that uses it.
However, sometimes Ektron cannot maintain the data when you change the style. For example, if you change a metadata definition style from number to date, Ektron cannot convert those styles, in which case any data stored in metadata definitions is lost. Data is maintained in the following conversion scenarios; data is lost for other conversions.
When you change metadata definition's style, the screen lets you use existing data (if possible) or the default value. Following these choices is a field that lets you define a default value. If you want to replace existing data, select Use default value and enter the new value in the Default field. If the data is convertible and you want to maintain existing data if possible, select Use existing data if possible, else default. Then, enter a default value.
After you create a metadata definition, assign it to folders whose content will use it. To do that, use the folder’s properties screen's Metadata tab > Assigned boxes to assign metadata definitions to a folder.
NOTE: Only metadata definitions created for the language in which you are viewing the folder are available. Use the language drop-down to choose a language.
You can require a metadata value to be inserted before content can be saved (see the Required checkboxes in the illustration above). If applied, the requirement is enforced when content is added or edited. Also, on the Edit Content screen's Metadata tab, a required metadata field has a red label and includes an asterisk (*).
NOTE: If a default value is supplied for a required metadata field, that value is used when the content is saved. The user is not prompted to enter a value.
Each folder can inherit metadata fields from its parent folder or have a unique set of them. The information includes metadata definitions that are assigned, and which are required. For example, you could assign the top folder (Content) all metadata definitions, while you assign the Contacts folder (directly below it) none.
On every folder property’s Metadata tab, use the Inherit Parent Configuration check box to determine if metadata definitions are inherited from the parent folder or unique. By default, Inherit Parent Configuration is checked, meaning that metadata definitions are inherited. If you uncheck Inherit Parent Configuration, you can change the settings as desired.
When a user creates or updates content, he can define its metadata within the assignments specified for its folder. Default metadata values are applied without user intervention.
To enter or edit content’s metadata:
Use content tags to apply terms by which you want users to find content when the terms are not in the content. The search can use the tags to find content.
Default content tags appear on the Metadata tab of every content item. Check any tag that you want to apply to a content item. You can also create a new tag and apply it to a content item. You cannot reapply that tag to other content. The following example shows Farm, Silo, and Combine added to the content tags.
You can assign an image to any content item’s metadata from a standard field that is available to every content item; it is not a definition in the Metadata fields. Use the Image field to identify an image that can be retrieved by Ektron Markup Language’s (EkMLEktron Markup Language)
For an example of using Image data, assume that your site promotes a soccer team. A list summary shows every player on the team. Next to each player’s name is an image.
Simple Dublin Core is a set of fifteen standard names for metadata fields designed to cover the most useful items of information on a document. From the Dublin Core site FAQ: “Dublin Core metadata provides card catalog-like definitions for defining the properties of objects for Web-based resource discovery systems.” For more information, refer to the Usage Guide: Using Dublin Core.
To generate Dublin Core metadata, set the
GenerateDublinCore property to True. This creates 7 of the fifteen Dublin Core metadata fields. These fields are automatically filled with the information from the equivalent Ektron property. The following list shows the 7 fields and their Ektron equivalent. For more information on the Metadata Server Control, see the Metadata server control.
To fully comply with the Simple Dublin Core metadata element set, the administrator must create the remaining 8 Dublin Core fields as standard Ektron Metadata definitions and apply them to all Ektron folders. Next, Ektron users complete the appropriate values for each content block.
IMPORTANT: When creating Dublin Core metadata fields in the Metadata section of the Workarea, you do not need to create the first 7 fields above. In addition, the names of the fields you create must match the names in the following list. For example, in the name field, enter “DC.subject”. DC identifies it as Dublin Core metadata.
These descriptions are from the Dublin Core Metadata Initiativesite.
Open topic with navigation