Managing repository structure and access
Repository administrator tasks
Adding, modifying, deleting files in the repository root directory
Files in the repository root directory can be accessed by all staff members with a network account, but they can only be added, modified, or deleted by a repository administrator. These files are meant to inform users in general about the content of the repository, how and where to request access to scientist branches of the repository, etc. An example of such a file is README.pdf. There should be very few files in the repository root directory and updating tasks for these files should be very infrequent. The normal desktop tools (e.g. Windows Explorer) can be used to perform these tasks.
Adding a scientist branch to the repository
The first step to creating a new scientist branch in the repository is to create a subdirectory in the repository root directory. The directory can be created as usual using the Windows Explorer. In the example below, the new directory created is TTuong. To see the permissions on this new directory, right-click on the directory icon in the Windows Explorer and select Properties from the submenu.
Click on the Security tab to display the current securities settings for the directory TTuong. The simple overview shows that there are four groups or users that have permissions to this new directory. These permissions have been automatically inherited from the parent directory, which is the repository root directory. Note that user TTuong has read permissions to this directory, since he is the head of the OU and has read permissions to the entire CESD repository. To see the detailed settings of the permissions, click on the Advanced button.
The advanced permissions display shows the details of the permissions type, the users or groups, the permissions themselves, the permission inheritance, and the scope of application of the permissions. At this stage, we have to add the scientist (To Phuc Tuong) as a user with full control (administrator) to this directory. Click on the Add button either in the simple permissions display, or in the advanced permissions display.
At this stage we have to enter the domain name of the user whom we want to add. The user domain name should normally be the same as the name in the email address, but without the separator dot. Click on the Check Names button to retrieve the full domain name of the user.
If the user is found, click on the OK button.
In the simple permissions display, the new user should initially appear without any permissions set. Note: The gray tick in the Read permissions box of user TTuong is there because is has been inherited from the repository root directory, since user TTuong is also the head of the organizational unit.
User TTuong needs to be given Full Control permissions (Allow) by ticking the appropriate box. All other permissions (Allow) will automatically be marked as well. Click on the Apply buttons to activate the permissions.
Now, all permissions (Allow) are set and the simple permissions display doesn't show which permissions were inherited from the parent directory and which permissions were set on the current directory. To review the details of the permissions setting, click on the Advanced button.
In the advanced permissions display, we can see that we have two separate entries for user TTuong, one with the inherited read permission, and one with the full control permissions set on the TTuong directory. As mentioned before, this is a special case since user TTuong is the head of the organizational unit with read permissions for the entire repository and at the same time a scientist with full control over his branch of the repository.
Click the Apply and/or OK buttons for the open permission settings windows to conclude the process