Skip to end of metadata
Go to start of metadata

How to get a turnin enabled repository

First a user will need to visit Apply and create a subversion repository. After the repository has been created, the user can revisit Apply and tie the repository to one or more courses. This will turnin enable the subversion repository and a nightly process will automatically update the repository access_file and turnin folder structure.

Turnin 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)

/turnin/SemesterCode/netId/

for each student's course use per semester

Admin=(rw),Instructor=(rw),TA=(rw),netId=(rw)

  • SemesterCode is F, S, Su plus the last two digits of the year by default;

Constraints

  • 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. There will be no support for having two sections of the same course with different turnin repositories.
  • ALL users of a repository will retain access to the repository for up to a minimum of 3 semesters; Currently implemented as three active semesters that the course is taught. If the course is only taught in the Fall of each year, then the full repository would be accessible by a user for 3 years. If the course is taught every semester, then the repository would be fully accessible for a year. On the 4th active semester, the oldest semester will be dropped from general access to the repository. This means that students will no longer be able to access any repository folders protected by the student group. However, until the student data is removed or they lose access to their netId, they will retain read/write access to their specific turnin folder.
  • Except for the one small controlled section of the access_file, all other user changes to the access_file should be carried forward.
  • The one exception to user changes being carried forward is that user permission blocks for active users can not be deleted by the user without them coming back automatically the next time the automatic process run.

Data changes controlled by the automatic turnin process

  • Repository data will never be deleted
  • General access to the repository will be controlled by updating the access_file turnin group list. The section of the access_file that is rewritten will be surrounded by comments and user changes are not allowed.
  • As new semesters (and students) are cycled into the turnin group list, the permission blocks for these new semesters and students will be added to the access_file.
  • As new semesters (and students) are cycled into the turnin group list, new repository folders will be added for the semesters and students.
  • The access_file turnin group list will be updated when new course groups are automatically created within Grouper. This means that a new semester may force an old semester out of the turnin group list before any new students have been added to the new course group.

Enhancements

  • I've added a special comment to the access file that will allow the owner of the repository to turn OFF the automatic processing of the access_file and repository. When the automatic process sees this comment, it will abort any changes to this repository and will move to the next repository.

access_file format

  • No labels