Record Versioning

[lbaertlein1]

Problem: When a submission is edited, we retain a record of when it was last edited and by who. However, there is no record of what the original submission was. This prevents the data from being fully auditable.

Proposed Solution: Create a versioning system for submissions, such that a record is retained of the submission at each point the submission is saved. If a submission is edited, a record of the original submission should be retained and a new record of the edited submission should be created. This could be done in the campaignformdata table, by adding a submission version uuid, and one row per submission per version rather than just one row per submission. Logic would have to be put in place to automatically archive versions when they are edited/replaced such that for one submission only one record is ever ‘active’, and all other records are ‘archived’. A diagram of the current structure and suggested revision are below.

Current Structure:

Suggested Revised Structure:

[Eutit5]

@bnygren it's not availble on the APMIS project