...
- Repository Layout
Folder
Use
Permissions
/course/
for course specific instructor provided material
Admin=(rw),Instructor=(rw),TA=(rw),Students=(r)
/rice_config/
for subversion configuration and permission management
Admin=(rw),Instructor=(rw),TA=(rw)
/turnin/for all students course use
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 They want repositories tied to a full course (eg COMP412). This means ALL sections.They
- DO Repositories ARE NOT want repositories tied to specific sections of a course.
- They want ALL users of a repository to will retain access to the repository for up to 3 semesters
This means that after three semesters, anyone no longer listed in an active Grouper group for the repository will become unmanaged. The access file permissions blocks for any deprecated users will be removed. The user's turnin folders will NOT be touched. If an instructor is no longer listed in one of the active instructor groups, their netid will be removed from the instructor group but any other permissions they have in the access file will be uneffected.
Usage
- 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.
Usage
- Create They will create a repository 'courseXXX'
- They will mark Mark this as a turnin capable repository and assign it to a specific course by subject and course number, eg COMP 412.
- The automatic turnin process will then use the members of the course as defined in Grouper to do the following:
- Create the user folders /turnin/netid within the repository
- Create a permissions block in the access file for each user folder
...