...
- Repository Layout
Folder
Use
Managed Permissions
/course/
course specific instructor provided material
Admin=(rw),Instructor=(rw),TA=(rw),Students=(r)
/rice_config/
configuration and permission management
Admin=(rw),Instructor=(rw),TA=(rw)
/turnin/
Admin=(rw),Instructor=(rw),TA=(rw),Student=(r)
/turnin/netId/
for each student's course use
Admin=(rw),Instructor=(rw),TA=(rw),netId=(rw)
- Repositories ARE tied to a full course (eg COMP412). This means ALL sections of a course are included for access to the repository.
- Repositories ARE NOT tied to specific sections of a course.
- The basic structure (layout) of the repository is fixed. It is possible to add new folders and change the permissions on any folders through the access_file but the locations of the turnin added folders must remain constant.
- ALL users of a repository will retain access to the repository for up to 3 semesters
- Except for the Turnin managed access_file block, nothing else in the access_file is changed. The one exception to this, is that new (non-existing) permission blocks will will be added as new students are added to the repository.
- The access file will be much more structured to allow for managed and unmanaged permissions. Breaking the functionality of turnin by corrupting the access file is possible. Fixing broken access files, is best effort or business hours.
- Each permission block in the access_file must remain the same name. This means that when the turnin process writes out a new permission block /turnin/netid, it expects to find this same block name in the access_file the next time it looks. If it doesn't, it will re-create it. You CAN NOT move these base turnin folders within the repository.
- Once a permission block has been written to the access_file it will no longer be managed. This means that you can change the permissions to anything you wish and they will carry forward.
...