Hey Rodney:
Yeah, it's a sticky wicket as they say over the pond, this whole issue
of Roles and Membership and 'Community' and the way the DNN Models
it right now. The 1K+ users in itself is a show stopper for
most communities. And yeah, sure wish someone on the core team
cared about this, and/or saw the *power*.
Now, about your ideas. I like the idea of two roles...but what
about a recursive role setup? I could do the database design for
that (done it before). You'd have to have extra tables to handle
it. This way (and I'm thinkin' of my application...see if you can
generalize it perhaps). I have a bunch of members. Each
member is a member of one or more writergroups (each of which would be
a role)...ahh. no. We still get stuck in this role issue.
Let's think of what the *ideal* would be. We already have the use
of multiple portals, right? Each portal can handle a certain
number of roles, say a 100, each which has members, lets say 3-400 or
so, right? Obviously you'd need some bandwidth the larger ya got,
but that's not our prob. ANd easier since DNN 3 is moving towards
a *better* load-balancing model.
So, how could we *use* that ability, and then add the ability for each
person to have their page, yet be a member of a number of roles, and
have edit roll for *their* page(s), and partial edit roles (for
modules, say) on other pages, on other portals? And still stick
w/the core, or at least w/minor changes to it?
I think the two or *whoever* of us that subscribe to your site, and
have these needs, can come up w/an elegant solution. I don't
*know* enough *yet* about the internals of the membership part of DNN
(they changed the heck out of it!) to come up w/solutions yet.
|
|