Collect all manage buttons on the manage screen

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

Current Situation in Course

2 Conceptual Summary

2.1 New arrangement of actions in View and Manage Subtab

The aim of the clear separation of actions with which the content of the page can be manipulated and actions ("Manage") with which the view of the page can be viewed ("View") is to make it clearer to users where they can find actions such as [Add new object] and [Import]. The similarity of [Add new objects], [Import] or (in courses and groups) [Adopt content] from existing containers leads to the conclusion that users should be able to find these actions in the same place.

New Button Arrangement in Content Subtabs

2.2 New Wording for "Manage"

To give users a better idea of what they can expect when they click on the Manage subtab, the term should be checked and optimized if possible.

The label should indicate that you can edit, add or import new objects here and manipulate several objects at the same time.

TODO Chris Potter ;) thx

2.3 Landing page depending on permission

We can assume that people with editing rights to an object most frequently want to perform one of the actions “Add new object” or edit the page. Therefore, users who have editing rights (often “Edit Settings”) should land directly on the Manage subtab when they open an object.
To view the page, they can then manually switch to the View subtab and see a tidy view of their object.

Users who do not have editing rights and can only view objects (Visible and Read) are taken to the View subtab.

3 User Interface Modifications

3.1 List of Affected Views

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

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

4 Additional Information

4.1 Involved Authorities

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

4.3 Privacy

{ Personal data that will need to be stored or processed to implement this feature have to be listed here. For each date give a short explanation why it is necessary to use that date. }

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

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers:  {Please add related profile link of this person}

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

6.3 Privacy

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

6.4 Approval

Approved at {date} by {user}.