I have a model lets say `ObservedMoves`. This model is referenced in many queries inside my views. So instead of applying the filters that I want directly inside each view I have them abstracted inside a filterclass let's say `ObservedMovesFilters` that subclasses `django_filters.Filterset` and has a meta field `model = ObservedMoves`. 

Now what I want to do is to enable the user to specify the ordering field when giving a request. For that I plan to use DRF's `OrderingFilter`. If I try to subclass the `OrderingFilter` class instead of the `Filterset` class the filters don't work. If I specify `OrderingFilter` as the default filter backend again the filters don't work. 

In DRF's documentation the only method presented is specifying inside a view the alternative filter back end and also specify the ordering parameters but I want to avoid explicitly defining it in every view that queries that model. Is there a way to do that?