After some great help by @afreeman on Friday, I've got a solid plan for implementing a lightweight user grouping function on my website. In a nutshell, I have "Club" nodes, that users can associate with. A taxonomy links the two. First problem: it doesn't seem possible to link a taxonomy term with a user. So, I'm using Content Profile, which turns user profiles into Nodes. Using this I can associate the user's profile node with a taxonomy term.
Second problem: I want to build a view that shows me all the nodes created by all the users tagged with a specific taxomony term. e.g. I want all the robot nodes created by all the users that have the taxonomy term, "Raleigh robot group". I can't seem to do this in Views, because I can only grab the nodes with the taxonomy term - which are just the user profile nodes.
What should I do?
Comments
You've got to account for the
You've got to account for the extra layer of indirection in your view. This means using Relationships.
Roger that. Been poking
Roger that. Been poking around with that this evening to no avail. I've added a relationship "Taxonomy: Node", which pulls in the node (user profile node) that has the taxonomy term matching the views argument. That works. I now have a list of associated user profiles.
Intuitively I would think to add another relationship that would include all the nodes belonging to a certain user ID, but there's not an explicit relationship for this, nor do I know of a way of getting a list of all the user IDs. That's where I'm stuck.
I see said the blind man
I can see where you ran into trouble. My explanation of how to implement this was faulty. I'd based it on an imperfect understanding of how the content_profile module works. However, there is hope. I spent some time trying to replicate the overall approach we discussed the other day and I've come up with a view that appears to work.
So far I have a list of all story nodes that have authors who are grouped by a specific term in their user profile node. This is, of course, not what you had in mind.
Fortunately after a little more tinkering I discovered you can add a Taxonomy:Term argument and use the Content Profile relationship. Now my list of story nodes is filtered by the term id of the author's profile node. This gets us closer. For additional fine-tuning there's also PHP default arguments as an option.
Catch me on skype when you have a minute and we can discuss this further.