I haven't decided how to go about adding this feature yet. The obvious solution is to add a title_id field to the staff table, which isn't being used for much right now. Because this table already has the date_start and date_end fields, it will work well as a history table.
This table should probably be renamed staff_history, as it's original purpose (authorizing users to log into the backend of the application) has been replaced with a privilege (to allow for freelance reporters), and the purpose of identifying staff members has been replaced with job titles (If someone has a title, they are a staff member. Anyone who doesn't have a title.....isn't).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I haven't decided how to go about adding this feature yet. The obvious solution is to add a title_id field to the staff table, which isn't being used for much right now. Because this table already has the date_start and date_end fields, it will work well as a history table.
This table should probably be renamed staff_history, as it's original purpose (authorizing users to log into the backend of the application) has been replaced with a privilege (to allow for freelance reporters), and the purpose of identifying staff members has been replaced with job titles (If someone has a title, they are a staff member. Anyone who doesn't have a title.....isn't).