Wiki source code of Versioning Architecture (Target)
Last modified by Robert Schaub on 2026/02/08 08:31
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{warning}} | ||
| 2 | **Not Implemented (v2.6.33)** - Entity versioning is **not yet implemented**. Current implementation stores analysis results as immutable JSON blobs. This diagram shows the **target architecture**. | ||
| 3 | {{/warning}} | ||
| 4 | |||
| 5 | = Target Versioning Architecture = | ||
| 6 | |||
| 7 | {{mermaid}} | ||
| 8 | |||
| 9 | graph LR | ||
| 10 | CLAIM[Claim] -->|edited| EDIT[Edit Record] | ||
| 11 | EDIT -->|stores| BEFORE[Before State] | ||
| 12 | EDIT -->|stores| AFTER[After State] | ||
| 13 | EDIT -->|tracks| WHO[Who Changed] | ||
| 14 | EDIT -->|tracks| WHEN[When Changed] | ||
| 15 | EDIT -->|tracks| WHY[Why Changed] | ||
| 16 | EDIT -->|if needed| RESTORE[Manual Restore] | ||
| 17 | RESTORE -->|create new| CLAIM | ||
| 18 | |||
| 19 | {{/mermaid}} | ||
| 20 | |||
| 21 | = Current vs Target = | ||
| 22 | |||
| 23 | |= Feature |= Current (v2.6.33) |= Target | ||
| 24 | | Edit tracking | No | Yes via EDIT table | ||
| 25 | | Before/after states | No | Yes JSON storage | ||
| 26 | | User attribution | No (anonymous) | Yes with user system | ||
| 27 | | Restore capability | No | Yes create new edit | ||
| 28 | |||
| 29 | = Target Details = | ||
| 30 | |||
| 31 | **V1.0 Target**: Simple edit history sufficient for accountability and basic rollback. | ||
| 32 | * Track who, what, when, why for each change | ||
| 33 | * Store before/after values in edits table | ||
| 34 | * Manual restore if needed (create new edit with old values) | ||
| 35 | |||
| 36 | **V2.0+ Future**: Add complex versioning if users request: | ||
| 37 | * Version history browsing | ||
| 38 | * Restore previous version | ||
| 39 | * Diff between versions |