Show Advanced KnowledgeHide Advanced Knowledge

Protected Sections in Portfolios from Portfolio Templates

1 Initial Problem

Portfolio templates serve a didactic purpose to both structure and provide the learning content. However, using the Portfolio may often result in the prepared Content being accidentally deleted. This is lived practice.

2 Conceptual Summary

We propose to protect sections in portfolio templates in order to prevent the deletion of the content inside this section. If activated, the author of the portfolio cannot be able to delete or edit the content in this section. Sections can be edited or deleted only in Portfolio Templates.

The dotted line arround of a section in edit mode of page editor should get a note about the protected status.

3 User Interface Modifications

3.1 List of Affected Views

Adding and Editing a Portfolio Page with a Section in Portfolio Template
Editing a Portfolio Page with a protected Section.

3.2 User Interface Details

3.3 New User Interface Concepts

no

4 Technical Information

Killing, Alexander [alex], 17 Mar 2021: This would be a very special handling for snippets in portfolio "only". I would suggest a more generic approach:

• A concext can define (e.g. portfolios or wikis), whether "protected sections" are possible or not. (via PageConfig)
• If activated the "Section" element will allow a "protected" attribute.
• The context will also provide information, if the current user is allowed to edit protected content (also via PageConfig).

Why this approach?

• The context can derive the "edit protected content" state from one of its permissions. E.g. the wiki may only allow this for "wiki admins" that have edit settings permissions (or introduce a special permission for this). The portfolio may set this to false always (no portfolio author can change this) and always to true for portfolio templates (portfolio template authors can always edit protected content).
• Sections are more suitable to have the "protected" attribute than snippets, since they may nest any other content, which would be "uneditable" in this case. This would also be true for snippets which use a section with a "protected" attribute. But it would also allow to add snippets without protected state.

Which user interface changes would come with this approach?

• The section properties would get an additional checkbox "protected" with an appropriate information text.
• The sections would state the state in the header, similar to the snippet header above.
• Trying to edit, delete or copy a single locked section would not be possible for the user. Moving around (drag and drop) would be possible. Note: If complete pages are copied, the copies include the protected sections.

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:
• 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

, 15 Apr 2021: Thank you Alex for your feedback and reasonable suggestions. I have made the necessary changes in the feature request.

Kunkel, Matthias [mkunkel], 15 APR 2021: I made a quite similar feature request for the wiki component, see Protected Sections in Wiki Pages. The aim of my request is similar to Oksana's. We want to prevent that selected content elements are changed or deleted by normal users. I strongly recommend to merge both requests and implement one feature that can be used in portfolios as well as in wikis (and probably in other COPage consumers in the future).

JourFixe, ILIAS [jourfixe], 19 APR 2021: We highly appreciate this suggestion and schedule the feature for ILIAS 8. The mentioned feature requests for read-only sections differs slightly because of the different context (here: portfolio, there: wiki). But the basic concept of implementation and permission handling is the same.

10 Implementation

To distinguish the sections from the page editor lock the uneditable status they assume is labeled "protected".

Test Cases

Test cases completed at 2021-10-07 by Tödt, Alexandra [atoedt]

• 49226: Block einfügen und schützen

Approval

Approved at 17-11-2021 by .