Architect MC traits about mc-map

[jossim]

Is it reasonable to assume that the number of contexts will be well defined? I can think of kind, day/time, location/region, mission/focus. There may be more that are useful. Will these traits just be used for filtering?

[elben]

Doesn't your statement "there may be more that are useful" show my point? ;)

[elben]

Not necessarily filtering. The front-end filtering should be de-coupled from back-end traits of a Community. Again these generalization problems are NOT worth solving right now for the Stone. This issue is just a reminder for us to think about it, and would need to be solved if other orgs start using the product.

[jossim]

Well the usefulness depends on the use, which was the point of the question at the end. I think it's fairly well defined what should be filterable on the front end so probably nothing extensible is needed there. I don't know what uses there will be on the back end so I can't define all those contexts, however that doesn't mean they can't be, we'd need to ask someone who uses the back end a lot to get an ideas; even still it's possible that they can't be well defined. So is a good feature to think about when this is being generalized to other organizations.