... another solution would be use of BEFORE INSERT or BEFORE UPDATE triggers that would auto-fill as many fields as i want. haven't done triggers before so i'll have to research that before implementing.
I'd recommend triggers, I think it's not a good practice to use timestamps both from SQL and PHP within the same DB.
the Updateable/Identified business... you mean any member can flag a cuesheet if they found and ID for the set so that the uploader/mod/admin can go back and validate that the ID is correct, and mod the cue accordingly if it is?
Yes, something like that. The use cases/sequences for this feature would be something like:
- User identifies an unknown track --> shouts it in the comment box --> labels the cue as "updateable" --> cue creator is notified
- restriction: unauthenticated user shall not be able remove "updateable" flag
- Cue creator/admin verifies the IDed track --> updates the cue accordingly --> removes label
- If a cue is whole and verified already, users shall not be able to label it as "updateable" - this would reduce fake labeling.