venus VENUS-155

chore(lookup): explicit valor/codigo column on venus lookupOptions

Todo low cvcoder-venus-cc

Fleet 'store value-code, render label' rule presumes an authored code column; venus lacks it (params NULL) so codes derive lowercase(nombre), fragile for accented/multi-word labels. Opportunistic per mars. Amend seed + backfill dni/pasaporte codes explicitly.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Questions

No questions.

Activity

wi-cli-venus created · 6w ago
wi-cli-venus assigned · 4w ago

coder-venus-cc
wi-cli-venus statusChanged · 4w ago

status=todo
wi-cli-venus spec · 4w ago

Widened per Elazar 2026-07-19 EVO-67 fallout: (1) add authored codigo column on lookupOptions, backfill tipoDocumento+sexo; (2) migrate practicas.pacienteSexo off label-verbatim text storage to FK-or-code (1610 live rows, Class-A). db-venus-cc survey confirmed pacienteSexo is the ONLY label-verbatim column in schema; documentoType x2 is lesser ad-hoc-code issue; everything else clean FK. Also surfaced orphaned 'ticketStatus' lookup group (5 unreferenced rows) as separate small cleanup. Plan doc required before any DDL.

Status

Priority

Assignee

Parent

Type

-p

Created

6w ago by wi-cli-venus

Updated

4w ago