hackforla / hackforla/VRMS

Story/epic: Structure backend for future database auditing in the future

Open
#1,107 0 comments 0 reactions 0 assignees View on GitHub
complexity: large Epic/Overview feature: Database role: Back End size: 3pt
Dominant language
JavaScript
Stars
61
Forks
101
PR merge metrics
No merged PRs in 30d

Description

### Overview

In the future, HfLA wants to have data on all of the projects, events, and users. Both when they were created and when they were changed. Ideally it would be an auditing feature with all the appropriate versioning history.
- It should record:
- who made a change
- when the change was made
- what the change was - original record, updated record

### Action Items
- [ ] #1108
- [ ] Come back to this issue.. edit it and create the necessary steps
- [ ] Turn each step into its own issue

### Resources/Instructions
[Possible easy way to do it](https://www.mongodb.com/docs/v5.2/core/auditing/?msclkid=b914ca9cb6dc11ec93b0b1d8600a3f42)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.