Bug 31598 – Result directory should be named by the uid and not the exam-uid

Bug 31598 - Result directory should be named by the uid and not the exam-uid


Summary:	Result directory should be named by the uid and not the exam-uid

Status:	RESOLVED WONTFIX

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - Exam mode
Version:	UCS@school 3.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:	44157
	Show dependency tree / graph

Reported:	2013-05-31 15:55 CEST by Sönke Schwardt-Krummrich
Modified:	2019-02-05 21:49 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Usability
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Sönke Schwardt-Krummrich

2013-05-31 15:55:47 CEST

If a teacher collects the results, the files of a user are stored in
"/home/$TEACHER/Klassenarbeiten/$EXAMNAME/$EXAMUSERUID $VERSION"

but it would be easier to understand if the UID of the student is used instead of the UID of the exam user:

"/home/$TEACHER/Klassenarbeiten/$EXAMNAME/$STUDENTUSERUID $VERSION"

Comment 1 Florian Best

2016-12-12 10:11:51 CET

Then one cannot differentiate between exam user and non exam user (e.g. if one student is able to bypass the relogin).

Comment 2 Sönke Schwardt-Krummrich

2019-02-05 21:49:33 CET

This issue has been filled against UCS@school 3. The maintenance with
bug and security fixes for the last UCS@school version for UCS 3.x 
(→ UCS@school 3.2) has ended on Dec 31, 2016.

Customers still on UCS 3.x are encouraged to update to UCS 4.3 (or later). 
Please contact your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug"
or simply reopen the issue. In this case please provide detailed information on
how this issue is affecting you.