BuddyPress.org

John is right when he says the bpc doesn’t do what magicdust wants to do. bpc organizes ‘things’ into a tree of ‘things’. It would be possible to create a tree of categories like magicdust wants with bpc. However it would just be the list of categories.

Custom code would have to be written to take that tree of categories and *do* something with them. Once you do something with the tree of categories, like sign up a user to a top level category and allow them to choose a sub-category, then bpc can record the fact that the user is now a member of top level cat X and sub-cat Y.

Here’s a use case for bpc in this situation. Given the category tree structure created in bpc of:

Australia

— sydney

—- grads 2000

—- grads 1999

—- grads 1998

— melbourne

—- grads 2000

—- grads 1999

—- grads 1998

— brisbane

—- grads 2000

—- grads 1999

—- grads 1998

One way to implement this is, display the tree to the user. Allow them to select the ‘grad year’ such as ‘brisbane/grads 2000’. Get the results back from the user selection form. See that they have selected ‘brisbane/grads 2000’ and make them members of the ‘brisbane/grads 2000’ group, the ‘brisbane’ group and the ‘australia’ groups.

Or display a list of the australia cities as links allowing the user do drill down into one city and select a grad year. How you implement the selection process depends on how you want the groups to be setup. Do you really want individual groups for each city and year? Or do you just want individual groups for each city and allow the user to select a grad year. Then organize things with each city group depending on what grad year they are?

The selection process that is implemented is directly related to the design of the group structure. It just reflects that structure.