You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

This page will contain a list of issues/questions that need to be addressed before moving forward with any changes to the Turnin process.

Step me through exactly what they are expecting.

Assumptions

  • Repository Layout

    Folder

    Use

    /course/

    for course specific instructor provided material

    /rice_config/

    for subversion configuration and permission management

    /turnin/

    for all students course use

    /turnin/netId/

    for each student's course use
  • They want repositories tied to a full course (eg COMP412). This means ALL sections.
  • They DO NOT want repositories tied to specific sections of a course.
  • They want ALL users of a repository to 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

  • They will create a repository 'courseXXX'
  • They will 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

Questions

  • 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
  • No labels