Yeah I understand that @Pat Hartman so here is how things are working at the moment.
So there will be some photoshop work done on the images. The person doing the edit work will quality check if the original image is good or not first of all. If the image wasn't camera captured correctly, then they would inform the photographer of an issue. Then that original image would then be replaced by another one. So essentially it becomes a rescan.
I want to see this in the database. So that the editor is confirming the requirement for the replacement. So I wanted the editor to see both the original and the replacement in two different tables to compare and confirm the changes. There have been instances of miscommunication and the replacement wasn't required to be made. In that case, the original remains. That's why I feel having both tables would help. So when the date last modified changes, it logs into that 2nd table. Then editor would check and confirm, or simply delete that row from the table.
This is sort of the requirement I was given by my higher ups too when I explained the situation. Hence why I wanted the two tables, it just seemed to make logical sense to all parties involved.
So there will be some photoshop work done on the images. The person doing the edit work will quality check if the original image is good or not first of all. If the image wasn't camera captured correctly, then they would inform the photographer of an issue. Then that original image would then be replaced by another one. So essentially it becomes a rescan.
I want to see this in the database. So that the editor is confirming the requirement for the replacement. So I wanted the editor to see both the original and the replacement in two different tables to compare and confirm the changes. There have been instances of miscommunication and the replacement wasn't required to be made. In that case, the original remains. That's why I feel having both tables would help. So when the date last modified changes, it logs into that 2nd table. Then editor would check and confirm, or simply delete that row from the table.
This is sort of the requirement I was given by my higher ups too when I explained the situation. Hence why I wanted the two tables, it just seemed to make logical sense to all parties involved.