Use user profile field match as precondition

1 Initial Problem

Granting access to objects by checking user profile fields is currently rarely possible in ILIAS. Using teh UserDefauls plugin and creating (local) roles may help in some cases, but has a lot of administrative effort and can only be configured if access to plugin administration is granted.

There should be a way to use the content of user profile fields (standard and self-created) as preconditions to allow such configurations without access to plugin administration and without the need for additional roles.

2 Conceptual Summary

Precondition creation shoud be extended with another tab, like "User Profile".

In this tab it should be possible to select a profile field (dropdown of visible fields?), a comparison type and a value (text input or dropdown).

Comparison types could be:

• is identical to
• starts with
• ends with
• contains
• regular Expression match
• in case of numerical fields
  • less
  • greater
  • equal
  • less or equal
  • greater or equal

3 User Interface Modifications

3.1 List of Affected Views

• additional tab on precondition creation screen
• Tab content that configures the profile match
• new entries on precondition configuration screen which reflect the settings of the new checks
• screens that list preconditions for object access with new precondition settings

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

3.3 New User Interface Concepts

none

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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

see 6

6 Security

If an author of preconditions could use fields with content not accessible to him/her, this screen could be used to find out the value a user has set in this profile. It should be only possible to use profile fields, for which the author has access to all users' entries.

7 Contact

• Author of the Request: Jackisch, Ingo [jackisch]
  
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

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}

Approval

Approved at {date} by {user}.