AEM Assets Developer Professional key terms

A system for storing, organizing, describing, and distributing rich media such as images, video, and documents. In AEM it is implemented by the Assets capability built on the content repository.

A binary file plus a repository node holding its metadata, renditions, and relationships. The binary is the original file; the node lets AEM index, version, and deliver it.

The stored original file content of an asset, kept in the data store rather than the node itself. It is streamed for download and used as the source for generated renditions.

A storage layer that keeps asset binaries outside the Jackrabbit node store, typically on a file system or cloud blob store. It allows large files and shared storage across cluster nodes.

Object storage commonly used as the AEM Assets data store in cloud deployments. Binaries live in buckets while metadata and node structure remain in the repository.

The repository layer that persists the content tree, including asset metadata nodes, folder structure, and references. It holds pointers to binaries rather than the file content itself.

The Java Content Repository standard that AEM implements. Assets are modeled as nodes with properties, and queries, versioning, and access control operate at this level.

The specific JCR implementation used by AEM, providing indexing, segment storage, and query support. Its indexes strongly influence how asset searches perform at scale.

A configuration that defines which metadata fields appear in the asset editor, their types, and their grouping into tabs. It controls the authoring form, not the storage format.

Descriptive data attached to an asset such as title, description, keywords, and technical properties. It drives search, organization, and delivery behavior.

An XML-based metadata standard embedded in many file formats. AEM reads and writes XMP properties, allowing descriptive data to travel with the file itself.

Technical metadata embedded in image files, covering camera, exposure, and orientation details. AEM extracts these values during ingestion and can map them into asset properties.

A configuration applied to folders that defines default metadata values, mandatory fields, and derived or cascading rules for assets uploaded beneath it.

A folder-level configuration that controls which post-ingestion actions run on uploaded assets, such as rendition generation, metadata extraction, and workflow steps.

An automated sequence of steps triggered by events such as asset upload. Workflows perform extraction, transcoding, review, and other processing tasks asynchronously.

A configuration that starts a workflow when a matching event occurs, such as a node being created or modified. It links repository events to automated processing.

A derived version of an asset generated for a specific use, such as a thumbnail, web-optimized image, or video transcode. Renditions are created by processing and served at delivery time.

The process of reading embedded properties from an uploaded file and writing them into asset metadata nodes. It can be configured and extended with custom extractors.

Ingesting many assets at once from a file system or external source, often with a mapping that sets folders and metadata. It is used for migrations and large content drops.

The overall process of bringing files into the repository, including upload, binary storage, metadata extraction, rendition generation, and workflow triggering.

A configuration that lets one AEM site environment use assets stored in a separate Assets environment. It is common when authoring and asset management are deployed apart.

A controlled vocabulary term applied to assets for classification and filtering. Tags live in a taxonomy namespace and can be used in search predicates and smart collections.

A collection whose membership is defined by a saved search query rather than manual selection. Assets matching the query are included automatically as they are added or edited.

A named grouping of assets that can be shared with users or used for campaigns and reviews. Collections reference assets without duplicating their binaries.

AEM's structured query API that assembles JCR queries from predicates such as path, type, property, and full-text. It is the basis for many asset search interfaces.

Search that matches terms against indexed text content and metadata rather than exact property values. It requires appropriate indexes to perform well across large asset repositories.

A cloud service for delivering and transforming assets through URL-based image and video services. It provides responsive renditions, smart cropping, and viewer components.

An automated feature that detects the focal point of an image so renditions can be cropped to different aspect ratios without losing the subject.

A feature for distributing selected assets to external parties through a link, with options such as expiration and download permissions. No AEM account is required to view them.

A separate cloud service for distributing approved brand assets to internal teams and agencies. Assets are published from AEM Assets to Brand Portal for controlled access.

Serving assets to end users through published renditions, dynamic media URLs, or APIs. It depends on replication or cloud delivery services and correct access configuration.

The mechanism that copies content from author to publish environments. For assets it moves metadata nodes and binaries so published pages can reference them.

Programmatic interfaces for creating, reading, updating, and delivering assets, including HTTP-based and Java APIs. They support integrations and custom automation.

Cloud-native processing services that handle rendition generation, metadata extraction, and transcoding outside the AEM instance. They scale processing independently of authoring.

Keeping historical copies of an asset so earlier states can be restored or compared. It applies to the metadata node and, depending on configuration, to binaries as well.

Access control rules that determine which users or groups can read, edit, delete, or publish assets. They are evaluated on repository paths and can restrict folders and collections.