Rather than use contexts for this, use aggregate navigation. It's not what aggregate navigation was designed for but it's something that I've used it for in the past. Typically you'd use it in an OLTP schema. As Amit says, you wouldn't generally put disparate tables in the same universe but it can often be the case that the same target audience would need them both.
↧