Text Field
A Metadata Text Field allows the user to enter text into the field. An example of a Text Field may be a Description field.
Bookmarks to the headings on this page:
Details Screen
The Details screen allows you to configure the settings for the Metadata Text Field.
Details
This section allows you to change various details to do with the Text Field. The Details section of the Details screen is shown in the figure below.
The Details section of the Details screen for a Text Field
This fields available are as follows:
-
Field Name: by default, the name that was entered when this field was created will appear in this field. You can change the name of the field by clicking into this field and entering the new name.
Tip: You should choose a name for your field that is unique across all Metadata Schemas in your system.
- Friendly Name: enter a friendly name for the field. This will be displayed as the field name on the Metadata screen of an asset. If the name of the field is complicated or does not reflect what should be entered, you may want to enter a Friendly Name. For example, if you have named your field DC.Keywords, you may want the label on the Metadata screen to show Keywords instead.
- Description: enter a description for the field. This will be displayed on the Metadata screen of an asset. It can be used to display instructions to your users about how to enter a sensible value into the metadata field. For example, if your field is called Description you may wish to enter a description Please enter a brief description about the content of your page.
- Default: enter a default value for the field. This will appear on the Metadata screen of an asset. A user can then override the default value for the asset. You can enter free text into this field as well as keyword replacements. For more information on how to use the keyword replacements, refer to the Using Keyword Replacements on the Details screen of a Metadata field section below.
- Scheme: enter the industry standard scheme for this field, for example AGLS. This will be placed in the HTML source code of a page.
- Language: enter the language for this field, for example English. This will be placed in the HTML source code of a page.
Value Components
Value Components allow you to define a structure for the value of your field. The Value Components section of the Details screen is shown in the figure below.
The Value Components section of the Details screen
The Dublin Core field DC.Creator has the following structure:
<META NAME="DC.Creator" CONTENT="corporateName=MyCorporateName; jurisdiction=MyJurisdiction; email=MyEmail; address=MyAddress">
You can represent this structure through the use of this field. To do this you would create a field in the Metadata Schema called DC.Creator. In the Value Components section for that field you would then add the components corporateName, jurisdiction, email and address, as shown in the figure below.
Value Components for a Text Field
The user will then be able to enter a value for each component on the Metadata screen of an asset.
The fields that available are as follows:
- New?: enter the name of the new component that you want to add and click Commit. The component will then be added to the Current section, as shown in the figure above.
- Current: this section shows the components that have been added to this field. By default, the name that was entered when the component was created will appear in the first box. You can change the name of the field by clicking into this field and entering the new name. The second box allows you to enter a default value for the component. If you want to delete a component, check the Delete box and click Commit.
Options
This section allows you to change the options for this field. The Options section of the Details screen of a Text Field is shown in the figure below.
The Options section
The fields available are as follows:
- Editable: select whether or not this field should be editable on the Metadata screen. If you have entered a default value that you do not want your users to override, you can change this option to No and the field will not be editable.
- Multi Line: select whether or not to make this field a multi-line field. If the user is going to enter a lot of information, for example a description of the page, you may want to make it a multi-line box.
- Required: select whether or not this field is a required field. If you select Yes, the assets that have this Metadata Schema applied to it will not be able to go Live until a value has been entered into this field.
- Contextable?: select whether or not this field is context-aware. If you select Yes, this field will be allowed to take a different value for each context within the system. The default value of this field can also be set individually for each context. For more information, refer to the Contexts manual.
-
Show On Frontend: select whether or not to show this field in the HTML source code of a page. The options you can select from include:
- Always: select this option to always show this field in the HTML source code of a page.
- Only if Filled: select this option to only show this field in the HTML source code of a page if it has been filled in.
- Never: select this option to never show this field in the HTML source code of a page.
- Character Limit: enter the maximum number of characters that a user can enter into this metadata field on the Metadata screen. By default this value is 0 meaning that there is no limit.
- Width: enter the width of the Text Field to be displayed on the Metadata screen. By default, this value is 30.
- Height: enter the number of rows for the field. By default, this value is 7 meaning that the field on the Metadata screen will be seven rows. This value will only be used if the Multi Line field is set to Yes.