Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
tutorial:adm:roles_-_import_data_from_csv [2019/08/05 11:17]
doischert 		tutorial:adm:roles_-_import_data_from_csv [2019/08/15 14:44]
doischert
Line 3: Line 3:
 ==== 1. Prepare the CSV file ==== ==== 1. Prepare the CSV file ====
  
-Here is an example of a CSV file which can be used for importing (or updating) roles, setting their role attributes, guarantees (by user, or by role) and criticality, for saving them in a created catalogue and for assigning their subordinate role. To use this CSV file, create a new identity with user name "user_login", and a new role with code "role_code".+Here is an example of a CSV file which can be used for importing (or updating) roles, setting their role attributes, guarantees (by user, or by role) and criticality, for saving them in a created catalogue and for assigning their subordinate role. To use this CSV file, create a new identity with user name <nowiki>"user_login"</nowiki>, and a new role with code <nowiki>"role_code"</nowiki>.
  
 <code> <code>
Line 21: Line 21:
  
 The result of this LRT used with this CSV file should: The result of this LRT used with this CSV file should:
-  * 4 new roles (Manager-A, LAY-SP, CORE-CLOSE, AB-role). +  * 4 new roles <nowiki>(Manager-A, LAY-SP, CORE-CLOSE, AB-role).</nowiki> 
-  * Manager-A will have a description set (Leader) and a subrole set (role_code). +  * <nowiki>Manager-A will have a description set (Leader) and a subrole set (role_code).</nowiki> 
-  *  +  * <nowiki>LAY-SP will have a description (Manager), attribute (attr1), criticality (3), guarantee by identity (with user-name "user-login"), and guarantee by role (with role-code "role_code") set. It will be saved in catalogue cat4.</nowiki>
-  * LAY-SP will have a description (Manager), attribute (attr1), criticality (3), guarantee by identity (with user-name "user-login"), and guarantee by role (with role-code "role_code") set. It will be saved in catalogue cat4.+
   * Roles CORE-CLOSE and AB-role will have a description (desc), an attribute (attr1), and criticality (2) set. They will be in catalogues cat1 and cat3.   * Roles CORE-CLOSE and AB-role will have a description (desc), an attribute (attr1), and criticality (2) set. They will be in catalogues cat1 and cat3.
  
Line 40: Line 39:
 - Import csv file - dropzone to select or drop csv file - Import csv file - dropzone to select or drop csv file
 - Column with roles - Name of the column with roles in csv file - Column with roles - Name of the column with roles in csv file
 +- Column with role codes - Name of the column with role codes in csv file; this is only used for updating role, not creating them! When creating them, role code is based on the role name, only space " " are replaced by "_"
 - Column with description - name of the column with role description, can be also used to update description (if your CSV file doesn't contain descriptions, i.e., you are not setting description for any of your roles, leave this line empty)  - Column with description - name of the column with role description, can be also used to update description (if your CSV file doesn't contain descriptions, i.e., you are not setting description for any of your roles, leave this line empty) 
 - Column with role attributes - name of the column with role attributes, can be also used to update attributes (if your CSV file doesn't contain attributes, i.e., you are not setting attributes for any of your roles, leave this line empty) - Column with role attributes - name of the column with role attributes, can be also used to update attributes (if your CSV file doesn't contain attributes, i.e., you are not setting attributes for any of your roles, leave this line empty)
  • by apeterova