Subgroup integration
RoboPhred - March 11, 2009 - 20:02
| Project: | OG Vocabulary |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Could this be adjusted to work with og subgroups in that taxonomy could be inhereted?
My case is that I am trying to create my own project management setup, using a group per project, and allowing subprojects (for things such as beta teams)
I am not sure whether this would be a vocab or subgroup task...
#1
Do you mean, you would like the Taxonomy categories to propagate?
#2
Yep.
In my specific case, I want to have a group for a project which contains components via og vocab, and I would like to have subgroups for testing teams (which will have different versions of the project). When a testing team posts in their group, I want them to be able to select a component from the main project.
Marking this down a priority as I am probably going to use a typed group post and cck NodeReference instead, in order to get better project-wide integration (as the concept of a component would not be project-dependant while the contents would be group defined).
Of course, if anyone else needs this, feel free to reset its priority.
#3
http://drupal.org/project/cckasetracker ?
#4
I have looked at that, as well as several other options, and probably will use it. However, I suspect that I will have to manually add each vocabulary for each project to the project content type manually, unless it has the option to automatically use all taxonomy associated with the type (I have not tested it yet).
However, the issue this feature request is here to solve is getting project components (defined via OG Vocab) to move through subgroups, which CCKaseTracker will not do.
I think I have a possible solution with CCK NodeReference being populated by a View with custom php arguments, hence the drop in priority.
If you want to see what my goal is and what I have so far, see my site's <out of date link removed>, which I am constantly changing around.
#5
subscribing