Nudging user who blocks page editor

1 Initial Problem

If 'Edit Lock' is activated for the ILIAS page editor, only one user can edit a page (in a wiki or in other components using the IPE). In case, user A starts editing at 09:00 and user B tries to edit the same page at 09:01, ILIAS sends a notification to user B telling that the page is currently edited until 09:xx (depending on the minutes defined in the administration setting).

Unfortunately, users like user A often forget to stop the editing process by hitting the related button on top of the editing view and just leave the object. Even if this user is no longer editing the page, ILIAS won't allow to edit the page for user B until the minutes of inactivity has been reached.

2 Conceptual Summary

It would be helpful for user B to contact user A easily and to ask if she/he could finish the editing process and to allow user B to edit the page as well. This notification should be delivered by an OSN (toast) and come with two options:

1. a button to finish the editing process immediatelly (in case the user is no longer in the object). This is the same button that exists in the IPE already.
2. a button to notify user B that A still needs some time to edit page. Message would be "I still need some time to finish editing." The notification text is a language variable. Text input is not supported to keep feature simple.

3 User Interface Modifications

3.1 List of Affected Views

• New On-Screen Notification

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: Kunkel, Matthias [mkunkel]
• Maintainer: Killing, Alexander [alex]
• 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}.