Hide individual metadata block

1 Initial Problem

On each page, a user can "hide" the Secondary Panel with Custom Metadata or show it via "Page Actions" entry "Show additional properties".

The action applies to the entire Custom Metadata panel, regardless of whether or not they have been entered in one or several individual sets.

It would, however, be useful to have the option to chose which sets should be shown or hidden, e.g. when you have a set of metadata for internal use only.

2 Conceptual Summary

Hide one metadata set

Metadata set can be hidden by clicking the action menu of a given metadata set and selecting "Hide". The functionality of this should be changed to hiding only this one particular set of metadata rather than hiding all of them.

Button Group "Show / Hide Metadata"

Hidden metadata panels are to be made visible again via a separate button group labeled with "Show / Hide Metadata".

Here you can find an entry for each metadata set to hide this set if it has not yet been hidden via the Actions menu, or to show it if it has already been hidden.

This button group is only displayed if the "Manage Custom Metadata" option is enabled in the wiki settings.

Metadata can still be edited via the Metadata tab.

3 User Interface Modifications

3.1 List of Affected Views

• Wiki > Content > Secondary Panel > Actions > Hide
• Wiki > Content > Page Actions
• Wiki > Content > Wiki Functions

3.2 User Interface Details

3.3 New User Interface Concepts

No new UI concepts.

3.4 Accessibility Implications

Button Group must be controllable with the keyboard.

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: Seiler, Yvonne [yvseiler], Thiel, Anja [athiel] (Universität Bern)
• 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.

• Universität Bern

9 Discussion

Killing, Alexander [alex] 7 June 2023: Thanks for the proposal. I fear migrating an action dropdown to a panel with (shy buttons?) representing actions is not a good idea. First, I am not aware of any similar panel in ILIAS mainly holding actions in this way. Additionally, what kitchen sink elements would be used inside the panel? A listing of shy buttons and links? The current "Wiki Functions" panel, which holds mostly links needs a legacy template. I would not like to introduce a new legacy template here (for the action panel content), for something that is currently (trunk) a full KS component (actions in a dropdown). Could you discuss these issues in the UI clinic, please? I think it would be better to have two separete feature requests for this. One for the migration of the actions to a panel, and one for the (de)activation of distinct metadata sets. I think the second is a valuable feature, but with different options regarding a possible UI. E.g. we could simply add corresponding actions to the existing dropdown. Or only one action that opens a modal offering checkboxes for each set (currently my preference).

Seiler, Yvonne [yvseiler] 13 JUNE 2023: Thanks for your comment @Killing, Alexander [alex]. Unfortunately, I do not yet understand exactly what should be discussed in the UI Clinic. Something like "Do we generally allow actions to be displayed in a secondary panel as a Shybutton" or ...? The use of such buttons has already been accepted and implemented in the following request for the Revamp Repository Chat. Or do you mean with "E.g. we could simply add corresponding actions to the existing dropdown" that you don't see any problems with the actions in the current "Wiki Functions" panel, but in a separate "Wiki Actions" panel?

I made a separate requests (removing actions from wiki functions: Separate Page Actions of Wiki Pages

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