...
- SemesterCode is F, S, Su plus the last two digits of the year by default; When initially configuring the repository for turnin the owner can state that they wish for each section to be placed in its own folder. If this flag is set, then the SemesterCode will have a letter appended based on course section. For example COMP221 for Fall 2010 would result in the following semester codes (F10, F10b) since it has two sections.
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.
...