Revise Prepopulation of Content for Recapitulation of Type Text

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ.

1 Initial Problem

At the time beeing setting up a content for recapitulation is supported by a prepopulated content that is generated by the HTML output that is also used for presenting the best solution (the best solution is a kind of content for recapitulation and this feature was called Suggested Solution in the past).
The problem is, that this content can contain images depending on the ilias version and not on the content itself that is managed by the user, because these images are taken from the templates dir instead of using an object of type mob. Serveral problems can come up with this circumstance.

• This images are taken from the templates dir, but the referencing html content is stored to the database permanently - changing the layout in ilias by switching to other images leads in the fact that the old images will be removed propably. The images cannot be shown anymore, until the question author corrects the images.
• Skins can get outdated and removed, this leads in unavailable images for the referencing content, trhat was created during the existance of this outdated skin.

2 Conceptual Summary

Sugegstions:

• create mobs for this purpose on demand
• new type for this feature: best solution
• defining placeholders for a whitelist of images depending on the content

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

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, please provide a link to separate feature wiki entries for each of them according to the kitchen sink template.}

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 Contact

• Author of the Request: {Please add your name.}
• 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.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• ...

7 Discussion

Kergomard, Stephan [skergomard], 2022 Mar 9: We close this as part of the cleaning up effort undertaken in the Splitting-Up Test & Assessment Workinggroup.

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