From dd52c913c454b9a6cf9ab7e7b102f9e7ede31754 Mon Sep 17 00:00:00 2001 From: Florian Fischer Date: Sun, 19 Jul 2026 11:55:51 +0200 Subject: use a single submit table to decrease load times --- doc/graduation.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) (limited to 'doc') diff --git a/doc/graduation.md b/doc/graduation.md index 3990744..2466c44 100644 --- a/doc/graduation.md +++ b/doc/graduation.md @@ -2,20 +2,24 @@ ## Tables -There exist three different tables to hold all graduation information per student. +There exist three different tables to hold all graduation information of a student. +One global submission table called `Submit` writable by all students and two individual ones per student. The separation is needed for the different required permissions to access the stored data. -All tables use the following naming scheme `${StudentId}${Purpose}`. +All individual tables use the following naming scheme `${StudentId}${Purpose}`. The section containing the student's tables is only available to teachers and the student. ### Submit Table -The submit table is writable by the student and is used to track observation requests from the student. +The submit table is writable by all students and is used to track observation requests from students. +It is configured to require approval to publish entries. +This ensures that entries are only readable by the submitter and the teachers. +Entries are simply never approved. ### Public Table The public table tracks all graduation changes known by the student. -The included information are sufficent to render a student's profile. +The included information are sufficient to render a student's profile. Changes can be submitted by any teacher. Each change is valid until a subsequent change renders it obsolete. -- cgit v1.2.3