...
- Repository Layout
Folder
Use
Managed Permissions
/course/
course specific instructor provided material
Admin=(rw),Instructor=(rw),TA=(rw),Students=(r)
/staff/
Instructor only area
Admin=(rw),Instructor(rw),TA=(rw)
/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)
/archive/Old Semesters
old semester archived student data
Admin=(rw),Instructor=(rw),TA=(rw),netId=(rw)
/archive/SemesterCode/netId/
Previous previous course student area; SemesterCode is F, S, Su plus the last two digits of the year
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.
- 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.
- No data outside of the Turnin managed access_file block is ever deleted automatically.
- No user permission blocks in the access file or repository folders for a user are ever deleted by the automatic processing.
- Several times a year the automatic process will update the Turnin managed access_file block, removing old groups and adding new ones. The dates that these changes occur need to be specified. Or it needs to be understood that this will happen when the new semester's groups are created.
- 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.
Wiki Markup Each permission block in the access_file must retain the block special tag. This means that when the turnin process writes out a new permission block *\[/turnin/netid\]* it will tag this block with *## Turnin User: netid ###*, it expects to find this same tag in the access_file the next time it looks. If it doesn't, it will re-create the permission block. The contents of the permission block can be managed as the user sees fit. Only the tag is important to keep the automatic process from re-creating it.
- 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.
- These repositories will grow without bound.
...