title: How can I use OrderingFilter along with other Filterset filtering on a model
body: <p>I have a model lets say <code>ObservedMoves</code>. 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 <code>ObservedMovesFilters</code> that subclasses <code>django_filters.Filterset</code> and has a meta field <code>model = ObservedMoves</code>. </p>
  
  <p>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 <code>OrderingFilter</code>. If I try to subclass the <code>OrderingFilter</code> class instead of the <code>Filterset</code> class the filters don't work. If I specify <code>OrderingFilter</code> as the default filter backend again the filters don't work. </p>
  
  <p>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?</p>