|
And then how do we handle all the children of the topics that appear in multiple places? Do we replicate everything every time? That will quickly become unwieldy and a significant performance concern - especially once we have web-based access. This is readily handled for aliases because an alias is not the "true" topic. But if the "true" topic actually lives in multiple places, now what do we do?
The primary reasons for only having a single container are to (a) keep everything simple AND (b) avoid some complex technical issues that crop up.
The solution for having things appear in multiple places is to leverage relationships. Then it's easy to find what you want visually via either a Relationship View or a Link Web view. In many cases, the Link Web view is better for visual navigation IMO.
Do relationships not cut it for some reason? If so, what are the problems you're experiencing with relationships for this purpose?
|