Paul,
I am focusing on organizational management and processes (translating into a database structure with some coding), while you are still focusing and embedding yourself with code...step back and look at the larger picture here...look at how companies and organizations functions.
I mean, you are basically trying to write a script that will assist organizations with administrating, tracking, and resolving problems that their customers or other employees experience with products and services, correct?
Anyway....
I need to delete from this table otherwise staff allocation will get messed up.
How will it be messed up? The EndDate column is the "flag" column that will allow the staff member to access different information -OR- like I have stated, add another column in the Users table.
By deleting the user out of the intersection table, you will have the following problems to deal with:
1) Loss of context since if you delete a staff person out of the table, you'll also have to delete all tickets that the person has responded to...(think in terms of discussion forums or message boards).
2) Loss of tracking mechanism (similiar to #1, but more mechanical with a bit organic meaning that you will not be able to see who responded to who and who said what to who).
This isn't the departments table....that is a seperate table. The allocation table is just for determining which staff member has access to which department. So if admin remove access from one department then I need to delete that row to stop the user seeing the tickets.
Again, you are missing my point...
Look at the following scenarios:
Scenario 1
Employee A works in the Customer Service department for six months when she addresses 675 trouble tickets...Employee A then moves to the Human Resources department where she answers 500 trouble tickets...
Scenario 2
Employee B works in the IT department where he answers 5,000 technical support tickets, then that employee moves up to IT director position as an administrator...
How are you going to handle these two scenarios?
The best thing to do is update the ENDDATE field in the Intersection table (tbl_User_Department) signifying that the employee's tenure is over in that particular department. Then in your "access" scripts, you would check that field/column to see if it's NULL...if so, then that employee is active and associated with that department that has the set of permissions you as administrator grants him.
BTW: This ain't just hypothetical examples above, we are employing the same logic in our faculty/staff/intern/student worker/etc. systems at my job...and also within Anthro TECH.
Bye...bye...and best of luck.
========================================
Buh Bye!
Cheers,
Me
I am focusing on organizational management and processes (translating into a database structure with some coding), while you are still focusing and embedding yourself with code...step back and look at the larger picture here...look at how companies and organizations functions.
I mean, you are basically trying to write a script that will assist organizations with administrating, tracking, and resolving problems that their customers or other employees experience with products and services, correct?
Anyway....
Quote:
I need to delete from this table otherwise staff allocation will get messed up.
How will it be messed up? The EndDate column is the "flag" column that will allow the staff member to access different information -OR- like I have stated, add another column in the Users table.
By deleting the user out of the intersection table, you will have the following problems to deal with:
1) Loss of context since if you delete a staff person out of the table, you'll also have to delete all tickets that the person has responded to...(think in terms of discussion forums or message boards).
2) Loss of tracking mechanism (similiar to #1, but more mechanical with a bit organic meaning that you will not be able to see who responded to who and who said what to who).
Quote:
This isn't the departments table....that is a seperate table. The allocation table is just for determining which staff member has access to which department. So if admin remove access from one department then I need to delete that row to stop the user seeing the tickets.
Again, you are missing my point...
Look at the following scenarios:
Scenario 1
Employee A works in the Customer Service department for six months when she addresses 675 trouble tickets...Employee A then moves to the Human Resources department where she answers 500 trouble tickets...
Scenario 2
Employee B works in the IT department where he answers 5,000 technical support tickets, then that employee moves up to IT director position as an administrator...
How are you going to handle these two scenarios?
The best thing to do is update the ENDDATE field in the Intersection table (tbl_User_Department) signifying that the employee's tenure is over in that particular department. Then in your "access" scripts, you would check that field/column to see if it's NULL...if so, then that employee is active and associated with that department that has the set of permissions you as administrator grants him.
BTW: This ain't just hypothetical examples above, we are employing the same logic in our faculty/staff/intern/student worker/etc. systems at my job...and also within Anthro TECH.
Bye...bye...and best of luck.
========================================
Buh Bye!
Cheers,
Me