Not every algorithm has a "learning method"

[johannesjmeyer]

Is your feature request related to a problem? Please describe. E.g. QAOA is an optimization algorithm and therefore no learning method, which is why the corresponding field is left blank. "Learning method" is therefore not a general property and should not appear on every algorithm page.

Describe the solution you'd like Remove "learning method". I suggest to replace this with "Tags". This would still allow the Stuttgarters to keep "Learning Method" as an implicit category for taxonomy purposes, but it will not be displayed to the user. The tags could then be either "Supervised Learning" or "Learning Method: Supervised Learning". I would prefer the first one, because the second one is redundant. If one would want to distinguish this special category "learning methods" one could do it via colors.

One could also think of subsuming all the existing "tags" under one "Tag" blob in the aforementioned way.

[johannesjmeyer]

An alternative could be to just hide fields that are not used. In this way, we couuld include more fields that people might be interested in, e.g. "References" or "Extensions", so that they need not be hacked in as in the QAOA algorithm currently

[miwurster]

At the moment it is implemented in a way that the "view" component of an algorithm can be used to directly "edit" it, i.e., we cannot simply hide the filed if there is no value otherwise user won't be able to add learning methods anymore. There are no plans to make a distinction in the near future in that area.