AEM Assets Developer Professional flashcards
AEM Assets Developer Professional · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- dam:Asset node type
- The JCR primary type for an asset. It extends nt:hierarchyNode and contains a dam:AssetContent child that holds metadata, renditions, and related subassets.
- Data store
- External binary storage for asset originals. FileDataStore or cloud blob (S3/Azure) stores the bytes; the JCR only keeps a reference node under renditions/original.
- DAM Update Asset workflow
- Default ingestion workflow that extracts metadata, generates thumbnails and web renditions, and optionally runs smart tagging and custom processing steps on upload.
- Assets HTTP API
- REST interface at /api/assets/{path} exposing JSON CRUD for assets and folders, plus metadata and rendition endpoints. Distinct from the query-based search API.
- Connected Assets
- Configuration that lets a Sites instance reference and deliver assets stored in a separate remote Assets instance using a shared lookup URL and credentials.
- sling:OrderedFolder
- Folder node type that preserves explicit child ordering. The Assets UI honors this ordering, unlike plain sling:Folder which sorts by name.
- Processing profile
- Folder-level configuration mapping MIME types to workflow models. Overrides the default DAM Update Asset behavior for assets uploaded into that folder.
- Metadata schema
- Editor-defined set of fields, namespaces, and cardinality rules that controls which metadata properties appear in the asset properties UI and their validation.
- XMP writeback
- Workflow step that writes JCR metadata properties back into the asset binary as XMP, keeping embedded metadata and repository metadata synchronized.
- Smart Tags
- AI-generated descriptive tags produced by the Sensei service. Requires a cloud configuration linked to the folder and the smart tag workflow enabled.
- Metadata profile
- Configuration applied to a folder that injects default or derived metadata values into assets at ingestion and can mark fields required or read-only.
- Custom namespace registration
- Custom metadata namespaces must be registered in the Namespace registry (Tools > General > Namespaces) before schema fields can use them; otherwise validation fails.
- cq5dam.web renditions
- Web-optimized renditions generated by the DAM Update Asset workflow, prefixed cq5dam.web.*, used for delivery instead of the full-resolution original.
- DamMetadataExtraction step
- Workflow process in DAM Update Asset that reads embedded XMP/EXIF/IPTC from the binary and writes the extracted values into jcr:content/metadata properties.
- QueryBuilder API
- Search API at /bin/querybuilder.json that converts predicates such as path, type, property, and fulltext into JCR-SQL2 or XPath queries against Oak.
- Static collection
- Collection whose membership is an explicit list of asset references. Assets are added or removed manually and do not change automatically.
- Smart collection
- Collection whose membership is defined by a stored search query evaluated at view time. Assets matching the query appear automatically as the repository changes.
- cq:tags property
- Multi-valued String property on an asset referencing tag IDs under /content/cq:tags. Tag-based search uses the tagid predicate against this property.
- OmniSearch index
- Oak Lucene full-text index backing the Assets search UI. It indexes metadata properties like dc:title and dc:description for fulltext queries.
- Saved search
- Persisted query stored in the repository and re-executed on demand. It is not cached; results reflect the current repository state each time.
- Search rail facets
- UI filters (file type, size, orientation, etc.) that map to additional QueryBuilder predicates layered on top of the base search query.
- Folder-based organization
- Assets live under /content/dam in a folder tree. Folders carry processing profiles and metadata profiles that apply to their descendants at ingestion.
- Rendition servlet path
- Renditions are served at /content/dam/{path}/_jcr_content/renditions/{name}; the original rendition is named original.
- Asset Compute Service
- Node.js worker extension point on AEM as a Cloud Service for custom renditions and metadata processing. Workers deploy to Adobe I/O Runtime.
- Dynamic Media
- Cloud service providing dynamic image/video delivery, smart imaging, and viewer presets. Separate from core AEM asset storage and rendition generation.
- Dispatcher caching
- Delivery layer that caches static renditions and responses at the edge. Cache invalidation must be triggered when assets or renditions change.
- Sling event handler
- OSGi component listening to dam:AssetCreated or dam:AssetModified events to run custom logic such as metadata enrichment or external system sync.
- Workflow process step
- Java implementation of a workflow process used in AEM 6.5 to add custom rendition or metadata logic to the DAM Update Asset workflow.
- Assets search API endpoint
- Query-based endpoint under /api/assets/.../search that accepts QueryBuilder-style parameters and returns matching assets as JSON.
- Asset delivery via API
- The Assets HTTP API returns JSON with metadata and rendition links; binaries are fetched separately from the rendition servlet or data store URL.
- Custom rendition generation
- On AEMaaCS, use Asset Compute workers; on AEM 6.5, add a workflow process step to DAM Update Asset to produce additional renditions.
- Cloud configuration linking
- Smart tagging and Dynamic Media require a cloud service configuration linked to the asset folder before the corresponding processing runs on upload.