[Role/Permission] Configuration tool (2 of 4)

[ridz1208]

This adds the Role infrastructure to LORIS. This is one of 4 PRs which will ultimately result in assigning roles to users. each role has affiliated permissions and automatically checks the proper permission when selected. This change will be mainly visible in the user_accounts module.

PART 2: Add tool used to configure the role/permission relationships as well as populate the data in the right table given an existing populated database.

in order to test, the following SQL inserts can be used:

INSERT INTO role (Name, Label) VALUES ('coordinator', 'Coordinator');
INSERT INTO role (Name, Label) VALUES ('data', 'Data-Entry');
INSERT INTO role (Name, Label) VALUES ('upload', 'Data-upload');


INSERT INTO role_permission_rel VALUES ((SELECT RoleID FROM role WHERE Name='coordinator'), (SELECT permID FROM permissions WHERE code='send_to_dcc'));
INSERT INTO role_permission_rel SELECT RoleID,permID FROM role JOIN permissions WHERE Name='data' AND code IN ('data_dict_view','data_entry','data_dict_edit','candidate_parameter_view');
INSERT INTO role_permission_rel SELECT RoleID,permID FROM role JOIN permissions WHERE Name='upload' AND code IN ('video_upload','media_write','media_read');

Original PR by @taracampbell : #2642
Updated/Standardized/DAO full version : ridz1208#9

[ridz1208]

Pending Merger of:

• Copy of [Core-Database] added 2 new functions to help avoid code duplication #3511
• [Role/Permission] Adding SQL schema and DAOs (1 of 4) #3537

[PapillonMcGill]

exit code other than 0 are normally for error or abnormal ending. When there is no error or problem, exit code is normally 0.

Could also use a single exit() call with a variable.

[PapillonMcGill]

"category" should be "role" as other messages

[PapillonMcGill]

I don't see why a "addPermission" function would remove a role from a user.

This portion should be in a "removeRole" function otherwise user might loose some permissions

[ridz1208]

if u add a permission to a rome, you have 2 choices,

• give that permission to all the users with that role
• remove the role from all the users who dont have that permission

that decision is left to the administrators running the patch

[PapillonMcGill]

Ok, now I understand, maybe I am slow, or maybe the text was not clear.

[PapillonMcGill]

again "category" instead of "role"

[PapillonMcGill]

multiple return

[driusan]

Closing until #3537 goes in, until then it's going to need continual rebasing and just make it look like our PRs aren't being worked on.