threefins
commented
4 months ago Front end wise, I'm keen to make the easiest/quickest/non-crap tag filtering thing to start with here. I suspect we'll need some back end data changes.
Currently we have :
- Gig:
- tags Venue:
- tags (possibly) Sets:
- act 1:
- genres
It's a bit tough to make a call on where we should get tags from. If a venue is normally wheelchair accessible, but for some reason a gig is not so accessible, or the venue is normally not age restricted but the gig is for the under-5s that will get a bit icky. Likewise, if your third headliner is "Simpsonwave" (yes that is a thing), it might be misleading to tag the gig as "Simpsonwave".
For that reason, I am thinking to only consume tags from the gig to use in filtering. We can always make the API populate gig tags more smartly from acts and venues without changing the API.
I think it may not be avoidable to use a controlled vocab for the tags too - specially if we want to do stuff like filtering by specific things. This may need a backend change but hopefully we can do something that does not increase the admin overhead!
It may be nice to fetch aggregated tags and values (maybe even indicative counts but let's not go crazy) from the api so it's easier to populate filtering etc.
bringthepunters
We need three kinds of categories (tags?) I dont think we have right now:
1) age limits - under 18 only, over 18 only, no restrictions 3) accessibility tags eg "wheelchair friendly"