Acquia DAM (Widen) Administrator flashcards
Acquia DAM (Widen) Administrator · Build recall with a focused review session.
31 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Category tree
- A hierarchical folder structure in the DAM that organizes assets. Permissions and visibility can be set per category, and an asset may reside in more than one category.
- Controlled vocabulary field
- A metadata field whose allowed values come from a predefined term list. It standardizes tagging and powers reliable faceted search and filtering across the asset library.
- Embedded metadata
- XMP, IPTC, and EXIF data stored inside the asset file itself. The DAM reads it on upload and can map it to metadata fields or write fields back to files.
- Asset expiration
- A lifecycle state that removes an asset from normal end-user access and search results without deleting it. Often tied to license or usage-rights end dates.
- Permission inheritance
- The rule that permissions set on a parent category flow down to child categories. An explicit setting on a child category overrides what it would otherwise inherit.
- Upload link
- A configured URL that lets external contributors submit files into a specified category without a full DAM account, usually routed into an approval or review workflow.
- Asset versioning
- A feature that keeps prior renditions of an asset when a new file replaces it. The current version is served by default; older versions remain retrievable.
- Derivative
- A file generated from an original asset, such as a thumbnail, web-optimized image, or preset conversion. Derivatives are produced automatically or by configured presets.
- Usage rights
- Metadata recording license terms and expiration for an asset. It supports governance by indicating when an asset may no longer be used and can trigger expiration.
- Metadata field type
- The data type assigned to a metadata field, such as text, date, or controlled vocabulary. The type determines validation, input controls, and search behavior.
- Role-based access
- An access model where permissions are assigned to roles and groups rather than individual users. Users inherit permissions through their group memberships.
- Asset status
- A lifecycle indicator such as active, expired, or archived. Status controls whether an asset is searchable and downloadable by end users without requiring deletion.
- Faceted search
- Filtering of search results by metadata attributes such as category, keyword, or date. Facets depend on well-structured, consistently populated metadata fields.
- Brand portal
- A curated, permissioned front end that exposes selected categories and assets to specific audiences, often partners or agencies, with limited download and search rights.
- Download preset
- A saved configuration defining output format, dimensions, and file settings applied when users download assets, ensuring consistent renditions for downstream use.
- Audit reporting
- Reports on DAM activity such as uploads, downloads, and searches. They support governance, adoption tracking, and identification of unused or overused assets.
- Acquia Cloud environment
- A discrete runtime instance within an application, typically Dev, Stage, or Prod. Each has its own code branch, database, files, and configuration settings.
- Configuration as code
- The practice of storing configuration in version-controlled files rather than editing the database directly, so deployments are reproducible across Dev, Stage, and Prod.
- Acquia Cloud IDE
- A browser-based development environment tied to an application's codebase. Developers edit and commit code there, and commits push to the application's Git repository.
- Deployment pipeline
- An automated sequence that builds an artifact and runs tests before deploying code to an environment. It reduces manual steps and enforces consistent release process.
- Acquia Cloud API
- A programmatic interface for managing environments, backups, and tasks. Authentication uses API keys or OAuth tokens, enabling automation and CI/CD integration.
- Environment backup
- A snapshot of an environment's database or files taken on demand or on a schedule. Restoring a backup overwrites the corresponding data in the target environment.
- Acquia Edge
- The CDN and edge security layer in front of Acquia-hosted sites. It caches content and enforces TLS and WAF rules, configured per environment and domain.
- Shared responsibility model
- The division of duties in Acquia hosting: Acquia manages the platform infrastructure and patching, while customers manage application code, configuration, and content.
- Environment variables
- Key-value settings injected at runtime to hold environment-specific values such as credentials or API endpoints, keeping them out of code and the database.
- Code artifact
- A packaged, immutable build of the application produced by the pipeline. The same artifact is deployed across environments, with configuration differing per environment.
- Production domain
- A public hostname pointed at the Prod environment's load balancer. Non-production environments use separate hostnames and are typically access-restricted.
- Git branch workflow
- A branching model where code is developed on branches and promoted via tags or merges to environment branches, matching the Dev, Stage, and Prod environments.
- SSL certificate
- A TLS certificate bound to a domain that enables HTTPS. It is configured per environment and must be valid and current to avoid browser trust errors.
- Acquia CLI
- A command-line tool for interacting with Acquia Cloud, automating tasks such as backups, deployments, and environment operations through authenticated API calls.
- Acquia Personalization
- A service that personalizes site content for visitors using behavioral data. It requires site integration and credentials configured per environment.