Skip to content
This repository has been archived by the owner on Jun 3, 2020. It is now read-only.

Smarter set selection #175

Open
rogerhutchings opened this issue Sep 3, 2015 · 0 comments
Open

Smarter set selection #175

rogerhutchings opened this issue Sep 3, 2015 · 0 comments

Comments

@rogerhutchings
Copy link
Contributor

At the moment we're using the new metadata filtering to select an artist's sets, which works great, apart from the fact that you have to know which artists have active sets in advance. This means that we have to hardcode some data on the front end, i.e. artist: { active: true }

But as metadata is now indexed, we could instead give all of the active sets a common property (active: true), and request all of them in one go without the speed penalty. This means we don't need to amend any front-end code when adding new artists, we only need to make one request for sets, and we can do a true random sampling for those who haven't chosen a set. Also, @ggdhines's aggregation code can deactivate sets independently once its members are classified.

Props to @camallen for the idea

Related to #109

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant