What problem are you trying to solve with Submitty
Currently only system administrators with direct database access can archive & un-archive courses.
(This setting is the 'status' field of course 'courses' table in the master Submitty database)
see also:
https://submitty.org/sysadmin/configuration/course_archiving
Describe the way you'd like to solve this problem
Let's add a UI for the instructors from the "Course Settings" page, add it in the new "Danger Zone" area introduced in this PR:
#10778
There should be on page documentation explaining what will happen if the instructor archives the course. And a link to the documentation above.
Instructors should also be able to un-archive a course -- but there should be more caution on this feature. On our system the sysadmin manages the files of old courses, and moves them to disks/partitions that may not have much available space, so unarchiving a course and then submitting large files or attaching large course materials could cause problems if the disk or partition space is exceeded. We may want to add an "unarchivable" status -- and then only a system can apply or unapply that status.
What problem are you trying to solve with Submitty
Currently only system administrators with direct database access can archive & un-archive courses.
(This setting is the 'status' field of course 'courses' table in the master Submitty database)
see also:
https://submitty.org/sysadmin/configuration/course_archiving
Describe the way you'd like to solve this problem
Let's add a UI for the instructors from the "Course Settings" page, add it in the new "Danger Zone" area introduced in this PR:
#10778
There should be on page documentation explaining what will happen if the instructor archives the course. And a link to the documentation above.
Instructors should also be able to un-archive a course -- but there should be more caution on this feature. On our system the sysadmin manages the files of old courses, and moves them to disks/partitions that may not have much available space, so unarchiving a course and then submitting large files or attaching large course materials could cause problems if the disk or partition space is exceeded. We may want to add an "unarchivable" status -- and then only a system can apply or unapply that status.