Use the metadata schema form use-the-metadata-schema-form

A metadata schema describes the layout of the Properties page and the metadata properties displayed for assets that use the particular schema. The schema that you apply to an asset determines the metadata fields that appear on its Properties page.

The Properties page for each asset includes default metadata properties depending upon the MIME type of the asset. Administrators can use the Metadata Schema Editor to modify existing schemas or add custom metadata schemas. Experience Manager Assets Brand Portal provides default forms for assets of various MIME types. However, you can also add custom forms for such assets.

Add a metadata schema form add-a-metadata-schema-form

To create a new metadata schema form, do the following:

Edit a metadata schema form edit-a-metadata-schema-form

Any added or existing metadata schema form can be edited. The metadata schema form contains content derived from its parent, including tabs and form items within tabs. You can map or configure these form items to a field within a metadata node.

You can add new tabs or form items to the metadata schema form. The derived tabs and form items (from the parent) are in the locked state. You cannot alter them at the child level.

To edit a metadata schema form, do the following:

Components in the Build Form tab components-in-the-build-form-tab

The Build Form tab lists items that you can use in your schema form. The Settings tab provides the attributes of each item that you select in the Build Form tab. The following table lists the form items available in the Build Form tab:

Edit the metadata component edit-the-metadata-component

To edit the properties of a metadata component on the form, click the component and edit its properties in the Settings tab.

The following are the valid values for this property:

– ./jcr:content/metadata/dc:title: Stores the value at the asset’s metadata node as the property dc:title.

– ./jcr:created: Displays the jcr property at the asset’s node. If you configured these properties on view properties, Adobe recommends that you marked them as Disable Edit, because they are protected. Otherwise, the error “Assets failed to modify” occurs when you save the asset’s properties.

Add or delete a tab in the schema form add-or-delete-a-tab-in-the-schema-form

The default schema form includes the Basic and Advanced tabs. The schema editor lets you add or delete a tab.

Apply a metadata schema to a folder apply-a-metadata-schema-to-a-folder

Brand Portal lets you customize and control the metadata schema so that the Properties page of an asset displays only the specific information you choose to reveal. To control the metadata displayed in the Properties page, remove the required metadata from the metadata schema form and apply it to the specific folder.

To apply a metadata schema form to a folder, do the following:

Delete a metadata schema form delete-a-metadata-schema-form

Brand Portal lets you delete custom schema forms only. It does not let you delete the default schema forms/templates. However, you can delete any custom changes in these forms.

To delete a form, select a form and click the Delete icon.

Schema forms for MIME TYPES schema-forms-for-mime-types

Adding new forms for MIME types adding-new-forms-for-mime-types

In addition to the default forms, you can add custom forms for assets of various MIME types, or create a new form under an appropriate form type. For example, to add a new template for the image/png subtype, create the form under the “image” forms. The title for the schema form is the subtype name. In this case, the title is “png.”

Using an existing schema template for various MIME types using-an-existing-schema-template-for-various-mime-types

You can use an existing template for a different MIME type. For example, use the image/jpeg form for assets of MIME type image/png.

In this case, create a new node at /etc/dam/metadataeditor/mimetypemappings in the CRX repository. Specify a name for the node and define the following properties:

Brand Portal maps the following MIME types and schema forms:

The following is a list of default metadata properties: