Feature Wiki

Information about planned and released features

Tabs

Cross-Assignment Data in Study Programmes: Continuous Validity

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 „gaps“ between times when users have a valid qualification which might easily be overlooked when users have many assigments.

2 Conceptual Summary

A type of data is introduced: "Validity Gaps" (German: "Lücken in Gültigkeit").
For each user account that has at least one existing assignment to the study programme, a "Validity Gaps" date (string) is determined and stored:
Pairs of dates are contained in it, comma-separated, each with a starting date of the gap (S) and its end date (E), separated by a hyphen: ("S1 - E1, S2 - E2, ...").
The starting date of retrievement is the date when the user first acquired a valid qualification.
The end date of retrievement is the current date.
By a migration, the data field should also be determined retrospectively (from the date, when the new version is deployed).

With users who until now didn’t ever have a valid qualification at all by now, both data have the value "-" (NULL).

3 User Interface Modifications

3.1 List of Affected Views

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 "Validity Gaps" (aggregation from single assignments)

6 Security

none

7 Contact

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]