global de-/activation of Taxonomies

1 Initial Problem

At the moment you can de-/activate taxonomies within a category. Furthermore you can see all existing taxonomies as an administrator in administration - search and find - taxonomies.

However, you cannot deactivate the taxonomy service globally, like for example the badge or competence services.

Why is this needed?

In the future, it should be possible to set up global taxonomies, what means that they should be set up in the administration just like metadata or badges. See FR: Global Taxonomies. 
For cases where only global taxonomies are to be used, it should be possible to prevent custom taxonomies.

2 Conceptual Summary

It should be possible to activate or deactivate the taxonomy service globally. The default should be "active".

In administration - search and find - taxonomies you can set the taxonomy service globally to inactive. By then no user on this platform is allowed to use taxonomies in categories. 

3 User Interface Modifications

3.1 List of Affected Views

• administration - taxonomy - settings

3.2 User Interface Details

3.3 New User Interface Concepts

none

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

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