Add Versioning of Objects

[L00tz1ffer]

Scope & Context

Every entry in the CRM is a momentary record. This means that if someone accidentally overrides data of any kind, it is effectively gone.

The idea is to provide the user with a journaling system, similar to an append-only interface, so that data is never truly deleted but instead flagged as deleted. At the same time, there must be an option to delete certain data when required, for example in response to a "DSGVO request" involving any contained user.

Current Behavior

• Data is stored only as a snapshot of the current state and does not maintain a history/log as expected.
• Once data is modified, it cannot be reverted to a previous state (step n).

Expected Behavior

• Consistent logging of all changes, potentially implemented via diffing.
• An append-only data structure where all changes are clearly traceable, e.g. via UUID + timestamp.
• Each object should provide a back button as well as a forward button.
• If the back button is used and the user moves n steps backwards and then modifies data, there are two possible approaches:
  • First: Add the changes as a new entry at the head of the existing diff chain (preferred).
  • Second: Handle it like branching, which may confuse users; therefore, the first approach is preferable.
• Maybe signing of entries for consitency

Challenges

• For DSGVO in Germany, it may be necessary to implement a form of soft delete that scrambles or anonymizes data across its entire history while still keeping references and links valid.

[Bonapara]

did you notice our soft-deleting feature? (records are not erased when you delete them, but stored for 14 days)