Differences

This shows you the differences between two versions of the page.

--- sysadmin:services:moss [2024/04/09 18:50] – created tshinin
+++ sysadmin:services:moss [2024/04/09 18:54] (current) – kjohns23
@@ Line 5: / Line 5: @@
 ===== Workflow =====
-SoCS hosts a webform available at "sneakoscope.socs.uoguelph.ca". Clients are to fill out the webform and attach an archive of both the files that must be evaluated and any code files that were provided for the students to use.
+SoCS hosts a webform available at "sneakoscope.socs.uoguelph.ca". Clients are to fill out the webform and attach an archive of both the files that must be evaluated and (optionally) any code files that were provided for the students to use.
+Once the submission has been processed, a link is provided (manually until the system is fixed) with the results. The instructor will the decide whether to proceed with any cases and the result link will also be provided to the Academic Integrity Officer.
 ===== Authentication =====
-Authentication for MOSS is done through SoCS LDAP and is available to any client that are part of the faculty, sessional, or TA groups. Every semester, the result pages are manually configured for each instructor.
+Authentication for MOSS is done through SoCS LDAP. The upload page is available to any client that are part of the faculty, sessional, or TA groups. Every semester, the result pages are manually configured for each instructor in the apache vhost config file.
 ===== Configuration =====
-The webform is implemented using Python CGI which updates masterlist.txt and creates a config file for each entry. A cron job checks the masterlist.txt every 5 minutes and processes any entries within it with local scripts stored on the server.
+The webform is implemented using Python CGI which updates masterlist.txt and creates a config file for each entry. A cron job checks the masterlist.txt every 5 minutes and processes any entries within it with local scripts stored on the server. These scripts are written in Python. They read the configuration for a submission and extract and process the archives into the format expected by Moss (one folder per student with all code at the root), and then class Moss.pl against the processed submission files.