...

• 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 semester archived student data	Admin=(rw),Instructor=(rw),TA=(rw),netId=(rw)
  /archive/SemesterCode/netId/	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. 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 3 semesters; However, for students, the repository location of their turnin folder will change once the course is over, moving to the archive tree.
• 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. This means that repository data in the archive area will be left untouched once it has been created.
• No user permission blocks in the access file 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\]* or *\[/archive/XxYY/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 other than to delete the access block after three semesters. This means that you can change the permissions to anything you wish and they will carry forward.
• These repositories will grow without bound.

Usage

• Due to the copy and delete method used to move student's turnin folders after the current semester, there will be no way to clean up the repository to delete this old data. If it ever comes to the point where we need to clean up a turnin repository, it will require deleting the repository and recreating it, losing all but the last revision of the repository.

Usage

• Create a repository 'courseXXX'
• Mark this as a turnin capable repository and assign it to a specific course by subject and course
• Create a repository 'courseXXX'
• 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:
  • Scan the access file for permission block tags, for any users that should exist in the repository but for which there is no tag
    • Create the user folder /turnin/netid within the repository for current students
    • Create a permissions block in the access file for the user folder

Questions

• • On semester changes, all current students with folders in the /turnin/ folder will be moved to the /archive/ folder under a subfolder named FYY, SYY, or SuYY where YY is the last two digits of the year.

Questions

• How do they expect to handle How do they expect to handle instances where
  • A course repository was setup for a course and now two instructors are teaching two different sections of the course
• How much flexibility do they want to make their own changes to the
  repository, the access file and the /turnin/ and /archive/ folders?
  What do they believe they would like to do themselves? Are there use
  cases where they could need to fiddle with the automatic process?
• When do they want the semester transitions to occur? Should it be
  handled automatically, if so when, or on a random schedule set by each
  professor? If each professor decides when to transition their turnin
  repository to the next semester, how do they envision doing this?
  running a command line tool or visiting a web page, or using direct
  subversion commands?

Examples

Current access_file

...