Global Taxonomies

1 Initial Problem

It is currently not possible to provide one or more taxonomies for the entire ILIAS installation. Taxonomy support is restricted to categories, glossaries and question pools/test questions. But if you want to use taxonomies as an additional access to the various content of your installation, the support for global taxonomies to which every content could be assigned is necessary.

2 Conceptual Summary

It should be possible to create one or more taxonomies for the entire repository and make it available in all components that are already supporting taxonomies.

• Global taxonomies are added and edited in Administration » Taxonomy.
• Global taxonomies can be set to Inactive / Active.
• Global taxonomies can be exported and imported (see also Considering taxonomy assignments in export and import )

3 User Interface Modifications

3.1 List of Affected Views

• Administration » Taxonomy » Settings
• Administration » Taxonomy » Global Taxonomies

3.2 User Interface Details

3.3 New User Interface Concepts

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.

• …

9 Discussion

JourFixe, ILIAS [jourfixe], 5 Feb 2013: We appreciate the feature and schedule it for 4.4.

Kunkel, Matthias [mkunkel], 30 Dec 2013: Implementation has been postponed due to missing funding. New status is 'not scheduled yet'. Please add this feature to the Jour Fixe agenda again when funding is available.

Kunkel, Matthias [mkunkel], 29 APR 2021 : Former request updated to new template and extended description.

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