Marking Assistant for COMPSCI 235 Labs

Problem: Marking

Marking means specifying 0, 1 or 2 marks for a student for the current lab based on amount of lab tasks completed by the student.

So in order to mark for a student, the tutor needs to do the following:

1. choose which lab number or week

2. choose the lab session or datetime

3. identify the student

   • name e.g. Arnav Shekaran
   • ID photo
   • AUID number e.g. 835020202
   • UPI e.g. aaba999
   • email e.g. aaba999@aucklanduni.ac.nz

4. assess student's tasks Depending on how many tasks the student has completed, provide a mark of 0, 1 or 2.

Design Ideas

• lab number and lab session can be selected before each session to avoid accidentally providing a mark for the correct student but on the wrong session.

• lab number and session can be selected automatically based on date and time?

• instead of typing 0, 1 or 2, press it for speed

• one more click to go back to search page

• scroll through students for quick find or perform a text search using any id property

• show how many students done so far (extension)

• show if student has already been marked

• for phone or tablet (extension) or touchscreen laptop (extension)

• if they are multiple students with the same name, show a warning when searching or assigning marks to them (extension)

UI Design

Figma Design File

Modules

• get students list
• update shared excel file
• log all changes for backup in database
  • log these events
    • lab number or lab session selected
    • add student marks
    • student not being shown in list
    • any errors!
  • each log should contain
    • event details
    • datetime
    • lab TA id

Architecture & Tech Stack

Module	Chosen Technology
Database of saved marks and logs	Neon DB
App Hosting	Vercel
App UI	SvelteKit

get students list - ideas

• manually upload once?
• power automate (couldn't find tables in file)
• zapier (requires uoa admin access :( )

update shared excel file - ideas

• manually after each lab using excel scripts

Improvement Ideas

After Lab 1

• add loading after 'mark student' button is clicked ✅
• automatic screenshot capture not as useful as 👇
• automatic download a log and the marks ✅(even if database works)
• some students weren't found in the app search so I noted them on whatsapp some students weren't in the app's database/server storage because the source is the excel file which was updated TEMP solution: update from excel ✅ permanent solution: read excel automatically or use a common database for both?

After Lab 2

• have to go to database to export mark students data for excel automate script once lab is over, would be great to display the inputs for the excel script e.g. as 3 copy-paste actions on a laptop ✅

• small wait time after finished marking ✅ reduced and added success message feedback

• encourage tutor to put all marks in db into excel spreadsheet (not just the one being marked currently!)

After Lab 5

Some improvements during week 6 (lab05). Smooth sailing so far! Nice

• Haptic feedback for error. When something goes wrong, vibrate! ✅✅ vibrates for a second

• have to reauthenticate every lab session because cookie becomes invalid after X time (increase time?) ✅✅

• PWA: app on phone, not website anymore! more screen real estate, more smooth 😎😎😎 ✅✅

• Better Logo, right now it is too small to read or recognise 😭😭 ✅✅

• a way to logout on app because hard to navigate to /logout when there is no URL bar 😅😅

• when searching, the 'clear search' button is tiny next to the search button. The search button is no longer needed because it is only an affordance for what the box is for. The actual search happens automatically (without clicking the search button icon).