DATA-CAT-003 — Hide catalog and schema fields without an authority
| Field | Value |
|---|---|
| Status | Open finding; source-verified |
| Severity | High |
| Affected surface | Catalog and schema overview pages |
| Implementation issue | oqullus #536 |
| Code-change repository | sparqd/oqullus |
Where the problem appears
Open catalog and schema details and inspect Owner, Created at, Description, and Tags; then navigate away and reload.
Concrete observed case
Schema Owner falls back to N/A and every schema receives the same hard-coded creation date. Catalog ownership and creation have no active authority. Description changes persist only in browser memory, while tag controls have no backed data or mutation behavior.
Expected condition
Show a field only when an authoritative, persistent, authorized source exists. Until then, hide Owner, Created at, Description, and Tags at catalog/schema scope rather than fabricating values or presenting inert controls.
Cause and evidence
- Schema rows do not receive authoritative owner or creation values.
- Catalog/schema descriptions are local state only.
- Persistent metadata routes currently cover table and column scope, not catalog/schema scope.
Why it matters
Invented lifecycle and governance metadata can be mistaken for auditable truth, while apparent saves are silently lost.
Existing controls and workarounds
Ignore these fields and controls at catalog/schema scope. Use supported table/column metadata or the authoritative external system directly.
Alternatives considered
- Recommended: hide unsupported fields now and add them only with an explicit authority.
- Display Unknown with provenance — acceptable for read-only fields once a real source exists.
- Keep placeholders as design scaffolding — rejected in a deployed user surface.
Component involvement
- Product defines which scopes are supported.
- Oqullus hides unsupported fields and reports persistence failures.
- BFF/DataHub integration owns any future durable catalog/schema metadata contract.
Reproduction and verification
Follow CAT-S017. Record the visible state, request outcome, effective identity, and recovery behavior relevant to this finding.
Resolution conditions
Close when every visible field has documented authority, persistence, authorization, audit, and reload behavior; unsupported fields remain absent.
Validation and blockers
Oqullus is primary. Product and DataHub owners must approve any expansion beyond table/column scope.