Substitute-Mechanism for Editing Forum Posting Drafts

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

Drafts of forum posts can currently only be edited and published by the creator themselves. However, in some scenarios - such as in the case of substitution - it makes sense for other users to also be able to access, edit and publish the created draft post.

2 Conceptual Summary

The forum should therefore be expanded to include a function that enables the forum post creator to grant users from his contact list access rights to a draft forum post he has created. The setting should be possible directly in the general forum settings. If a blanket representation policy has been set up in the forum, then “Release for defined users” can be selected for the individual post draft. To do this, the existing action menu must be expanded to include a corresponding entry.

Approved forum post drafts are displayed in the post thread of the user who received the approval in the respective forum with the note “Approved”.

The published forum post contains information about the creator and the publisher.

3 User Interface Modifications

3.1 List of Affected Views

• general forum settings - approval
• Approval of draft forum posts
• View for users who received the approval
• View for users after publication

3.2 User Interface Details

General forum settings - approval

There is a new entry “approvals for draft posts” in the general forum settings. 

Here the user can specify which other users from his contact list can edit his draft forum posts.

After click on "save" a message appears: "your changes have been saved".

Approval of draft forum posts

To approve a draft forum post, the user clicks “Approval for specified users”.

A message appears: "Approved for specified users".

View for users who received the approval

View for users after publication

3.3 New User Interface Concepts

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

{ 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

{ 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: René Sens, Bundesverwaltungsamt
• 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}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.