Adobe Experience Manager Assets keeps metadata for every asset. It allows easier categorization and organization of assets and it helps people who are looking for a specific asset. With the ability to extract metadata from files uploaded to Experience Manager Assets, metadata management integrates with the creative workflow. With the ability to keep and manage metadata with your assets, you can automatically organize and process assets based on their metadata.
Metadata means data about data. In this regard, data refers to your digital asset, say an image. Metadata is critical for efficient asset management.
Metadata is the collection of all the data available for an asset but that is not necessarily contained in that image. Some examples of metadata are:
The above are the basic metadata properties that Experience Manager can manage for assets, which allows users to see all assets. For example, ordering assets by last modification date is useful when trying to discover recently added assets.
You can add more high-level data to digital assets, for example:
More metadata helps you further categorize assets and is helpful as the amount of digital information grows. It is possible to manage a few hundred files based on just the filenames. However, this approach is not scalable. It falls short when the number of people involved and the number of assets managed increase.
With the addition of metadata, the value of a digital asset grows, because the asset becomes,
For these reasons, Assets provides you with the right means of creating, managing, and exchanging metadata for your digital assets.
The two basic types of metadata are technical metadata and descriptive metadata.
Technical metadata is useful for software applications that are dealing with digital assets and should not be maintained manually. Experience Manager Assets and other software automatically determine technical metadata and the metadata may change when the asset is modified. The available technical metadata of an asset depends largely on the file type of the asset. Some examples of technical metadata are:
Descriptive metadata is metadata concerned with the application domain, for example, the business that an asset is coming from. Descriptive metadata cannot be determined automatically. It is created manually or semi-automatically. For example, a GPS-enabled camera can automatically track the latitude and longitude and add geotag the image.
The cost of manually creating descriptive metadata information is high. So, standards are established to ease the exchange of metadata across software systems and organizations. Experience Manager Assets supports all relevant standards for metadata management.
There are various ways to embed metadata in files. A selection of encoding standards are supported:
Extensible Metadata Platform (XMP) is an open standard that is used by Experience Manager Assets for all metadata management. The standard offers universal metadata encoding that can be embedded into all file formats. Adobe and other companies support XMP standard as it provides a rich content model. Users of XMP standard and of Experience Manager Assets have a powerful platform to build upon. For more information, see XMP.
Data stored in these ID3 tags is displayed when you play back a digital audio file on either your computer or a portable MP3 player.
ID3 tags are designed for the MP3 file format. Additional information on formats:
Exchangeable image file format (Exif) is the most popular metadata format used in digital photography. It provides a way of embedding a fixed vocabulary of metadata properties in many file formats, such as JPEG, TIFF, RIFF, and WAV. Exif stores metadata as pairs of a metadata name and a metadata value. These metadata name-value-pairs are also called tags, not to be confused with the tagging in Experience Manager. Modern digital cameras create Exif metadata and modern graphics software support it. Exif format is the lowest common denominator for metadata management especially for images.
A major limitation of Exif is that a few popular image file formats such as BMP, GIF, or PNG do not support it.
Metadata fields defined by Exif are typically technical in nature and are of limited use for descriptive metadata management. For this reason, Experience Manager Assets offers mapping of Exif properties into common metadata schemata and into XMP.
Other metadata that can be embedded from files include Microsoft Word, PowerPoint, Excel, and so on.
Enterprise Manager Assets lets you edit the metadata of multiple assets simultaneously so you can quickly propagate common metadata changes to assets in bulk. Use the Properties page to change metadata properties to a common value or add or modify tags. To customize the metadata Properties page, including adding, modifying, deleting metadata properties, use the Schema editor.
The bulk editing methods work for assets available in a folder or a collection. For the assets that are available across folders or match a common criteria, it is possible to bulk update the metadata after searching.
Navigate to the location of the assets that you want to edit.
Select the assets for which you want to edit common properties.
From the toolbar, tap/click Properties to open the Properties page for the selected assets.
When you select multiple assets, the lowest common parent form is selected for the assets. In other words, the Properties page only displays metadata fields that are common across the Properties pages of all the individual assets.
Modify the metadata properties for selected assets under the various tabs.
To view the metadata editor for a specific asset, deselect the remaining assets in the list. The metadata editor fields are populated with the metadata for the particular asset.
To select a different metadata schema for the assets, tap/click Settings from the toolbar, and select the desired schema. Save the changes.
To append the new metadata with the existing metadata in fields that contain multiple values, select Append mode. If you do not select this option, the new metadata replaces the existing metadata in the fields. Tap/click Submit.
For single-value fields, the new metadata is not appended to the existing value in the field even if you select Append mode.
Assets as a Cloud Service can generate custom metadata for an asset using cloud-native services. Configure a processing profile to generate custom metadata. See how to use processing profile.
Only one processing profile can be applied to a folder. To apply multiple processing to assets in a folder, add more options to a single processing profile. For example, a single profile can generate renditions, transcode assets, generate custom metadata, and so on. You can apply MIME type filters for each task so that the appropriate task is triggered for the required file format.
Metadata schemas are predefined sets of metadata property definitions that can be used in various applications. Properties are always associated with an asset, meaning that the properties are ‘about’ the resource.
You can also design your own metadata schemata if none exists that meet your needs. Do not duplicate existing information. Within an organization, separating schemata makes it easier to share metadata. Experience Manager provides you with a default list of the most popular metadata schemata. The list helps you to jumpstart your metadata strategy and quickly pick the metadata properties that you need.
The supported metadata schemata supported are listed below.
iptc4xmpExt- International Press Communications Standard contains many subject-specific metadata.
xmpBJ- Basic Job Ticketing.
The application-specific metadata includes technical and descriptive metadata. If you use such metadata, other applications may not be able to use the metadata. For example, a different image-rendering application may not be able to access Adobe Photoshop metadata. You can create a workflow step that changes an application-specific property to a standard property.
xmpPlus- Integration of PLUS with XMP.
xmpPG- XMP metadata for paged text.
xmpDM- Dynamic Media.
xmpMM- Media Management.
Creating metadata-driven workflows help you automate some processes, which improves efficiency. In a metadata-driven workflow, the workflow management system reads the workflow and as a result performs some pre-defined action. For example, some of the ways you could use metadata-driven workflows: