Show group audience according to subgroups hierarchy
DaniOrama - August 12, 2008 - 23:47
| Project: | Subgroups for Organic groups |
| Version: | 6.x-0.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Jump to:
Description
Hello, I know Views is able to created a list for the groups but it would be nice if there were a block or page the same as with normal groups but showing the subgroups tree (I mean a tree with all the info like members, private, etc...)
It would be also really good if there were a way to show an Audience select tree and not only a list. It would make really easy for the users decide the right audience and/or It could activate the groups in the Audience checkboxes following the propagation. Right now is a bit difficult to know the hierarchy for the Audience.

#1
It would be awesome if there were options in the Audience select of the create/edit Group node for propagate to parents, children or brothers...
Would it be also possible to limit which Audience groups could be selected? (for example not allowing to select children, parents, brothers or groups who don't belong to the same branch...)
Thank you for this wonderful module!
#2
1. I've added a block 'Subgroups navigation', similar to 'Book navigation' but adjusted to og_subgroups. You can test it. http://drupal.org/cvs?commit=133465
2. what is the use case of limiting the audience?
#3
Hey, that was good! I will try it right now!
Limiting audience is a way to make normal users from a subgroup post their content in other groups which has some kind of dependency. For example if I use some kind of geographical order, I would like to post in Berlin, Deutschland (parent) but not in other lands groups. I know the module use dependencies for the groups, but if the users try to post to other audiences it's everything too confusing because they do not have any way to know which groups are children or parents...
I think a way to show the users the hierarchy in the Audience selection is needed. Limiting access by roles could make that just some users could propagate the content (to all groups following the propagation rule or selecting each one) or being able to post wherever they want...
#4
I'm not sure about this feature - I don't thing subgroups should take care about audience visability, maybe you have a more solid use case - but what you need sounds very specific.
@ezra-g, agree?
#5
I'm not sure exactly what's being asked for here. @DaniOrama: Could you give another example and create a "diagram" of your group structure and describe the desired behavior? Are you looking for per-node, or per-content type or per-user propagation settings?
Also, it sounds like this thread covers 2 different features, one having to do with propagation and another having to do with an interface change. If that's correct, let's create a new issue for one discuss the other here.
#6
@Ezra-g: you are right, these are 2 different features(ok, really 3). But they are (or could be) interconnected:
1-Show select Audience with Group Hierarchy. Right now is very easy to select different audience that doesn't follow a hierarchy line.
2-Limit per roles, if the users are able to select some groups following propagation rules (this could be made with OG Audience but there is no real interaction with the Subgroups) or even not showing the groups who don't follow the propagation.
3-(optional) is that the propagation could be selected on each content we create (in the audience selection) or/and that at first the audience groups checkboxes are checked following the propagation so the user could change them (it will allow fewer errors and clicks)
Anyway the first one is the more important, because it will make the subgrouping easier to see. The other 2 could be delegated to moderators.
My personal case is this one:
I have a Tabletop RPG Website, there I have created 2 main groups: Genre and Locations. Genre with the different Genres as subgroups (Sci-fi, Fantasy, etc...) and different Worlds as Subgroups for these Subgroups (Warcraft and D&D inside Fantasy); Locations with different places as subgroups (Germany, England, etc...) and Cities as subgroups for the former (Koln inside Germany, London inside England, etc...)
When someone wants to write something about Warcraft, sometimes these contents should stay only in Warcraft (something about the game itself), sometimes they should propagate to Fantasy (for example Events that everyone should know). Right now if I do not have a hierarchy for the audience selection is a bit difficult to know which groups are for each genre, so it could happen that something that is in Warcraft go to Sci-fi... It could be manually moderated, but it would better to show the hirarchy so there would be not so many errors, and it would be even better that some users who are not moderators could just select as Audience the parents, siblings or children, letting the moderators change the audience as they want. I know it could be made with Taxonomy, but I like to have control on access, events, forums and show different themes for each group (maybe the locations should be made with Taxonomy only)
An easy Diagram: (the audience selection could be just ordered per hierarchy, and not alphabetically and with - for showing the hierarchy)
-Genre
--Fantasy
---D&D
--Sci-fi
---Star wars
-Locations
--Germany
---Koln
--England
---London
Amitaibu is also right, subgroups shouldn't take care about audience control, but it should give the other og modules the tools to consider them. I really think subgroups should be a standard feature in og. But what I ask me is what is easier? Consider subgroups in each og module or change a bit subgroups for using features from other modules? Right now I think the most extended og modules are OG Calendar, OG Forums, OG Audience and OG Roles. Maybe my case is too specific, I don't know, but I think if people use subgroups they would be interested to have some subgroup features applied to other modules. (I do not know what will happen with OG Forums and Subgroups, maybe my Server will implode, I will have to wait until this weekend when the D6 Port come)
Sorry for making a so long post.
#7
Ok, let's leave 2-3.
1 is a valid feature request. Patches are welcome.
#8
I tried this, the breadcrumbs and path but I didn't manage to do anything useful... :(
Maybe the OG Audience By Role module could help to give ideas...