Save Individual Taxonomy Settings

1 Requirements

By now (version 5.1), users can filter category content by means of taxonomies, however, they have to state their choice every time they open the category.

This way, category taxonomies loose a lot of their – potentially tremendous – benefit  category structures: In a lot of cases, taxonomies could replace huge category structures which now have to be nested into each other.
Moreover, taxonomies could solve the problem that with nested categories the administrator always has to make a decision on what dimension is more important and, thus, is mapped on a higher repository level (like location vs. topic vs. time interval).

In order to save those benefits, I see the need for taxonomy settings being saveable by the users. Otherwise, the effort of choosing taxonomy settings every time is too high.

So, I’d like to suggest to introduce taxonomy settings that can be saved (similar to how settings of learning progress tables can be saved).

The settings should then only be reset if a user actively asks for it. For the latter purpose, there should be a “reset” button below the taxonomy settings.

2 Additional Information

• Idea / concept: Suittenpointner, Florian [suittenpointner]
• Interest in funding: (please indicate if you are interested/able to fund this feature)
• Maintainer: (will be set by Jour Fixe / maintainer)
• Implementation of the feature is done by (will be set by Jour Fixe / maintainer)
• Testcases by: (please add your name if you want to create the testcases for this feature)

3 Discussion

Zenzen, Enrico [ezenzen], 05 SEP 2022: This request no longer fulfills the requirements of the Feature Wiki. In consultation with the maintainer I change the status of the feature request to "Redundant / outdated". If the request is still relevant, please update template and mockups.

4 Implementation

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