Profile: Fully-featured 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.

1. Purpose

Models a reference-data code important and heavily-used enough to warrant the full UI surface: bulk CSV/XML import-export for operational data loading, and version navigation for auditing change history record-by-record. The exception, not the norm — most lookups fit simple-lookup instead; reach for this profile only once an entity's actual usage (high edit frequency, external data feeds, audit scrutiny) earns the extra surface.

2. Reference entity

currency — the most complete entity in the codebase, and the reference specimen the entity commissioning process reference's per-layer criteria are derived from; every optional UI feature is exercised at least once.

3. 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 Value
has_tenant_id true
has_workspace_id false
has_uuid_primary_key false
has_change_reason_cache true
has_csv_xml_io true
has_version_navigation true

4. Physical space

Address Enabled
ores.cpp.shell-command true
ores.cpp.eventing-integration-test true

5. See also

Emacs 29.3 (Org mode 9.6.15)