Cross-Assignment Data in Study Programmes: Assignment Cycle

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 whose re-assignment „cycle“ isn't intact anymore (e.g., it terminates although they are supposed to persistently have a valid qualification) which might easily be overlooked when users have many assigments.

2 Conceptual Summary

A type of data is introduced: "Assignment Cycle" (German: "Zuweisungszyklus").
It mirrors whether at runtime there are obstacles to proper re-assignment after expiry of qualification.

For each user account that has at least one existing assignment to the study programme, the "Assignment cycle" may have one the following characteristics:

• intact (German: intakt):
  For the user account in question, there is exactly one assignment due to which re-assignment will take place.
• open (German: offen):
  For the user account in question, there is no assignmentdue to which re-assignment is warranted.
  The reason for this may be: Assignments have at most the status "In Progress".
• interrupted (German: unterbrochen):
  For the user account in question, there is no assignment due to which re-assignment is possible.
  The reason for this may be: Assignments have the status "Failed".
• not applicable (German: nicht anwendbar):
  For the user account in question, there is exactly one assignment with a qualification that will never expire.
• multiple (German: mehrfach):
  For the user account in question, there are more than one assignment due to which re-assignment will take place.
• no training event available (German: kein Training verfügbar):
  For the user account in question, there is at least one assignment that is "In Progress", but there is no course linked in which the user in question doesn't have the LP status "Completed" (so he/she hasn't any means to prove his/her qualifiaction).

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 "Assignment Cycle" (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.

• CaT Concepts and Training GmbH

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}.