A customer warns to ado a field to the properties of all existing and new assets in AEM Assets to capture the asset rating. After the team uploads an asset the review team needs to go through the uploaded assets and fill ta the ratings. How should the Business Practitioner meet this requirement?

The requirement is to add a new field to the properties page for all assets, which can be filled in by a review team. The Metadata Schemas tool in AEM Assets is specifically designed for this purpose. It allows administrators to define the layout and the fields (including custom ones like "asset rating") that appear on an asset's properties page. Once the schema is created or edited to include the new field, it can be applied to folders. Assets within those folders will then display this new field on their properties page, making it available for the review team to edit.

B. Create a new schema with the rating property via the Folder Metadata Schemas tool This tool is used to define metadata properties for folders, not for the assets contained within them.
C. Build a new profile with the rating property for assets via the Metadata Profiles tool Metadata Profiles are used to automatically apply default metadata values to assets upon upload, not to add new fields to the properties user interface.
D. Create a new profile with the rating property via the image Profiles tool Image Profiles are used to automate the creation of different image renditions (e.g., different sizes or crops) and are unrelated to metadata fields.

1. Adobe Experience Manager as a Cloud Service Documentation, "Metadata schemas." This document states, "Experience Manager Assets lets you create metadata schemas for assets, which define the layout and metadata displayed in asset properties pages. ... The metadata schema editor lets you add or edit a form tab and the form items within a tab." This directly confirms that schemas are used to add fields to the properties UI.

2. Adobe Experience Manager as a Cloud Service Documentation, "Metadata profiles." This source clarifies the function of profiles: "A metadata profile lets you apply default metadata to assets within a folder. Create a metadata profile and apply it to a folder. Any asset that you subsequently upload to the folder inherits the default metadata that you configured in the metadata profile." This shows profiles are for applying values, not creating the fields themselves.

3. Adobe Experience Manager as a Cloud Service Documentation, "Folder metadata schema." This document specifies the tool's purpose: "Adobe Experience Manager Assets lets you create metadata schemas for asset folders, which define the layout and metadata displayed in folder properties pages." This distinguishes it from schemas for assets.