You're viewing help content for version:
- 6.5
- 6.4
- 6.3
- Older Versions
When capturing the metadata information of an asset, users provide information in the various available fields. You can display specific metadata fields or field values that are dependent on the options selected in the other fields. Such conditional display of metadata is called cascading metadata. In other words, you can create a dependency between a particular metadata field/value and one or more fields and/or their values.
Use metadata schemas to define rules for displaying cascading metadata. For example, if your metadata schema includes an asset type field, you can define a pertinent set of fields to be displayed based on the type of asset a user selects.
Here are some use cases for which you can use and define cascading metadata:
- Where user location is required, display relevant city names based on the user's choice of country and state.
- Load pertinent brand names in a list based on the user's choice of product category.
- Toggle the visibility of a particular field based on the value specified in another field. For example, display separate shipping address fields if the user wants the shipment delivered at a different address.
- Designate a field as mandatory based on the value specified in another field.
- Change options displayed for a particular field based on the value specified in another field.
- Set the default metadata value in a particular field based on the value specified in another field.
Consider a scenario where you want to display cascading metadata based on the type of asset that is selected. Some examples
- For a video, display applicable fields such as format, codec, duration, and so on.
- For a Word or PDF document, display fields, such as page count, author, and so on.
Irrespective of the asset type chosen, display the copyright information as a required field.
-
Key-values pairs are the options provided to a form-user. You can provide the key-value pairs either manually or from a JSON file.
- To specify the values manually, select Add Manually, and tap/click Add Choice and specify the option text and value. For example, specify Video, PDF, Word, and Image asset types.
- To fetch the values from a JSON file dynamically, select Add Through JSON Path and provide the path of the JSON file. AEM fetches the key-value pairs in the real time when the form is presented to the user.
Both options are mutually exclusive. You cannot import the options from a JSON file and edit manually.
Note:
When you add a JSON file, the key-value pairs are not displayed in the metadata schema editor but are available in the published form.
-
Under Requirement, choose the Required, based on new rule option.
Tap/click Add Rule and choose the Asset Type field to create a dependency. Also, choose the field value upon which to create the dependency. In this case, choose Video. Tap/click Done to save the changes.
Note:
Dropdown with manually predefined values can be used with rules. Dropdown menus with configured JSON path can't be used with rules that use predefined values to apply conditions.
-
Under Visibility, choose the Visible, based on new rule option.
Tap/click Add Rule and choose the Asset Type field to create a dependency. Also, choose the field value upon which to create the dependency. In this case, choose Video. Tap/click Done to save the changes.
Note:
Tapping/clicking anywhere on the UI other than values resets the values. In this case, select the values again.
Note:
You can apply Requirement condition and Visibility condition independent of each other.
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.