CUED - Qualtrics Surveys. Tests that the TO can run

Checking the program that reminds staff

~tl136/QUALTRICS/programs/mailstaff.py studentyear=3 term=Mich message=~tl136/QUALTRICS/mailtemplates/mailmessage2 mail=no

produces lines like

mail tso24 about 3F1 Information Theory URL=3F1_Mich.html attaching image3.jpg

showing that tso24 is thought to be lecturing 3rd year students in Mich. It will also show the message they'll get - in this case the one in ~tl136/QUALTRICS/mailtemplates/mailmessage2. The attachment will be a QR code for http: ... 3F1_Mich.html.

You can see what a particular staff member will be mailed by using the id option. For example, you could try

~tl136/QUALTRICS/programs/mailstaff.py studentyear=3 term=Mich message=~tl136/QUALTRICS/mailtemplates/mailmessage2 mail=no id=tso24

The information is extracted from the TODB. The program will print messages if the TODB data isn't clear. For example,

Term for 4PG jml1010 is blank. Ignore it

would mean that the Term field for 4PG is blank.

With mail=yes instead of mail=no in these commands, the staff are mailed.

Checking the configuration files

Each survey is created from configuration files that are created using the TOBD information. These files can be checked before the surveys are created. Error messages will be printed if the TODB data isn't clear.

IA - Running the ~tl136/QUALTRICS/programs/createIAconfigs.py program outputs information - e.g.
```
Creating Lectures
In total -
26 courses
31 course/lecturer pairs
Creating Coursework
In total -
30 courses
32 course/lecturer pairs
```
The Lectures configuration files contains Lecture information and has lines like
```
"Maths (Fast)" "Mich"
 Professor Smith
```
The CourseworkInfo file has Coursework information with lines like
```
"Drawing" "Mich"
```
IB - The ~tl136/QUALTRICS/programs/createIBconfigs.py program creates 3 files. The lecture and coursework ones are like IA's. The extra one for electives has lines like
```
Professor Flewitt "Electrical"
```
The program also outputs information
IIA and IIB - The ~tl136/QUALTRICS/programs/createIIAconfigs.py and ~tl136/QUALTRICS/programs/createIIBconfigs.py programs create a folder (default name tmp) of configuration files, each filename being the code of a module. Each configuration file contains the module name and lecturer names. For example, 3B1 might contain
```
3B1: Radio Frequency Electronics
Dr Robertson_PA
```
Some multi-lecturer modules have per-lecturer titles. For example, 3A1 might contain
```
3A1: Fluid Mechanics I
Applications to External Flows: Prof Babinsky
Boundary Layer Flows: Dr Li
Flow Around Vehicles: Prof Tucker
Incompressible Flow: Prof Juniper
```

Testing the surveys

The installed surveys can be run by any Raven-authenticated person.

Listing available surveys

To get a full list of installed survey files available, run ~tl136/QUALTRICS/programs/listsurveys.py. You will need the Qualtrics password for this - the "API token". You will see a list with items like

81 4C8: Vehicle Dynamics SV_cvbxW3PGV8XhVqJ False
82 IA course survey 2018/19 SV_d5UmziDOX4KmLiJ True

The first number on the line is just a count of the surveys. Then there's the survey title, the survey ID, and finally False or True to indicate whether the survey is enabled.

Checking number of replies

~tl136/QUALTRICS/programs/getnumberofreplies.py outputs a CSV file showing for each active survey the number of replies and the date of the newest reply. Here's an extract -

30,2020-03-05,"3E6: Organisational Behaviour"
1,2020-03-02,"4M1: French"
25,2020-01-22,"4M17: Practical Optimization"

Checking who will receive reports

IA - If the per-lecturer reports for IA are put in a folder, then running ~tl136/QUALTRICS/programs/mailIAdocs.py mail=no in that folder will do a dummy run
IB - If the per-lecturer reports for IB are put in a folder, then running ~tl136/QUALTRICS/programs/mailIBdocs.py mail=no in that folder will do a dummy run
IIA and IIB - If the PartII per-lecturer reports for a student-year are put in a folder, then running ~tl136/QUALTRICS/programs/mailIIdocs.py mail=no in that folder will do a dummy run

The output of all these programs will show you which attachments each staff member will be sent. For example, this section of output shows the mail that would be sent about the 3D3 course.

mail fam20@cam.ac.uk
Subject: 3D3 student feedback 
Attachment 3D3:___Structural_Materials_and_Design_Lectures_+fam20+mo318.pdf
Mail disabled
mail mo318@cam.ac.uk
Subject: 3D3 student feedback 
Attachment 3D3:___Structural_Materials_and_Design_Lectures_+fam20+mo318.pdf
Mail disabled

File naming convention

Many files are produced, especially during report production. The programs that automated the process expect filenames in particular forms. It may help to know what the names mean. As far as possible the files produced are text files

File types

*.png - image files (QR codes)
*.tex - LaTeX files. The PDF reports are produced from them
*.html - HTML files, to be put on the web
*.aux, *.log - junk files left over from producing the PDF files
*.pdf - PDF reports

File names

There are names like IALectures.pdf, which are self-explanatory. For Part I there are names in the form
Module title+Lecturer+Term.tex
where the lecturer is in the form Title Surname. For example, there's

Mathematical Methods+Professor Woodland+Easter.tex

Sometimes the term appears in the module name, so the term might appear twice.

Department of Engineering

IT Services