[ftr] Dynamic taxonomies for annotations

[bwbohl]

Is your feature request related to a problem? Please describe.

Edirom Online is designed to classify annotations with two taxonomies: Edirom Category and Edirom Priority. Often, editions endeavour to use their own categories, do not use priorities or come up with their own concept. This might result in empty columns or, e.g., the category column filled with categories from different taxonomies.

Describe the solution you'd like
It would be good to dynamically create the columns and fields in the annotation list and annotation views, based on the taxonomies used.

Describe alternatives you've considered
none

Additional context
This requires changes, both in the Edirom-Backend and Edirom-Frontend.

[daniel-jettka]

Isn't it a feature that only the categories and priorities actually used are displayed?

Or is there another problem in the frontend that it looks weird when no categories and/or priorities are used?

[bwbohl]

It’s not about displaying more than is needed, so if an edition doesn’t use ediromPriority or ediromCategeory taxonomies but other taxonomies, these would have to use the former as classes to be displayed. Moreover, e.g., when not using priority, the annotations JSON would include the priority property for every annotation, and the corresponding column would be shown, although it’s of no use for the edition.

For example, in the BAZ-GA, we came up with our own system that only partly fits into the category/priority system.

[bwbohl]

The intention of this modification is to make the annotation view more data-driven and display the columns provided by the data.