Improving usability of set up taxonomies

1 Initial Problem

ILIAS already supports taxonomies in categories with nodes at the same and on lower levels (nested). However the usabilty of taxonomies in categories in general is awful, as the user has to open alot of different tabs and has to know where to find the different functions or has to find them "accidantally". This feature is NOT user-friendly in this way.

2 Conceptual Summary

ILIAS should support the use of (nested) taxonomies in a user-friendly and intuitive way. This requires a different presentation of taxonomies in the editing area (Category > Metadata > Taxonomy Definition). It should be possible to add taxonomies and nodes as well as "sub-nodes" on the same page and also edit them from here. In addition, the user should be able to move nodes within the taxonomies of the category and change the sorting of the nodes AND taxonomies. Also without leaving the page.

Users should also be able to select on this page whether the taxonomies are displayed in the side block. This will eliminate the need for the "Category > Metadata > Taxonomy Settings" page.

2.1 In detail

Actions-menu of taxonomies:

Taxonomies are editable and deletable. After clicking on Delete you will be asked if you are sure (same screen as before). After clicking on Edit the Settings of the Taxonomy are loaded, where you can change title, description and Sorting of Nodes.

Note: Only when Sorting is set to manual, the nodes can be sorted manually. Otherwise the counters in front of the node names are not displayed.

Taxonomies can be shown in side block of the category by activating the checkbox and saving afterwards (by that the subtab Taxonomy Settings isn't needed any longer).

Actions-menu of nodes:

Nodes are

• editable
• deletable
• in case they are NOT ON TOP of the taxonomy: moveable one level back
• in case they already have been moved a level back: moveable one level forward

Nodes can be moved to another taxonomy by using the dropdown in front and saving afterwards. 

3 User Interface Modifications

3.1 List of Affected Views

• Category » Metadata » Taxonomy Definition
• Category » Metadata » Taxonomy Definition » Add/Edit Taxonomy
• Category » Metadata » Taxonomy Definition » Create Node
• Category » Metadata » Taxonomy Definition » Edit (no longer needed: most of the functions are in "Taxonomy Definitions" or in Editing tab of a single taxonomy. Advantage: no deeper structure needed)
• Category » Metadata » Taxonomy Settings (no longer needed: you can find the function in "Taxonomy Definitions")

3.2 User Interface Details

Subtab: Taxonomy Definition

Taxonomy tree in side block of category:

Add / Edit Taxonomy

Create / Edit Node

3.3 New User Interface Concepts

the legacy table is used as long as there is no new KS element for tables

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 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: Kunkel, Matthias [mkunkel], Seibt, Alina [alina.seibt]
• 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.

• ILIAS-Verein

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}

Approval

Approved at {date} by {user}.