Version 1 (modified by saw, 10 years ago) (diff)


The repository must have the capability to allow a particular user to access data sets that they have been given permission to access. The initial concept for this delegation functionality is to use the LDAP database to store information about what repositories a user has access to, and what folder levels within a repository they have access to.

A directory will be created for each repository entity (individual counties for example) that contains folders for a predefined number of levels. The initial concept is to provide 3 levels in each repository.

Here is an example repository directory structure:

<pre> \repositories



-1 -2 -3


-1 -2 -3


-1 -2 -3



-1 -2 -3



-1 -2 -3


When a user logs in to, they will be presented with a list of repositories that they have been given permission to access. When the user selects a repository to browse , they will be presented with a list of the levels that they have been given permission to access within that repository. When the user selects a level to browse, the BrowseRepository module will present the directory and file structure within the level subdirectory that corresponds to the level and repository that was selected.

The LDAP_USER environment variable supplied by Apache will be used to query the LDAP database for repositories and levels that are available to that user. Site administrators can use the MaintainGroup function to create groups that can also be given permission to a repository. A user will have access to any repository level that has been assigned directly to them or to a group they are a member of.

A web interface must be developed to allow repository administrators to select the levels that will be available to a user or group diring normal and EmergencyDeclaration situations. Repository administrators should also be able to specify an expiration date for the permission that is granted. This will allow for users who only need access during specific projects, or who purchased access for a period of time. A possible interface might look like:

<table border=1 frame=border rules=all><form> <tr><td colspan=2>User: John Doe<br> <input type=checkbox value=expires class=noborder>Access expires</input> on <input type=text value="12/31/2005" />. </td></tr> <tr> <td border=0>Normal Permissions<br> <input type=checkbox value=normal1 class=noborder>Level 1</input><br> <input type=checkbox value=normal2 class=noborder>Level 2</input><br> <input type=checkbox value=normal3 class=noborder>Level 3</input><br> <input type=checkbox value=normal4 class=noborder>Level 4</input><br> <input type=checkbox value=normal5 class=noborder>Level 5</input> </td> <td border=0>Permissions During Declared Emergency<br> <input type=checkbox value=emergency1 class=noborder>Level 1</input><br> <input type=checkbox value=emergency2 class=noborder>Level 2</input><br> <input type=checkbox value=emergency3 class=noborder>Level 3</input><br> <input type=checkbox value=emergency4 class=noborder>Level 4</input><br> <input type=checkbox value=emergency5 class=noborder>Level 5</input> </td> </tr> </form></table>

The DataUpload process will store files in the repository directories for a given user.