movilba
MOVILBA-526
· child of MOVILBA-449 Tracker Eugenia 2026-09-17: items abiertos de la hoja Para Elazar Done
Plate change: keep prior plate as retired vehicle while preserving history
Done high
cmcoder03assistant-mba-l-ca
Stakeholder answer received in tracker 2026-09-19, Para Eugenia #4: when a unit changes plate, keep the previous plate as a vehicle retired from the fleet; these are uncommon and mostly provisional-to-definitive plate changes. Analyze and implement the consequences across current vehicle identity, VIN/chassis chains, detail/history, exports, and import projection. Do not merge two simultaneously visible vehicle identities merely because they share a chassis. Validate example chassis LA6C3K1G6TB102087, old AH846SI, current AI086HB, and document how historical continuity remains accessible.
Activity
-
parent=#3883
-
coder03-mba-l-ca / coder
-
coder04-mba-l-ca | 2026-09-24 04:01 ART. The ticket describes plate-change identity/history retention; no current DEV/PROD identity operation or stakeholder-approved design was exercised in this pass. Leaving backlog on parked coder03-mba-l-ca as unverified DB/design work.
-
coder03assistant-mba-l-ca
-
coder03assistant-mba-l-ca | 2026-09-28 14:04 ART — Current SSOT /data-lezama/movilba/libro/2026-09-28-1042-parque-rutap.xlsx, Base, has three rows for chassis LA6C3K1G6TB102087: row 3066 AI086HB 2026-02-25..2026-04-30 (Alta); row 3558 AH846SI 2026-04-30..2026-08-19 (Modif); row 4196 AH846SI open from 2026-08-19 (Modif). Thus the ticket example’s “AH846SI old / AI086HB current” is stale or reversed against current SSOT. This verifies source chronology only; no DEV/PROD identity/history/import query or code path was exercised. Keep backlog pending current-source alignment and DB-lane import continuity check before design or edits.
-
coder03assistant-mba-l-ca | 2026-10-06: Read-only check against SSOT /data-lezama/movilba/libro/2026-10-06-1140-parque-rutap.xlsx (SHA256 a72ade6a52621051e5a1dc7a01281de7b11e69c2332c8bf5163fea943b2c5f1a): the example is reversed from the ticket. AI086HB is prior (2026-02-25..2026-04-30, Alta); AH846SI follows (2026-04-30..2026-08-19 and open from 2026-08-19, Modif). PROD SELECT-only: imported snapshot 8 is still 2026-09-30-1305-parque-rutap.xlsx (5,548 rows). Its matching rows preserve separate vehiculos IDs 6991 (AI086HB, Baja, history through 2026-04-30) and 5819 (AH846SI, Alta, open since 2026-08-19), both with VIN LA6C3K1G6TB102087; public.v_vehiculo_cadena links the IDs for history continuity by VIN without conflating the vehicle records. Deployed v_vehiculos_detalle and v_vehiculos_list likewise show prior AI as Baja and current AH as Alta. Code reader getRutapHistorialByChain loads chain events while keeping each event's vehiculo_id and dominio. This is already represented in PROD against snapshot 8; no code or data change made. Remaining verification: latest 10/06 SSOT import has not reached PROD, and DEV was unavailable per outage notice; recheck source-to-import plus DEV/pod after refresh before closing.
-
coder03assistant-mba-l-ca | 2026-10-06: Rechecked after DEV DB recovered. PROD and DEV are both on snapshot 2026-09-30-1305-parque-rutap.xlsx (snapshot IDs 8 and 20, each 5,548 rows), not the 10/06 workbook. Read-only deployed-view check in both: separate vehicle identities for LA6C3K1G6TB102087; AI086HB is Baja, 2026-02-25..2026-04-30; AH846SI is Alta, open since 2026-08-19. This matches the 10/06 SSOT chronology already recorded. No code/data changes. The requested outcome is already present on PROD and DEV; the remaining limitation is the newer snapshot has not yet been imported. Pod uses DEV service; health had matching serviceId 24886.
-
coder03assistant-mba-l-ca | 2026-10-07 read-only recheck after import. Both bases now contain the target SSOT /data-lezama/movilba/libro/2026-10-06-1140-parque-rutap.xlsx: PROD snapshot 11 and DEV snapshot 21, each 5,558 rows. The workbook's actual chronology is AI086HB Alta 2026-02-25..2026-04-30, then AH846SI Modif 2026-04-30..2026-08-19 and open from 2026-08-19 (ticket example had old/current reversed). In both bases, v_vehiculos_detalle and v_vehiculos_list show separate vehicle IDs and current states AI086HB=Baja / AH846SI=Alta. v_vehiculos_export emits the same two identities and dates. Current-snapshot history has all three periods across the two IDs, and v_vehiculo_cadena links both IDs bidirectionally by VIN without merging the records. All three service health endpoints return 200 with serviceId 25571. No code/data change was needed; requested retired-prior-plate + preserved-history behavior is already live on PROD, DEV, pod.
-
Closed as already satisfied by current PROD/DEV/pod behavior; latest SSOT source and live histories preserve prior AI086HB as Baja, current AH846SI as Alta, and chain continuity across distinct vehicle records.
decision
3w ago by wi-cli-venus
1w ago
2026-10-07 15:04