collections will likely be difficult for a couple really big reasons:
choosing one collection is equivalent to choosing two variables. that makes for some complicated ui/ux and/or variable constraints issues.
collections have more than 8 values very often, but we dont want to have a dependency on derived collections
since collections are functionally two variables and the map markers all take one variable, we need to get creative about how collections play in the map markers
Some thoughts of my own that might mitigate the above:
If we can agree collections only can be overlay, at least for the start, that will simplify things some
if collections are only overlay, then they are part of marker config. that is already somewhat complicated and sets the expectation to choose values for the donuts and bar modes. so choosing values from a collections vocabulary would somewhat naturally extend there. but we def needs mockups for this, and those mockups need to keep in mind we now need to support both cont and cat collections.
we might want new collection aware viz plugins? then whether you used a cat collection, cont collection or regular variable in the map markers we might show different floaters as being available?
im hoping @asizemore can make and present mockups in a ux meeting. but id like to be involved in drafting them.
collections will likely be difficult for a couple really big reasons:
Some thoughts of my own that might mitigate the above:
im hoping @asizemore can make and present mockups in a ux meeting. but id like to be involved in drafting them.