Feature Wiki
Tabs
Cross-Assignment Data in Study Programmes: Currently Validity
Page Overview
[Hide]This page is related to Use PresentationTable for Cross-Assignment Data in Study Programmes as specifies one of the new data types mentioned there.
1 Initial Problem
A risk for study programme administrators (whose responsibility is often to warrant satisfaction of crucial legal requirements to their organsation) is that there are users without a currently valid qualification which might easily be overlooked when users have many assigments.
2 Conceptual Summary
A type of data is introduced: "Current Validity" (German: "Aktuelle Gültigkeit").
In case a user has any valid qualification now (no matter from which assignment), the value is „Yes“, otherwise it’s „No“.
3 User Interface Modifications
3.1 List of Affected Views
- new view ("Aggregated by Users", German: Nach Benutzern aggregiert), s. Use PresentationTable for Cross-Assignment Data in Study Programmes
3.2 User Interface Details
s. Use PresentationTable for Cross-Assignment Data in Study Programmes
3.3 New User Interface Concepts
none
3.4 Accessibility Implications
none
4 Technical Information
{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }
5 Privacy
Data type "Current Validity" (aggregation from single assignments)
6 Security
none
7 Contact
- Author of the Request: Suittenpointner, Florian [suittenpointner]
- Maintainer: Klees, Richard [rklees]
- Implementation of the feature is done by: Klees, Richard [rklees]
8 Funding
If you are interest in funding this feature, please add your name and institution to this list.
9 Discussion
10 Implementation
{ The maintainer has to give a description of the final implementation and add screenshots if possible. }
Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
Privacy
Information in privacy.md of component: updated on {date} by {user} | no change required
Approval
Approved at {date} by {user}.
Last edited: 8. Feb 2024, 18:11, Suittenpointner, Florian [suittenpointner]