Page tree
Skip to end of metadata
Go to start of metadata

If the setting for the Data Steward topic creation is set to 'Pending' or 'Approved' within shrine.conf, all query topics must be approved by a designated role called the 'Data Steward'. The Data Steward is a special role that can see all pending topics and then has the authority to approve or reject them. If a topic is approved, then the topic will appear in the SHRINE webclient for the user who requested it. If the topic is rejected, then the topic will not appear for that user. In order to assign 'Data Steward' privileges, you will need to add a special parameter ('DataSteward') for an existing user in the pm_user_params table.

In particular, the Data Steward role cannot create any query topics for itself, but it is an administrative role whose function is to approve or reject query topic requests from all other users.

The following code fragment creates a new user called 'shrine_steward' and gives it Data Steward privileges. To assign the Data Steward privileges to an existing user, you will simply execute the last insert statement to assign the role to that user.

insert into PM_USER_DATA
(user_id, full_name, password, status_cd)
values
('shrine_steward', 'SHRINE Data Steward User', '5f4dcc3b5aa765d61d8327deb882cf99', 'A');
 
-- The password hash you see above is for 'password'

insert into PM_PROJECT_USER_ROLES
(PROJECT_ID, USER_ID, USER_ROLE_CD, STATUS_CD)
values
('SHRINE', 'shrine_steward', 'USER', 'A');

insert into PM_PROJECT_USER_ROLES
(PROJECT_ID, USER_ID, USER_ROLE_CD, STATUS_CD)
values
('SHRINE', 'shrine_steward', 'DATA_OBFSC', 'A');

insert into PM_USER_PARAMS
(DATATYPE_CD, USER_ID, PARAM_NAME_CD, VALUE, CHANGEBY_CHAR, STATUS_CD)
values
('T', 'shrine_steward', 'DataSteward', 'true', 'i2b2', 'A');


Please refer to Chapter 8.1 on information regarding the generation of the password hash.

  • No labels