Metadata Schemas

Søg
Experience Manager 6.2 Assets Brugerhåndbog

På denne side

Gælder for: Experience Manager 6.2 Assets

某些 Creative Cloud 应用程序、服务和功能在中国不可用。

Du får vist hjælpeindhold for version:

A metadata schema describes the properties, layout, and so on for the Properties page of an asset in Adobe Experience Manager (AEM) Assets Brand Portal. The schema that you apply to an asset determines the metadata fields that appear on its Properties page.

Normally, the Properties page for each asset includes default metadata properties depending upon the MIME type of the asset. To include more metadata properties or modify existing properties, edit the Metadata Schema Forms editor, which defines the properties and layout of the Properties page. You can also use a different Metadata Schema form for assets of a particular MIME type to enable their Properties pages to conform to a specific layout.

chlimage_1

  1. In the Properties page, click the Edit icon.

    chlimage_1

    When you modify a metadata schema for a certain MIME-type of assets, the layout for the current MIME-type and all asset subtypes are modified. For example, modifying a jpeg schema under default/image only modifies the metadata layout (asset properties) for the IMAGE/JPEG MIME-type of assets. However, if you edit the default schema, your changes modify the metadata layout for all types of assets.

  2. To view a list of forms/templates, click Tools > Metadata Schemas from the rail.

    Brand Portal provides the following templates out of the box:

    • default: This is the base form for assets. Every asset uses this template.
              The following child forms inherit the properties of the default form:
                i. image: Schema form for assets with the MIME type "image", for example, image/jpeg,image/png, and so on.
                    The "image" form has the following child form templates:
                    a. jpeg: Schema form for assets with sub type jpeg.
                    b. tiff: Schema form for the assets with sub type tiff.
     
                ii. application: Schema form for assets with MIME type "application", for example application/pdf, application/zip, and so on.
                    a. pdf: Schema form for assets with sub type pdf.
     
               iii. video: Schema form for assets with MIME type "video", such as video/avi, video/mp4, and so on.
    • bulkview: This form defines the template used for Bulk Metadata editing. 
              To use Bulk Metadata Editing, select multiple assets from the Brand Portal user interface.

  3. Click the View Properties icon.

    chlimage_1

Bemærk:

To view the child forms of a schema form, click the schema form name.

Adding A Metadata Schema Form

  1. To add a custom template to the list, click the Add icon and create the custom form. 

    chlimage_1

    Bemærk:

    Unedited templates have a Lock icon before them. If you customize any of the templates, the Lock icon before the template disappears.

  2. Enter the title of the Schema form, and then click Submit to complete the form creation process.

Editing Metadata Schema Forms

You can edit a newly-added or existing metadata schema form. The metadata schema form contains content derived from it's parent, including:

  • Tabs 
  • Form items within tabs.

You can map/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.

  1. In the Schema Editor user interface, select the check box before a form and then click the Edit icon on the toolbar.

    chlimage_1

  2. In the Edit Form page, customize the Properties page of the asset by dragging one or more components from a list of component types in the Build Form tab to the Basic tab.

    chlimage_1

  3. To configure a component, select it and modify its properties in the Settings tab.

 

 

Components within the Build Form tab

The Build Form tab lists form items that use 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: 

Component Name Description
Section Header  Add a section heading for a list of common components.
Single Line Text  Add a single line text property. It is stored as a string.
Multi Value Text  Add a multi value text property. It is stored as a string array.
Number  Add a number component.
Date  Add a date component.
Dropdown  Add a dropdown list.
Standard Tags  Add a tag. 
Hidden Field  Add a hidden field. It is sent as a POST parameter when the asset is saved.
Asset Referenced By  Add this component to view list of assets referenced by the asset.
Asset Referencing  Add to display a list of assets that reference the asset.
Products References  Add to show the list of products linked with the asset.

Editing 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.

 

Field Label: The name of the metadata property that is displayed on the asset's Properties page.

Map to Property: The value of this property provides the relative path/name to the asset node where it is saved in the CRX repository. It starts with "./" because indicating that the path is under the asset's node.

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 configure these properties on view properties, we recommend that you mark them as Disable Edit, because they are protected. Otherwise, the error "Asset(s) failed to modify" occurs when you save the asset's properties.

Placeholder: Use this property to provide the user any relevant information regarding the metadata property.

Required: Use this property to mark a metadata property as mandatory on the Properties page.

Disable Edit: Use this property to make a metadata property uneditable on the Properties page.

Show Empty Field In Read Only: Mark this property to display a metadata property on the Properties page even if it has no value. By default, when a metadata property has no value, it is not be listed on the Properties page.

Description : Use this property to add a short description for the metadata component.

Delete icon Click this icon to delete a component from the schema form. 

chlimage_1

Bemærk:

Only the Hidden Field component does not have the attributes Map to Property, Placeholder, Required, Disable edit and Show Emplty Field in Read Only properties. It has the attributes Name, Value, Field Label, and Description. The values for the Hidden Field component are sent as a POST parameter whenever the asset is saved. It is not be saved as metadata for the asset.

Adding/deleting a tab in the schema form

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

chlimage_1

Click + to add a new tab on a schema form. By default, the new tab has the name "Unnamed-1." You can modify the name from the Settings tab. 

Click X to delete a tab.

chlimage_1

Deleting Metadata Schema Forms

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.

chlimage_1

Bemærk:

After you delete custom changes to a default form, the Lock icon reappears before it on the Metadata Schema interface to indicate that the form reverted to its default state.

Schema 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. Create a new form under the appropriate form type. For example, to add a new template for the image/png subtype, created 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

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:

Name Type Value
exposedmimetype String image/jpeg
mimetypes String[] image/png

exposedmimetype: Name of the existing form to be mapped 

mimetypes: List of MIME types that use the form defined in the exposedmimetype attribute

Brand Portal maps the following MIME types and schema forms:

Schema Form MIME type(s)
image/jpeg image/pjpeg
image/tiff image/x-tiff
application/pdf application/postscript
application/x-ImageSet Multipart/Related; type=application/x-ImageSet
application/x-SpinSet Multipart/Related; type=application/x-SpinSet
application/x-MixedMediaSet Multipart/Related; type=application/x-MixedMediaSet
video/quicktime video/x-quicktime
video/mpeg4 video/mp4
video/avi video/avi, video/msvideo, video/x-msvideo
video/wmv video/x-ms-wmv
video/flv video/x-flv

Here is the list of default metadata properties:

  • jcr:content/metadata/cq:tags
  • jcr:content/metadata/dc:format
  • jcr:content/metadata/dam:status
  • jcr:content/metadata/videoCodec
  • jcr:content/metadata/audioCodec
  • jcr:content/metadata/dc:title
  • jcr:content/metadata/dc:description
  • jcr:content/metadata/xmpMM:InstanceID
  • jcr:content/metadata/xmpMM:DocumentID
  • jcr:content/metadata/dam:sha1
  • jcr:content/metadata/dam:solutionContext
  • jcr:content/metadata/videoBitrate
  • jcr:content/metadata/audioBitrate
  • jcr:content/usages/usedBy
  • jcr:content/jcr:lastModified
  • jcr:content/metadata/prism:expirationDate
  • jcr:content/onTime
  • jcr:content/offTime
  • jcr:content/metadata/dam:size
  • jcr:content/metadata/tiff:ImageWidth
  • jcr:content/metadata/tiff:ImageLength

Granting Access To Metadata Schemas

The Metadata Schema feature is available to administrators only. However, administrators can provide access to non administrators by modifying some permissions.

The non administrator should have Create, Modify, and Delete permissions on the /apps folder.