Matt:P : good!
Klauss, it’s late here, and I am still up only because of completing the EE design survey, but I am feeling from what you say that there may actually be two nested challenges here.
a. there is some categorized information that is the same for a number of users, but differing across categories of users.
b. there is also some individualized unique information, per user.
I think we suggested approaches for a., and agree that switch-decisioning on a member custom field for the user’s category is a good way to choose that.
For b., if there’s not so much unique information, and you enter it through EE, then that information also can go in custom member fields. Or alternately in a channel’s custom fields, where you have more flexibility and ability in custom channel fields, and key on a member id.
If you are instead linking some external-to-EE database tables, you can put the key in a member or channel custom field to guide an exp:query which retrieves it.
Klauss, probably at this point the official tech support will suggest moving this thread to the Community Help area, as it’s really about application design (patterns). But let’s see what they say.
Regards, and sleep now,
Clive