Additional Search Parameters for Copy Permission Target Roles in Administration

1 Initial Problem

On large and long-lasting installations, local roles have to update regularly to add ur substract permissions becasue a new plugin has been installed or because some new functionality has been introduced. Existing courses and groups need to be touched with the "copy permission" function.

The problem is, however, that the "copy permissions" funtion in the role administration currently only offers to search for (parts of) role names, i.e. "course admin" or "group member". For the installation of a mid-sized university this search yield 30.000 hits which are the paged into 60+ 400 packets (depending on the amount of rows selected). It takes approx. 2 minutes (!) to complete. This search and browsering through the pages results takes ages (because for every page change the search is performed again)! Finding and updating a subset if target roles by whatever parameters is not possible at all.

It is, in addition not possible limit / narrow down this search by any means, like restricitng it to only ccover a branch in the repository (scenario: all courses of branch "Summer Term 2019") or to search for the course title like "Introduction to linguistics" or to the owner. And so on.

2 Conceptual Summary

We propose ot introduce search parameters / "filters" (I know that this is not the right term) to narrow down the search for role targets by adding limiting parameters, like:

• context / part of repository through a multi-select repository picker
• object title text input
• owner > text input with auto completion
• type of object / role descendance > radio group + drop down for did templates:
  • default vs. derived from didactive template (with picker for didactive template)
  • for groups this could be: open / closed (which are default and a default did. template called "closed group"
• date of creation from / until > date picker

3 User Interface Modifications

3.1 List of Affected Views

Administration > Roles > "Copy Permission" > "Search for Role Title"

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

{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

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 Information

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security Implications

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Glaubitz, Marko [mglaubitz]
• Maintainer: Meyer, Stefan [smeyer]
• 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.

• Universität Freiburg

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