Agorakit enables collaborative groups. Given this focus, location considerations are inescapable. Some groups will be geographically based. Others may not be. How should location be modelled in Agorakit?
Currently, we have:
Part of the question comes down to: what, if any, should be the geographic model of a particular Agorakit instance? Clearly, one way to address locality is to assume one instance per locality. So, for example, a given city has an instance, and all groups on that instance are de facto associated with that locality.
But this model quickly raises challenges. Even a city may have different neighbourhoods or boroughs.
So, maybe, we introduce an (optional) location for a group. But ideally we'd make that location (region?) an entity in its own right. One of my primary interests as a site user might be: what groups exist in my area? For that, we need the ability to filter by location. But what is a location? What scale does it exist on? Is it something that's derived from some geographic data set? Are regions nested?
Should event locations (venues) be a distinct entity, also mappable, and able to be linked to multiple events, even events of multiple groups?