Integrate Permission Manager Plugin into trunk

1 Requirements

Editing permission settings is a neccessary evil if existing objects need to be updated or if new repository objects are supposed to be available in existing courses.

The role management system offers the feature "Copy permissions", however covering large numbers of objects including all local roles (crs_admin, crs_tutor, ...) really takes a long time.

The plugin "PermissionManager" makes this work far easier and offfers bulk actions for subtrees. It should be integrated as a core feature, because it is really handy and saves all admins a looooooooooaaaaaaddddddddd of time.

In addition, the Permission Manager functionality should be extended for a trunk integration to support didactic templates. It should be possible to filter for

• those objects that do currently use a certain didcatic template
• those objects the do not use a certain didcatic template
• to select multiple templates in one go (alter all object except "collaborative courses" and "study groups"

Screenshot

2 Additional Information

• Idea / concept: Christian Bogen (Uni Stuttgart) and Marko Glaubitz (Uni Freiburg)
  
• Interest in funding: (please indicate if you are interested/able to fund this feature)
• Maintainer: (will be set by Jour Fixe / maintainer)
• Implementation of the feature is done by (will be set by Jour Fixe / maintainer)
• Testcases by: (please add your name if you want to create the testcases for this feature)

3 Discussion

Amstutz, Timon [amstutz] 25. July 2016: This FR lacks some relevant information. Where is this new screen to be placed? In the Admin menu? If yes, in which node? What permissions are needed to use this component for a certain aspect of the tree?

Further, the selection of the ref_id needs to be improved. We should use a Picker (where the user sees the tree visually and picks a node from it) for this. What is a role filter?

Glaubitz, Marko [mglaubitz] 25.07.2016: I suggest placing this function under "Administration" -> "Roles" als a new Tab. This would solve the permission question as well, because if somebody has the permission to alter the set of global / local roles and role templates, they should be able to use the "permission manager".

JourFixe, ILIAS [jourfixe]: July 25, 2016: We like the feature and think it is a very useful improvement of the RBAC that helps a lot of administrators. According to Stefan, he won't have the time to finish this feature until end of August. So it won't make it into 5.2. But this gives us a bit more time to finalise the concept. It would be nice

• to use also 'Roles' as a template to change roles (and not only 'role templates').
• to get the list of objects in a alphabetically sorted list with all plugin object titles translated.
• to add an information to the filter which expressions can be used for the search query.
• to flag all role templates that are only used for this purpose and to hide them in the list of role templates when a new role is created.
• to know more use cases about this feature and to get a clear impression about where this feature is presented.

Kiegel, Colin [kiegel] 2016-07-27: This ticket should clarify where this function can be found. I would prefer some kind of action on roles and role templates. I would even suggest to merge this concept with the existing "copy role" action - because this is just a different aspect of copying roles.

IMO the copy roles action could lead to a new screen with two options

• Option 1: change definition of target role (or target role template)
  • this is the old copy-role-action with no additional options but the target role
• Option 2: change repository objects for target role
  • sub-options according to this ticket

Bogen, Christian [bogen] 28.07.2016: I’m not sure if you realize how much more the plugin does right now than the copy role action. The plugin is all about flexible (and complex) filters and being able to recursivley travese defined category trees. I don’t see how the copy role actions solves this. That being said, if Stefan Meyer thinks the (plugin’s) functionality can be fully integrated there, I wouldn’t mind.

As to the JF request for use cases: I will try to add some ASAP.

4 Implementation

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