Reputation: 8773
I have a small web application with a few tables where users can post and edit data. I also have an application admin which moderates the new posted or edited data. What I would like to do is to audit each table and display the data only after the admin has approved it.
The application flow is something like this: a user enters an information in some table; the admin will be noticed and he will approve or reject that information. If the approves it, the information will be displayed in the front-end. Once an information is approved, it can be edited later. When a user edits an information, the admin gets noticed again and he has to approve or reject the edited information, but the previous approved information must be still available on the website.
I also need to keep each version of the changed information (something like v1, v2, v3 etc.).
In your opinion, what is the best way to make this work?
Thank you.
Upvotes: 0
Views: 852
Reputation: 25574
IS_FOR_DISPALY
default NO.Create table with approvals containing fields: post_record_id, new_content, aprove_status, aprove_date, aprove_person, entered ....
This is just general work flow
Upvotes: 2
Reputation: 5722
make history and queue tables ? edits go to queue table and if admin aproves queue->real->history...
Upvotes: 0