Here's where the complication starts...
After the deadline has passed, they are no longer allowed to make changes. There is going to be a reviewer, who will have access to all the submitted applications, and this reviewer is free to make any changes to the submitted applications. This reviewer will likely edit fields like 'project fund amounts' and 'project description' to fix grammar errors or anything that is deemed incorrect. Now, I want to keep the 'edited versions' done by the reviewer separate from the original submitted versions. So in case if there is a dispute raised by the original submiter on what he/she has entered and what the reviewer has edited, the administrator of the program can easily pull the two versions and compare the fields in question.
I am more interested in database design help. What I am thinking right now is right after the deadline, before the reviewer making changes, I dup the db schema and back that up, and the current schema will have the current data, including changes made by the reviewer. If there is dispute and I need to compare original version and edited version, I can toggle my variable that has the schema name? Is there a better to do this? I need a viable design that will take maintenance into consideration.
Any suggestion or advice is appreciated. Thanks in advance.
Nick Han
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
