Profile: UUID surrogate lookup

Table of Contents

This page is a named element-scope MASD profile instantiating ORE Studio Variability Model § "Profiles: naming a recurring configuration point". A model file binds to this profile (rather than authoring each feature individually) to guarantee the exact feature combination below, with no ad hoc variation.

Purpose

Models a plain reference-data/configuration entity that picked a manufactured UUID as its identity instead of a human-meaningful natural code – typically because rows are authored through a UI form rather than referenced by name elsewhere in the system (a report definition, a synthetic data-generation config), so there is no natural key worth exposing. Same tenant scope and Qt tier as Simple lookup – change-reason cache, pagination – just keyed by id instead of a code. Distinct from FK-scoped child and Self-referencing hierarchy: those are also UUID-keyed, but because they need a stable handle for a parent/child relationship; this profile is for a UUID-keyed entity with no relationship at all. Recurs across ores.dq (dataset_bundle, report_definition, synthetic_fx_spot_config), which is what earns it a name here rather than being left ad hoc per entity.

Reference entity

dataset_bundle — a UUID-surrogate-keyed, tenant-scoped entity with the full standard Qt tier (change-reason cache, pagination), no relationships to any other entity.

Assignments

One row per feature this profile fixes a value for — any feature not listed here is left to the model's own choice. Feature names are literal — exactly what ORE Studio Variability Model documents them as, so this table can be read directly by whatever eventually resolves :profile: bindings, with no translation layer:

Feature Value
has_tenant_id true
has_workspace_id false
system_scope false
nullable_tenant_id false
has_uuid_primary_key true
has_change_reason_cache true
has_pagination true

See also

Emacs 29.3 (Org mode 9.6.15)