jooola
If I understand this correctly the admin would define some defaults for the filter params but those values can be changed from the UI ? This isn't about creating a new "quality" property that will be used to always filter the content ?
That's correct. The plan is not to limit the quality of uploads etc. since people should be able to upload any content they want to. This is just to give a good first impression for the landing page by specifying some minimum quality parameters. There's no plan at the moment to extend this to other parts of the app such as search screens, although once the filters exist we would be able to consider it if there's call for it.
A bitrate can represent a lot of different quality depending on the format/bit depth/sample rate..., so I feel like it doesn't make sens to use it alone. To keep the filter simple, we could provide a function that transform abstract qualities (e.g. 1 to 10) to a set of formats/bitrates/... (mp3, >=256kbps), (ogg, >=192kbps), flac (24bit) ...
Interesting idea. This would require us to come up with a sensible set of defaults for each filetype as well as document each one and communicate the implications of the quality scale properly in the frontend. If done correctly, an abstract scale would be much more user friendly!
The has_art filter seem only to apply for albums right ? It could also be applied to artists, and we could require the artist to has some artwork.
Yes, there's no reason it can't be extended to artists. At the moment I don't think we show artists on the front page, but there's no harm building it in for future use.
has_release_date: false
Could you explain why you wouldn't set this one by default? If we're assuming an admin turns on the quality filter to give the best impression to new users, wouldn't having proper release dates (at least years) be desirable as a default?